Cursor · 19d ago
Investigating service degradation — Grok Bot
ResolvedYes — Cursor had a problem on September 25, 2026, and Cursor has since marked it resolved. Cursor's latest word: “The service degradation affecting Grok Bot has been resolved.”
Timeline
Started: 9/25/2026, 5:17:29 AM
Last update: 9/25/2026, 6:51:32 AM
Resolved: 9/25/2026, 6:51:32 AM
Affected: sm5wkcnqkvr9
Updates
resolved
The service degradation affecting Grok Bot has been resolved.
9/25/2026, 6:51:32 AM
monitoring
We have identified the cause and are deploying a fix. We are monitoring recovery as the fix rolls out. Some Grok Bot computers may remain temporarily unavailable or unable to be created or reset during this time.
9/25/2026, 5:52:23 AM
investigating
We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.
9/25/2026, 5:17:29 AM
More Cursor incidents
- Grok Bot routines not triggering — resolved, 58m 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