Is xAI (Grok) down?
For agents
proceed
Proceed.
GET upbutler.com/status/xai/status.agent.json
MCP: upstream_status {"service":"xai"}
The Grok API and apps.
What xAI (Grok) reports
Operational
Taken as is from xAI (Grok)'s own incident feed. Incident titles and component names below are theirs.
Open status.x.aiUpButler's independent probe
API edge is answeringHTTP 401 · 176 ms
One request without credentials to api.x.ai every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:24 UTC
xAI (Grok) incidents, last 90 days
2 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by xAI (Grok).
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| [grok.com] grok.com | major | under a minute | |
| [Voice] Enterprise Voice Degraded | minor | under a minute |
Tell your outage from xAI (Grok)'s
Declare that your project depends on xAI (Grok). When one of your monitors fails while xAI (Grok) has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- xaicurl -s https://upbutler.com/status/xai/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "xai",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is xAI (Grok) down right now?
- No. As of 2026-10-10 05:12 UTC, xAI (Grok) is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From xAI (Grok)'s own incident feed at https://status.x.ai. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are xAI (Grok)'s words.
- What does UpButler's own xAI (Grok) check prove?
- Every two minutes UpButler sends one request without credentials to the xAI (Grok) API edge (api.x.ai). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while xAI (Grok) reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check xAI (Grok) status?
- Fetch https://upbutler.com/status/xai/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"xai"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or xAI (Grok)'s?
- Add "xai" to the dependencies of your UpButler workspace. When one of your monitors fails while xAI (Grok) has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in ai models and tooling
UpButler is not affiliated with xAI (Grok). Status and incident text belong to xAI (Grok) and are read from their public status source; the probe result is UpButler's own measurement.