Outage recap · OpenAI

ChatGPT outage — September 18, 2026

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

Delayed support responses

none
Started
Sep 18, 5:36 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 291 ms, against 325 ms over the 24 hours before. OpenAI's feed showed the incident by Sep 18, 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.

Overbilling for OpenAI-hosted containers in the Agent API

none
Started
Sep 18, 6:29 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 310 ms, against 324 ms over the 24 hours before. OpenAI's feed showed the incident by Sep 18, 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.

SSO sign-in and SCIM provisioning issues

none
Started
Sep 18, 7:00 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 340 ms, against 323 ms over the 24 hours before. OpenAI's feed showed the incident by Sep 18, 7: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.

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.