Investigating service degradation — Grok Bot
A record of the Cursor incident on September 16, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
2 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.
- GitHubDegradation with Gemini 3.8 Flash
- OpenAIElevated errors in ChatGPT Work
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 390 minutes. Across 45 major incidents recorded for Cursor, the median duration is 80 minutes, making this the 1th 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
- Service Degradation - Billing and Usage DashboardNovember 1, 2026
- Multiple services degradedOctober 31, 2026
- Auto Review DegradationOctober 29, 2026
- Cloud Agent DegradationOctober 29, 2026
- Investigating Service Degradation with VS Code ExtensionsOctober 29, 2026