Is Cursor Down?

No — Cursor is up

Reachable from all 8 checked regions

Average response time: 375ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://status.cursor.com

Cursor uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

356ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

55-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

bom

345ms

DNS 25ms TCP 1ms TLS 7ms TTFB 331ms

cdg

512ms

DNS 42ms TCP 9ms TLS 17ms TTFB 475ms

dfw

486ms

DNS 116ms TCP 0ms TLS 68ms TTFB 431ms

ewr

345ms

DNS 117ms TCP 1ms TLS 18ms TTFB 326ms

fra

299ms

DNS 78ms TCP 1ms TLS 9ms TTFB 228ms

gru

402ms

DNS 142ms TCP 2ms TLS 5ms TTFB 390ms

iad

213ms

DNS 73ms TCP 1ms TLS 7ms TTFB 190ms

jnb

404ms

DNS 91ms TCP 0ms TLS 40ms TTFB 365ms

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 18 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.
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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Cursor goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required