OpenAI Outage History

OpenAI's ChatGPT Codex experienced elevated error rates, leading to degraded performance for users. The incident began at 9:36 PM UTC and was resolved by 10:17 PM UTC. OpenAI issued two status updates during the event, first noting elevated errors and that a mitigation was being implemented, then confirming the service had returned to normal. The issue affected the ChatGPT / Codex component and caused noticeable disruption for a brief period.

OpenAI experienced a brief degradation across its API endpoints beginning at Jul 7, 2025 6:01 PM UTC and lasting about 36 minutes until Jul 7, 2025 6:37 PM UTC. The disruption affected a broad set of API components, causing requests to fail or time out for developers and their applications. Affected components included APIs / Realtime, APIs / Responses, APIs / Login, APIs / Fine-tuning, APIs / Assistants, APIs / Audio, APIs / Batch, APIs / Embeddings, APIs / Files, APIs / Images, APIs / Completions (legacy), APIs / Chat, APIs / Compliance, APIs / Moderations, and APIs / Uploads. OpenAI issued two status updates during the incident to communicate the elevated error rates and ongoing mitigation.

OpenAI's updates also noted that users were experiencing elevated errors across the impacted endpoints and that mitigation steps were underway, with services returning to normal by the end of the window.

OpenAI Pay-As-You-Go API accounts experienced a temporary quota-related incident, with some users seeing 429 errors indicating quota issues. The issue affected 15 API components, including Chat, Completions, Embeddings, Images, Audio, and more, causing requests to fail for affected accounts. Users reported messages such as 'You exceeded your current quota' during API calls. The incident involved multiple API surfaces and degraded the experience for pay-as-you-go users.

OpenAI's Sora service experienced a brief outage that affected multiple Sora components, including Image Generation, Video Generation, Video Viewing, and Feed. Users reported elevated errors and partial access issues during the event. The outage began at Jul 1, 2025 4:47 PM UTC and was resolved by Jul 1, 2025 5:11 PM UTC, lasting about 24 minutes.

OpenAI's status page documented two updates during the incident. The first noted increased errors for Sora and identified the affected components, while the second confirmed restoration of services. The incident involved four Sora components and was reflected in user reports from across regions.

The OpenAI API experienced a broad outage starting at Jun 23, 2025 10:06 PM UTC with initial Compliance API data delays, leading to degraded performance and elevated errors across a wide range of endpoints. Users relying on OpenAI services reported slower responses and intermittent errors across APIs including Realtime, Responses, Embeddings, Fine-tuning, Login, Images, Batch, Files, Assistants, Audio, Completions (legacy), Chat, Moderations, and Uploads. The incident lasted about 5 days and 2 hours, with recovery progressing as mitigations were deployed and more components returned to normal. Full restoration for affected APIs and related features was completed by Jun 29, 2025 12:16 AM UTC.

OpenAI experienced a global login and authentication incident beginning at Jun 23, 2025 7:19 PM UTC and ending by Jun 23, 2025 9:12 PM UTC. The outage lasted about 1 hour and 53 minutes and affected users trying to sign in or authenticate to OpenAI services. Reports described sign-in failures, authentication errors, and server errors across regions, with some users unable to sign in while others encountered repeated sign-in prompts or errors when accessing APIs and dashboards. The issue appears to have impacted access to ChatGPT, the OpenAI API, and related services, hindering normal workflows for a broad set of users.

OpenAI experienced a short-lived degradation affecting the ChatGPT / Conversations component with elevated errors reported for paid ChatGPT users. The issue began at Jun 19, 2025 2:11 AM UTC when the component was downgraded to a warning and a mitigation was started. The provider issued two status updates during the incident, and service was restored by Jun 19, 2025 2:17 AM UTC. The disruption lasted roughly 6 minutes and did not indicate a broader outage across OpenAI services.

OpenAI reported a degraded login experience for ChatGPT, with some users seeing a “Content failed to load” error after signing in. The issue began at Jun 18, 2025 8:06 PM UTC and was resolved by Jun 19, 2025 12:21 AM UTC, lasting about 4 hours and 15 minutes. The incident involved the ChatGPT / Login component and spanned two official status updates before full restoration. User reports were limited, with at least one account of chatGPT not responding during the incident.

OpenAI reported a brief degraded period affecting ChatGPT / Conversations, with users experiencing elevated errors. The incident began at Jun 18, 2025 1:21 AM UTC and was resolved by Jun 18, 2025 1:37 AM UTC, lasting about 16 minutes. The OpenAI status page posted two updates during the incident, describing conversation errors and then confirming restoration. User reports showed a noticeable spike in issues around the middle of the event, with impact focused on ChatGPT / Conversations.

The outage began around 1:10 AM UTC when users started reporting errors in the ChatGPT message stream. StatusGator detected the issue at Jun 18, 2025 1:10 AM UTC, about 11 minutes before OpenAI acknowledged the problem on their status page. OpenAI listed Conversation errors for ChatGPT and began mitigation; services remained degraded until they returned to normal by 1:37 AM UTC.

The impact appeared global, with user reports spanning multiple regions including the Americas, Europe, and other territories. Symptoms described include errors when sending or receiving messages, messages being rejected as too long, and generic 'Something went wrong' prompts.

During the incident, OpenAI issued two official status updates and worked to stabilize the system. The incident is classified as a minor outage with degraded performance.