Cursor · 57d ago
Investigating service degradation
ResolvedYes — Cursor had a problem on August 17, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 8/17/2026, 9:32:24 AM
Last update: 8/17/2026, 1:40:26 PM
Resolved: 8/17/2026, 1:40:26 PM
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, jh0714rgjgt4, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
8/17/2026, 1:40:26 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
8/17/2026, 10:11:00 AM
investigating
We are investigating a service degradation for requests that use Grok 4.6 (non-fast). Users may experience slowness and high error rates. Other models are unaffected.
8/17/2026, 9:32:24 AM
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