Partial outageCursor ・ October 13, 2026
Grok Bot routines not triggering
A record of the Cursor incident on October 13, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
Started
Oct 13, 2026, 08:29 PM UTC
Resolved
Oct 13, 2026, 08:29 PM UTC
Duration
—
Impact
Partial outage
Other providers down at the same time
No other provider we monitor recorded an incident during this window. This appears to have been specific to Cursor.
Derived from our own archive of official status pages across 13 providers. Items lasting more than 24 hours and unresolved items are excluded, as they would misrepresent the moment.
Current status
Cursor is operating normally now. This incident has been resolved.
See current Cursor status →What you can do during an outage
Source: Cursor's official status page.
Other Cursor incidents
- Investigating service degradation — Grok BotOctober 14, 2026
- Degraded performance and errors across Cursor servicesOctober 13, 2026
- Investigating service degradation — Cloud Agents and Grok BotOctober 9, 2026
- Investigating service degradation — Cloud AgentsOctober 9, 2026
- Elevated errors affecting Opus 5.5October 8, 2026