Cursor · 45d 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, mwv1g9sc7kdh, vsny1qv7v86c, rflc60xp5jp2, cursor-ios, sm5wkcnqkvr9, xwjpvdf81qh9, 2x2chyqwmkzl
Updates
resolved
This incident has been resolved at 6pm Eastern.
9/15/2026, 10:00:04 PM
investigating
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
investigating
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 with VS Code Extensions — resolved, 1d ago
- Cloud Agent Degradation — resolved, 1d ago
- Auto Review Degradation — resolved, 1d ago
- Degraded performance — Origin and Cloud Agents — resolved, 2d ago
- Multiple services degraded — resolved, 2d ago
- Delayed responses in Grok Bot — resolved, 3d ago