Cursor · 50d ago
Increased error rates for Composer 2.5
ResolvedYes — Cursor had a problem on August 19, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 8/19/2026, 12:52:32 PM
Last update: 8/19/2026, 3:54:55 PM
Resolved: 8/19/2026, 3:54:55 PM
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, jh0714rgjgt4, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
8/19/2026, 3:54:55 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
8/19/2026, 2:26:15 PM
identified
The root cause has been identified and a fix is being implemented.
8/19/2026, 2:20:54 PM
investigating
We are investigating a service degradation affecting Composer 2.5 (non-fast). Users may experience errors when making requests using this model.
8/19/2026, 12:52:32 PM
More Cursor incidents
- Opus 5.5 is Experiencing 429s — ongoing, 22m ago
- Investigating service degradation — Grok Bot — resolved, 22h 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