Cursor reported this major-impact incident on its official status page on Oct 28, 2026, 21:15 UTC. It was resolved after 1h 58m.
Right now Cursor is degraded. Live Cursor status →
This incident has been resolved. All services have returned to normal operation.
Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.
Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.
A fix has been implemented and services are starting to recover. We will share another update shortly.
We are investigating service degradation for multiple services. Users may see failures across Automations, Bugbot, Cloud Agents, Grok Bot, and Origin. We are working on a fix and will update shortly.
We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.
Overlapping incidents aren't necessarily related.
Cursor reported 90 incidents in the last 90 days, 22 of them major or critical. A typical incident lasted 1h 11m. See Cursor's uptime and incident history