Cursor · 83d ago
Investigating service degradation
ResolvedYes — Cursor had a problem on July 20, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 7/20/2026, 2:00:42 AM
Last update: 7/20/2026, 2:19:28 AM
Resolved: 7/20/2026, 2:19:28 AM
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
7/20/2026, 2:19:28 AM
investigating
We are investigating a service degradation of Cursor Grok 4.5, Cursor Grok 4.5 Fast, and Auto.
7/20/2026, 2:00:42 AM
More Cursor incidents
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 19h ago
- Investigating service degradation — Cloud Agents — resolved, 20h ago
- Elevated errors affecting Opus 5.5 — resolved, 2d ago
- Opus 5.5 is Experiencing 429s — resolved, 2d ago
- Investigating service degradation — Grok Bot — resolved, 3d ago
- Investigating service degradation — Cloud Agents — resolved, 4d ago