Cursor · 46d 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, mwv1g9sc7kdh, vsny1qv7v86c, rflc60xp5jp2, cursor-ios
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 is currently degraded — resolved, 7h ago
- Computer use in Grok Bot fails for users in a few regions. — resolved, 9h ago
- composer-2.5 degraded — resolved, 1d ago
- Degraded Performance - Grok Bot — resolved, 2d ago
- 3 "Slow clones from GH due to Github degradation" — resolved, 3d ago
- Issues with source control integrations — resolved, 4d ago