Outage recap · OpenAI

ChatGPT outage — November 13, 2026

On November 13, 2026, ChatGPT had 2 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
Nov 13, 11:10 AM EST
Resolved
Nov 15, 7:17 PM EST
Duration
56h 7m

OpenAI's updates (4)

  1. identified · Nov 13, 11:10 AM EST

    We have identified an issue causing delays in publishing Organization cost data through the Costs API. API and ChatGPT usage are not affected. We are working to restore normal data freshness.

  2. monitoring · Nov 13, 1:56 PM EST

    We’ve applied a mitigation and are monitoring the affected services to confirm recovery. Delays in cost data are still expected.

  3. monitoring · Nov 14, 12:31 AM EST

    We are monitoring the affected services to confirm recovery. Delays in cost data are still expected.

  4. resolved · Nov 15, 7:17 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 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 354 ms, against 466 ms over the 24 hours before. OpenAI posted the incident at Nov 13, 11:10 AM EST.

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

Elevated errors with ChatGPT billing and Ads billing

none
Started
Nov 13, 11:11 PM EST
Resolved
Nov 14, 12:27 AM EST
Duration
1h 17m

OpenAI's updates (2)

  1. monitoring · Nov 13, 11:11 PM EST

    We are monitoring recovery from errors affecting ChatGPT billing, including checkout, and Ads invoice retrieval.

  2. resolved · Nov 14, 12:27 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 15 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 334 ms, against 398 ms over the 24 hours before. OpenAI posted the incident at Nov 13, 11:11 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

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