Is Grok down right now?
HostTracker's monitoring network reached grok.com and completed a full check without errors. It has been up for 9d 17h.
Stop finding out from a search - HostTracker's website monitoring checks the services you depend on from 300+ locations and alerts you the moment one changes.
Checking grok.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
Incident history
LAST 90 DAYSAbout Grok outages
Written by the HostTracker monitoring team · updated from live probe data.
Grok is xAI's conversational assistant, reachable both through its own site and app and through its integration with X, which gives it two access paths that can fail separately - the assistant can be unavailable inside X while grok.com works, or the reverse. As a relatively young product growing quickly, its outages skew toward capacity: new model releases and viral moments drive demand spikes that outpace serving capacity, producing errors, queueing and truncated responses rather than a flat unreachable service. Access tiers also matter more here than for older assistants, since availability and limits differ between free and subscriber access, and hitting a limit can look very much like a service failure from the user's side.
Common causes of Grok downtime
Capacity saturation after model launches and viral demand spikes, producing errors and long waits rather than a clean outage
Divergence between grok.com and the X integration, where one path works and the other does not
Rate limits and tier-based quotas that block further requests in a way that resembles an outage
Authentication problems tied to the X account system, which block sign-in while the assistant itself is healthy
Not sure whether it's Grok or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests grok.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Grok being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
That pattern points at the integration rather than the assistant. Grok is reachable through more than one front end, and the path through X involves that platform's own authentication and interface layers, either of which can fail while grok.com keeps serving normally. So a failure in one place and success in the other is genuinely informative: it tells you the model backend is up and the problem is in a specific access path. If neither works, the question becomes whether the service is reachable at all, which the live check on this page answers directly.
Language-model serving is expensive and capacity is finite, so demand spikes - a new model, a widely shared conversation, a news moment - press against limits quickly. The visible result is usually errors, queueing or responses that stop part-way rather than the site becoming unreachable, because the web front end stays healthy while the inference backend sheds load. Retrying after a pause often works, since a new request may land on free capacity. Persistent failure across many attempts and a long period is more likely a genuine incident than ordinary load shedding.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.