Statuspy
AI Tools

Is Cursor down right now?

No, it’s up.

Cursor appears to be up and running normally.

checked responded in 134msHTTP 200

Over the last 7 days, Cursor has answered our automated checks with 100.00% availability and a typical response time of ~184 ms. According to Cursor's official status page, the most recent outage began 2026-08-04 23:34 UTC and lasted 27m (severity: down). It was reported as "Degraded performance for Cloud Agents".

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.

Response time (last 24h)
Last 24hpeak 2051 ms
Incident history (last 90 days)
JunJulAug
  • up
  • slow
  • down
  • no reading

50 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
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
Degraded Performance for Composer 2.5Reported by Cursor50mDegraded
Investigating service degradation — Composer 2.5Reported by Cursor51mDown
Elevated errors across many models on AnthropicReported by Cursor1h 41mDown
Investigating service degradation of the Auto modelReported by Cursor33mDegraded
Investigating service outageReported by Cursor37mDegraded
Investigating service degradation — Cloud AgentsReported by Cursor2h 25mDegraded
Investigating service degradation — Cloud AgentsReported by Cursor1h 47mDegraded
Degraded Performance for Agent SessionsReported by Cursor39mDown
Cloud Agents degradationReported by Cursor37mDown
Composer 2.5 Fast degradationReported by Cursor4h 33mDegraded
Degraded Performance for Composer 2Reported by Cursor14mDown
Investigating service degradation for Composer 2.5Reported by Cursor4mDegraded
Investigating Service Degradation in AI FeaturesReported by Cursor15mDegraded
Degraded user summarizations and Gemini 2.5 FlashReported by Cursor1hDegraded
Degraded Performance for Agent SessionsReported by Cursor4h 6mDegraded
Composer 2.5 Fast Service DegradationReported by Cursor1h 8mDegraded
Investigating service degradation of Composer 2.5 FastReported by Cursor40mDegraded
Uptime
100.00%
7 days
100.00%
30 days
100.00%
90 days
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
Is Cursor down right now?
Cursor appears to be up and running normally. Last checked 2026-08-05 06:59 UTC (2 minutes ago).
When was Cursor's last outage?
According to Cursor's official status page, the most recent outage began 2026-08-04 23:34 UTC and lasted 27m (severity: down). It was reported as "Degraded performance for Cloud Agents".
What should I do if Cursor is down for me?
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.
Cursor’s official status page

Related services