Cursor · 47d ago
Investigating service degradation — cursor.com and IDE
ResolvedYes — Cursor had a problem on August 27, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved. Sign-in to Cursor has returned to normal operation.”
Timeline
Started: 8/27/2026, 7:31:41 PM
Last update: 8/27/2026, 7:38:48 PM
Resolved: 8/27/2026, 7:38:48 PM
Affected: jh0714rgjgt4, rflc60xp5jp2
Updates
resolved
This incident has been resolved. Sign-in to Cursor has returned to normal operation.
8/27/2026, 7:38:48 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
8/27/2026, 7:35:40 PM
investigating
We are investigating a service degradation affecting sign-in to Cursor.
8/27/2026, 7:31:41 PM
More Cursor incidents
- Degraded performance and errors across Cursor services — resolved, 17h 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