Outage recap · OpenAI

ChatGPT outage — November 9, 2026

On November 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.

Elevated ChatGPT Conversation Errors

minor
Started
Nov 9, 1:16 PM EST
Resolved
Nov 9, 2:08 PM EST
Duration
52 min

OpenAI's updates (2)

  1. monitoring · Nov 9, 1:16 PM EST

    We’ve applied a mitigation and are monitoring the affected services to confirm recovery.

  2. resolved · Nov 9, 2:08 PM EST

    All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

What our checks recorded

We checked ChatGPT 10 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 660 ms, against 451 ms over the 24 hours before. OpenAI posted the incident at Nov 9, 1:16 PM EST.

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

Elevated Errors On API

minor
Started
Nov 9, 6:08 PM EST
Resolved
Nov 9, 6:50 PM EST
Duration
43 min

OpenAI's updates (2)

  1. identified · Nov 9, 6:08 PM EST

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

  2. resolved · Nov 9, 6:50 PM EST

    All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

What our checks recorded

We checked ChatGPT 9 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 524 ms, against 451 ms over the 24 hours before. OpenAI posted the incident at Nov 9, 6:08 PM EST.

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

Incorrect cost data in Costs API exports

none
Started
Nov 9, 11:42 PM EST
Resolved
Nov 10, 2:02 AM EST
Duration
2h 20m

OpenAI's updates (2)

  1. monitoring · Nov 9, 11:42 PM EST

    We have identified an issue causing incorrect cost data in Costs API exports published between November 6 and 9. We are working to correct the affected records and will provide an update once recovery is confirmed.

  2. resolved · Nov 10, 2:02 AM EST

    All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

What our checks recorded

We checked ChatGPT 28 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 498 ms, against 475 ms over the 24 hours before. OpenAI posted the incident at Nov 9, 11:42 PM EST.

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
Is ChatGPT down right now? →ChatGPT status history →

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