Resolved · lasted 9 h
Cursor outage on October 28
Reports for Cursor jumped to 261 an hour and stayed high for 9 h.
- Started
- 2:00 PM
- October 28, 2026 · UTC
- Back to normal
- 11:00 PM
- 9 h later
- Peak
- 261/hr
- 52× normal
- Cursor’s incident
- 1 h 58 min
- Multiple services degraded
Reports during the outage
What Cursor said
status.cursor.comMultiple services degraded
- Resolved · 11:13 PM
This incident has been resolved. All services have returned to normal operation.
- Investigating · 10:42 PM
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.
- Resolved · 10:40 PM
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.
- Investigating · 10:06 PM
A fix has been implemented and services are starting to recover. We will share another update shortly.
- Investigating · 9:39 PM
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.
- Investigating · 9:15 PM
We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.
Cursor posted its first update 7 h 15 min after reports started rising.
What people said
- DimitarEnschede, NL · 9:43 PM
can't login
1 comments during the outage
Is Cursor down right now?
Live status, today’s reports and other past outages.