Cursor · 27d ago
Investigating service degradation — Grok Bot
ResolvedYes — Cursor had a problem on September 16, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/16/2026, 2:27:16 PM
Last update: 9/16/2026, 8:57:14 PM
Resolved: 9/16/2026, 8:57:14 PM
Affected: sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
9/16/2026, 8:57:14 PM
identified
The root cause has been identified and a fix is being implemented.
9/16/2026, 7:51:37 PM
investigating
We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.
9/16/2026, 2:27:16 PM
More Cursor incidents
- Grok Bot routines not triggering — resolved, 59m 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