There were 294 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?
Major
: OpenAI Chat Completions and Responses APIs down briefly
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(25 minutes)
The OpenAI Chat Completions and Responses APIs experienced a brief outage beginning at and ending at . The incident affected 2 components within OpenAI: APIs / Chat Completions and APIs / Responses, causing errors for users attempting to generate chat completions or standard responses. The outage lasted about 25 minutes before services were restored. OpenAI issued 2 status updates during the incident to communicate the issue and the resolution.
Minor
: OpenAI chat and message streaming impacted globally for ~46 minutes
Detected by StatusGator:
Officially acknowledged:
No
Outage ended:
(46 minutes)
The outage affected OpenAI's chat functionality and message streaming, with users reporting errors in the message stream and unresponsiveness in the chat app. The disruption began at and ended at , lasting about 46 minutes. Reports came from users across multiple regions, indicating a broad, global impact on core messaging features.
There were no official OpenAI status updates posted during the incident. StatusGator detected the issue at based on user reports, signaling an Early Warning Signal ahead of any OpenAI acknowledgment. With reports spanning regions worldwide, the disruption appeared global in scope and primarily affected chat and message streaming functionality.
Minor
: OpenAI SFT delays and web chat issues affect users
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 day, 23 hours and 30 minutes)
The outage began on with delays in supervised fine-tuning (SFT) jobs, impacting the APIs / Fine-tuning component. Over the next 47 hours, issues expanded to web chat and login workflows, with users reporting problems loading chat and logging in across multiple regions. The disruption affected three OpenAI components: APIs / Fine-tuning, ChatGPT / Connectors, and ChatGPT / Conversations, causing training delays and degraded chat experiences for many users.
OpenAI shared a series of updates on the status page, including mitigation steps and ongoing investigations. The incident involved six official status updates, documenting progress from investigation to mitigation and recovery. Key milestones included a partial Apps SDK Dev Mode outage around , followed by web chat disruptions around and subsequent mitigation by . A renewed note at indicated continued SFT delays before recovery. By , the APIs / Fine-tuning component had recovered and the incident was returning to normal as reported across services. User reports came from multiple regions, indicating broad impact on login, chat, and model-training workflows.
Minor
: OpenAI services degraded across APIs and ChatGPT features
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(4 days, 5 hours and 55 minutes)
From OpenAI began observing elevated error rates and degraded performance across multiple components, including APIs / Responses, APIs / Realtime, APIs / Images, and several ChatGPT modules such as Image Generation, Deep Research, Agent, Codex, along with Login and Sora Image Generation. Users encountered errors, timeouts, and slow responses when invoking APIs or using ChatGPT workflows, with reports of login difficulties and content generation delays. The issue persisted for multiple days with gradual recoveries noted in status updates, affecting a wide range of OpenAI services.
Major
: OpenAI ChatGPT outage disrupts global chat service
Detected by StatusGator:
Officially acknowledged:
No
Outage ended:
(22 minutes)
OpenAI's ChatGPT chat service experienced an outage where users could not send or receive messages. Reports came in from multiple countries across Asia-Pacific, including the Philippines, New Zealand, Indonesia, Australia, Pakistan, and Thailand, indicating broad impact. StatusGator recorded an Early Warning Signal at , suggesting user-reported issues before any OpenAI acknowledgment. The issue lasted roughly 22 minutes, with no OpenAI status updates posted during the incident.
Major
: OpenAI multi-service outage disrupts Codex, GPTs, and login
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 hours and 5 minutes)
OpenAI experienced a multi-service outage starting at with elevated errors across Codex, Search, Agent, and custom GPTs. Over the following hours, several components were listed as degraded or unavailable, and users reported issues such as failed logins and inability to create new accounts. By , most affected services had returned to normal operation. The incident involved a series of official updates (five in total) as OpenAI worked to mitigate and investigate the root cause. The outage appeared across multiple regions, with reports from places including Singapore, Denver, and Mascouche, indicating broad geographic impact. The outage lasted approximately 5 hours and 5 minutes.
Minor
: OpenAI outage briefly affects some users; New Jersey report
Detected by StatusGator:
Officially acknowledged:
No
OpenAI experienced a short outage affecting some users. A user in Clementon, New Jersey reported issues starting by and the service was restored by . StatusGator detected the outage at . OpenAI did not publish status updates during the event. The incident appears to be localized with limited user reports and no obvious regional pattern.
Minor
: OpenAI Android Google sign-in errors briefly impacted signups
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(9 hours and 15 minutes)
OpenAI's ChatGPT Mobile on Android experienced a brief degradation in the Google sign-in flow, causing sign-up errors for some users. The issue affected the Android sign-up experience and was reflected on OpenAI's status page for the ChatGPT / Mobile - Android component. The outage began on and was resolved by . The incident lasted approximately 9 hours and 15 minutes, and the provider issued 2 status updates over its course.
Minor
: OpenAI API degraded performance for Chat Completions and Responses
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(10 minutes)
OpenAI API experienced a brief degraded performance due to elevated error rates on gpt-5-nano-2025-08-07-4292, impacting the APIs for Chat Completions and API Responses. Users attempting to generate or retrieve completions may have encountered errors during the incident. The outage began at and lasted about 10 minutes, with services returning to normal by .
OpenAI documented mitigation efforts on their status page, and the affected components reverted to the up state after the issue was resolved. The incident affected two components: APIs / Chat Completions and APIs / Responses.
Minor
: OpenAI outage: Compliance API ingestion delays and ChatGPT issues
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 day and 10 minutes)
OpenAI experienced a degradation affecting two areas: the Compliance API ingestion pipeline and ChatGPT Conversations. Compliance ingestion delays impacted data flows for compliance workflows, while ChatGPT users encountered increased error rates and slower responses during conversations.
Timeline and response: The incident began at with Compliance API ingestion delays. By the issue expanded to ChatGPT Conversations with elevated error rates. OpenAI issued four status updates during the incident, including mitigation steps around and eventual restoration by .
Impact and recovery: The outage lasted roughly a day, affecting a broad set of users across OpenAI services with failed requests, slow responses, and degraded performance. Mitigations were applied and monitoring continued until services returned to normal.
