Skip to service list
IU

Is Cursor down?

Cursor status · AI & APIs · checked (5s ago)

Also searched as Cursor AI, Cursor IDE, Cursor editor.

Operational

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.72% of our checks.

No outage reported (30d)
99.72%
Share of our checks where Cursor's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
999 ms
How long the last status check took
Reported by
Operational
All Systems Operational

Is Cursor down for you right now?

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.

What Cursor is

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.

What Cursor's status feed covers

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.

Cursor uptime, last 30 days

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.

2026-10-0616 of 30 days recorded · lowest day 91.64%Today
  • No outage reported (99%+)
  • 95–99%
  • 80–95%
  • Under 80%
  • No data

Other services reporting problems right now

10 other services isuptime tracks were also reporting a problem as of the same check, 5s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.

2 more services are reporting problems — see all →

Cursor response time trend

Each point is one check of Cursor's status endpoint.

Cursor outage history

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.

Cursor status — frequently asked

Is Cursor down right now?
No — Cursor is not down. All Cursor systems are reported operational. Checked (5s ago).
What is Cursor's status right now?
Cursor is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 999 ms. isuptime reads this from Cursor's own published feed and does not test Cursor independently.
When did Cursor last go down?
The most recent incident Cursor published was “3 "Slow clones from GH due to Github degradation"”, opened Nov 3, 09:40 PM UTC (9h ago) and marked resolved Nov 3, 10:53 PM UTC. That is the latest entry in Cursor's own incident feed, not every problem users experienced.
What is Cursor's uptime?
isuptime does not measure Cursor's uptime directly — it reads Cursor's own published status feed. Over the last 30 days, Cursor's own status feed reported no outage in 99.72% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is Cursor down for everyone?
Cursor reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.

Cursor says operational but it is not working for me

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.

Open Cursor's official status page

Other AI & APIs services

← See live status for all 102 services