Cursor · 26d ago
Investigating Grok service degradation
ResolvedYes — Cursor had a problem on September 14, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/14/2026, 8:14:46 AM
Last update: 9/14/2026, 9:07:24 AM
Resolved: 9/14/2026, 9:07:24 AM
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
9/14/2026, 9:07:24 AM
monitoring
We are monitoring Grok 4.6 for service restoration.
9/14/2026, 8:15:24 AM
investigating
We are investigating a service degradation affecting Grok 4.6.
9/14/2026, 8:14:46 AM
More Cursor incidents
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 18h ago
- Investigating service degradation — Cloud Agents — resolved, 19h ago
- Elevated errors affecting Opus 5.5 — resolved, 2d ago
- Opus 5.5 is Experiencing 429s — resolved, 2d ago
- Investigating service degradation — Grok Bot — resolved, 3d ago
- Investigating service degradation — Cloud Agents — resolved, 4d ago