Cursor · 49d ago
Degraded performance of Grok models
ResolvedYes — Cursor had a problem on August 25, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 8/25/2026, 8:34:50 PM
Last update: 8/25/2026, 9:28:42 PM
Resolved: 8/25/2026, 9:28:42 PM
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
8/25/2026, 9:28:42 PM
monitoring
We are seeing signs of improvement and will continue to monitor for service restoration.
8/25/2026, 8:50:34 PM
investigating
We are investigating a service degradation affecting Grok models.
8/25/2026, 8:34:51 PM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 15h 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