Cursor · 36d ago
Investigating service degradation
ResolvedYes — Cursor had a problem on September 3, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/3/2026, 1:41:00 PM
Last update: 9/3/2026, 5:07:00 PM
Resolved: 9/3/2026, 5:07:00 PM
Affected: k0trcq273dr6, 2x2chyqwmkzl, mwv1g9sc7kdh, rflc60xp5jp2, sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
9/3/2026, 5:07:00 PM
identified
We have identified the cause and are actively working on a mitigation.
9/3/2026, 3:33:57 PM
investigating
We are investigating a service degradation affecting All Grok Models, Automations, Cloud Agents, Grok Bot and Review Agents
9/3/2026, 1:41:25 PM
More Cursor incidents
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 4h ago
- Investigating service degradation — Cloud Agents — resolved, 5h ago
- Elevated errors affecting Opus 5.5 — resolved, 1d ago
- Opus 5.5 is Experiencing 429s — resolved, 2d ago
- Investigating service degradation — Grok Bot — resolved, 2d ago
- Investigating service degradation — Cloud Agents — resolved, 3d ago