Cursor · 1h 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: Sep 25, 2026, 5:17 AM UTC
Last update: Sep 25, 2026, 6:51 AM UTC
Resolved: Sep 25, 2026, 6:51 AM UTC
Affected: sm5wkcnqkvr9
Updates
resolved
The service degradation affecting Grok Bot has been resolved.
Sep 25, 2026, 6:51 AM UTC
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.
Sep 25, 2026, 5:52 AM UTC
investigating
We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.
Sep 25, 2026, 5:17 AM UTC
More Cursor incidents
- Investigating service degradation - Grok 4.7 — resolved, 2d ago
- Investigating — Cloud Agent Dockerfile Builds — resolved, 2d ago
- Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7 — resolved, 3d ago
- Investigating service degradation — resolved, 3d ago
- Investigating service degradation — resolved, 4d ago
- Sign-in and dashboard errors for some users — resolved, 6d ago