Cursor outage on 23 October 2026
Major outageAn email when it goes down, and when it’s back.
“Investigating service outage - Grok models unavailable”
On 23 October, Cursor had a major outage that left Grok models unavailable from 23:40 to 00:21 UTC, about 41 minutes. The status page listed Automations, CLI, Cloud Agents, cursor.com, IDE and Grok Bot as affected. Its updates said a fix was in place and Grok models were recovering by 23:50, though the incident stayed open until 00:20. Other services, including Claude, GitHub, Asana and OpenAI, reported problems around the same time.
Cursor’s own incident page ↗- When
- 23:40–00:21 UTC
- How long
- 41 min
- Incident open on its page
- 23:39–00:20 UTC
- Components affected
- 6
- Cursor, 30 days before
- 4 other outages
What broke when
From Cursor’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 60 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Automations: partial outage
- CLI: partial outage
- Cloud Agents: partial outage
- cursor.com: partial outage
- IDE: partial outage
- Grok Bot: partial outage
- Fix in place, monitoring
- Resolved
- Automations: back to normal
- CLI: back to normal
- Cloud Agents: back to normal
- cursor.com: back to normal
- IDE: back to normal
- Grok Bot: back to normal
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.