Outage recap · OpenAI

ChatGPT outage — October 6, 2026

On October 6, 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 error rates in ChatGPT Go conversations

minor
Started
Oct 6, 9:35 AM 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 247 ms, against 270 ms over the 24 hours before. OpenAI's feed showed the incident by Oct 6, 9:40 AM 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.

Errors processing large PDFs in the Responses API

minor
Started
Oct 6, 11:45 AM 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 235 ms, against 266 ms over the 24 hours before. OpenAI's feed showed the incident by Oct 6, 11:55 AM 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.

Computer Use Is Experiencing Issues

minor
Started
Oct 6, 1:15 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 334 ms, against 262 ms over the 24 hours before. OpenAI's feed showed the incident by Oct 6, 1:20 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.

Workspace Agents Degraded and Responses Impacted

minor
Started
Oct 6, 9:12 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 268 ms, against 280 ms over the 24 hours before. OpenAI's feed showed the incident by Oct 6, 9:20 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

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