Cursor · 47d ago
Investigating service degradation — Grok Bot
ResolvedYes — Cursor had a problem on August 27, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 8/27/2026, 2:23:20 PM
Last update: 8/27/2026, 3:05:23 PM
Resolved: 8/27/2026, 3:05:23 PM
Affected: sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
8/27/2026, 3:05:23 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
8/27/2026, 2:51:37 PM
investigating
We are investigating a service degradation affecting Grok Bot.
8/27/2026, 2:23:20 PM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 17h 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
- Investigating service degradation — Grok Bot — resolved, 6d ago