Cursor · 45d ago
Investigating service degradation — Grok Bot
ResolvedYes — Cursor had a problem on September 18, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/18/2026, 5:19:03 PM
Last update: 9/18/2026, 11:02:23 PM
Resolved: 9/18/2026, 11:02:23 PM
Affected: sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
9/18/2026, 11:02:23 PM
investigating
A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.
9/18/2026, 7:53:41 PM
investigating
The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly.
9/18/2026, 7:01:17 PM
investigating
We are investigating a service degradation affecting Grok Bot.
9/18/2026, 5:19:03 PM
More Cursor incidents
- Issues with source control integrations — resolved, 14h ago
- Service Degradation - Billing and Usage Dashboard — resolved, 2d ago
- Multiple services degraded — resolved, 3d ago
- Investigating Service Degradation with VS Code Extensions — resolved, 4d ago
- Cloud Agent Degradation — resolved, 4d ago
- Auto Review Degradation — resolved, 4d ago