Cursor · 49d ago
Degraded performance of Grok 4.6
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, 2:54:02 PM
Last update: 8/25/2026, 5:36:45 PM
Resolved: 8/25/2026, 5:36:45 PM
Affected: vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2, sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
8/25/2026, 5:36:45 PM
monitoring
We are seeing signs of improvement and will continue to monitor for service restoration.
8/25/2026, 4:20:12 PM
identified
The root cause has been identified and a fix is being implemented.
8/25/2026, 3:29:11 PM
investigating
We are investigating a service degradation affecting Grok 4.6.
8/25/2026, 2:54:02 PM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 17h 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