OpenAI Outage History

OpenAI experienced degraded performance for the ChatGPT / Conversations component as GPT 5.2 showed elevated error rates. The incident began at 4:47 PM UTC and was resolved by 7:32 PM UTC, lasting about 2 hours and 45 minutes. Users across multiple regions reported errors in message streams, prompts failing, and pages not loading when interacting with ChatGPT, indicating a broad but partial disruption of the service.

OpenAI reported Codex Cloud issues tied to GitHub dependencies, resulting in degraded experiences for ChatGPT and Codex users. Some users could not load ChatGPT on desktop, and others saw heavy load warnings. The incident began at Feb 9, 2026 4:31 PM UTC and was resolved by Feb 9, 2026 8:26 PM UTC, lasting approximately 3 hours and 55 minutes. The OpenAI status page showed two official updates during the event.

OpenAI experienced a brief issue affecting the ChatGPT Conversations component, with some users reporting that conversations could not be loaded. The incident began at 9:01 AM UTC and a mitigation was implemented as engineers worked to restore normal operation. The issue was resolved and service returned to normal by 9:06 AM UTC. OpenAI issued 2 status updates during the incident describing the degraded experience and the subsequent recovery. The impact appeared limited to a subset of users, with a small number of reports and no clear regional pattern.

OpenAI's ChatGPT ecosystem experienced a brief degradation as elevated errors affected 13 components, including Codex, Voice mode, GPTs, Agent, Atlas, Connectors/Apps, Search, Login, Compliance API, File uploads, Deep Research, Conversations, and Image Generation. The outage began on 12:17 AM UTC and was resolved by 12:26 AM UTC, lasting about 9 minutes. Users reported issues across multiple features during the incident, indicating broad impact though not a full platform outage. OpenAI issued 2 status updates during the event, noting ongoing mitigation and listing the affected components before services returned to normal.

OpenAI experienced a brief outage affecting ChatGPT services for a portion of users. The incident began at Feb 4, 2026 5:41 PM UTC and was resolved by 6:01 PM UTC, lasting about 20 minutes. The disruption affected 13 ChatGPT components, including Codex, Voice mode, GPTs, Agent, Atlas, Connectors/Apps, Search, Login, Compliance API, File uploads, Conversations, Image Generation, and Deep Research. Users reported issues such as chats not loading, prompts failing, and errors like too many concurrent requests.

OpenAI acknowledged elevated errors on the status page and worked on a mitigation. The provider issued two status updates during the incident as it restored services. The outage appeared to impact a broad portion of the user base, with reports of degraded performance and failures across multiple features until services returned to normal.

OpenAI's ChatGPT experienced a brief global disruption with elevated errors across many features, making chats, prompts, and related capabilities intermittently unusable for about 20 minutes. The incident impacted 13 core components including ChatGPT / Codex, Voice mode, GPTs, Agent, ChatGPT Atlas, Connectors/Apps, Search, Conversations, Image Generation, Login, Compliance API, File uploads, and Deep Research. Users worldwide reported issues such as chats not loading, prompts failing, and various errors during the incident.

StatusGator detected the issue early at Feb 4, 2026 5:15 PM UTC, roughly 26 minutes before OpenAI acknowledged the problem. OpenAI issued 2 status updates during the incident and services were restored by 6:01 PM UTC. The outage lasted from 5:41 PM UTC to 6:01 PM UTC. A high volume of user reports indicated broad, worldwide impact across users.

OpenAI reported that updates to Custom GPT configurations were failing for some users, affecting the Custom GPTs feature within ChatGPT. The incident began at Feb 4, 2026 12:46 PM UTC and was resolved by Feb 4, 2026 2:52 PM UTC, lasting about 2 hours and 6 minutes. Users reported issues saving or applying changes to their Custom GPTs, with some references to heavy load and memory-related errors.

OpenAI posted two status updates during the incident to inform users about the ongoing investigation and eventual restoration of services. The issue was localized to Custom GPT updates in ChatGPT / GPTs and the service returned to normal after the updates were completed.

OpenAI experienced a brief degraded period impacting ChatGPT / Conversations, with some users reporting difficulties loading or starting conversations. The incident began at Feb 4, 2026 1:26 AM UTC when OpenAI flagged a degradation and began investigating. User reports started around 2:30 AM UTC, including a Los Angeles example at 2:42 AM UTC describing generation issues. The outage lasted about 2 hours and 20 minutes and was resolved by Feb 4, 2026 3:46 AM UTC when status returned to normal.

OpenAI posted two official status updates during the incident: the initial alert at Feb 4, 2026 1:26 AM UTC and a recovery update at Feb 4, 2026 3:46 AM UTC. The issue appeared to be limited to ChatGPT / Conversations and did not affect all users, reflecting a localized degradation rather than a global outage.

OpenAI reported a global incident impacting ChatGPT and related services, with elevated error rates beginning at Feb 3, 2026 8:36 PM UTC. Users worldwide experienced login failures, stalled conversations, and errors across multiple ChatGPT components including Conversations, Login, Image Generation, File uploads, and more. The incident affected 13 components, indicating broad degradation rather than a single outage. The outage lasted roughly 3 hours, with most services recovering by around Feb 3, 2026 11:36 PM UTC. OpenAI issued five status updates during the event to acknowledge the issue and describe mitigation steps and progress.

OpenAI's ChatGPT services experienced elevated error rates that impacted login, conversations, and a broad set of APIs, leading to widespread disruption for users trying to chat, generate responses, or access their chats. The outage began around 7:45 PM UTC with initial user reports, and StatusGator detected the issue at Feb 3, 2026 7:54 PM UTC, about 42 minutes before the first official update at Feb 3, 2026 8:36 PM UTC. Affected components included ChatGPT Atlas, Conversations, Login, Deep Research, Agent, Codex, Compliance API, Search, File uploads, Voice mode, GPTs, Image Generation, Connectors/Apps, APIs / Login, and Fine-tuning. The incident involved a large volume of user reports at the peak, reflecting global disruption.