Live / Cursor / Incident
Cursor: Investigating service degradation
Cursor · cursor.comMinor incidentResolved2026-10-21 17:40 UTC
Public — what happened
Summary
Cursor reported a minor service degradation that began at 15:46 UTC on 2026-10-21 and affected its billing dashboards. The company said users might see errors involving billing, usage, and plan changes. About ten minutes later, at 15:56 UTC, Cursor said a fix had been put in place and it was watching for services to recover. It marked the incident resolved at 17:40 UTC and did not state a cause.
Affected
cursor.com, Grok Bot
Timeline
- Started — 2026-10-21 15:46 UTC
- Investigating — 2026-10-21 15:46 UTC (2 updates)
- Resolved — 2026-10-21 17:40 UTC · 1h 54m 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 44, 2026, our weekly internet health report.