Cursor outage on 12 November 2026
Major outageAn email when it goes down, and when it’s back.
“Elevated errors for some requests”
On 12 November, Cursor had a major outage in which some requests failed, including purchases and other billing actions, from 20:08 to 21:39 UTC (1 h 31 min). According to the status page, a fix was in place by 20:43, and the incident stayed in monitoring until it was marked resolved at 21:39. Zoom, Salesforce Spiff, Microsoft 365 (consumer), GitHub, Lever, Notion, Musixmatch and Supabase also reported problems around the same time.
Cursor’s own incident page ↗- When
- 20:08–21:39 UTC
- How long
- 1 h 31 min
- Incident open on its page
- 20:08–21:39 UTC
- Cursor, 30 days before
- 1 other outage
At the same time
Started in the hour before or during it
And 200 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Fix in place, monitoring
- Resolved
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.