Statuspy
AI Tools

Is Cursor down right now?

No, it’s up.

Cursor appears to be up and running normally.

checked responded in 101msHTTP 200

Over the last 7 days, Cursor has answered our automated checks with 100.00% availability and a typical response time of ~132 ms. According to Cursor's official status page, the most recent outage began 2026-08-27 19:31 UTC and lasted 7m (severity: down). It was reported as "Investigating service degradation — cursor.com and IDE".

Cursor is an AI-powered code editor built on VS Code, combining a familiar editing experience with inline completions, chat over your codebase, and agentic multi-file edits. Because the AI features run against Cursor's servers rather than locally, an outage usually shows up as completions timing out, Composer requests hanging, or chat returning an error while the editor itself keeps working normally.

Is Cursor down for everyone or just you?

Our automated checks are reaching Cursor normally right now, and it answered our last one in 101ms. That makes any trouble you are hitting more likely to be local to your connection, account or network than a full outage, which usually means you can fix it from your end.

Still not working for you?Try the fixes

Cursor response time (last 24h)

Last 24hpeak 762 ms

Cursor incident history (last 90 days)

JulAugSep
  • up
  • slow
  • down
  • no reading
All 38 recorded outages

38 of the incidents below were reported by Cursor on days we were not yet monitoring, so the timeline above leaves those days hatched rather than colouring them in.

DateWhat happenedDurationSeverity
Investigating service degradation — cursor.com and IDEReported by Cursor7mDown
Investigating service degradation — Grok BotReported by Cursor42mDegraded
Degraded performance of Grok modelsReported by Cursor53mDegraded
Degraded performance of Grok 4.6Reported by Cursor2h 42mDegraded
Investigating service degradation — AutomationsReported by Cursor29mDegraded
Elevated errors for Claude Opus 5Reported by Cursor3h 12mDegraded
Investigating service degradationReported by Cursor47mDegraded
Fable 5 unavailableReported by Cursor2h 41mDown
Increased error rates for Composer 2.5Reported by Cursor3h 2mDegraded
GitHub-connected Cloud Agent workflows degradedReported by Cursor6h 56mDegraded
Grok Bot connector delaysReported by Cursor1h 29mDegraded
Investigating service degradationReported by Cursor1h 7mDown
Investigating service degradationReported by Cursor1h 7mDegraded
Grok 4.6 availability issuesReported by Cursor1h 6mDegraded
GitHub degradation affecting some Cursor services — Automations, Cloud Agents, CodebaseReported by Cursor6h 6mDown
Investigating service degradationReported by Cursor4h 8mDegraded
Investigating service degradation — Automations, Cloud Agents, and IDEReported by Cursor4h 3mDown
Investigating service degradationReported by Cursor20mDegraded
Investigating service degradation — Automations, Cloud Agents, and IDEReported by Cursor2h 32mDegraded
Investigating service degradation — Automations, Cloud Agents, and IDEReported by Cursor6h 16mDegraded
MCP authentication failures in Automations and Cloud AgentsReported by Cursor2h 56mDegraded
Degraded Performance for Grok 4.5Reported by Cursor28mDegraded
Investigating service degradation — Cloud Agents & AutomationsReported by Cursor2h 20mDegraded
Investigating service degradationReported by Cursor6h 34mDegraded
Degraded performance for Cloud AgentsReported by Cursor27mDown
Investigating service degradationReported by Cursor1h 19mDown
Investigating service degradation — IDEReported by Cursor51mDegraded
Investigating service degradation — IDEReported by Cursor17mDegraded
Elevated errors affecting Anthropic modelsReported by Cursor3h 17mDown
Investigating Composer degradationReported by Cursor2h 47mDegraded
Investigating service degradation — cursor.com, Automations, and Cloud AgentsReported by Cursor4mDegraded
Investigating service degradation — IDEReported by Cursor1h 11mDegraded
Investigating Elevated Cursor Grok 4.5 ErrorsReported by Cursor10mDegraded
Investigating service degradation — Cloud AgentsReported by Cursor2h 29mDegraded
Investigating service degradation — IDEReported by Cursor50sDegraded
Investigating service degradation — IDEReported by Cursor1mDegraded
We're Investigating an issue with requests to Fable causing degraded behaviourReported by Cursor40mDegraded
Anthropic elevated errorsReported by Cursor3hDegraded
Investigating service degradationReported by Cursor9h 29mDegraded
Investigating service degradationReported by Cursor18mDegraded
Investigating Anthropic degradationReported by Cursor5h 10mDegraded
Investigating service degradation — Cloud AgentsReported by Cursor1h 42mDegraded
Authentication System degradationReported by Cursor2h 14mDown
Investigating Grok 4.5 degradationReported by Cursor2h 35mDown
Investigating GPT-5.6 Sol degradationReported by Cursor44mDegraded
Investigating service degradation — Cloud AgentsReported by Cursor1h 9mDegraded
Investigating service degradationReported by Cursor2h 40mDown
Investigating service degradation - SolReported by Cursor15mDegraded
Investigating service degradationReported by Cursor13h 19mDegraded
Investigating service degradationReported by Cursor17mDegraded
Investigating service degradationReported by Cursor0sDegraded
Degraded Performance for AutoReported by Cursor5mDown
Incorrect Usage Amount on DashboardReported by Cursor30mDegraded
Degraded Performance for Anthropic ModelsReported by Cursor1h 12mDown
Investigating service degradationReported by Cursor1h 32mDegraded
Elevated errors across Anthropic modelsReported by Cursor2h 20mDegraded
Investigating service degradation — AutomationsReported by Cursor9mDown

Cursor uptime

100.00%
7 days
100.00%
30 days
100.00%
90 days

Measured since 2026-08-12. Windows reaching further back are averaged over the 39 days we watched, not the full period. Counts our own checks. Days Cursor reported an incident are coloured in the timeline above but do not change this figure.

What to do if Cursor is down for just you

  • Check the indexing status in the bottom bar — a stalled codebase index makes Cursor feel broken while the editor itself is fine.
  • Open Settings → Models and try a different model; a single upstream provider can be failing while the rest work.
  • If completions stall but the editor responds, sign out and back in — an expired session breaks the AI features before it breaks the UI.
  • Cursor is a VS Code fork, so disabling recently installed extensions rules out a conflict rather than an outage.

Frequently asked questions

Cursor appears to be up and running normally. Last checked 2026-09-19 05:06 UTC.

Cursor’s official status page

Related services