Outage recap · OpenAI

ChatGPT outage — October 30, 2026

On October 30, 2026, ChatGPT had 2 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 errors for GPT Image 2 API image edits

minor
Started
Oct 30, 10:35 AM EDT
Resolved
Oct 30, 2:36 PM EDT
Duration
4h 1m

OpenAI's updates (3)

  1. identified · Oct 30, 10:35 AM EDT

    We are experiencing elevated errors for some GPT Image 2 API image edit requests. We have identified the issue and are working on a fix

  2. monitoring · Oct 30, 12:06 PM EDT

    We’ve applied a mitigation and are monitoring the affected services to confirm recovery.

  3. resolved · Oct 30, 2:36 PM EDT

    All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

What our checks recorded

We checked ChatGPT 48 times from OpenAI's start time to its resolution, 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 270 ms, against 271 ms over the 24 hours before. OpenAI posted the incident at Oct 30, 10:35 AM EDT.

Updates are OpenAI's own words from its status page (status: resolved); we never add an inferred cause.

Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences

minor
Started
Oct 30, 3:38 PM EDT
Resolved
Oct 30, 5:14 PM EDT
Duration
1h 35m

OpenAI's updates (2)

  1. investigating · Oct 30, 3:38 PM EDT

    We’re aware of issues affecting search in Dots, ChatGPT Work, and some ChatGPT thinking experiences. We’re investigating and will share updates here.

  2. resolved · Oct 30, 5:14 PM EDT

    All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

What our checks recorded

We checked ChatGPT 19 times from OpenAI's start time to its resolution, 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 181 ms, against 265 ms over the 24 hours before. OpenAI posted the incident at Oct 30, 3:38 PM EDT.

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
Is ChatGPT down right now? →ChatGPT status history →

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