Live / Cursor / Incident
Cursor: Multiple services degraded
Cursor · cursor.comMajor incidentResolved2026-10-28 23:13 UTC
Public — what happened
Summary
Cursor reported a major incident beginning at 21:15 UTC on 2026-10-28 in which users could hit failures across several of its services. At first it listed Cloud Agents, Grok Bot and Origin, and by 21:39 UTC it had added Automations and Bugbot. Cursor said a fix was in place by 22:06 UTC and services began recovering, and it kept monitoring afterward. It declared the incident resolved at 23:13 UTC, saying all services were back to normal; it did not state a cause.
Affected
Automations, Review Agents, Cloud Agents, Grok Bot, Origin
Timeline
- Started — 2026-10-28 21:15 UTC
- Investigating — 2026-10-28 21:15 UTC (3 updates)
- Investigating — 2026-10-28 22:42 UTC
- Resolved — 2026-10-28 23:13 UTC · 1h 58m 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 45, 2026, our weekly internet health report.