Cursor · 75d ago
Investigating service degradation — Cloud Agents
ResolvedYes — Cursor had a problem on July 27, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved.”
Timeline
Started: 7/27/2026, 5:09:47 PM
Last update: 7/27/2026, 7:39:45 PM
Resolved: 7/27/2026, 7:39:45 PM
Affected: mwv1g9sc7kdh
Updates
resolved
This incident has been resolved.
7/27/2026, 7:39:45 PM
monitoring
Automations are back to normal, and cloud agent start failures have subsided. We're monitoring closely to confirm full recovery.
7/27/2026, 6:46:40 PM
identified
Some Cursor Automations may fail to start, and running Automations may be unable to post replies in Slack or open pull requests. We've identified the causes and fixes are rolling out.
7/27/2026, 5:41:16 PM
investigating
We are investigating a service degradation affecting Cloud Agents.
7/27/2026, 5:09:47 PM
More Cursor incidents
- Investigating service degradation — Cloud Agents and Grok Bot — resolved, 19h ago
- Investigating service degradation — Cloud Agents — resolved, 20h 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