Cursor · 4h 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: “This incident has been resolved.”
Timeline
Started: Sep 25, 2026, 11:47 PM UTC
Last update: Sep 26, 2026, 12:32 AM UTC
Resolved: Sep 26, 2026, 12:32 AM UTC
Affected: sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
Sep 26, 2026, 12:32 AM UTC
monitoring
A fix has been implemented and we are monitoring for service restoration.
Sep 26, 2026, 12:22 AM UTC
investigating
We are investigating a service degradation affecting Grok Bot.
Sep 25, 2026, 11:47 PM UTC
More Cursor incidents
- Investigating service degradation — Grok Bot — resolved, 23h ago
- 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, 4d ago
- Investigating service degradation — resolved, 4d ago
- Investigating service degradation — resolved, 5d ago