Cursor · 52d ago
Grok Bot connector delays
ResolvedYes — Cursor had a problem on August 18, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved. Affected Grok Bot sessions have been restored, and connectors are operating normally.”
Timeline
Started: 8/18/2026, 6:46:26 PM
Last update: 8/18/2026, 8:15:48 PM
Resolved: 8/18/2026, 8:15:48 PM
Affected: sm5wkcnqkvr9
Updates
resolved
This incident has been resolved. Affected Grok Bot sessions have been restored, and connectors are operating normally.
8/18/2026, 8:15:48 PM
monitoring
A fix has been implemented and affected Grok Bot sessions have been restored. We are monitoring for full recovery.
8/18/2026, 8:03:38 PM
investigating
We are continuing to investigate an issue causing some Grok Bot connectors to hang. We are working to restore normal operation.
8/18/2026, 7:29:03 PM
investigating
We’re investigating an issue causing Grok Bot connectors to hang. We’ll share updates as we learn more.
8/18/2026, 6:46:26 PM
More Cursor incidents
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 4h ago
- Investigating service degradation — Cloud Agents — resolved, 5h ago
- Elevated errors affecting Opus 5.5 — resolved, 1d ago
- Opus 5.5 is Experiencing 429s — resolved, 2d ago
- Investigating service degradation — Grok Bot — resolved, 2d ago
- Investigating service degradation — Cloud Agents — resolved, 3d ago