Outage recap · Anysphere

Cursor outage — October 13, 2026

On October 13, 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.

Grok Bot routines not triggering

major
Started
Oct 13, 5:13 PM EDT
Resolved
Oct 13, 4:29 PM EDT
Duration
—

Anysphere's updates (1)

  1. resolved · Oct 13, 4:29 PM EDT

    Between 10:52 AM and 1:29 PM PT on October 13, many Grok Bot routines started by webhooks, Slack, git, email and Linear events didn't run. Webhook callers may have seen an HTTP 400 "Automation run rate limit exceeded" error, and other triggers failed without an error. Your own usage didn't cause this. Routines are running normally again. Events sent during this window weren't processed and won't be retried automatically, so please resend anything important.

What our checks recorded

We have no checks recorded from Anysphere's start time to its resolution.

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.