New! Check service status instantly with our Chrome extension
There were 318 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?
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.
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.
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.
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.
OpenAI experienced a cloud service outage caused by a gateway timeout, impacting chat interactions and file uploads. Users reported gateway timeouts, slow chat responses, and web client unresponsiveness across multiple regions. The incident began around and was resolved by , lasting roughly 38 minutes and affecting core features during the window.
StatusGator detected the issue at , and the Early Warning Signal concluded at . OpenAI did not post any official status updates during the incident. The event drew a handful of user reports during the window, indicating a broader outage affecting multiple users.
OpenAI reported degraded performance for the Fine-tuning APIs, with increased latency affecting fine-tuning jobs for an extended period. Users experienced slow responses and occasional unavailability when dealing with fine-tuning tasks. The incident began at and was resolved by , lasting about 21 hours and 35 minutes. The issue was tied to the APIs / Fine-tuning component, which showed degraded performance during the event.
OpenAI's Sora service experienced a global outage affecting user access for about 55 minutes. Users across regions reported that Sora was not loading, login prompts were failing, and error messages appeared. The incident appeared to be widespread, with feedback from North America and Europe indicating the service was unavailable or degraded.
The OpenAI service experienced an outage affecting the ability to download files, with user reports starting at and continuing until . StatusGator detected the issue at , ahead of any official acknowledgment. The outage lasted roughly 2 hours and 5 minutes and generated a high volume of user reports indicating broad impact on file retrieval workflows. OpenAI did not publish any status updates during the incident, and there were no official updates on the OpenAI status page to help users understand the situation.
The OpenAI Code Interpreter feature within the API experienced elevated errors, resulting in degraded functionality for users invoking Code Interpreter workflows. The incident began at and was resolved by , lasting about 1 hour and 15 minutes. The affected component was APIs / Responses, and OpenAI issued 2 status updates during the incident. Users reported API failures and errors related to Code Interpreter around while the issue was active.
OpenAI users experienced a brief login issue impacting access to the OpenAI app and video downloads. The incident appears to have started around and was resolved by . StatusGator detected the issue at , and the problem ended the same minute. There were no official status updates published by OpenAI during the incident in the provided data, suggesting a rapid resolution or a brief, localized disruption. User reports were limited, indicating the impact was not widely felt. An Early Warning Signal was triggered, with StatusGator observing login issues before a formal acknowledgment by OpenAI.
Looking for more OpenAI outage stats?
Get real-time insights and historical data on OpenAI outages.
