Investigating Cloud Agent Degradation
A record of the Cursor incident on May 13, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
1 other incident(s) at different providers overlapped with this one. It may not have been limited to a single service — several providers were degraded at once.
- ElevenLabsEU Residency: Elevated Error Rates for STT API Calls that use the source_url Parameter
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.
How big was this outage?
This outage lasted 80 minutes. Across 43 major incidents recorded for Cursor, the median duration is 80 minutes, making this the 22th longest.
About average in length.
Only incidents recorded as major-or-worse and already resolved are counted.
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 outage - Grok models unavailableOctober 23, 2026
- Elevated errors for Bitbucket Cloud integrationsOctober 21, 2026
- Investigating service degradationOctober 21, 2026
- Investigating service degradationOctober 21, 2026
- Investigating service degradation — Grok BotOctober 19, 2026