Cursor · 2h 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
- Investigating service degradation — Grok Bot — resolved, 3d ago
- Investigating service degradation — Grok Bot — resolved, 4d ago
- Investigating service degradation - Grok 4.7 — resolved, 5d ago
- Investigating — Cloud Agent Dockerfile Builds — resolved, 5d ago
- Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7 — resolved, 6d ago
- Investigating service degradation — resolved, 7d ago