LATEST CODEX INCIDENT
ChatGPT Work and Dots Errors
ResolvedFirst reported 14 days ago (14 days 22 hours); 2026-11-05 15:25:03 UTC
Affected: Codex Web
Component impact window: 0 hours
Read the official incident ↗Codex RescueService status
Start with the official report. Then decide whether to wait or troubleshoot your own setup.
LATEST CODEX INCIDENT
First reported 14 days ago (14 days 22 hours); 2026-11-05 15:25:03 UTC
Affected: Codex Web
Component impact window: 0 hours
Read the official incident ↗Tracking since 2026-07-01 03:38:18 UTC · Longest observed streak 17 days
First report: 2026-11-05 15:25:03 UTC · Marked resolved: 2026-11-06 04:31:37 UTC
First report: 2026-10-21 22:36:29 UTC · Marked resolved: 2026-10-20 17:35:00 UTC
This is OpenAI’s public component report, not a test of your account. A healthy public report cannot prove that your own session works. Some historical component attribution is still being backfilled, and report timestamps may differ from the actual start or end of an outage.
Snapshots are checked hourly. Refreshing this page does not force an upstream check.
An incident can explain failures affecting several users. An operational report does not prove your account, network or session is working: reports can lag, and local problems may never appear here.
Follow the outage-versus-local-error checklist →
We read OpenAI’s public component feed and incident feed hourly. We also check incident details for component impacts, including events whose titles do not name Codex. Failed checks retry no more often than every 15 minutes. Successful records are retained in our database; this page shows records first reported within the past 30 days and any unresolved records. The incident card calculates days since the official first-report time in your browser; the last-updated timestamp below refers to the most recent successful source check, not a new incident.
Missing or stale component data is shown as unknown. Reporting timestamps are not necessarily a measurement of the actual outage duration. We do not calculate an uptime percentage from them.
Need to distinguish an incident from an allowance refresh? Compare the public reset signals for today with the personal reset guide. The six reset scenarios are listed there; none can read your private account.
Usually these require separate checks. A message saying you reached a usage limit concerns your allowance; use your account’s usage view. Public service status cannot read your balance or reset time.