Cursor outage on 29 September 2026
Major outageAn email when it goes down, and when it’s back.
“Investigating service degradation - xAI models”
On 29 September, Cursor had a major outage from 19:43 to 20:18 UTC (35 minutes), affecting xAI models across its CLI, Cloud Agents, IDE and Grok Bot. The status page said users might see errors, slow responses or rate limiting on these models, and that some Agent and Cloud Agent requests could fail. It also said the cause had been identified, but did not say what it was. ElevenLabs, Bluesky, Daxko and Affirm also reported problems around the same time.
Cursor’s own incident page ↗- When
- 19:43–20:18 UTC
- How long
- 35 min
- Incident open on its page
- 19:43–20:18 UTC
- Components affected
- 4
- Cursor, 30 days before
- No 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 64 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- CLI: partial outage
- Cloud Agents: partial outage
- IDE: partial outage
- Grok Bot: partial outage
- Cause identified
- Resolved
- CLI: back to normal
- Cloud Agents: 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.