Cursor
Grok Bot
No data
Last success —
No component payload
Grok Bot routines not triggering
4 up1 degraded0 down0 unknown
Snapshot 03:19:44 UTC
updates every 60s
Official incident · Grok Bot
Grok Bot routines not triggering
resolved · 2026-10-13 21:13:09 UTC · Resolved 2026-10-13 20:29:00 UTC
Official component matchmajorGrok Bot
Official updates
- 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.
Could not read official status. Unknown is not operational.
DATA SOURCE
Data from each vendor official status page, refreshed every 60 seconds. Failed reads show unknown and last success time.
- status.claude.com/api/v2/summary.json
- status.openai.com/api/v2/summary.json + components.json
- status.x.ai/api/compat/summary.json (Cursor)
- status.x.ai/feed.xml (Grok)
- www.githubstatus.com/api/v2/summary.json
Snapshots and status changes are retained for up to 7 days; official incidents remain in the site index. Everything is generated only from official data captured by this site.