Investigating service degradation — Composer 2.5
A record of the Cursor incident on June 17, 2026 (Japan time): start time, duration and severity, plus current status, what to do, and alternatives.
Other providers down at the same time
1 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 Opus 4.8
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 52 minutes. Across 34 major incidents recorded for Cursor, the median duration is 76 minutes, making this the 23th 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
- Grok Bot computers unreachable for some usersSeptember 8, 2026
- Investigating service degradation — CLI, Cloud Agents, and IDESeptember 7, 2026
- Degraded performance for Grok Bot routine triggersSeptember 4, 2026
- Degraded performance of Grok 4.6September 4, 2026
- Elevated errors for OpenAI ModelsSeptember 4, 2026