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.
Cursor splits its status into six components — IDE, Cloud Agents, Automations, CLI, Bugbot and cursor.com. They fail independently, so read which one an incident names before assuming everything is down.
What Cursor's incident history actually looks like
Cursor's page is a busy one: 50 incidents across the 76 days to 13 August 2026, about four and a half a week. The median closed in 72 minutes, but the tail is long. One in ten ran past four hours and the worst stayed open just over thirteen.
The component spread shows where it actually hurts. Of those 50, the IDE was named in 36, Cloud Agents in 32, Automations in 25 and the CLI in 20. Bugbot and cursor.com trailed at nine each.
The popular explanation for a Cursor outage is that some upstream model provider fell over. The record only half supports it. Thirteen of the 50 named a model or a provider at all — Anthropic models, Grok 4.5, Composer — and the rest were Cursor's own backend. Switching models is still the cheapest thing to try, but on this evidence it addresses about a quarter of what goes wrong.
50 incidents, 30 May – 13 August 2026. Counted from status.cursor.com/api/v2/incidents.json, pulled . The live board at the
top of this page is current; these numbers are a snapshot and will drift.
Is Cursor down, or is it just you?
- The editor runs on your machine. A backend outage takes the AI features and leaves plain editing, git and the terminal alone, so if those are broken too, the problem is local.
- Agent requests failing while Tab completions still work, or the reverse, is a normal incident shape here rather than a broken install. Cursor tracks those surfaces separately because they break separately.
- A sign-in loop or a 401 is auth, not availability. Every Cursor component can be green while your session is dead.
- Cloud Agents and Automations run on Cursor's infrastructure rather than yours, so they can be down while the IDE in front of you behaves perfectly.
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.
How often does Cursor go down?
Cursor posted 50 incidents in the 76 days to 13 August 2026, roughly four and a half a week, with a median resolution of 72 minutes. The IDE component was involved in 36 of them, Cloud Agents in 32 and the CLI in 20. The long tail is the part that hurts: one in ten ran past four hours.
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.