Loading status…
Cursor status · AI & APIs · checked (1m ago)
Also searched as Cursor AI, Cursor IDE, Cursor editor.
No — Cursor is not down. All Cursor systems are reported operational.
According to Cursor's official status page, Cursor was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Cursor's feed reported no outage in 99.05% of our checks.
Everything above is read from Cursor's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Cursor in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Cursor is a code editor built on VS Code with model-backed editing at its centre — tab completion, inline edits, the chat sidebar and the background agent all call out to hosted models rather than running locally. That matters for outages: the editor keeps working when Cursor's servers do not, but every feature people actually pay for stops.
Cursor's status page separates the model-backed features from the account and licensing systems, and it is the licensing side that produces the most visible failures — an authentication problem locks people out of Pro features while completions would otherwise be fine. Model capacity problems are usually posted as degraded rather than an outage, because a subset of models stays available.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Cursor's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Cursor was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Cursor's status endpoint.
Cursor has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Cursor posted itself — not every problem users hit.
resolved · Sep 18, 11:02 PM (1d ago)
resolved · Sep 18, 05:19 PM (1d ago)
resolved · Sep 18, 11:37 AM (1d ago)
resolved · Sep 17, 03:20 PM (2d ago)
resolved · Sep 17, 12:30 PM (2d ago)
resolved · Sep 16, 02:27 PM (3d ago)
resolved · Sep 16, 08:03 AM (3d ago)
resolved · Sep 15, 09:26 PM (4d ago)
resolved · Sep 14, 08:14 AM (5d ago)
resolved · Sep 11, 11:08 AM (8d ago)
resolved · Sep 10, 05:07 PM (9d ago)
resolved · Sep 7, 08:32 PM (12d ago)
resolved · Sep 7, 01:08 PM (12d ago)
resolved · Sep 3, 11:42 PM (16d ago)
resolved · Sep 3, 05:42 PM (16d ago)
resolved · Sep 3, 03:17 PM (16d ago)
resolved · Sep 3, 02:17 PM (16d ago)
resolved · Sep 3, 01:41 PM (16d ago)
resolved · Sep 2, 02:50 PM (17d ago)
resolved · Sep 2, 12:48 AM (18d ago)
Cursor calls through to upstream providers, so a completion failure can be Anthropic's or OpenAI's rather than Cursor's — check those pages too. Hitting your monthly fast-request quota looks identical to an outage from inside the editor and is not one. If tab completion dies but chat works, the two use different backends; restarting the editor genuinely does clear a stuck connection more often than it should.
