Cursor · 23d 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, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2
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
- Grok Bot routines not triggering — resolved, 29m ago
- Degraded performance and errors across Cursor services — resolved, 21h ago
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 4d ago
- Investigating service degradation — Cloud Agents — resolved, 4d ago
- Elevated errors affecting Opus 5.5 — resolved, 5d ago
- Opus 5.5 is Experiencing 429s — resolved, 5d ago