Major incident
Cursor: Grok Bot routines not triggering
Oct 13, 2026, 21:13 UTC
started
20:29 UTC
resolved
—
duration
Current status of Cursor: Operational — live Cursor status
Timeline
- Oct 13, 2026, 20:29 UTCresolvedBetween 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.
Updates as published by Cursor (original).
Other services with incidents at the same time
- Sparrow 22:07 UTC · Login issues reported
- IPVanish 21:49 UTC · Tallinn, Estonia
- IPVanish 21:46 UTC · Ljubljana, Slovenia
- NVIDIA GeForce NOW 21:45 UTC · External Network Issues in LATAM South (ABY)
- WiscNet 21:01 UTC · [2303532] Tomorrow River School District - DOWN
- Verkada Command 21:00 UTC · Cameras reporting inaccurate historical online/offline state
- Plaid 20:55 UTC · Delayed Transactions Update Webhooks
- LiveRamp External 20:54 UTC · Incident Resolved for Connect UI - Connect UI Website via Grafana
- Cloudflare 20:37 UTC · Network Performance Issues in LAX
More Cursor incidents
- October 26, 2026 Elevated errors for Claude Sonnet 5.5
- October 23, 2026 Investigating service outage - Grok models unavailable
- October 21, 2026 Elevated errors for Bitbucket Cloud integrations
- October 21, 2026 Investigating service degradation
- October 19, 2026 Investigating service degradation — Grok Bot
- October 19, 2026 Investigating service degradation