Official OpenAI incidents answer what broke. This independent record adds the missing layer: which Codex surfaces were affected, when service recovered, and whether a compensation reset followed.
CHECKING LIVE CODEX STATUSOfficial data has not loaded yet.official source
incidents24Codex-impacting on record
recovery1h 51mmedian public window
compensated1explicit reset links
reset lag8h 09mmedian after recovery
codex-status --surfaces5 surfaces
Current component state from OpenAI. An unrelated ChatGPT incident does not mark Codex as down.
Codex Webchecking live
Codex APIchecking live
CLIchecking live
VS Code extensionchecking live
ChatGPT Desktopchecking live
Availability is aggregate across plans and models. Individual availability can vary.
codex-status --latest-compensation
confirmed linkhard reset
Outage recovered. Usage reset followed.
Usage limits reset for all Codex and ChatGPT Work users after an almost-global outage the previous night.
incidentCodex stream is disconnecting intermittently27m public recovery window
official status
Times switch from UTC to your local time after browser sync. Raw data: /api/status-history.
Evidence, not outage prediction
Official incident states come from OpenAI Status, with a 90-day history backfill and 180-day forward retention. Compensation links come from source posts and are labeled explicit or temporal. This page does not promise that a future outage will cause a reset.