Outage recap · OpenAI

ChatGPT outage — August 11, 2026

On August 11, 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.

Increased error rates

minor
Started
Aug 11, 8:54 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 286 ms, against 289 ms over the 24 hours before. OpenAI's feed showed the incident by Aug 11, 9:00 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 affecting ChatGPT Go conversations

minor
Started
Aug 11, 10:10 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 294 ms, against 289 ms over the 24 hours before. OpenAI's feed showed the incident by Aug 11, 10:15 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.

Users unable to login to ads manager

minor
Started
Aug 11, 1:25 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 294 ms, against 287 ms over the 24 hours before. OpenAI's feed showed the incident by Aug 11, 1:25 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.

Increase in errors on API, Codex and Work Mode

none
Started
Aug 11, 5:35 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 283 ms, against 289 ms over the 24 hours before. OpenAI's feed showed the incident by Aug 11, 5:40 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.