Cursor · 3h 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: Sep 15, 2026, 9:26 PM UTC
Last update: Sep 15, 2026, 10:00 PM UTC
Resolved: Sep 15, 2026, 10:00 PM UTC
Affected: k0trcq273dr6, 2x2chyqwmkzl, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2, xwjpvdf81qh9, sm5wkcnqkvr9
Updates
resolved
This incident has been resolved at 6pm Eastern.
Sep 15, 2026, 10:00 PM UTC
monitoring
A fix has been implemented and we are monitoring for service restoration. Only Grok 4.6 (non-fast) is affected in Cursor.
Sep 15, 2026, 9:41 PM UTC
monitoring
A fix has been implemented and we are monitoring for service restoration.
Sep 15, 2026, 9:38 PM UTC
investigating
We are investigating a service degradation. Affected agent surfaces: Composer and xAI.
Sep 15, 2026, 9:26 PM UTC
More Cursor incidents
- Investigating Grok service degradation — resolved, 2d ago
- Investigating service degradation — resolved, 5d ago
- Investigating service degradation — Review Agents and Cloud Agents — resolved, 5d ago
- Grok Bot computers unreachable for some users — resolved, 8d ago
- Investigating service degradation — CLI, Cloud Agents, and IDE — resolved, 9d ago
- Degraded performance for Grok Bot routine triggers — resolved, 12d ago