Outage recap · OpenAI

ChatGPT outage — October 14, 2026

On October 14, 2026, ChatGPT had 3 reported incidents on OpenAI's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded performance in Codex and ChatGPT Work

minor
Started
Oct 14, 3:05 AM EDT
Resolved
Oct 14, 5:53 AM EDT
Duration
2h 47m

OpenAI's updates (3)

  1. identified · Oct 14, 3:05 AM EDT

    We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

  2. identified · Oct 14, 5:19 AM EDT

    We have identified that users are experiencing elevated errors for the impacted services. We are still implementing the mitigation.

  3. resolved · Oct 14, 5:53 AM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 33 times from OpenAI's start time to its resolution, once every five minutes. Every one of them reached ChatGPT's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 187 ms, against 194 ms over the 24 hours before. OpenAI posted the incident at Oct 14, 3:05 AM EDT.

Updates are OpenAI's own words from its status page (status: resolved); we never add an inferred cause.

Limited availability on gpt-image-2.5-flare and gpt-image-2.5-sunburst

minor
Started
Oct 14, 6:18 AM EDT
Resolved
Oct 14, 6:58 AM EDT
Duration
40 min

OpenAI's updates (3)

  1. investigating · Oct 14, 6:18 AM EDT

    We are investigating limited availability when using gpt-image-2.5-flare and gpt-image-2.5-sunburst in the API.

  2. monitoring · Oct 14, 6:40 AM EDT

    We have applied the mitigation and are monitoring the recovery.

  3. resolved · Oct 14, 6:58 AM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 8 times from OpenAI's start time to its resolution, once every five minutes. Every one of them reached ChatGPT's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 116 ms, against 191 ms over the 24 hours before. OpenAI posted the incident at Oct 14, 6:18 AM EDT.

Updates are OpenAI's own words from its status page (status: resolved); we never add an inferred cause.

Delayed Costs data in the Compliance API

minor
Started
Oct 14, 1:00 PM EDT
Resolved
Oct 16, 6:44 AM EDT
Duration
41h 44m

OpenAI's updates (5)

  1. identified · Oct 14, 1:00 PM EDT

    We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.

  2. identified · Oct 14, 1:02 PM EDT

    We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.

  3. identified · Oct 14, 4:00 PM EDT

    We have identified an issue causing delays in publishing organization cost data through the Costs API. A fix is in progress and currently undergoing testing. API and ChatGPT usage are not affected, and other reporting channels remain available. We are continuing work to restore normal data freshness.

  4. monitoring · Oct 15, 6:36 PM EDT

    We have deployed a fix and are monitoring recovery. Costs data in the Compliance API remains delayed while we process the backlog. We will provide further updates as processing catches up.

  5. resolved · Oct 16, 6:44 AM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 500 times from OpenAI's start time to its resolution, once every five minutes. Every one of them reached ChatGPT's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 207 ms, against 197 ms over the 24 hours before. OpenAI posted the incident at Oct 14, 1:00 PM EDT.

Updates are OpenAI's own words from its status page (status: resolved); we never add an inferred cause.

The AI cascade

ChatGPT depends on OpenAI. When that upstream has an incident, it doesn't hit ChatGPT alone — these AI tools share the dependency and can degrade at the same time:

CursorWindsurfGitHub CopilotTabnineSourcegraph CodyClineRoo CodeContinue

AIDownCheck is not affiliated with OpenAI. This recap summarizes incidents published on OpenAI's official status page.