Is Cursor Down?

No — Cursor is up

Cursor's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 301 ms

Right now

The verdict is the worse of these two. How we decide

Cursor's status page

status.cursor.com · read 4 minutes ago · checked every 3 minutes

Operational

Cursor's components, as its status page reports them
Component	Status
IDE	Operational
Cursor IDE (iOS)	Operational
CLI	Operational
cursor.com the service itself	Operational
Cloud Agents	Operational
Automations	Operational
Bugbot	Operational
Grok Bot	Operational
Third-party models	Operational
Origin	Operational
Enterprise Dashboard	Operational

Open their status page

FlareWarden checks

cursor.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 301 ms
Checked: 3 hours ago

By region

Amsterdam reachable, 214 ms
Dallas reachable, 411 ms
Frankfurt reachable, 208 ms
Newark reachable, 338 ms
Paris reachable, 246 ms
Stockholm reachable, 298 ms
São Paulo reachable, 278 ms
Toronto reachable, 416 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	27 ms	6 ms	19 ms	184 ms
Dallas	46 ms	0 ms	52 ms	356 ms
Frankfurt	103 ms	3 ms	7 ms	193 ms
Newark	43 ms	10 ms	12 ms	297 ms
Paris	42 ms	9 ms	15 ms	195 ms
Stockholm	27 ms	1 ms	9 ms	283 ms
São Paulo	148 ms	14 ms	5 ms	268 ms
Toronto	75 ms	18 ms	21 ms	341 ms

We check that cursor.com loads, not every feature behind it. Test it yourself

History

Incidents Cursor reported

Since Oct 22, 15 days · from status.cursor.com

Incidents: 19
Major or critical: 3
Median to resolve: 1h 16m

composer-2.5 degraded
minor · Nov 5
lasted 50m
Degraded Performance - Grok Bot
minor · Nov 5
lasted 1h 16m
3 "Slow clones from GH due to Github degradation"
Unrated · Nov 3
lasted 1h 13m
Issues with source control integrations
minor · Nov 2
lasted 1h 18m
Service Degradation - Billing and Usage Dashboard
minor · Nov 1
lasted 5h 15m
Multiple services degraded
minor · Oct 31
lasted 44m
Auto Review Degradation
minor · Oct 29
lasted 1h 36m
Cloud Agent Degradation
minor · Oct 29
lasted 7h 43m

And 11 more in this window. Full history on their status page

Cursor website availability

Measured by FlareWarden · cursor.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 396ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of cursor.com from multiple regions every 6 hours. Cursor's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Cursor does

Cursor is a code editor built around AI assistance, offering inline completion, chat over a codebase and agents that make multi-file edits. The editor runs locally but the model calls do not, so an outage leaves developers with a working editor whose assistance has quietly stopped rather than with no tool at all.

What an outage looks like

Completions stop appearing as you type, with no error to explain the silence. Chat requests hang on a spinner or return a generic failure after a long wait. Agent runs stall partway through a multi-file edit, leaving some files changed and others untouched. Sign-in fails on a fresh install, and cloud agents queue without ever starting.

What to do about it

Check status.cursor.com, which lists the IDE, Cloud Agents, the CLI, Bugbot, Automations and cursor.com as separate components, so a failing agent does not mean the editor itself is affected. Local editing, search and version control keep working throughout. If an agent stopped mid-edit, review the diff before rerunning it rather than starting a second pass over partly changed files.

Is it down for everyone, or just you?

If this page says Cursor is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Cursor outage FAQ

Is Cursor down or is my model provider rate limiting me?

Rate limits return an explicit message naming the limit or quota, while an outage gives timeouts or generic failures. status.cursor.com separates the IDE from Cloud Agents, so check which component is affected. If everything is green and only your account is failing, usage limits or a billing problem are the more likely explanation than a platform incident.

Can I keep coding while Cursor's AI features are down?

Yes. The editor runs locally, so files, search, extensions, terminals and version control all work normally. You lose completions, chat and agents rather than the ability to write code. This is worth remembering before restarting or reinstalling: the failure is on the service side, and reinstalling the editor changes nothing about it.

What happens if an agent stops halfway through editing files?

You are left with a partial change set, which is the genuinely risky outcome of a Cursor incident. Review the diff before doing anything else, and either commit the coherent part or revert it. Rerunning the agent over half-edited files tends to compound the mess, since it now reasons about a codebase in a state you did not intend.

Do Cursor outages affect the CLI and cloud agents separately?

Yes, they are listed as distinct components. Cloud Agents run on Cursor's infrastructure and fail when that is degraded, while the local IDE may keep working with reduced features. The CLI is tracked separately again. Matching your failure to the right component saves debugging a local setup that was never the problem.

Is my code sent anywhere when Cursor is down?

An outage does not change what the product does with your code; it means requests are not completing. If a request fails, the assistance simply does not arrive. Questions about what is transmitted during normal operation are answered by Cursor's own privacy settings and documentation rather than by the status page, and are worth reviewing separately.

How we measure this

We request Cursor's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Cursor publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Cursor itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Cursor goes down

We check Cursor every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required