Outage recap · OpenAI

ChatGPT outage — October 27, 2026

On October 27, 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 error rates for most hosted Code Reviews and Security Reviews on private GitHub repositories

none
Started
Oct 27, 4:00 AM EDT
Resolved
Oct 27, 4:30 AM EDT
Duration
29 min

OpenAI's updates (3)

  1. investigating · Oct 27, 4:00 AM EDT

    We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.

  2. monitoring · Oct 27, 4:21 AM EDT

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

  3. resolved · Oct 27, 4:30 AM EDT

    The issue is now resolved.

What our checks recorded

We checked ChatGPT 5 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 235 ms, against 266 ms over the 24 hours before. OpenAI posted the incident at Oct 27, 4:00 AM EDT.

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

6.1 Sol Degraded Model Performance

minor
Started
Oct 27, 11:02 AM EDT
Resolved
Oct 27, 12:20 PM EDT
Duration
1h 18m

OpenAI's updates (3)

  1. investigating · Oct 27, 11:02 AM EDT

    We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.

  2. monitoring · Oct 27, 11:40 AM EDT

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

  3. resolved · Oct 27, 12:20 PM EDT

    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 272 ms, against 259 ms over the 24 hours before. OpenAI posted the incident at Oct 27, 11:02 AM EDT.

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

Degraded Performace on ChatGPT Work

minor
Started
Oct 27, 11:39 PM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked ChatGPT 24 times in the two hours after OpenAI's start time (it published no end time), 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 274 ms, against 266 ms over the 24 hours before. OpenAI's feed showed the incident by Oct 27, 11:45 PM EDT (we read it every five minutes).

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.