Is OpenAI Codex down right now?

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 19d 8h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will 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 19d 8h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will 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.