Cursor · 3h 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: Sep 23, 2026, 8:28 PM UTC
Last update: Sep 23, 2026, 8:36 PM UTC
Resolved: Sep 23, 2026, 8:36 PM UTC
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
Sep 23, 2026, 8:36 PM UTC
monitoring
A fix has been implemented and we are monitoring for service restoration.
Sep 23, 2026, 8:31 PM UTC
investigating
We are investigating degraded performance for requests that use Grok 4.7.
Sep 23, 2026, 8:28 PM UTC
More Cursor incidents
- Investigating — Cloud Agent Dockerfile Builds — resolved, 7h ago
- Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7 — resolved, 1d ago
- Investigating service degradation — resolved, 2d ago
- Investigating service degradation — resolved, 3d ago
- Sign-in and dashboard errors for some users — resolved, 5d ago
- Investigating service degradation — Grok Bot — resolved, 5d ago