Outage recap · OpenAI

ChatGPT outage — September 13, 2026

On September 13, 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.

Codex GitHub Review and Pull Request Failures

minor
Started
Sep 13, 5:26 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 262 ms, against 286 ms over the 24 hours before. OpenAI's feed showed the incident by Sep 13, 5:30 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.

Elevated errors for ChatGPT users in Europe

minor
Started
Sep 13, 12:56 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 290 ms, against 281 ms over the 24 hours before. OpenAI's feed showed the incident by Sep 13, 1:05 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.

Elevated error rates for ChatGPT Chat/Work

none
Started
Sep 13, 10:46 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 185 ms, against 282 ms over the 24 hours before. OpenAI's feed showed the incident by Sep 13, 10:55 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.