Cursor · 37d ago
Degraded performance of Grok 4.6
ResolvedYes — Cursor had a problem on September 3, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/3/2026, 5:42:36 PM
Last update: 9/3/2026, 7:21:13 PM
Resolved: 9/3/2026, 7:21:13 PM
Affected: vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2, sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
9/3/2026, 7:21:13 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
9/3/2026, 6:57:57 PM
investigating
We are investigating a service degradation affecting Grok 4.6
9/3/2026, 5:42:36 PM
More Cursor incidents
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 20h ago
- Investigating service degradation — Cloud Agents — resolved, 21h ago
- Elevated errors affecting Opus 5.5 — resolved, 2d ago
- Opus 5.5 is Experiencing 429s — resolved, 2d ago
- Investigating service degradation — Grok Bot — resolved, 3d ago
- Investigating service degradation — Cloud Agents — resolved, 4d ago