Outage recap · Anysphere

Cursor outage — November 6, 2026

On November 6, 2026, Cursor had 2 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.

Computer use in Grok Bot fails for users in a few regions.

minor
Started
Nov 6, 6:49 AM EST
Resolved
Nov 6, 7:03 AM EST
Duration
14 min

Anysphere's updates (2)

  1. investigating · Nov 6, 6:49 AM EST

    We've identified an issue where computer use in Grok Bot is failing for users in some regions. Other Grok Bot features are working normally. Our team is working on a fix, and we'll share an update as soon as we have more information.

  2. resolved · Nov 6, 7:03 AM EST

    The issue is resolved and computer use in Grok Bot is working normally again for all users.

What our checks recorded

We checked Cursor 3 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 536 ms, against 441 ms over the 24 hours before. Anysphere posted the incident at Nov 6, 6:49 AM EST.

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

Grok Bot is currently degraded

minor
Started
Nov 6, 8:57 AM EST
Resolved
Nov 6, 10:15 AM EST
Duration
1h 17m

Anysphere's updates (2)

  1. investigating · Nov 6, 8:57 AM EST

    Grok Bot is currently degraded, and our team is investigating.

  2. resolved · Nov 6, 10:15 AM EST

    This issue has been resolved.

What our checks recorded

We checked Cursor 15 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 529 ms, against 452 ms over the 24 hours before. Anysphere posted the incident at Nov 6, 8:57 AM EST.

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.