Cursor outage on October 28, 2026: Multiple services degraded
Cursor reported an incident affecting Cursor for 1 hour 58 minutes on 28 October 2026, from 21:15 to 23:13 UTC.
Resolved
Official incident reported by Cursor
- Started
- 21:15
- 28 Oct 2026 UTC
- Resolved
- 23:13
- 28 Oct 2026 UTC
- Duration
- 1h 58m
- 1 hour 58 minutes
- Impact
- Major
- as rated by Cursor
- Updates
- 6
- posted by Cursor
Timeline
All times UTC.
Official incident from Cursor
Multiple services degraded
-
Official
Investigating
We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.
-
Official
Investigating
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.
-
Official
Investigating
A fix has been implemented and services are starting to recover. We will share another update shortly.
-
Official
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.
-
Official
Investigating
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.
-
Official
Resolved
This incident has been resolved. All services have returned to normal operation.
"Official" rows are quoted from Cursor's public status page, status.cursor.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test cursor.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Cursor status shows what our checks see right now.
Does your product depend on Cursor?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Cursor. Official updates are quoted from Cursor's public status page and remain Cursor's own words.