Is Cursor down? Grok model errors on October 15, fix implemented after 33 minutes
On October 15, 2026, Cursor reported elevated errors with Grok models starting at 22:25 UTC. Some requests failed with a capacity error in the CLI, Cloud Agents and IDE. Cursor implemented a fix at 22:58 UTC and was monitoring for service restoration. The incident was not yet marked resolved.
SessionWatcher editorial · Published · Updated · Source announcement: 2026-10-15
What happened
Cursor's status page reported elevated errors affecting Grok models in Cursor on October 15, 2026. Cursor said some requests may fail with a capacity error.
The incident lists three affected components: the CLI, Cloud Agents and the IDE. It covers Grok models only. Other models are not listed as affected.
Timeline
Cursor posted that it was investigating at 22:25 UTC. At 22:58 UTC, 33 minutes later, it said a fix had been implemented and it was monitoring for service restoration.
At the latest update the incident was still in monitoring and not marked resolved. The status page does not yet give an end time.
What you can do
Cursor says retrying the request or switching to another model may help. If a Grok request fails with a capacity error, try another model until the incident is resolved.
The status page does not say whether failed requests count toward usage. It also mentions no refunds or billing changes linked to this incident.
AI assisted reporting, checked against the linked official sources. Source pages checked 2026-10-15. Editorial process and corrections.