STATUS + RESET IMPACT

Codex status, with the reset impact.

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 Web checking live
  • Codex API checking live
  • CLI checking live
  • VS Code extension checking live
  • ChatGPT Desktop checking live

Availability is aggregate across plans and models. Individual availability can vary.

codex-status --latest-compensation
confirmed link hard reset

Outage recovered. Usage reset followed.

Usage limits reset for all Codex and ChatGPT Work users after an almost-global outage the previous night.

incident 1h 51m
usage reset 8h 09m after recovery

Codex + ChatGPT Work users

codex-status --history

Incident and reset ledger

Solid evidence badges mean the reset announcement explicitly named the outage. Nearby timing alone is never presented as causation.

  1. reset Usage limits reset for all Codex and ChatGPT Work users after an almost-global outage the previous night. hard reset · codex + chatgpt work
    confirmed link
  2. incident Elevated error rates 22m public recovery window
    official status
  3. incident Elevated error rates 1h 51m public recovery window
    official status
  4. incident Elevated Errors in Codex Review 1h 40m public recovery window
    official status
  5. incident Some users may experience elevated error rates in ChatGPT 27m public recovery window
    official status
  6. incident Elevated Error Rates 4h 26m public recovery window
    official status
  7. incident Elevated errors for GitHub-dependent ChatGPT and Codex workflows 2h 51m public recovery window
    official status
  8. incident Some users are unable to access Codex 4h 53m public recovery window
    official status
  9. incident New ChatGPT App Not Available For Enterprise Users Without Codex Permissions 41m public recovery window
    official status
  10. incident Elevated errors affecting ChatGPT 40m public recovery window
    official status
  11. incident Codex Usage Limits Depleting Faster Than Expected 6h 20m public recovery window
    official status
  12. incident Users may encounter issues using access token with Codex 5h 12m public recovery window
    official status
  13. incident Codex "Selected Model is at Capacity" Error 3h 16m public recovery window
    official status
  14. incident Users may experience issue with Codex Cloud tasks 49m public recovery window
    official status
  15. incident Elevated error rates for GPT 5.5 in Codex 1h 28m public recovery window
    official status
  16. incident Increased latency for Codex compaction for a subset of users 1h 40m public recovery window
    official status
  17. incident Elevated error rates on Codex, ChatGPT and Responses API 1h 29m public recovery window
    official status
  18. incident codex-gpt-image-2-does-not-exist-errors 38m public recovery window
    official status
  19. incident Codex Context Compaction Latency 13h 02m public recovery window
    official status
  20. incident Increase in users hitting Codex rate limits 18h 21m public recovery window
    official status
  21. incident Codex 5.5 engines are experiencing high error rate 2h 02m public recovery window
    official status
  22. incident Users may experience elevated errors in ChatGPT uploading files and Codex Cloud creating tasks 2h 01m public recovery window
    official status
  23. incident Degraded Performance with Codex Cloud Tasks 1h 10m public recovery window
    official status
  24. incident Elevated transcription failures affecting ChatGPT & Codex 15h 15m public recovery window
    official status
  25. incident Codex stream is disconnecting intermittently 27m 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.