Live / Cursor / Incident
Cursor: Investigating service degradation — Grok Bot
Cursor · cursor.comMinor incidentResolved2026-10-07 17:25 UTC
Public — what happened
Summary
Cursor reported a minor service degradation involving Grok Bot's computers in some regions, beginning at 15:59 UTC on October 7, 2026. The company said it was looking into the problem but did not share a cause or say which users were affected. Cursor marked the incident as resolved at 17:25 UTC the same day.
Affected
Grok Bot
Timeline
- Started — 2026-10-07 15:59 UTC
- Investigating — 2026-10-07 15:59 UTC
- Resolved — 2026-10-07 17:25 UTC · 1h 26m 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 42, 2026, our weekly internet health report.