Cursor · 15d ago
Investigating service degradation — Grok Bot
ResolvedYes — Cursor had a problem on September 28, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/28/2026, 8:23:05 PM
Last update: 9/28/2026, 8:36:19 PM
Resolved: 9/28/2026, 8:36:19 PM
Affected: sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
9/28/2026, 8:36:19 PM
investigating
We are investigating a service degradation affecting Grok Bot.
9/28/2026, 8:23:06 PM
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