Cursor outage on October 14, 2026: Investigating service degradation — Grok Bot
Cursor reported an incident affecting Cursor for 5 hours 18 minutes on 14 October 2026, from 15:46 to 21:04 UTC.
Resolved
Official incident reported by Cursor
- Started
- 15:46
- 14 Oct 2026 UTC
- Resolved
- 21:04
- 14 Oct 2026 UTC
- Duration
- 5h 18m
- 5 hours 18 minutes
- Impact
- Minor
- as rated by Cursor
- Updates
- 3
- posted by Cursor
Timeline
All times UTC.
Official incident from Cursor
Investigating service degradation — Grok Bot
-
Official
Investigating
We are investigating a service degradation affecting Grok Bot and preventing some users from reaching their computers
-
Official
Identified
We've identified the issue impacting Grok Bot for some users and are working on a fix.
-
Official
Resolved
This incident has been resolved.
"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.