Cursor · 68d ago
Degraded Performance for Grok 4.5
ResolvedYes — Cursor had a problem on August 6, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 8/6/2026, 7:59:13 PM
Last update: 8/6/2026, 8:27:32 PM
Resolved: 8/6/2026, 8:27:32 PM
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, jh0714rgjgt4, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
8/6/2026, 8:27:32 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
8/6/2026, 8:15:12 PM
investigating
We are investigating a service degradation with Grok 4.5.
8/6/2026, 7:59:13 PM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 12h 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
- Investigating service degradation — Grok Bot — resolved, 6d ago