OpenAI Outage History

OpenAI's Codex Cloud experienced a brief degradation affecting the ChatGPT / Codex component. Users reported elevated errors across Codex Cloud, and OpenAI transitioned the service to a degraded performance state at Feb 16, 2026 5:31 PM UTC, followed by mitigation and ongoing monitoring. The issue was resolved about 20 minutes later, with the component returning to normal by Feb 16, 2026 5:51 PM UTC. OpenAI issued 3 status updates during the incident as they worked to restore operation. The disruption primarily impacted developers relying on Codex Cloud features through ChatGPT / Codex and was limited in scope.

OpenAI's image-related services started showing high error rates, causing degraded image generation and Images API failures. The incident affected two components: ChatGPT / Image Generation and APIs / Images. The outage began on Feb 14, 2026 1:36 AM UTC and was resolved by Feb 14, 2026 4:26 AM UTC, lasting about 2 hours and 50 minutes. The provider issued two status updates during the incident. Users reported server not responding and heavy-load messages while trying to generate images.

From Feb 13, 2026 8:17 AM UTC to Feb 13, 2026 9:01 AM UTC, OpenAI experienced elevated errors affecting ChatGPT / Image Generation and APIs / Images, resulting in degraded image generation for a subset of users. The outage lasted about 44 minutes. OpenAI issued two status updates during the incident as mitigation was implemented, and services returned to normal afterward. A small number of user reports described image generation failures during the event.

OpenAI experienced a brief degradation in the ChatGPT Conversations component, impacting a subset of users during chat sessions. The outage began on 9:41 PM UTC and was resolved by 9:57 PM UTC, lasting about 16 minutes. User reports spiked during the event, indicating real-time chat issues. OpenAI's status page noted a ChatGPT Conversation Issues incident and showed two official updates as the team investigated. The component status shifted from up to warn at Feb 12, 2026 9:41 PM UTC and then back to up at Feb 12, 2026 9:57 PM UTC. The outage appeared limited to ChatGPT Conversations and did not indicate a broader OpenAI outage.

OpenAI users worldwide faced a brief outage with degraded performance, including errors generating responses and difficulty using apps across web and mobile. The incident appeared global based on scattered user reports spanning multiple regions and lasted about 27 minutes, during which some users experienced intermittent issues and reduced access to chat/completion features.

OpenAI experienced a disruption impacting ChatGPT conversations starting around Feb 11, 2026 4:31 PM UTC, making it difficult for users to start chats. The incident expanded to include the text-embedding-3-small API by Feb 12, 2026 2:42 PM UTC, with elevated errors and degraded performance reported worldwide. Users across regions encountered slow responses, timeouts, and under heavy load messages while generating content or creating embeddings. The outage persisted for roughly a day, from Feb 11, 2026 4:31 PM UTC to Feb 12, 2026 5:01 PM UTC.

OpenAI reported increased login errors for ChatGPT, preventing sign-in for many users for roughly two hours. The outage began at 10:41 PM UTC and was resolved by 12:42 AM UTC. Users described authentication failures and sign-in timeouts while attempting to access ChatGPT. OpenAI's status page documented the incident as 'Increased login errors for ChatGPT' and showed the ChatGPT / Login component moving from up to warn and back to up as the issue was investigated and resolved.

OpenAI issued two status updates during the incident, noting ongoing investigation and eventual recovery. User reports began around 10:45 PM UTC and continued through 12:00 AM UTC. The impact appeared limited to a small set of users rather than a service-wide outage.

OpenAI reported a brief degraded performance affecting ChatGPT Go, with users experiencing elevated errors during the incident. The issue impacted the ChatGPT / Conversations component and began at 8:11 PM UTC and was resolved by 9:02 PM UTC, lasting about 51 minutes. OpenAI issued two status updates during the event describing the issue and its resolution. The impact appeared limited to the affected service with a small volume of user reports.

OpenAI experienced elevated error rates in GPT-5.2 that degraded ChatGPT / Conversations for users globally. Reported symptoms included prompts not responding, errors in message streams, and pages failing to load. The incident began around Feb 10, 2026 4:47 PM UTC when the OpenAI status page indicated a degraded experience for the GPT-5.2 component, and lasted about 2 hours and 45 minutes until Feb 10, 2026 7:32 PM UTC when services returned to normal. The issue affected the ChatGPT / Conversations component and led to widespread user impact.

During the incident, OpenAI issued two official status updates describing the investigation and eventual resolution.

OpenAI's ChatGPT and Codex experienced a temporary degradation beginning at 4:31 PM UTC as Codex Cloud faced issues tied to GitHub dependencies. Users reported problems loading ChatGPT on desktop and intermittent generation delays, indicating a partial outage affecting Codex Cloud components.

The incident lasted until 8:26 PM UTC (about 3 hours and 55 minutes). OpenAI issued two official status updates during the event, noting that Codex Cloud issues were tied to GitHub functionality due to outages in GitHub dependencies. Services returned to normal after GitHub dependencies stabilized, with ChatGPT and Codex returning to an up state. Reports from users in multiple regions described inconsistent performance during the window.