Cursor · 45d ago
Investigating service degradation
ResolvedYes — Cursor had a problem on September 21, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/21/2026, 6:39:00 AM
Last update: 9/21/2026, 7:00:48 AM
Resolved: 9/21/2026, 7:00:48 AM
Affected: k0trcq273dr6, mwv1g9sc7kdh, vsny1qv7v86c, rflc60xp5jp2, cursor-ios
Updates
resolved
This incident has been resolved.
9/21/2026, 7:00:48 AM
investigating
We are investigating degraded performance for requests that use Grok 4.6. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok 4.6 is used. Other models are unaffected.
9/21/2026, 6:39:25 AM
More Cursor incidents
- Degraded Performance - Grok Bot — resolved, 13h ago
- 3 "Slow clones from GH due to Github degradation" — resolved, 2d ago
- Issues with source control integrations — resolved, 3d ago
- Service Degradation - Billing and Usage Dashboard — resolved, 4d ago
- Multiple services degraded — resolved, 5d ago
- Investigating Service Degradation with VS Code Extensions — resolved, 7d ago