Investigating service outage - Grok models unavailable
A record of the Cursor incident on October 23, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
3 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.
- AnthropicElevated errors for Claude Fable 5.1, Sonnet 5.5, and Haiku 5.5
- OpenAIDegraded experience with ChatGPT app connections using CIMD
- GitHubGrok 4.6 and Grok 4.7 Service Issues
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 41 minutes. Across 43 major incidents recorded for Cursor, the median duration is 80 minutes, making this the 31th longest.
Shorter 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
- 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
- Investigating service degradation — Grok BotOctober 19, 2026