Investigating service degradation - xAI models
A record of the Cursor incident on September 29, 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.
- ElevenLabsAgents, STT, and Creative Platform: Increased Latency, Conversation Failures, and STT Failures
- OpenAIElevated errors across ChatGPT, Codex, and the API including the Agents API
- RunwayWe've identified a problem and are working on a fix
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 35 minutes. Across 39 major incidents recorded for Cursor, the median duration is 80 minutes, making this the 30th 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
- Investigating service degradation — Cloud Agents and Grok BotSeptember 29, 2026
- Investigating service degradation — Grok BotSeptember 28, 2026
- Investigating service degradation — Grok BotSeptember 25, 2026
- Investigating service degradation — Grok BotSeptember 25, 2026
- Investigating service degradation - Grok 4.7September 23, 2026