~/Codex Reset alerts codex: checking…

状态 + 重置影响

Codex 状态，以及重置影响。

OpenAI 官方事故告诉你哪里出了问题。这个独立记录补上缺失的一层：哪些 Codex 界面受到影响、服务何时恢复，以及之后是否出现了补偿重置。

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

OpenAI Status Reset announcement
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 错误率升高 22m public recovery window
    official status
  3. incident 错误率升高 1h 51m public recovery window
    official status
  4. incident Codex Review 中的错误增加 1h 40m public recovery window
    official status
  5. incident 部分用户在 ChatGPT 中可能遇到更高的错误率 27m public recovery window
    official status
  6. incident 错误率升高 4h 26m public recovery window
    official status
  7. incident 依赖 GitHub 的 ChatGPT 和 Codex 工作流出现更高的错误率 2h 51m public recovery window
    official status
  8. incident 部分用户无法访问 Codex 4h 53m public recovery window
    official status
  9. incident 没有 Codex 权限的 Enterprise 用户无法使用新的 ChatGPT App 41m public recovery window
    official status
  10. incident 影响 ChatGPT 的错误率升高 40m public recovery window
    official status
  11. incident Codex 用量限制消耗速度快于预期 6h 20m public recovery window
    official status
  12. incident 用户使用 access token 连接 Codex 时可能遇到问题 5h 12m public recovery window
    official status
  13. incident Codex “Selected Model is at Capacity” 错误 3h 16m public recovery window
    official status
  14. incident 用户在 Codex Cloud tasks 中可能遇到问题 49m public recovery window
    official status
  15. incident Codex 中 GPT 5.5 的错误率升高 1h 28m public recovery window
    official status
  16. incident 部分用户的 Codex compaction 延迟增加 1h 40m public recovery window
    official status
  17. incident Codex、ChatGPT 和 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 上下文压缩延迟 13h 02m public recovery window
    official status
  20. incident 触及 Codex 速率限制的用户增加 18h 21m public recovery window
    official status
  21. incident Codex 5.5 引擎出现高错误率 2h 02m public recovery window
    official status
  22. incident 用户在 ChatGPT 上传文件和 Codex Cloud 创建任务时可能遇到更高错误率 2h 01m public recovery window
    official status
  23. incident Codex Cloud Tasks 性能下降 1h 10m public recovery window
    official status
  24. incident 影响 ChatGPT 和 Codex 的转录失败率升高 15h 15m public recovery window
    official status
  25. incident Codex stream 间歇性断开 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.