Codex status
Build-time snapshot of OpenAI's own status feed, filtered to Codex-related components (names containing “Codex”, plus CLI and the VS Code extension). See status.openai.com for the live page.
Overall indicator
As of .
none All Systems Operational
- Codex Weboperational
- Codex in ChatGPT Desktopoperational
- Codex APIoperational
- VS Code extensionoperational
- CLIoperational
Incident ledger
Everything the collector has seen in the last 90 days.
Elevated Error Rates for ChatGPT Work, across Plus, Pro, Business, Enterprise and Education plans.
Increased error rate for Plus and Pro users.
SSO sign-in and SCIM provisioning issues
Overbilling for OpenAI-hosted containers in the Agent API
Delayed support responses
We are seeing elevated error rates across API models
Elevated errors affecting ChatGPT Work mode
Elevated errors in ChatGPT Work
Elevated errors with gpt-image-2.5-flare
Ads Manager login issues
Elevated errors from GPT-5.6 and GPT-5.6 Instant on paid plans
Degraded Performance affecting Agents API
Elevated errors affecting Work Mode in ChatGPT
Elevated error rates for Codex and ChatGPT Work
Elevated errors for ChatGPT users in Europe
Codex GitHub Review and Pull Request Failures
1% of ChatGPT Work (mobile/web) turns are failing for existing threads
Elevated errors for GPT-5.6 Sol on the API
Elevated errors for ChatGPT users in Europe
Delays in customer support responses
Elevated errors affecting ChatGPT Work
Unable to open shared ChatGPT Project using direct link
Investigating unexpected usage limit resets
Increased Error Rate For Pro and Plus Plan Conversations
File uploads are delayed or failing
Resets near an incident
Timing only — not evidence of cause.
No recent recorded reset had a Codex-related incident within the prior 48 hours.
Frequently asked questions
Is Codex down right now?
See the indicator above — it's OpenAI's own status feed, checked at build time. For the live page, see status.openai.com directly.
Does a status incident mean a reset is coming?
Not necessarily — the incident ledger below only shows timing, never a causal claim. See /forecast-method/ for how (if at all) status incidents feed into the probability numbers.