Is Cursor down? October 13 outage resolved after 2 hours 45 minutes
Cursor reported errors and failed requests across its services on October 13, 2026. Its status timeline runs from 00:22 to 03:07 UTC. The IDE and CLI were affected, while Cloud Agents still had problems after other services recovered.
SessionWatcher editorial · Published · Updated · Source announcement: 2026-10-13
Cursor's October 13 outage is resolved
Cursor's status page reported a widespread incident on October 13, 2026, with errors or failed requests across its services. The first investigating notice was posted at 00:22 UTC, and Cursor marked the incident resolved at 03:07 UTC, a timeline of 2 hours 45 minutes.
The affected components were IDE, CLI, Cloud Agents, Automations, Review Agents, cursor.com, Origin and Grok Bot.
Sources: Investigating service degradation - Grok Bot, IDE, and Cloud Agents
Cloud Agents recovered later than other services
At 00:53 UTC, Cursor said a fix had been implemented and services were recovering, although intermittent errors remained possible. Grok Bot was reported recovered at 01:49 UTC.
At 02:23 UTC, Cursor said all services except Cloud Agents were operating normally. Some Cloud Agents could still be slow to start or fail to run. The final 03:07 UTC notice confirmed resolution. The incident report does not state any usage reset, refund or billing adjustment.
Sources: Investigating service degradation - Grok Bot, IDE, and Cloud Agents
AI assisted reporting, checked against the linked official sources. Source pages checked 2026-10-13. Editorial process and corrections.