Cursor · 17h ago
Investigating service degradation
ResolvedYes — Cursor had a problem on September 22, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: Sep 22, 2026, 1:07 AM UTC
Last update: Sep 22, 2026, 1:42 AM UTC
Resolved: Sep 22, 2026, 1:42 AM UTC
Affected: k0trcq273dr6, vsny1qv7v86c, mwv1g9sc7kdh, rflc60xp5jp2
Updates
resolved
This incident has been resolved.
Sep 22, 2026, 1:42 AM UTC
investigating
We are investigating degraded performance for requests that use Grok models. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok models are used. Other models are unaffected.
Sep 22, 2026, 1:07 AM UTC
More Cursor incidents
- Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7 — resolved, 6h ago
- Investigating service degradation — resolved, 2d ago
- Sign-in and dashboard errors for some users — resolved, 4d ago
- Investigating service degradation — Grok Bot — resolved, 4d ago
- Investigating service degradation — Grok Bot — resolved, 4d ago
- Investigating service degradation — Cloud Agents and Automations — resolved, 5d ago