Live / Cursor / Incident
Cursor: Delayed responses in Grok Bot
Cursor · cursor.comMajor incidentResolved2026-10-27 20:43 UTC
Public — what happened
Summary
Cursor reported a major incident in which some replies from its Grok Bot were slow to arrive. The company said it began looking into the problem at 20:33 UTC on 2026-10-27 and did not name a cause. By 20:43 UTC Cursor said the issue was resolved, that responses were back to normal, and that the delays had lasted only a short time. It also apologized for the disruption.
Affected
Grok Bot
Timeline
- Started — 2026-10-27 20:33 UTC
- Investigating — 2026-10-27 20:33 UTC
- Resolved — 2026-10-27 20:43 UTC · 10 min 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.