Skip to main content

Cursor outage on November 19, 2026: Degraded Gemini 4 Carbon

Cursor has reported an incident affecting Cursor since 16:01 UTC on 19 November 2026 (47 minutes so far).

cursor.com All times UTC

Open

Official incident reported by Cursor

Started
16:01
19 Nov 2026 UTC
Status
Open
not resolved yet
Duration
47m
47 minutes so far
Impact
-
as rated by Cursor
Updates
1
posted by Cursor

Timeline

All times UTC.

Official incident from Cursor

Degraded Gemini 4 Carbon

Investigating 19 Nov 2026 16:01 UTC View on Cursor's status page
  1. Official
    Investigating

    We are investigating a service degradation affecting the Gemini 4 Carbon model.

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