STATUS + RESET IMPACT

Codex status、reset 影響まで。

公式 OpenAI incident は何が壊れたかを示します。この独立記録はそこにもう 1 層加えます。どの Codex surface が影響を受け、いつ復旧し、その後に補償 reset があったのかです。

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.

incident2026-07-25 09:17:49 UTC 1h 51m

usage reset2026-07-25 19:17:12.695Z 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.

2026-07-25 19:17:12.695Z
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
2026-07-25 11:35:24.966Z
incident エラー率の上昇 22m public recovery window
official status
2026-07-25 09:17:49 UTC
incident エラー率の上昇 1h 51m public recovery window
official status
2026-07-24 07:55:28.019Z
incident Codex Review でエラー増加 1h 40m public recovery window
official status
2026-07-23 17:56:06.761Z
incident 一部ユーザーで ChatGPT のエラー率が上昇する可能性 27m public recovery window
official status
2026-07-23 15:56:57.525Z
incident エラー率の上昇 4h 26m public recovery window
official status
2026-07-20 00:34:34.443Z
incident GitHub 依存の ChatGPT と Codex ワークフローでエラー率上昇 2h 51m public recovery window
official status
2026-07-18 08:05:37.238Z
incident 一部ユーザーが Codex にアクセスできない 4h 53m public recovery window
official status
2026-07-18 07:43:22.982Z
incident Codex 権限のない Enterprise ユーザーは新しい ChatGPT App を利用不可 41m public recovery window
official status
2026-07-14 23:39:00 UTC
incident ChatGPT に影響するエラー増加 40m public recovery window
official status
2026-06-26 17:04:02.053Z
incident Codex の利用上限が想定より早く減少 6h 20m public recovery window
official status
2026-06-25 05:51:27.890Z
incident Codex で access token を使う際に問題が発生する可能性 5h 12m public recovery window
official status
2026-06-16 10:32:11.139Z
incident Codex「Selected Model is at Capacity」エラー 3h 16m public recovery window
official status
2026-06-16 00:07:04.865Z
incident Codex Cloud tasks で問題が発生する可能性 49m public recovery window
official status
2026-06-11 20:59:52.891Z
incident Codex で GPT 5.5 のエラー率上昇 1h 28m public recovery window
official status
2026-06-04 02:57:25.894Z
incident 一部ユーザーで Codex compaction の遅延増加 1h 40m public recovery window
official status
2026-06-03 05:42:19.206Z
incident Codex、ChatGPT、Responses API でエラー率上昇 1h 29m public recovery window
official status
2026-06-02 23:35:44.163Z
incident codex-gpt-image-2-does-not-exist-errors 38m public recovery window
official status
2026-05-27 17:57:17.742Z
incident Codex コンテキスト圧縮レイテンシ 13h 02m public recovery window
official status
2026-05-22 16:37:50.540Z
incident Codex のレート上限に達するユーザー増加 18h 21m public recovery window
official status
2026-05-13 08:18:13.633Z
incident Codex 5.5 エンジンで高いエラー率 2h 02m public recovery window
official status
2026-05-11 01:23:13.085Z
incident ChatGPT でのファイルアップロードと Codex Cloud でのタスク作成でエラー増加の可能性 2h 01m public recovery window
official status
2026-05-08 15:07:16.117Z
incident Codex Cloud Tasks のパフォーマンス低下 1h 10m public recovery window
official status
2026-05-07 17:15:58.750Z
incident ChatGPT と Codex に影響する文字起こし失敗の増加 15h 15m public recovery window
official status
2026-04-28 22:46:00.492Z
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.