OpenAI Outage History

OpenAI APIs experienced a short degraded performance due to an elevated error rate tied to the GPT-5.1 Codex Max feature. Users began reporting issues by 8:30 AM UTC. The APIs / Responses component was listed as degraded at Jan 6, 2026 9:06 AM UTC and the problem persisted until Jan 6, 2026 9:56 AM UTC, lasting about 50 minutes. During this window, API calls could be slower or fail for some users.

OpenAI stated that mitigation had been applied and they were monitoring the recovery, with the status returning to normal by Jan 6, 2026 9:56 AM UTC. The disruption was limited to the APIs / Responses component and did not indicate broader impact.

OpenAI experienced a partial outage affecting loading of conversation history and downloading files from Custom GPTs, impacting ChatGPT Conversations and GPTs. The incident began at 3:57 AM UTC and was resolved by 9:41 AM UTC, lasting about 5 hours and 44 minutes. During the incident, OpenAI issued three status updates documenting the issue and mitigation steps.

A subset of Android users reported elevated errors when using OpenAI's ChatGPT. The incident began at 8:36 PM UTC and lasted about 1 hour, with service restored by 9:37 PM UTC. OpenAI indicated issues across 14 ChatGPT components, including ChatGPT Agent, Conversations, Login, Image Generation, Deep Research, and other related services. A small number of user reports were observed, with symptoms such as failures loading or interacting with ChatGPT on Android devices.

OpenAI communicated via its status page with two updates during the event: an initial note of degraded performance across Android users and a follow-up confirming restoration to normal operation. The impact appeared confined to Android users and the outage resolved within an hour, with affected components returning to normal as updates progressed.

OpenAI's Sora API experienced elevated error rates beginning at Dec 19, 2025 6:16 AM UTC, with users reporting failures when generating images and related Sora tasks. The issue affected the APIs / Sora component, causing intermittent outages and degraded functionality for a subset of users. The incident lasted approximately 45 minutes and was resolved by Dec 19, 2025 7:01 AM UTC.

The OpenAI status page issued two updates during the incident, noting increased error rates and the initiation of mitigation efforts. Reports of service disruption came from multiple locations worldwide, indicating a broad, though not global, impact on users relying on Sora API features.

OpenAI's Sora API experienced a brief degradation in latency and increased error rates, impacting clients making requests to the Sora endpoint. The incident began at Dec 19, 2025 1:21 AM UTC and the degraded performance persisted until Dec 19, 2025 1:26 AM UTC when services returned to normal. A small number of user reports indicated issues earlier, around 12:30 AM UTC and 12:45 AM UTC. OpenAI's status page described the event as degraded latency and increased error rates for the Sora API, with mitigation applied and monitoring ongoing. Two status updates were issued during the incident, reflecting the recovery progress.

OpenAI ChatGPT login issues briefly degraded the login experience after SSO authentication. Users began reporting intermittent login loading problems around 10:15 PM UTC. The OpenAI status page shows the ChatGPT / Login component moving from up to warn at Dec 18, 2025 11:21 PM UTC and returning to up at Dec 18, 2025 11:26 PM UTC after mitigation.

OpenAI issued two status updates during the incident, noting that mitigation had been applied and recovery was being monitored. The outage lasted about 5 minutes and primarily affected the ChatGPT login flow, with services restored to normal after the final update.

An authentication outage blocked sign-in to OpenAI's Sora Web, preventing access for users trying to login and use Sora features. The issue affected Sora / Login and later ChatGPT / Login, with sign-in errors reported across regions. The incident began at 9:55 PM UTC and OpenAI published updates including a down state for Sora / Login at 10:06 PM UTC. Mitigation steps were applied and monitoring continued, with the status moving to a degraded state at 10:36 PM UTC and recovery by 10:51 PM UTC.

OpenAI experienced a login outage affecting Sora Web sign-in and ChatGPT login flows. Users reported sign-in errors and authentication failures when attempting to access Sora Web or ChatGPT via SSO, with some receiving errors or blank screens. The disruption impacted two components: Sora / Login and ChatGPT / Login, and appeared to be global as reports came from many regions. The outage lasted about 45 minutes, beginning at 10:06 PM UTC and ending at 10:51 PM UTC.

OpenAI issued multiple status updates during the incident (six updates were observed). The messages described mitigation efforts and monitoring as the team worked to restore sign-in. Updates progressed from initial outage notices to confirmation of mitigations, culminating in restored access for users by the end of the window.

OpenAI reported elevated errors affecting two components: ChatGPT / Codex and APIs / Responses, causing degraded functionality for users attempting Codex workflows or API calls. The incident began at Dec 17, 2025 1:06 AM UTC when the OpenAI status page showed a degraded state and noted that mitigation had been applied and recovery was being monitored. The outage lasted about 3 hours and 10 minutes and was resolved by Dec 17, 2025 4:16 AM UTC.

OpenAI issued two status updates during the incident as they worked to restore normal service, and communications indicated mitigation steps and ongoing recovery. Some users reported issues during the window, reflecting a localized impact on those interacting with Codex features and API responses.

OpenAI reported degraded performance beginning at Dec 16, 2025 6:46 PM UTC as Codex CLI began experiencing elevated errors. A follow-up update at Dec 16, 2025 10:36 PM UTC expanded the issue to the Codex & Responses API, with impacts to ChatGPT / Codex and the API/Responses. Users attempting code generation, chat interactions, or API calls encountered errors or degraded responsiveness, with reports of heavy load and missing responses from multiple regions. The disruption lasted approximately 5 hours and 55 minutes, and recovery began by Dec 17, 2025 12:41 AM UTC as affected components returned toward normal.

OpenAI issued three status updates during the incident, describing mitigation steps and ongoing monitoring. The issue affected two main components: ChatGPT / Codex and APIs / Responses, indicating a broad impact on both interactive chat/code generation and programmatic access. User reports came from diverse regions around the world, including North America, Europe, and the Asia-Pacific, suggesting wide geographic reach. By the end of the window, the status page indicated recovery and continued monitoring while services stabilized.