Live / Cursor / Incident
Cursor: Degraded performance and errors across Cursor services
Cursor · cursor.comMinor incidentResolved2026-10-13 03:07 UTC
Public — what happened
Summary
Cursor said a widespread problem beginning at 00:22 UTC on 2026-10-13 caused errors and failed requests in its IDE, Cloud Agents, Automations, Grok Bot, and Origin. About half an hour later it reported that a fix was in place and services were recovering, though some users still saw intermittent errors. Cursor said Grok Bot was back to normal by 01:49 UTC and that everything except Cloud Agents had recovered by 02:23 UTC, with some Cloud Agents still slow to start or failing. The company marked the incident resolved at 03:07 UTC and did not state a cause in its updates.
Affected
Automations, Cloud Agents, CLI, cursor.com, IDE, Cursor IDE (iOS), Grok Bot, Origin, Review Agents
Timeline
- Started — 2026-10-13 00:22 UTC
- Investigating — 2026-10-13 00:22 UTC (5 updates)
- Resolved — 2026-10-13 03:07 UTC · 2h 45m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Cursor against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Cursor: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Cursor report →
More from Cursor
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.