Opus 5.5 is Experiencing 429s
DegradedOngoing · started Oct 8, 2026, 1:54 PM UTC (1h ago)
Wondering “is Cursor down?” — yes: Anysphere confirms an ongoing incident (“Opus 5.5 is Experiencing 429s”, started Oct 8, 2026, 1:54 PM UTC). Live timeline below. This incident affects Cursor — see live Cursor status. Source: official vendor status feed.
Timeline
Oct 8, 2026, 2:08 PM UTC
A fix has been implemented and we are monitoring for service restoration.
Oct 8, 2026, 1:54 PM UTC
We are investigating a service degradation with Opus 5.5 being used across all product components.
More Cursor outages
- Investigating service degradation — Grok BotOct 7, 2026, 3:59 PM UTC · resolvedDegraded
- Investigating service degradation — Cloud AgentsOct 6, 2026, 10:48 PM UTC · resolvedPartial outage
- Investigating service degradation — Cloud Agents and Grok BotOct 6, 2026, 7:27 PM UTC · resolvedPartial outage
- Investigating service degradation — Security Reviewer AgentsOct 6, 2026, 5:49 PM UTC · resolvedPartial outage
- Elevated errors affecting Anthropic modelsOct 6, 2026, 12:40 PM UTC · resolvedDegraded
- Investigating service degradation — Grok Bot and Review AgentsOct 3, 2026, 6:50 AM UTC · resolvedDegraded