OpenAI Outage History

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 3:00 PM UTC and was resolved by 3:38 PM UTC, lasting roughly 38 minutes and affecting core features during the window.

StatusGator detected the issue at Sep 29, 2025 3:13 PM UTC, and the Early Warning Signal concluded at Sep 29, 2025 3:38 PM UTC. 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 Sep 26, 2025 11:56 PM UTC and was resolved by Sep 27, 2025 9:31 PM UTC, 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 Sep 26, 2025 12:45 AM UTC and continuing until Sep 26, 2025 2:50 AM UTC. StatusGator detected the issue at Sep 26, 2025 12:45 AM UTC, 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 Sep 25, 2025 5:16 PM UTC and was resolved by Sep 25, 2025 6:31 PM UTC, 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 6:00 PM UTC 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 11:30 AM UTC and was resolved by 11:32 AM UTC. StatusGator detected the issue at Sep 25, 2025 11:32 AM UTC, 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.

OpenAI's ChatGPT on WhatsApp experienced a prolonged outage beginning at Sep 24, 2025 3:32 AM UTC, when the OpenAI status page reported the service moved from up to down for ChatGPT / WhatsApp and ChatGPT / 1-800-CHAT-GPT. Users could initiate messages but often did not receive responses, with the disruption affecting the WhatsApp integration as well as related web, login, and mobile interfaces. The outage persisted until Sep 25, 2025 1:01 AM UTC, lasting about 21 hours and 29 minutes, before services began returning to normal.

The OpenAI status page issued 8 updates during the incident, detailing progression from degraded performance to restoration and tracking component-level impact. The updates tracked changes across multiple components, with WhatsApp and 1-800-CHAT-GPT bearing the brunt of the disruption, along with variations in Login, Web, and mobile clients. By Sep 25, 2025 1:01 AM UTC the affected channels were back to up, marking the end of the incident.

OpenAI's image creation endpoint experienced a brief outage, blocking image generation for about 5 minutes. The incident began around 2:29 AM UTC and was resolved by 2:34 AM UTC, with a handful of user reports across multiple locations describing server errors and failed image requests. The issue appeared isolated to image creation and did not indicate a broader service disruption.

StatusGator detected an Early Warning Signal at Sep 24, 2025 2:29 AM UTC, and OpenAI did not publish an official status update during the incident. Communication from the service was limited to user-reported symptoms until the issue was resolved.

OpenAI reported increased errors affecting ChatGPT Context Connectors, causing degraded performance for users interacting with ChatGPT where Connectors are used. The issue appeared to impact the reliability of Connector functionality, with some requests failing or returning errors.

The incident began at Sep 23, 2025 2:21 AM UTC and was resolved by Sep 23, 2025 3:26 AM UTC. OpenAI posted 2 status updates during the incident as they investigated and remediated the cause. The outage lasted roughly 1 hour and 5 minutes, primarily impacting the ChatGPT Context Connectors component.

OpenAI reported an elevated error rate impacting ChatGPT services, including ChatGPT / Codex and ChatGPT / Agent. The issue began when the status page transitioned from up to warn at 10:01 PM UTC, indicating degraded performance. The problem persisted for about 3 hours until the status returned to up at 1:01 AM UTC. During the incident, users could have encountered failed requests and slower responses across the affected components. OpenAI posted updates acknowledging the investigation and the eventual restoration of normal service.