Cursor incident
Grok Bot routines not triggering
Started
October 13, 2026 at 08:29 PM UTC
Duration
0 min
Resolved
October 13, 2026 at 08:29 PM UTC
Updates timeline
- Resolved
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.
Get an email the next time Cursor goes down
Outage alerts for Cursor, straight to your inbox. No account needed, unsubscribe in every email.
Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.
Live Cursor status
Current indicator + 24h latency
All incidents
Cross-service timeline
Subscribe via RSS
Atom feed for any reader