Live / Cursor / Incident
Cursor: Investigating service degradation — Grok Bot
Cursor · cursor.comMinor incidentResolved2026-10-14 21:04 UTC
Public — what happened
Summary
Cursor reported a minor service degradation involving its Grok Bot, which it said stopped some users from reaching their computers. The company began investigating at 15:46 UTC on 2026-10-14. At 20:08 UTC it said it had identified the issue affecting some users and was working on a fix, and at 21:04 UTC it marked the incident as resolved.
Affected
Grok Bot
Timeline
- Started — 2026-10-14 15:46 UTC
- Investigating — 2026-10-14 15:46 UTC (2 updates)
- Resolved — 2026-10-14 21:04 UTC · 5h 18m 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.