Is Cursor Down?
Reachable from all 8 checked regions
Average response time: 332ms
Last checked · checks run every 6 hours
Official status page: https://status.cursor.com
Investigating service degradation
A fix has been implemented and we are monitoring for service restoration.
A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Cursor fail from enough regions to rule out probe noise.
Cursor uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
21-day clean streakReachability 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.
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 all 18 regions to find out where it breaks.
Related services
Cursor outage FAQ
Is Cursor down or is my model provider rate limiting me?
Can I keep coding while Cursor's AI features are down?
What happens if an agent stops halfway through editing files?
Do Cursor outages affect the CLI and cloud agents separately?
Is my code sent anywhere when Cursor is down?
How we measure this
- We request Cursor's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
- A region counts as down only when it gets no usable HTTP response. A
403or429means 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 the same 18 regions, and tell you the moment something breaks.
Start Free Monitoring