Outage recap · OpenAI

ChatGPT outage — October 21, 2026

On October 21, 2026, ChatGPT had 4 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 FedRAMP API error rates for Astra and Sol

minor
Started
Oct 21, 10:17 AM EDT
Resolved
Oct 21, 3:34 PM EDT
Duration
5h 17m

OpenAI's updates (4)

  1. identified · Oct 21, 9:42 AM EDT

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

  2. investigating · Oct 21, 9:51 AM EDT

    We are investigating the issue for the listed services.

  3. monitoring · Oct 21, 12:46 PM EDT

    We have applied the mitigation and are monitoring the recovery.

  4. resolved · Oct 21, 3:34 PM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 63 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 179 ms, against 199 ms over the 24 hours before. OpenAI posted the incident at Oct 21, 10:17 AM EDT.

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

Elevated error rates for gpt-5.6-luna API requests

minor
Started
Oct 21, 11:34 AM EDT
Resolved
Oct 21, 12:44 PM EDT
Duration
1h 9m

OpenAI's updates (3)

  1. identified · Oct 21, 11:34 AM EDT

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

  2. monitoring · Oct 21, 11:47 AM EDT

    We have applied the mitigation and are monitoring the recovery.

  3. resolved · Oct 21, 12:44 PM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 14 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 179 ms, against 196 ms over the 24 hours before. OpenAI posted the incident at Oct 21, 11:34 AM EDT.

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

Authentication errors for some users

major
Started
Oct 21, 6:36 PM EDT
Resolved
Oct 20, 1:35 PM EDT
Duration
—

OpenAI's updates (2)

  1. investigating · Oct 20, 12:35 PM EDT

    Some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex.

  2. resolved · Oct 20, 1:35 PM EDT

    On October 20, from 9:35 to 10:35 a.m. PDT, some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex. We rolled back a configuration change, and service was restored.

What our checks recorded

We have no checks recorded from OpenAI's start time to its resolution.

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

Elevated ChatGPT conversation and Responses API errors

minor
Started
Oct 21, 10:18 PM EDT
Resolved
Oct 22, 4:50 AM EDT
Duration
6h 32m

OpenAI's updates (3)

  1. investigating · Oct 21, 10:18 PM EDT

    This is impacting users in India, Japan, and Korea. We are investigating the issue for the listed services.

  2. monitoring · Oct 21, 10:42 PM EDT

    This is impacting users in India, Japan, and Korea. We have applied the mitigation and are monitoring the recovery.

  3. resolved · Oct 22, 4:50 AM EDT

    All impacted services have now fully recovered.

What our checks recorded

We checked ChatGPT 79 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 194 ms over the 24 hours before. OpenAI posted the incident at Oct 21, 10:18 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.