Outage recap · Anysphere

Cursor outage — October 19, 2026

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

Investigating service degradation

minor
Started
Oct 19, 9:24 AM EDT
Resolved
Oct 19, 9:52 AM EDT
Duration
27 min

Anysphere's updates (3)

  1. investigating · Oct 19, 9:24 AM EDT

    We are investigating elevated errors for Anthropic Opus 5.5.

  2. investigating · Oct 19, 9:35 AM EDT

    A fix has been implemented and we are monitoring for service restoration.

  3. resolved · Oct 19, 9:52 AM EDT

    This incident has been resolved. Thank you for your patience!

What our checks recorded

We checked Cursor 6 times from Anysphere's start time to its resolution, 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 233 ms, against 199 ms over the 24 hours before. Anysphere posted the incident at Oct 19, 9:24 AM EDT.

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

Investigating service degradation — Grok Bot

minor
Started
Oct 19, 12:15 PM EDT
Resolved
Oct 19, 1:21 PM EDT
Duration
1h 7m

Anysphere's updates (4)

  1. investigating · Oct 19, 12:15 PM EDT

    We are investigating a service degradation affecting Grok Bot where routines may be delayed.

  2. investigating · Oct 19, 12:52 PM EDT

    We are continuing to investigate this issue. We will provide updates as more information becomes available.

  3. investigating · Oct 19, 1:10 PM EDT

    A fix has been implemented and we are monitoring for service restoration.

  4. resolved · Oct 19, 1:21 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 14 times from Anysphere's start time to its resolution, 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 180 ms, against 199 ms over the 24 hours before. Anysphere posted the incident at Oct 19, 12:15 PM EDT.

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

Investigating service degradation — Grok Bot

minor
Started
Oct 19, 2:09 PM EDT
Resolved
Oct 19, 2:28 PM EDT
Duration
19 min

Anysphere's updates (2)

  1. investigating · Oct 19, 2:09 PM EDT

    We are investigating a service degradation affecting Grok Bot and grok.com. You may notice errors related to billing, plans, and usage.

  2. resolved · Oct 19, 2:28 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 4 times from Anysphere's start time to its resolution, 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 190 ms, against 200 ms over the 24 hours before. Anysphere posted the incident at Oct 19, 2:09 PM EDT.

Updates are Anysphere's own words from its status page (status: resolved); 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.