Live / Cursor / Incident
Cursor: Investigating service degradation — Grok Bot
Cursor · cursor.comMinor incidentResolved2026-10-19 17:21 UTC
Public — what happened
Summary
Cursor reported a minor service degradation affecting its Grok Bot, saying routines might be delayed. The company began investigating at 16:15 UTC on 2026-10-19 and did not name a cause in its updates. At 17:10 UTC it said a fix had been put in place and it was watching for service to recover, and at 17:21 UTC it marked the incident resolved.
Affected
Grok Bot
Timeline
- Started — 2026-10-19 16:15 UTC
- Investigating — 2026-10-19 16:15 UTC (3 updates)
- Resolved — 2026-10-19 17:21 UTC · 1h 07m 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.