xAI: Grok Bot routines not triggering

What to do

Check whether your product depends on xAI. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-10-13 21:13 UTC and 2026-10-13 21:13 UTC may need a replay.
Subscribe to xAI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=xai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedOct 13, 2026, 9:13 PM UTC
Status: RESOLVED Severity: disruption Resolved: Tue, 13 Oct 2026 20:29:00 GMT Updates: Tue, 13 Oct 2026 20:29:00 GMT 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.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is xAI still down?

No, this incident was resolved 2026-10-13 21:13 UTC. For xAI's live state, see https://down.guide/xai.

How long did it last?

0m, from 2026-10-13 21:13 UTC to 2026-10-13 21:13 UTC, by the times xAI posted.

What caused it?

xAI hasn't published a root cause. If it does, it shows here.

Where does this come from?

xAI's official status page, https://status.x.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.