Cursor · 26d ago
Investigating service degradation — Cloud Agents and Automations
ResolvedYes — Cursor had a problem on September 17, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 9/17/2026, 3:20:00 PM
Last update: 9/17/2026, 8:04:04 PM
Resolved: 9/17/2026, 8:04:04 PM
Affected: k0trcq273dr6, 2x2chyqwmkzl, mwv1g9sc7kdh, sm5wkcnqkvr9
Updates
resolved
This incident has been resolved.
9/17/2026, 8:04:04 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
9/17/2026, 6:12:05 PM
investigating
Affected services are back to normal operation. Our team continues to monitor everything closely.
9/17/2026, 6:02:30 PM
investigating
We are continuing to investigate this issue. Cloud Agents, Automations, and Review Agents (resulting from Cloud Agents) are affected. Bugbot is not affected.
9/17/2026, 5:31:53 PM
investigating
We are continuing to investigate this issue.
9/17/2026, 3:58:35 PM
investigating
We are currently investigating this issue. We will provide updates as more information becomes available.
9/17/2026, 3:50:25 PM
investigating
We are investigating a service degradation affecting Cloud Agents and Automations
9/17/2026, 3:20:59 PM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 12h 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