Cursor outage, 12 November 2026
Elevated errors for some requests
- Started
- Resolved
- 12 Nov 2026, 21:39 UTC (after 1 h 31 min)
- Impact
- Major
- Affected
- cursor.com, Grok Bot
Is this still happening?
No. Cursor marked this incident resolved on 12 Nov 2026, 21:39 UTC, 1 h 31 min after it began.
Right now: Cursor reports all systems operational. (as of 13 Nov, 20:51 UTC) Live Cursor status
At a glance
- Cursor rated this a major incident (partial outage).
- It was resolved after 1 h 31 min. That is longer than a typical Cursor incident: the median of the 51 other resolved ones we recorded is 58 min.
- Cursor had 30 other incidents in the 30 days before it.
- 5 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 31 Oct 2026.
- Cursor has not posted a root cause analysis on its status page.
Our summary from the Cursor incidents we have recorded since 18 Sept 2026 - how we count.
Last update from Cursor
This incident has been resolved.
Similar Cursor incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 2 h 45 min
-
, resolved after 44 min
-
, resolved after 41 min
-
, resolved after 1 h 54 min
-
, resolved after 58 min
Other recent Cursor incidents
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.