Cursor outage on 13 October 2026
CriticalAn email when it goes down, and when it’s back.
“Degraded performance and errors across Cursor services”
On 13 October, Cursor had an outage from 00:23 to 03:08 UTC, lasting 2 h 45 min. Users saw errors and failed requests across the IDE, Cloud Agents, Automations, Grok Bot and Origin. The status page said a fix was in place by 00:53, and Grok Bot had recovered by 01:49. At 02:23 all services except Cloud Agents were reported as working normally, and Cloud Agents stayed slow or failing until the incident was resolved at 03:07. Patreon, Musixmatch, GitLab and Bus Times also reported problems during the same period.
Cursor’s own incident page ↗- When
- 00:23–03:08 UTC
- How long
- 2 h 45 min
- Incident open on its page
- 00:22–03:07 UTC
- Components affected
- 3
- Cursor, 30 days before
- 3 other outages
What broke when
From Cursor’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 108 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Cloud Agents: degraded performance
- IDE: degraded performance
- Grok Bot: degraded performance
- Fix in place, monitoring
- Resolved
- Cloud Agents: back to normal
- IDE: back to normal
- Grok Bot: back to normal
Where this comes from
Stackpulse reads Cursor’s official status page at status.cursor.com every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with Cursor. Names and logos belong to their owners.