Cursor · 3h ago

Investigating service degradation

Resolved

Yes — Cursor had a problem on October 19, 2026, and Cursor has since marked it resolved. Cursor's latest word: “This incident has been resolved. Thank you for your patience!”

See Cursor's live status →

Timeline

Started: 10/19/2026, 1:24:52 PM

Last update: 10/19/2026, 1:52:07 PM

Resolved: 10/19/2026, 1:52:07 PM

Affected: vsny1qv7v86c, mwv1g9sc7kdh, jh0714rgjgt4, rflc60xp5jp2

Cursor's official report →

Updates

resolved
This incident has been resolved. Thank you for your patience!
10/19/2026, 1:52:07 PM
monitoring
A fix has been implemented and we are monitoring for service restoration.
10/19/2026, 1:35:14 PM
investigating
We are investigating elevated errors for Anthropic Opus 5.5.
10/19/2026, 1:24:52 PM

More Cursor incidents

Investigating service degradation — Grok Bot — ongoing, 9m ago
Elevated errors affecting Grok models — resolved, 4d ago
Investigating service degradation — Grok Bot — resolved, 5d ago
Grok Bot routines not triggering — resolved, 6d ago
Degraded performance and errors across Cursor services — resolved, 7d ago
Investigating service degradation — Cloud Agents and Grok Bot — resolved, 10d ago

Is Cursor down right now?All outage history →