Live  /  Providers  /  xAI

xAI

x.aiNo open incidents

Independent assessment — SquidGrid is not affiliated with xAI. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

AI · SquidGrid tracks xAI’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what xAI is reporting

Current & recent incidents

Resolved

[Grok Bot] Grok Bot is currently degraded

2026-11-06 13:57 UTC · source

Resolved

[Grok Bot] Computer use in Grok Bot fails for users in a few regions.

2026-11-06 11:49 UTC · source

Resolved

[Review Agents] composer-2.5 degraded

2026-11-05 15:06 UTC · source

Resolved

[Grok Bot] Degraded Performance - Grok Bot

2026-11-05 00:34 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 220 incidents from xAI’s own status page since 2025-01-15: 105 in the last 90 days, against 23 in the 90 days before.

Recent incidents in the archive

Computed by SquidGrid from the incidents xAI published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what xAI has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

xAI runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of xAI is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with xAI.