Cursor · 25d ago
Investigating service degradation
ResolvedYes — Cursor had a problem on September 15, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved at 6pm Eastern.”
Timeline
Started: 9/15/2026, 9:26:49 PM
Last update: 9/15/2026, 10:00:04 PM
Resolved: 9/15/2026, 10:00:04 PM
Affected: k0trcq273dr6, 2x2chyqwmkzl, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2, xwjpvdf81qh9, sm5wkcnqkvr9
Updates
resolved
This incident has been resolved at 6pm Eastern.
9/15/2026, 10:00:04 PM
monitoring
A fix has been implemented and we are monitoring for service restoration. Only Grok 4.6 (non-fast) is affected in Cursor.
9/15/2026, 9:41:33 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
9/15/2026, 9:38:02 PM
investigating
We are investigating a service degradation. Affected agent surfaces: Composer and xAI.
9/15/2026, 9:26:49 PM
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