Provider incident title: “Grok Bot routines not triggering”
Started
Tuesday, October 13, 2026
08:29 PM UTC
Duration
< 1 minute
total
Resolved
08:29 PM UTC
Oct 13, 2026
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 alerted next time
Install Tickerr MCP — your agent auto-reports & routes around outages
When Cursor goes down again, your agent reports anonymously and instantly gets a fallback recommendation from the swarm.
Cursor is back online
View current status and uptime history
Cursor 30-day uptime: 100% based on Tickerr's independent monitoring checks.
This incident was sourced from Cursor's official Atlassian Statuspage. Tickerr ingests updates every 10 minutes to surface incidents as they are posted by the provider.
This incident lasted < 1 minute.
Tickerr monitors 90+ AI tools independently. View live Cursor status or all AI tool status.
Get alerted next time Cursor goes down
Tickerr monitors 90+ AI tools. We'll email you when an incident starts or resolves.
Weekly AI pricing & uptime digest
Price drops, new model releases, and incident summaries - every Monday. Free.
Also on Tickerr