There were 262 OpenAI outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
OpenAI not working for you?
OpenAI not working for you?
Minor
: OpenAI API endpoints brief outage on July 8, 2025
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(55 minutes)
OpenAI reported a brief outage affecting multiple API endpoints, including /v1/chat/completions, /v1/completions, Private Link, and the /Responses API. Users attempting to use chat completions or text completions may have encountered errors or timeouts during the incident. The issue degraded two components: APIs / Responses and APIs / Completions (legacy).
Major
: OpenAI finetuning API outage blocks new job creation
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(18 hours and 40 minutes)
The OpenAI finetuning API outage blocked the creation of new finetune jobs via the API. Customers relying on custom model training were unable to start new finetune runs, disrupting workflows that depend on model customization. The incident began at and the service remained degraded from until full recovery at .
OpenAI issued 3 status updates during the incident, documenting the outage, the mitigation applied, and the recovery progress. Mitigation was put in place and monitoring continued as OpenAI worked to restore normal operation of the APIs / Fine-tuning component. A small volume of user reports described authentication-related issues during the outage, reflecting the broader disruption while the service was degraded.
Minor
: OpenAI ChatGPT / Codex briefly degraded during incident
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(40 minutes)
The OpenAI ChatGPT / Codex component experienced elevated error rates, causing degraded performance for Codex-powered features within ChatGPT. Users attempting Codex-powered tasks may have encountered errors or timeouts during the incident. The outage began on and was resolved by , lasting about 41 minutes.
The provider issued 2 status updates during the incident, describing mitigation steps and the recovery. The service returned to normal after the final update.
Minor
: OpenAI API endpoints briefly degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(35 minutes)
OpenAI reported a brief degradation of API endpoints beginning at with elevated error rates across 15 API components, including Realtime, Responses, Login, Fine-tuning, Assistants, Audio, Batch, Embeddings, Files, Images, Completions (legacy), Chat, Compliance, Moderations, and Uploads. Users could experience failed requests or timeouts across multiple OpenAI services during the window. The incident affected a broad portion of the API surface, indicating widespread impact across the platform.
The issue lasted about 36 minutes and OpenAI posted 2 status updates during the incident. All components returned to normal by . The event involved a broad set of API components, but overall user-reported activity remained low during the window.
Minor
: OpenAI Pay-As-You-Go API 429 errors affect 15 API components
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(3 hours and 45 minutes)
On OpenAI flagged an outage relating to Pay-As-You-Go API accounts experiencing 429 errors tied to negative balance checks. The issue impacted 15 API components, including Chat, Completions (legacy), Embeddings, Login, Files, Images, Moderations, and other core APIs, leading to degraded access for affected users. The incident lasted about 3 hours and 44 minutes, and OpenAI published two status updates during the event. Services were restored by .
Minor
: OpenAI Sora brief outage affects image and video features
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(25 minutes)
OpenAI Sora briefly went offline, affecting Image Generation, Video Generation, Video Viewing, and Feed. Users encountered elevated errors during the incident, with service degraded for about 24 minutes. The outage began at and was resolved by .
OpenAI issued 2 status updates as the team investigated and then restored functionality.
Major
: OpenAI APIs face multi-day degraded performance across services
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 days, 2 hours and 10 minutes)
The outage began on with Compliance API data delays. By the issue had expanded to a broad set of OpenAI APIs, causing elevated errors and degraded responsiveness across multiple services including Realtime, Responses, Embeddings, Fine-tuning, Login, Images, Chat, and more. A subset of Sora services also experienced outages during the period. The incident generated a large volume of user reports and affected more than a dozen components.
OpenAI issued multiple status updates over the course of the incident as mitigation steps were implemented. The situation gradually improved, with most services returning to normal by . The outage lasted approximately 5 days and 2 hours.
Minor
: OpenAI ChatGPT Conversations brief degradation for paid users
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
OpenAI ChatGPT / Conversations experienced a brief degradation that affected paid users, with elevated errors during conversations. The outage began at and was resolved by , lasting about 6 minutes. Users may have seen errors or intermittent responses during the chat interactions.
OpenAI issued two status updates during the incident. The first noted high error rates for paid users and that a mitigation was being implemented. The second confirmed that the issue had been resolved and that normal operation had resumed for ChatGPT / Conversations.
Minor
: OpenAI ChatGPT login content load errors during outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(4 hours and 15 minutes)
OpenAI reported a degraded login experience when some users saw a 'Content failed to load' message after signing in, affecting the ChatGPT / Login component. The outage began on and was resolved by , lasting about 4 hours and 15 minutes. Affected users could not load content after login, limiting access to chat features in affected sessions.
OpenAI released two status updates during the incident, first noting an investigation into the login-related content loading issue and later confirming restoration of normal login content loading. A reported example from a user in San Diego described chatGPT not responding during the outage.
Minor
: OpenAI ChatGPT Conversations brief outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(15 minutes)
OpenAI reported a brief degraded period affecting ChatGPT / Conversations, with users experiencing elevated errors. The incident began at and was resolved by , 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.