Cursor · 22d ago
Investigating service degradation
ResolvedYes — Cursor had a problem on September 22, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/22/2026, 1:07:24 AM
Last update: 9/22/2026, 1:42:57 AM
Resolved: 9/22/2026, 1:42:57 AM
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
9/22/2026, 1:42:57 AM
investigating
We are investigating degraded performance for requests that use Grok models. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok models are used. Other models are unaffected.
9/22/2026, 1:07:24 AM
More Cursor incidents
- Grok Bot routines not triggering — resolved, 1h ago
- Degraded performance and errors across Cursor services — resolved, 22h 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