Experimental historical estimate, not a promise or your account reset time. Waiting longer does not raise this memoryless model's odds.
How we calculate this
We use up to eight completed intervals between source-marked confirmed reset records, deduplicate by UTC date, and exclude banked grants, previews and future records. Rate = intervals / total days; P(t) = 1 − exp(−rate × t). Displayed estimates are capped at 46% and 71%. This is our own implementation, not the original provider's exact model or a validated prediction.
OFFICIAL SERVICE REPORT
Service status
Waiting for OpenAI Status.
Only Codex-named components actually reported by the official API are shown. Other surfaces and your personal quota are unknown.
A conservative wording rule, separate from the historical percentage. A watch score is a rule level, not a measured probability. Banked grants do not reset this model's clock.
Data: codex-reset.com. Service status: OpenAI Status. Our backend fetches and briefly caches these public sources on request. It does not operate its own X API collector or account-monitoring fleet. No request is sent with your saved personal time or usage.
The visible page checks about every two minutes; source timestamps may be older than our fetch time. If an upstream fails, we show failure or stale data, not the old archived snapshot as a live result.
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 · Codex + ChatGPT Work users
Outage recovered. Usage reset followed.
Usage limits reset for all Codex and ChatGPT Work users after an almost-global outage the previous night.
Solid evidence badges mean the reset announcement explicitly named the outage. Nearby timing alone is never presented as causation.
--range
usage resetUsage limits reset for all Codex and ChatGPT Work users after an almost-global outage the previous night.hard reset · Codex + ChatGPT Work users
confirmed link
incidentElevated error rates22m public recovery window
official status
incidentElevated error rates1h 51m public recovery window
official status
incidentElevated Errors in Codex Review1h 40m public recovery window
official status
incidentSome users may experience elevated error rates in ChatGPT27m public recovery window
official status
incidentElevated Error Rates4h 26m public recovery window
official status
incidentElevated errors for GitHub-dependent ChatGPT and Codex workflows2h 51m public recovery window
official status
incidentSome users are unable to access Codex4h 53m public recovery window
official status
incidentNew ChatGPT App Not Available For Enterprise Users Without Codex Permissions41m public recovery window
official status
incidentElevated errors affecting ChatGPT40m public recovery window
official status
incidentCodex Usage Limits Depleting Faster Than Expected6h 20m public recovery window
official status
incidentUsers may encounter issues using access token with Codex5h 12m public recovery window
official status
incidentCodex "Selected Model is at Capacity" Error3h 16m public recovery window
official status
incidentUsers may experience issue with Codex Cloud tasks49m public recovery window
official status
incidentElevated error rates for GPT 5.5 in Codex1h 28m public recovery window
official status
incidentIncreased latency for Codex compaction for a subset of users1h 40m public recovery window
official status
incidentElevated error rates on Codex, ChatGPT and Responses API1h 29m public recovery window
official status
incidentcodex-gpt-image-2-does-not-exist-errors38m public recovery window
official status
incidentCodex Context Compaction Latency13h 02m public recovery window
official status
incidentIncrease in users hitting Codex rate limits18h 21m public recovery window
official status
incidentCodex 5.5 engines are experiencing high error rate2h 02m public recovery window
official status
incidentUsers may experience elevated errors in ChatGPT uploading files and Codex Cloud creating tasks2h 01m public recovery window
official status
incidentDegraded Performance with Codex Cloud Tasks1h 10m public recovery window
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.
