OpenAI Outage History

OpenAI reported a memory-related issue affecting ChatGPT Memory within ChatGPT Conversations beginning at 6:46 PM UTC. Users across multiple regions experienced memory recall failures and errors saving or retrieving memories, impacting how conversations remember past context. The incident manifested as degraded memory functionality within ChatGPT Conversations and was reflected in user reports across a broad base.

OpenAI issued two status updates during the incident. The issue persisted until 4:16 PM UTC, for an outage duration of about 21 hours and 30 minutes. The service was restored after the final update, with ChatGPT Conversations returning to normal operation. Reports spanned North America, Europe, and other regions, indicating widespread but partial impact rather than a full downtime.

OpenAI reported a brief degradation in the ChatGPT / Conversations component as users encountered errors indicating conversations were too long. The degraded period began at Nov 6, 2025 4:11 AM UTC and lasted about 1 hour and 10 minutes, with the service returning to normal by Nov 6, 2025 5:21 AM UTC. The issue affected the ChatGPT conversations flow, causing interruptions for some chats or prompts.

OpenAI's ChatGPT / Codex experienced elevated errors that disrupted generation requests. Users across several U.S. locations reported issues, including 'Please try again' errors and timeouts when generating responses, indicating degraded performance. The incident began at 7:46 PM UTC and lasted about 2 hours and 10 minutes, until 9:56 PM UTC, with 5 user reports observed during the window.

The OpenAI status page indicated an elevated error and that mitigation was being implemented as the ChatGPT / Codex component moved from normal to degraded and back to normal after mitigation. The provider issued 2 official status updates during the incident, and service is now reported as restored.

OpenAI experienced a login incident impacting three login-related components: APIs / Login, Sora / Login, and ChatGPT / Login. Users reported sign-in failures and difficulty accessing affected services. The outage began on 3:02 PM UTC and was resolved by 5:41 PM UTC, lasting roughly 2 hours and 39 minutes. Reports from multiple regions described errors during sign-in and API access attempts.

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.