Breaking

OpenAI Restores ChatGPT and Codex After Routing Error Hits 19 Components

September 3, 2026 at 18:08 EDT

Foundation Models
Software Dev & Coding

OpenAI restored ChatGPT and Codex on September 3, 2026, after elevated errors spread across every tracked component of both products, an incident the company classified as degraded performance and later tied to a routing error.

September 3, 2026 · OpenAI

ChatGPT and Codex go degraded — then recover

A routing error produced elevated errors across 19 ChatGPT and Codex components. OpenAI applied a mitigation and marked the incident resolved after about two hours.

Components degraded

~2h

Incident window

ChatGPT components

Codex components

Affected components, drawn to scale

Every tracked ChatGPT and Codex surface was listed. Column height equals component count.

ChatGPT

Codex

Incident path

1 · 2:43 p.m. UTC

Investigating

Elevated errors listed for ChatGPT and Codex.

→

2 · 3:17 p.m. UTC

Mitigation

A fix was applied and recovery monitored.

→

3 · 4:55 p.m. UTC

Resolved

Elevated errors cleared on both products.

After the all-clear

Service restored, with one Codex pairing note

Remote control

Some Codex remote-control users may need to pair their mobile device again.

Not listed

APIs, FedRAMP, and Ads Platform were not named as affected components.

Cause stated

OpenAI described a routing error; no longer postmortem was posted on the incident thread.

What recovered

ChatGPT and Codex restored

The status page returned both products to resolved. Core API, FedRAMP, and ads groups were never listed on this incident.

What users hit

404s and stalled coding turns

Login, conversations, voice, images, and agents failed for many users. Codex Desktop, CLI, and MCP clients returned 404 on the responses endpoint even when account checks still worked.

Continue reading

The rest of this article is for AI News Blitz readers. Choose an option below to keep reading.