Outage recap · Anysphere

Cursor outage — November 19, 2026

On November 19, 2026, Cursor had a reported incident on Anysphere's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded Gemini 4 Carbon

none
Started
Nov 19, 11:01 AM EST
Resolved
—
Duration
not marked resolved

Anysphere's updates (4)

  1. investigating · Nov 19, 11:01 AM EST

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

  2. investigating · Nov 19, 2:21 PM EST

    We are continuing to monitor an issue with an upstream provider affecting the Gemini 4 Carbon model. Some requests may fail intermittently while the provider works on a fix.

  3. investigating · Nov 19, 3:41 PM EST

    Our upstream provider has added capacity, and error rates for the Gemini 4 Carbon model are improving. Some requests may still fail intermittently while we continue to monitor.

  4. investigating · Nov 19, 4:34 PM EST

    We are continuing to work with an upstream provider on intermittent errors affecting the Gemini 4 Carbon model. Some requests may fail while work on a fix continues.

What our checks recorded

We checked Cursor 66 times from Anysphere's start time to its last update, once every five minutes. Every one of them reached Cursor's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 390 ms, against 397 ms over the 24 hours before. Anysphere posted the incident at Nov 19, 11:01 AM EST.

Updates are Anysphere's own words from its status page (status: investigating); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Anysphere. This recap summarizes incidents published on Anysphere's official status page.