Is Codex down, or is it just me?

A service incident, an account usage limit, or a sign-in, connection, or client problem can look similar. Start with the current official status and the exact error message. A green status alone cannot confirm that every account is working.

It is a general message, not a diagnosis. Check official incidents, then your account and connection. Note the exact error, time, and affected Codex surface if you need support; do not share credentials.

If Codex says you have reached your usage limit or tells you when you can try again, that is your plan’s allowance, not an outage. It refreshes on its own schedule. Connection errors, timeouts, or server errors while a service above shows a problem usually mean an outage.

Read the latest official update above. This page refreshes on its own and shows when each service is operational again. Incidents often affect specific surfaces, so another surface, such as the CLI instead of Codex Web, may still work.

Not automatically. OpenAI has sometimes reset Codex limits after a disruption and announced it publicly. The reset history lists past announcements with their sources.

OpenAI’s official status page. Codex Limits checks it every 5 minutes and keeps its own record of status changes, so uptime figures here are our observations, not OpenAI’s official numbers. Codex Limits is independent and not affiliated with OpenAI.