OpenAI Outage History

OpenAI's ChatGPT services across desktop, web, and mobile experienced elevated network errors, causing connectivity issues for some users. Impacted platforms included ChatGPT / Desktop (Windows and macOS), ChatGPT / Web, and ChatGPT / Mobile (iOS and Android), with reports of intermittent errors and failed requests. The outage began on 10:41 PM UTC and was resolved by 2:56 AM UTC, lasting about 4 hours and 15 minutes. The provider issued two status updates during the incident. A sample user reported in Chattanooga, Tennessee that repeated network errors occurred while using ChatGPT.

OpenAI experienced a broad outage beginning at 9:06 AM UTC, with GPT-4.1 high error rate and latency affecting the APIs that power responses and completions. The issue soon expanded to Login, Images, Chat, and related components, causing degraded performance and failed operations for users across regions. Initial impact was observed on the APIs / Responses and APIs / Completions (legacy).

OpenAI published eight status updates over the course of the incident, detailing the ongoing investigation and mitigation efforts. By 5:21 PM UTC, the majority of affected components had recovered and returned to normal operation. The outage lasted approximately 8 hours and 15 minutes.

Users reported issues from multiple regions around the world, including login problems, chat disruptions, and image generation errors, indicating a global impact across the OpenAI platform. The incident is classified as major due to its broad reach across many APIs and services.

OpenAI experienced a brief outage affecting EU Data Residency API customers, with 15 API components briefly unavailable (including Chat, Completions, Embeddings, Images, Files, Login, Realtime, and more). The incident began for EU Data Residency users at Jul 16, 2025 11:17 PM UTC and recovery started at Jul 16, 2025 11:24 PM UTC, with full restoration by Jul 16, 2025 11:51 PM UTC. OpenAI issued 2 official status updates during the incident.

OpenAI experienced a brief authentication disruption impacting ChatGPT Single Sign-On and the Login APIs, which prevented users from signing in during the incident. Two components were affected: ChatGPT / Single Sign-On and APIs / Login. The outage began at 21:11 UTC and was resolved by 21:16 UTC, lasting about 5 minutes. OpenAI issued two status updates to communicate the issue and recovery, and user reports were limited, indicating a short-lived disruption on the login path.

OpenAI experienced broad elevated error rates across multiple services, notably Sora Video generation and a wide range of ChatGPT features. Users reported server errors, timeouts, sign-in problems, and difficulty loading conversations or histories. The disruption appeared global and persisted for roughly two hours, beginning around Jul 16, 2025 1:36 AM UTC.

OpenAI's status page documented the investigation and mitigation across several updates. The provider issued seven updates between Jul 16, 2025 1:36 AM UTC and Jul 16, 2025 3:51 AM UTC, noting mitigation steps and ongoing monitoring as recovery progressed. By the final updates, many components had returned to normal, with recovery completed for the majority of services by around Jul 16, 2025 3:51 AM UTC.

Scope and impact: The incident affected more than a dozen ChatGPT subsystems in addition to Sora Video generation, including Web, Codex, Context connectors, Desktop and Mobile clients, Memory, File uploads, Dall-E, Login, Conversations, and related features. User reports tracked a global pattern of issues across regions, consistent with a widespread outage rather than a regional fault. Overall, the event represented a major disruption to OpenAI services during the window.

OpenAI experienced a period of elevated error rates affecting ChatGPT and Sora video generation, beginning around 1:36 AM UTC. Users reported sign-in failures, conversations not loading, and failed or slow requests across ChatGPT features and Sora. The disruption appeared global, with reports of server errors and timeouts across multiple regions as a broad set of ChatGPT components and Sora were affected for roughly two hours, impacting access to chats, content generation, and related functionality.

OpenAI's ChatGPT and API services experienced elevated error rates that affected a broad range of features and API endpoints. User reports began around 4:30 PM UTC, with OpenAI acknowledging the issue at 5:02 PM UTC and indicating mitigation efforts. The incident involved dozens of ChatGPT components and API paths, including login, messaging, file uploads, search, image generation, embeddings, and more, leading to degraded performance and failed requests for users. The disruption lasted about 7:46 PM UTC, with services gradually recovering by that time.

The OpenAI 4.1-mini API experienced elevated errors and degraded performance starting at 9:31 PM UTC, with a broad degradation across 15 API components including Assistants, Audio, Images, Fine-tuning, Realtime, Responses, Login, Batch, Embeddings, Files, Completions (legacy), Chat, Compliance, Moderations, and Uploads. Users attempting requests to the 4.1-mini API observed errors or slower responses, impacting typical workflows.

OpenAI issued two status updates describing the degradation and ongoing mitigation, and the incident was resolved by 9:57 PM UTC. The outage lasted about 26 minutes. User reports were limited but indicated intermittent issues across the affected services.

OpenAI experienced a partial outage affecting multiple API endpoints, including /v1/chat/completions, /v1/completions, the Private Link, and the API responses surface. The status page indicated an issue labeled as Errors on API Endpoints, with the affected components listed as APIs / Responses and APIs / Completions (legacy). The incident involved two status updates from OpenAI during the event, and normal operation was restored after.

OpenAI experienced an outage impacting the API used to create new fine-tuning jobs. Users attempting to start fine-tuning runs encountered errors, disrupting workflows that rely on programmatic model training. The incident affected the APIs / Fine-tuning component and appeared to be global based on reports from multiple regions.

Timeline: The outage began at Jul 8, 2025 12:16 AM UTC and was mitigated by Jul 8, 2025 1:22 AM UTC. The status subsequently moved to a degraded state and recovery was completed by Jul 8, 2025 6:56 PM UTC. OpenAI issued 3 official status updates during the incident.

Impact and recovery: The outage lasted approximately 18 hours and 40 minutes, with full fine-tuning job creation restored by late Jul 8, 2025 6:56 PM UTC. User reports indicate global distribution of issues, confirming widespread impact. OpenAI's team implemented mitigation and monitoring as the service returned to normal.