Is the xAI API down? Live status, latency & uptime by region
· rebuilt about every 30 minutes
Is the xAI API down right now?
Reachable from all 4 regions
Last successful probe Nov 10, 15:45 UTC · every 5 minutes from 4 region(s)
2 isolated failure(s) in the last 72 hours, the most recent (host probes) visible from only one region (Europe (Germany)). A single-region failure cannot be separated from a problem on that network path, so it is not called an outage. Measured from outside xai’s own network, independently of its status page; full log: measured AI API incidents.
Real requests: not measured for xAI — only the API host is probed here, so errors limited to specific models are invisible to these probes. That is exactly what a status page tends to report, hence the line below.
xAI publishes no machine-readable status page, so there is nothing to cross-check against.
As of November 10, 2026, the xai AI API responds in 111 ms p50 (edge, time-to-first-byte) from US (Central) — its fastest measured region — with 100% uptime. Slowest is Europe (Germany) at 308 ms p50.
Endpoint response (TTFB), 24 h
111 ms
Typical (p50) from US (Central), the fastest region
Uptime, 24 h
99.9%
1,153 probes across 4 region(s)
Failed probes, 72 h
3
of 3,465 · Europe (Germany)
Reported by xAI, 72 h
—
no machine-readable status page
Was xAI down in the last 3 days?
No. 2 isolated single-region probe failure(s) were recorded, none of which meets the bar for an outage (two or more regions at once).
Europe (Germany) only — not an outage · under one 5-minute probe cycle · 1 failed probe(s) · timeout
Europe (Germany) only — not an outage · at least 5 minutes · 2 failed probe(s) · timeout
xAI publishes no machine-readable status page, so there is nothing to set against the measurements above.
Is xAI getting faster or slower?
Endpoint response (TTFB) · milliseconds · lower is faster
Last 72 hours · UTC · newest time on the right · current hour is incomplete.
Each line shows a region’s typical response per hour (p50), using the same scale. A gap means no successful timed probe in that hour.
typical response per hour (p50)all probes succeededsome failed (under half)half or more failedno probes recorded
Probe counts by region
Europe (Germany): 3 failed / 871 endpoint probesUS (Central): 0 failed / 861 endpoint probesAsia (Tokyo): 0 failed / 861 endpoint probesSouth America (Santiago): 0 failed / 656 endpoint probes · 17 hour(s) without data
Chart details
The strip shows endpoint probe outcomes, not model-request success. Adjacent hours with all successes or no data are joined. Hover an hour for its recorded values.
Latest is the most recent hourly p50 with data. Median is the median of hourly p50 values over these 72 hours. The “slower than usual” label means latest is at least 25% above that median; it is a relative change, not a fixed speed rating.
How fast is the xAI API from each region?
Endpoint response (TTFB) · last 24 hours · milliseconds (ms) · lower is faster.
How to read these metrics
Endpoint response (TTFB)Network connection and the first response byte, without model inference.
Typical · p5050% of successful timed samples finish within this time.
Slower · p9595% of successful timed samples finish within this time.
Region
Typical (p50 TTFB)
Slower (p95)
Uptime
Asia (Tokyo)
174 ms
263 ms
100%
Europe (Germany)
308 ms
325 ms
99.7%
South America (Santiago)
201 ms
266 ms
100%
US (Central)
111 ms
193 ms
100%
Measured from US (Central), xai responds in 111 ms; from Europe (Germany) the same API takes 308 ms — 2.8× longer for an identical request. That difference is the network path, not the model, and it applies to every call you make.
What is actually being measured here?
A probe in each region opens a real connection to xai’s own API host every five
minutes and times DNS resolution, the TCP handshake, the TLS handshake and the first byte of the
response. Nothing is routed through a gateway or aggregator, so these figures describe
xai’s infrastructure rather than a reseller’s. Uptime counts a probe as failed only when the
service genuinely fails — a 401 from an unauthenticated probe means the endpoint answered
correctly and is counted as up, while a 410 Gone means the API has been shut down and is counted as
neither (rule).
What this page does not tell you
These are edge latency numbers: the time before the model begins generating. They
say nothing about answer quality, throughput, price, or how long a full completion takes — those
depend on the model you call. Edge latency matters because it is unavoidable: it is paid on every
request, before a single token exists, and no prompt engineering removes it. Where an API key is
available, inference time-to-first-token is measured separately and shown on the region pages with the
model named next to the figure. Likewise, an unauthenticated probe cannot see errors that hit only some
models or some accounts — the kind a status page usually reports — which is why xAI’s
own reports are shown next to the measurements rather than folded into them.