Is Cursor down?
This page asks Cursor’s own status feed, straight from your browser, when you open it and once a minute while it stays open. It shows what Cursor reports and never fills in a gap with a guess.
Not checked
Checking needs JavaScript, which is off or has not loaded. Cursor’s own page has the answer: status.cursor.com.
What this checks
The editor, the helpers it runs in the cloud, and the Cursor command-line tool. On this page that means every part Cursor’s status page lists.
- The list appears after the live check.
Open incidents
Anything open appears here after the live check.
Recent incidents
Finished incidents from the last 30 days appear here after the live check.
If it is down
- Cursor lists its parts separately (the editor, its cloud agents, the command-line tool), so the list below shows which one is affected. If the editor opens but its AI features do not answer, that list is where to look.
- If Cursor reports no problems and it still fails, the cause is more likely on your side: your key, your code or your network. The error explainers cover the common messages.
- A status page shows what the company has reported. A problem that has started but has not been reported yet will not show here, so if the answer above is no and something still fails for everyone you know, check again in a few minutes.
- Do not rewrite working code to chase an outage. Commit what you have now, so that when the service is back you can tell whether anything you changed in the meantime broke something.
- Down? Save your place before you switch tools: Cold Handoff writes the note you paste into the next session, so it picks up where this one stopped instead of starting over.
Where this comes from
Your browser reads status.cursor.com/api/v2/summary.json and, once per visit, status.cursor.com/api/v2/incidents.json for the history.
The request goes straight to Cursor, without cookies, and does not pass through this site. The same feed drives the
Cursor row on the Vibe Board, which shows all 7 services at once.