Cursor outage, 13 October 2026

Grok Bot routines not triggering

Started
Resolved
13 Oct 2026, 20:29 UTC - reported afterwards
Impact
Major

Last update from Cursor

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.

13 Oct 2026, 20:29 UTC

Read the full incident on the official Cursor status page

Is Cursor down now?

This page is the record of one past incident. For the live status, see Is Cursor down right now? - it reads the official status page every 2 minutes.

Other Cursor incidents

  1. Investigating service degradation - Grok Bot

  2. Degraded performance and errors across Cursor services

  3. Investigating service degradation - Cloud Agents and Grok Bot

  4. Investigating service degradation - Cloud Agents

  5. Elevated errors affecting Opus 5.5

  6. Opus 5.5 is Experiencing 429s

  7. Investigating service degradation - Grok Bot

  8. Investigating service degradation - Cloud Agents

All recorded Cursor incidents