Is Cursor down?
How to check Cursor's status properly
Cursor incidents typically affect AI features (Agent, Tab, chat) while the editor keeps opening files fine — a "down" Cursor usually still edits text.
Cursor routes to multiple model providers, so an upstream model outage (Anthropic, OpenAI) can surface as Cursor errors while Cursor itself is green.
Is it down, or is it just you?
A 401 or 403 error is almost always your own auth — an expired token or a session that needs re-login, not an outage. A run of 5xx errors, or a 529 "overloaded" response, during an incident that's actually listed on the vendor's status page is on them, not you.
Before you conclude it's a real outage: try a second surface (the web app instead of the CLI, or vice versa), rule out your own network or VPN, and only then treat the vendor's official status page as the final word.
What to do while Cursor is down
- If agent requests fail, try switching the model — an upstream provider incident often affects one family only.
- Auto mode routes around some provider issues; manual model selection pins you to the affected provider.
- The editor itself is local — plain editing, git, and terminals keep working through any Cursor outage.
Frequently asked questions
How do I check if Cursor is down?
The live board above reads status.cursor.com's official API in your browser. If AI requests fail while the board shows green, the culprit is often the upstream model provider — check the Claude and OpenAI rows on our main status board.
Why does Cursor say "connection failed" on agent requests?
Agent requests need Cursor's backend plus the model provider. Either being degraded produces the error; the editor itself keeps working locally either way.