Cursor outage on October 29, 2026: Cloud Agent Degradation

Cursor has reported an incident affecting Cursor since 23:29 UTC on 29 October 2026 (4 hours 29 minutes so far).

cursor.com All times UTC

Open

Official incident reported by Cursor

Started: 23:29; 29 Oct 2026 UTC
Status: Open; not resolved yet
Duration: 4h 29m; 4 hours 29 minutes so far
Impact: Minor; as rated by Cursor
Updates: 1; posted by Cursor

Timeline

All times UTC.

Official incident from Cursor

Cloud Agent Degradation

Investigating Minor impact 29 Oct 2026 23:29 UTC View on Cursor's status page

23:29 Official
Investigating
We are investigation a degradation to Cloud Agents

"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.

All Cursor incidents Live Cursor status Every service we track

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.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with Cursor. Official updates are quoted from Cursor's public status page and remain Cursor's own words.