Cursor outage on October 13, 2026: Grok Bot routines not triggering
Cursor reported an incident affecting Cursor for 1 minute on 13 October 2026, from 20:29 to 20:29 UTC.
Resolved
Official incident reported by Cursor
- Started
- 20:29
- 13 Oct 2026 UTC
- Resolved
- 20:29
- 13 Oct 2026 UTC
- Duration
- <1m
- 1 minute
- Impact
- Major
- as rated by Cursor
- Updates
- 1
- posted by Cursor
Timeline
All times UTC.
Official incident from Cursor
Grok Bot routines not triggering
-
Official
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.
"Official" rows are quoted from Cursor's public status page, status.cursor.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test cursor.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Cursor status shows what our checks see right now.
Does your product depend on Cursor?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Cursor. Official updates are quoted from Cursor's public status page and remain Cursor's own words.