Outage recap · OpenAI

ChatGPT outage — October 9, 2026

On October 9, 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.

Delayed Costs data in the Compliance API

minor
Started
Oct 9, 1:23 PM EDT
Resolved
Oct 12, 12:02 PM EDT
Duration
70h 39m

OpenAI's updates (5)

  1. identified · Oct 9, 1:23 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 9, 1:27 PM EDT

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

  3. identified · Oct 9, 2:46 PM EDT

    Some customers may continue to experience delayed Costs data through the Compliance API. ChatGPT usage and API Platform requests are not affected, and other reporting channels remain available. We have identified the cause and are continuing work to restore normal data freshness. We will provide another update as work progresses.

  4. monitoring · Oct 9, 6:03 PM EDT

    We have implemented a mitigation, and delayed Costs data is now processing through the Compliance API. Some customers may continue to see incomplete Costs data while the backlog catches up. We expect this catch-up process to continue through Sunday, October 11. ChatGPT usage and API Platform requests remain unaffected. We are monitoring recovery.

  5. resolved · Oct 12, 12:02 PM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 576 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 178 ms, against 278 ms over the 24 hours before. OpenAI posted the incident at Oct 9, 1:23 PM EDT.

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

Some ChatGPT content may be unavailable on Android

major
Started
Oct 9, 5:00 PM EDT
Resolved
Oct 9, 8:26 PM EDT
Duration
3h 26m

OpenAI's updates (2)

  1. identified · Oct 9, 5:00 PM EDT

    We have identified an issue affecting the ChatGPT Android app where users may see “This content is unavailable in this version of the app” instead of certain content. A fix is rolling out gradually in the latest Android version. Users can use ChatGPT on the web while we work to restore the experience for older app versions.

  2. resolved · Oct 9, 8:26 PM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 41 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 215 ms, against 270 ms over the 24 hours before. OpenAI posted the incident at Oct 9, 5:00 PM EDT.

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

Workspace admins may be unable to manage plugins

major
Started
Oct 9, 5:48 PM EDT
Resolved
Oct 9, 7:26 PM EDT
Duration
1h 38m

OpenAI's updates (3)

  1. investigating · Oct 9, 5:48 PM EDT

    We are investigating an issue affecting some ChatGPT workspace administrators’ ability to view and manage plugin availability and settings. Some users may also see plugins as unavailable. We will provide another update as soon as we have more information.

  2. monitoring · Oct 9, 6:52 PM EDT

    We are seeing recovery in workspace administrators’ ability to view and manage plugin availability and settings. We are monitoring to ensure service remains stable.

  3. resolved · Oct 9, 7:26 PM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 20 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 246 ms, against 269 ms over the 24 hours before. OpenAI posted the incident at Oct 9, 5:48 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.