Cursor · 20d ago
Investigating service degradation - Grok 4.7
ResolvedYes — Cursor had a problem on September 23, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/23/2026, 8:28:02 PM
Last update: 9/23/2026, 8:36:47 PM
Resolved: 9/23/2026, 8:36:47 PM
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
9/23/2026, 8:36:47 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
9/23/2026, 8:31:44 PM
investigating
We are investigating degraded performance for requests that use Grok 4.7.
9/23/2026, 8:28:02 PM
More Cursor incidents
- Grok Bot routines not triggering — resolved, 1h ago
- Degraded performance and errors across Cursor services — resolved, 22h ago
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 4d ago
- Investigating service degradation — Cloud Agents — resolved, 4d ago
- Elevated errors affecting Opus 5.5 — resolved, 5d ago
- Opus 5.5 is Experiencing 429s — resolved, 5d ago