Outage recap · OpenAI

ChatGPT outage — August 31, 2026

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

ChatGPT Work seeing elevated errors and latency

major
Started
Aug 31, 11:04 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 318 ms, against 298 ms over the 24 hours before. OpenAI's feed showed the incident by Aug 31, 11:10 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 latency in the Responses API

minor
Started
Aug 31, 6:27 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 321 ms, against 305 ms over the 24 hours before. OpenAI's feed showed the incident by Aug 31, 6:35 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 errors in ChatGPT conversations for Free and Go plans

minor
Started
Aug 31, 8:38 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 309 ms, against 306 ms over the 24 hours before. OpenAI's feed showed the incident by Aug 31, 8: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

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