Live - 300+ check locations
Is OpenAI Codex down right now?
HostTracker's monitoring network reached chatgpt.com and completed a full check without errors. It has been up for 1d 9h.
Stop finding out from a search - HostTracker's website monitoring checks the services you depend on from 300+ locations and alerts you the moment one changes.
Up
for 1d 9h
- Last check
- just now
- Next check
- -
- HTTP
- OK
Checking chatgpt.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
Codex status
What OpenAI's status page reports about Codex - separate from HostTracker's own checks above. Codex is part of OpenAI, so the parts listed are all of OpenAI's.
Operational according to OpenAI's status page, updated just now
No open incidents on OpenAI's status page.
OpenAI parts
36 parts on its status page- Chat Completions
- Responses
- Agents
- Decisions
- Fine-tuning
- Embeddings
- Images
- Batch
- Audio
- Moderations
- Realtime
- Files
- Login
- Live
- Conversations
- ChatGPT Work
- Codex in ChatGPT Desktop
- Compliance API
- Search
- File uploads
- Voice mode
- GPTs
- Image Generation
- Deep Research
- Agent
- dots
- Space
- Sites
- Connectors/Apps
- Codex Web
- Codex API
- CLI
- VS Code extension
- FedRAMP
- Ads Manager
- Ads API
Last 90 days on OpenAI's status page
5 incidents: 5 minor.
- Degraded performance in ChatGPT, Codex, and APIs Minor impact 1h 2m
- Degraded performance in Codex and ChatGPT Work Minor impact 2h 47m
- Degraded performance in GPT-6.1 Sol Codex and Work mode Minor impact 8h 27m
- Degraded performance in Codex and Work mode: Dot turn failures, delayed responses, and reduced proactivity Minor impact 1h 2m
- Dot in Codex may fail to create new threads Minor impact 1h 35m
HostTracker is not affiliated with OpenAI. Incident text is quoted briefly from their status page, with a link to the full post.
Want this on Slack, Teams, SMS or email, only for the parts you use? See Vendor Watch below.
How OpenAI Codex has behaved
Every figure here comes from HostTracker's own checks of chatgpt.com, not from the vendor's status page.
Response time
675ms avg · 26487ms peak
What we check
-
HTTP655 ms average, every 10 minutesOK
-
Ping12 ms average, every 10 minutesOK
-
Page Speed1248 ms average, every 15 minutesOK
90-day uptime
99.968% · 7 incidents · 41 min in total · longest 30.4 min
- Operational
- Degraded
- Down
- No data
Incident history
Every outage of OpenAI CodexGet alerted the next time OpenAI Codex goes down
One alert per incident, on Slack, Teams, SMS or email, and only for the parts you use. To start, we pre-select Chat Completions, Responses and Embeddings.
- OpenAI's own post, linked and quoted
- Problem reports from people checking OpenAI on HostTracker
- Our own check of the OpenAI API
OpenAI Codex is part of OpenAI, so the watch is on OpenAI - you choose which of its parts to follow.
30-day trial, no card. OpenAI comes pre-selected - nothing is watched until you press Start watching.
Already have an account? Sign in
HostTracker is not affiliated with OpenAI.
Is OpenAI Codex not working for you?
Tell us what is broken. One click, no account.
One report per visitor per hour. We keep only the country and the problem type, never your IP address.
Problem reports, last 24 hours
Reports come from visitors of this page. A sharp rise above the usual level means many people hit a problem at once, even while our checks stay clear: those checks test the public site from outside and do not sign in.
Top reported problems
Share of reports in the last 2 hours.
About OpenAI Codex outages
Written by the HostTracker monitoring team · updated from live probe data.
Codex is OpenAI's coding agent, and it doesn't run as a separate standalone service: the version built into ChatGPT lives inside chatgpt.com, and the Codex CLI that runs from a terminal authenticates against and sends its requests through the OpenAI API. That means Codex doesn't fail on its own infrastructure so much as it inherits problems from whichever surface it's riding on at the time - a ChatGPT-wide issue affects the in-app agent, while an API-side issue affects the CLI. If a check here or on /en/is-chatgpt-down or /en/is-openai-down shows a problem, that's very likely Codex's problem too, since it has no independent backend of its own to fall back on.
Common causes of OpenAI Codex downtime
Not sure whether it's OpenAI Codex or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Task queue backlogs, where a coding task is accepted but sits waiting far longer than usual before Codex actually starts working on it
Sandbox or container start failures, where the isolated environment Codex runs a task in fails to provision, blocking the task before any code even executes
GitHub connection errors that break Codex's ability to read a repository, open a pull request, or push changes, independent of whether Codex itself is reachable
Model capacity constraints during high-demand periods, which slow or queue task completion the same way they would for any other product built on the same underlying models
CLI authentication failures, where a stale or expired login blocks the terminal client from reaching the API even though the API itself is healthy
Other services we track
AWSOperational
G
InstagramOperational
X
AmazonOperational
T
ShopifyOperational
DHostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests chatgpt.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than OpenAI Codex being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
No - as of the most recent check, chatgpt.com is responding normally to HostTracker's monitoring network, and has been up for 1d 9h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is usually local - your network, DNS cache, or a regional route - or a problem behind the sign-in, which a check from outside cannot see. The live probe results above show which locations, if any, are affected.
No - as of the most recent check, chatgpt.com is responding normally to HostTracker's monitoring network, and has been up for 1d 9h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is usually local - your network, DNS cache, or a regional route - or a problem behind the sign-in, which a check from outside cannot see. The live probe results above show which locations, if any, are affected.
It can be, though a queue backlog is a narrower symptom than a full outage. Codex tasks go through a processing queue before they actually start running, and a backlog there delays a task's start without necessarily meaning the underlying service is unreachable. If tasks eventually start and complete, just slowly, that points at a temporary capacity crunch; if they never start at all, checking chatgpt.com and the OpenAI API's status separately narrows down which layer is actually failing.
Usually not. A CLI authentication failure most often comes from a stale or expired login rather than the OpenAI API being unreachable, since the CLI needs a valid session to send requests through the API in the first place. Signing out and back in through the CLI resolves most of these. If sign-in fails for many people at once and the API check on /en/is-openai-down also shows a problem, that points at a genuine authentication-service incident instead.
That's typically a GitHub connection problem rather than a Codex or OpenAI issue. Codex needs to reach GitHub separately from generating the code itself, so a connection error, a permissions problem, or an incident on GitHub's side can block the final step - opening a PR, pushing a branch - after the actual coding work has already completed successfully. Checking GitHub's own reachability alongside this page is worth doing when the failure looks specific to the repository step.