Cursor · 92d ago
Investigating service degradation
ResolvedYes — Cursor had a problem on July 13, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 7/13/2026, 7:41:00 AM
Last update: 7/13/2026, 7:58:52 AM
Resolved: 7/13/2026, 7:58:52 AM
Affected: k0trcq273dr6, 2x2chyqwmkzl, vsny1qv7v86c, mwv1g9sc7kdh, jh0714rgjgt4, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
7/13/2026, 7:58:52 AM
investigating
We are investigating a service degradation. Affected agent surfaces: Composer, Grok
7/13/2026, 7:41:35 AM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 13h ago
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 4d ago
- Investigating service degradation — Cloud Agents — resolved, 4d ago
- Elevated errors affecting Opus 5.5 — resolved, 5d ago
- Opus 5.5 is Experiencing 429s — resolved, 5d ago
- Investigating service degradation — Grok Bot — resolved, 6d ago