Multiple services degraded
A record of the Cursor incident on October 28, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
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.
How big was this outage?
This outage lasted 118 minutes. Across 45 major incidents recorded for Cursor, the median duration is 80 minutes, making this the 18th longest.
Longer than a typical outage.
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
- Degraded performance — Origin and Cloud AgentsOctober 29, 2026
- Delayed responses in Grok BotOctober 27, 2026
- Elevated errors affecting repository integrationsOctober 27, 2026
- Payment System Sync IssuesOctober 27, 2026
- Degraded agent personalization and codebase syncOctober 26, 2026