Cursor · 45d ago
Investigating service degradation - Grok 4.7
ResolvedYes — Cursor had a problem on September 23, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/23/2026, 8:28:02 PM
Last update: 9/23/2026, 8:36:47 PM
Resolved: 9/23/2026, 8:36:47 PM
Affected: k0trcq273dr6, mwv1g9sc7kdh, vsny1qv7v86c, rflc60xp5jp2, cursor-ios
Updates
resolved
This incident has been resolved.
9/23/2026, 8:36:47 PM
investigating
A fix has been implemented and we are monitoring for service restoration.
9/23/2026, 8:31:44 PM
investigating
We are investigating degraded performance for requests that use Grok 4.7.
9/23/2026, 8:28:02 PM
More Cursor incidents
- Grok Bot is currently degraded — resolved, 1d ago
- Computer use in Grok Bot fails for users in a few regions. — resolved, 2d ago
- composer-2.5 degraded — resolved, 2d ago
- Degraded Performance - Grok Bot — resolved, 3d ago
- 3 "Slow clones from GH due to Github degradation" — resolved, 4d ago
- Issues with source control integrations — resolved, 6d ago