Live / Cursor / Incident
Cursor: Elevated errors affecting Grok models
Cursor · cursor.comMinor incidentResolved2026-10-16 05:20 UTC
Public — what happened
Summary
Cursor said it began looking into a higher-than-normal rate of errors affecting Grok models on October 15, 2026 at 22:25 UTC. It reported that some requests could fail with a capacity error, and suggested trying again or choosing a different model. About half an hour later, at 22:58 UTC, Cursor said a fix was in place and it was watching to confirm service came back. At 05:20 UTC on October 16, it marked the incident resolved and said Grok models were working normally again; it did not state a cause.
Affected
Cloud Agents, CLI, IDE, Cursor IDE (iOS)
Timeline
- Started — 2026-10-15 22:25 UTC
- Investigating — 2026-10-15 22:25 UTC (2 updates)
- Resolved — 2026-10-16 05:20 UTC · 6h 56m 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.