OpenAI Outage History

OpenAI experienced a brief outage affecting Codex task creation within ChatGPT / Codex. Users attempting to create new Codex tasks encountered errors, impacting workflows that rely on programmatic task submission. The issue began at 12:51 AM UTC and was resolved by 1:46 AM UTC, lasting about 55 minutes. OpenAI listed the problem on the status page as an investigation with a mitigation in progress and subsequently restored normal operation within the same window. The incident involved the ChatGPT / Codex component and the provider issued two status updates during its course.

OpenAI's ChatGPT / Conversations component experienced a brief degraded performance incident, with elevated error rates affecting a portion of users. Across regions, users reported issues such as login failures, prompts not responding, and missing chat history. The incident affected the ChatGPT / Conversations component, and the service began showing degraded behavior at Dec 2, 2025 7:46 PM UTC. The issue was addressed and the service returned to normal by Dec 2, 2025 8:17 PM UTC, lasting about 31 minutes.

OpenAI issued 2 status updates during the event, describing elevated error rates and later confirming remediation. The issue was categorized on the status page as degraded performance in the ChatGPT / Conversations component, and the service returned to normal after roughly 31 minutes.

OpenAI's ChatGPT Conversations experienced a brief outage with elevated error rates, impacting user access and responsiveness for ChatGPT features. Users reported login failures, prompts not returning results, and missing chat history across regions. The outage began at Dec 2, 2025 7:46 PM UTC and lasted about 31 minutes, with service returning to normal by Dec 2, 2025 8:17 PM UTC.

Status communications showed a rapid response: OpenAI updated its status page to indicate a degraded experience at Dec 2, 2025 7:46 PM UTC and later confirmed restoration at Dec 2, 2025 8:17 PM UTC. StatusGator’s Early Warning Signal had flagged the issue earlier at Dec 2, 2025 7:33 PM UTC, with the alert ending at 8:02 PM UTC as users continued to report effects before official acknowledgment. The incident involved the ChatGPT / Conversations component and saw a large volume of user reports indicating widespread impact, with activity appearing global rather than regional.

OpenAI's ChatGPT Conversations experienced a brief outage starting at 6:56 PM UTC, with users reporting conversation errors and connectivity issues. The issue affected the ChatGPT / Conversations component and lasted about 5 minutes, being resolved by 7:01 PM UTC. OpenAI issued two status updates during the incident, noting that mitigation had been applied and that recovery was being monitored, before returning to normal.

OpenAI's ChatGPT / Conversations component briefly encountered elevated errors affecting a subset of users. The incident began on Nov 26, 2025 10:51 PM UTC and was resolved by Nov 26, 2025 10:56 PM UTC, lasting roughly 5 minutes. OpenAI's status page published two updates during the event to communicate the ongoing investigation and the resolution. User reports described errors when using ChatGPT, but the impact remained limited to the ChatGPT / Conversations component and did not indicate a broader OpenAI service disruption.

OpenAI's ChatGPT Conversations deletion functionality on the web experienced an outage, preventing users from deleting conversations. The issue began at 5:31 PM UTC and was resolved by 9:31 PM UTC, lasting roughly four hours. The problem manifested as elevated errors when users attempted to delete chats, impacting the ChatGPT / Conversations component. OpenAI issued two status updates during the incident and worked on mitigation.

The impact appeared limited to the delete action, with other ChatGPT features remaining accessible. Reports came from users in multiple regions, indicating broad but partial impact. After mitigations were deployed, deletion functionality returned to normal.

OpenAI reported degraded performance for ChatGPT across multiple features, with users experiencing errors. The incident began on Nov 26, 2025 12:06 AM UTC and was resolved by Nov 26, 2025 3:06 AM UTC, lasting about 3 hours. The issue affected 13 components including ChatGPT / Search, ChatGPT / Login, ChatGPT / Conversations, ChatGPT / Image Generation, ChatGPT / Deep Research, ChatGPT / Agent, ChatGPT / Codex, ChatGPT / ChatGPT Atlas, ChatGPT / Connectors, ChatGPT / Compliance API, ChatGPT / GPTs, ChatGPT / File uploads, and ChatGPT / Voice mode. OpenAI posted two status updates during the incident: an initial notice of degraded performance and ongoing investigation, followed by a restoration notice indicating services had returned to normal.

OpenAI reported an incident affecting ImageGen in ChatGPT Workspaces tied to EU Data Residency and Non-US Data Residency. Users experienced image generation failures and some generated images disappearing. The issue began at Nov 25, 2025 7:41 PM UTC and expanded to a broader set of ChatGPT components by Nov 25, 2025 8:16 PM UTC, impacting 13 components in total across the ChatGPT suite. The event prompted ongoing investigation and status updates as engineers worked on a fix to restore normal operation for affected regions.

OpenAI Codex (ChatGPT / Codex) experienced elevated errors, causing degraded performance for Codex-enabled features. The incident began on Nov 23, 2025 4:26 AM UTC and was resolved by Nov 23, 2025 6:56 AM UTC, lasting about 2 hours and 30 minutes. The disruption affected Codex-related interactions across the platform.

OpenAI's status page documented two updates during the incident: the first noted elevated errors and that a mitigation was applied, and the second confirmed that Codex services had returned to normal and the issue was resolved.

OpenAI Codex experienced elevated errors that degraded ChatGPT and Codex performance starting at 7:21 PM UTC. The outage affected Codex-related functionality, with users reporting non-responsive Codex models such as GPT-5.1-Codex-Max from several locations. The incident lasted about 3 hours and 30 minutes and was resolved by 10:51 PM UTC.