Skip to main content

Is Grok Down?

No — Grok is up

Reachable from all 6 checked regions

Average response time: 384ms

Last checked · checks run every 6 hours

Official status page: https://status.x.ai

Grok uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
426ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 16 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

16-day clean streak
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: 100.00% uptime, 29 checks
Aug 4: 100.00% uptime, 26 checks
Aug 5: 100.00% uptime, 24 checks
Aug 6: 100.00% uptime, 31 checks
Aug 7: 100.00% uptime, 31 checks
Aug 8: 100.00% uptime, 35 checks
Aug 9: 100.00% uptime, 36 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 29 checks
Aug 13: 100.00% uptime, 28 checks
Aug 14: 100.00% uptime, 38 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 31 checks
Aug 17: 100.00% uptime, 28 checks
Aug 18: 100.00% uptime, 35 checks
Jul 20 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
531ms
DNS 0ms TCP 1ms TLS 6ms TTFB 280ms
arn
587ms
DNS 0ms TCP 1ms TLS 5ms TTFB 277ms
bom
364ms
DNS 0ms TCP 2ms TLS 14ms TTFB 328ms
cdg
317ms
DNS 0ms TCP 1ms TLS 10ms TTFB 230ms
dfw
218ms
DNS 1ms TCP 4ms TLS 7ms TTFB 183ms
sin
HTTP 403 · challenge

Answered in 21ms — the origin is serving traffic, it just refused our client.

sjc
291ms
DNS 0ms TCP 1ms TLS 8ms TTFB 210ms
syd
1150ms
DNS 0ms TCP 1ms TLS 5ms TTFB 537ms
yyz
187ms
DNS 0ms TCP 1ms TLS 5ms TTFB 151ms

What Grok does

Grok is the AI assistant built by xAI, used at grok.com, through iOS and Android apps, inside the X app, and through an API that developers call directly. xAI serves that API from three regional endpoints, so companies building on it depend on Grok the same way they would on any other model provider.

What an outage looks like

xAI tracks Grok separately on iOS, Android, the web and inside X, so one surface can fail while the others answer normally. Its status page splits each API region into inference and non-inference measurements, which means model responses can fail while sign-in and account pages keep working. Single Sign-On is its own component, so a login problem is not the same as a model problem.

What to do about it

Check status.x.ai, which is where status.grok.com redirects. It lists Grok on iOS, Android, web and in X, plus Single Sign-On, the API Console, the docs and three regional API endpoints, each showing live inference and non-inference percentages rather than only a coloured pill. If one region's inference is degraded, an API caller can often move to another endpoint.

Is it down for everyone, or just you?

If this page says Grok is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

C
ChatGPT
C
Claude
G
Google Gemini
O
OpenRouter

Grok outage FAQ

Is Grok down, or just the app I am using?
xAI tracks four Grok surfaces separately: iOS, Android, the web, and Grok inside the X app. One can be unavailable while the others answer normally, so whichever app you happened to open is not a reliable test on its own. Open status.x.ai and read the line for your platform rather than judging from a single failed conversation.
Is Grok the same thing as Groq?
No, and they are different companies. Grok is the AI assistant from xAI at grok.com, with its status published at status.x.ai. Groq, spelled with a q, is a separate company selling fast model inference at groq.com and runs its own status page. Search results and autocorrect mix the two constantly, so check the spelling before trusting any outage report.
Does a Grok outage affect the rest of X?
Usually not. xAI lists Grok in X as one component among several, separate from the xAI website and from the API, and X itself runs on its own infrastructure. If the timeline loads normally but Grok will not answer inside it, that points at the Grok component rather than at X being down.
What do inference and non-inference mean on the xAI status page?
They separate the model from everything around it. xAI publishes both figures for each regional API endpoint, so you can see whether generating a response is what is failing or whether the surrounding request handling is. A high non-inference number alongside degraded inference points at the model tier rather than at connectivity, a distinction most status pages do not offer.

How we measure this

  • We request Grok's public endpoint every 6 hours from Fly.io regions across six continents — 6 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Grok publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Grok goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required