OpenAI Outage History

The OpenAI Codex service on the web experienced degraded availability, with Codex Tasks on the web briefly unavailable for users. The outage affected web-based Codex Tasks during a roughly one-hour window from 19:15 to 20:15 Pacific Time. The outage began on Nov 5, 2025 3:15 AM UTC and was resolved by Nov 5, 2025 4:15 AM UTC, with mitigation applied and monitoring ongoing as the fix was implemented.

OpenAI communicated the issue via its status page, listing the incident as degraded Codex availability on the web and posting two official updates during the event. The updates were issued at Nov 4, 2025 4:26 AM UTC and Nov 4, 2025 5:16 AM UTC, after which Codex Tasks on the web returned to normal functionality.

OpenAI's Responses API (APIs / Responses) experienced a brief degradation with elevated errors, impacting requests to the API and causing intermittent failures for about 25 minutes. The incident affected only the Responses API, with other OpenAI services remaining unaffected.

Timeline: The issue began at Nov 4, 2025 2:06 AM UTC and was resolved by Nov 4, 2025 2:31 AM UTC. OpenAI issued 2 status updates during the incident, confirming elevated errors and that mitigation was in progress.

OpenAI's video generation feature briefly experienced failures starting around 10:00 PM UTC and ending at 10:02 PM UTC, with at least one user reporting a 400 error. The outage lasted about 2 minutes and appears isolated to video generation, with no evident impact on other OpenAI services. OpenAI did not publish any status updates during the incident. StatusGator logged an Early Warning Signal at Nov 3, 2025 10:02 PM UTC based on user reports, highlighting timely detection of the issue.

OpenAI's Responses API in background mode experienced degraded performance, with elevated latency and timeouts affecting background requests. The issue began on 1:06 PM UTC and was resolved by 6:56 PM UTC, lasting about 5 hours and 50 minutes. Users attempting to run tasks via the Responses API in background mode may have seen slower responses or failed requests.

OpenAI issued 2 status updates during the incident to describe the degraded condition and its resolution. The impact was focused on the Responses API endpoints used in background mode, with reports indicating slower responses and intermittent timeouts.

OpenAI experienced an outage affecting ChatGPT Conversations, with user reports of errors and unresponsive chats beginning at 7:11 PM UTC. Users described issues like failed responses and errors during conversations, indicating degraded performance across ChatGPT Conversations. The issue appeared to be widespread, with reports from multiple regions suggesting global impact.

OpenAI issued two status updates during the incident: the first noted increased errors on the ChatGPT / Conversations component and that the team was investigating, and the second announced that the issue had been resolved and that ChatGPT Conversations were returning to normal. The outage lasted from 7:11 PM UTC to 9:21 PM UTC, for an approximate duration of 2 hours and 10 minutes. The primary affected component was ChatGPT / Conversations.

OpenAI reported a partial outage affecting the ChatGPT / Connectors component, with some users unable to activate connectors that were enabled for their workspace. This disrupted automation and integrations that rely on workspace-based connector permissions, with effects varying by user configuration. The issue was tracked and communicated via OpenAI's status updates to help teams understand the impact.

The outage began at 10:46 AM UTC and was resolved by 12:16 PM UTC, lasting about 1 hour 30 minutes. OpenAI issued 2 status updates during the incident as teams investigated and then restored functionality for the ChatGPT / Connectors component.

OpenAI reported a brief incident affecting ChatGPT / Conversations, with increased errors for paid users. The issue began at 3:31 PM UTC and was resolved by 4:12 PM UTC, lasting about 41 minutes. During the event, users reported errors in message streams and failed outputs across regions, indicating a global impact.

OpenAI posted two status updates during the incident as they investigated and then restored service. The outage impacted the ability to send messages and receive outputs, with reports spanning North America, Europe, Asia-Pacific, and other regions. After the resolution, services returned to normal as indicated by the status page.

OpenAI's gpt-4o-audio-preview service within the APIs / Audio component experienced elevated error rates beginning at Oct 27, 2025 3:41 AM UTC, resulting in failures for users attempting to use the audio preview features. The incident lasted about 4 hours and 5 minutes and was resolved by Oct 27, 2025 7:46 AM UTC.

OpenAI published two status updates during the incident to communicate the elevated errors and ongoing mitigation. The APIs / Audio component returned to normal once the mitigation took effect.

OpenAI web search services experienced elevated error rates affecting ChatGPT / Search, ChatGPT Atlas, and Deep Research, leading to degraded web search functionality for users. The issue began at Oct 24, 2025 8:56 PM UTC and was resolved by Oct 24, 2025 10:31 PM UTC, lasting approximately 1 hour and 35 minutes. OpenAI issued four status updates during the incident, describing elevated errors and ongoing mitigation efforts. By the end of the incident, the affected components had returned to normal operation.

OpenAI’s Sora remix and creation features were inaccessible for a brief period, with users reporting page freezes and inability to remix or create content. StatusGator logged an early warning beginning at Oct 24, 2025 5:43 PM UTC, covering user-reported issues that occurred before any OpenAI status updates. The early signal ended around Oct 24, 2025 6:12 PM UTC. This incident appeared to affect the Sora-related capabilities for roughly 29 minutes, based on the timing of the signals.