Cursor · 1h ago
Opus 5.5 is Experiencing 429s
ResolvedYes — Cursor had a problem on October 8, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 10/8/2026, 1:54:56 PM
Last update: 10/8/2026, 3:31:30 PM
Resolved: 10/8/2026, 3:31:29 PM
Affected: k0trcq273dr6, 2x2chyqwmkzl, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2, sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
10/8/2026, 3:31:29 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
10/8/2026, 2:08:09 PM
investigating
We are investigating a service degradation with Opus 5.5 being used across all product components.
10/8/2026, 1:54:57 PM
More Cursor incidents
- Investigating service degradation — Grok Bot — resolved, 1d ago
- Investigating service degradation — Cloud Agents — resolved, 2d ago
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 2d ago
- Investigating service degradation — Security Reviewer Agents — resolved, 2d ago
- Elevated errors affecting Anthropic models — resolved, 2d ago
- Investigating service degradation — Grok Bot and Review Agents — resolved, 5d ago