Cursor · 36d ago

Investigating service degradation — CLI, Cloud Agents, and IDE

Resolved

Yes — Cursor had a problem on September 7, 2026, and Cursor has since marked it resolved. Cursor's latest word: “Between 12:12 and 13:08 UTC on September 7, 2026, some users may have experienced login or account-related errors. This incident has been resolved. All services have returned to normal operation.”

See Cursor's live status →

Timeline

Started: 9/7/2026, 1:35:48 PM

Last update: 9/7/2026, 1:36:19 PM

Resolved: 9/7/2026, 1:08:00 PM

Cursor's official report →

Updates

resolved
Between 12:12 and 13:08 UTC on September 7, 2026, some users may have experienced login or account-related errors. This incident has been resolved. All services have returned to normal operation.
9/7/2026, 1:35:48 PM

More Cursor incidents

Grok Bot routines not triggering — resolved, 1h ago
Degraded performance and errors across Cursor services — resolved, 22h 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

Is Cursor down right now?All outage history →