Pulse
IS GROK DOWN RIGHT NOW?
Grok is not one service: grok.com, Grok in X, the iOS and Android apps and the API fail independently, so the answer to “is Grok down” depends on which surface you are on. We check the official status feed every five minutes.
The official status feed could not be reached on this page load, so we cannot confirm the current state. The incident record below is unaffected.
Outage history →Uptime by month →Latest release →Status by component →
1 process is beyond their alert threshold
Published history remains available, but new readings may be missing until collection resumes. Each process and its own threshold are shown below.
Grok status by surface
Checked
The live status feed could not be reached. The incident record below is unaffected.
Where does this status data come from?
This site is collected automatically from the official status feed. If a collector stops, it is stated here rather than left as a silent gap in the record.
Alert delivery — a process past its threshold is shown on this page and sent once by email from notify.grok46.com. One notice per incident; the alert resets after the next successful run.
Last probe · 0 failed of 96 in 24 h
Alert threshold 2 h
- Status feednot publishing
Last 24 h: 286 runs, seen 5434, new 4862, published 0
Alert threshold 2 h
54 incidents collected but never given a page for more than 24 hours. Collection is working; publication is not.
Last checked
- Changelog feedno new rows
Last 24 h: 24 runs, seen 24, new 0, published 0
Alert threshold 12 h
The source was read normally and had nothing new. Rows seen counts everything the source returned; new counts what entered or changed here.
Last checked
- xAI documentationnothing fetched
Last 24 h: 0 runs, seen 0, new 0, published 0
Alert threshold 48 h
Nothing was fetched at all in the last 24 hours. This is a collection failure, not a quiet week.
Last checked
- Community feednot reporting
Last 24 h: 1 runs, seen 3, new 0, published 0 · 1 failed
Alert threshold 48 h · incident open since
The source was read normally and had nothing new. Rows seen counts everything the source returned; new counts what entered or changed here.
Last checked
No successful run in the last 990 h 53 min. New readings may be missing until collection resumes.
- Weekly digestnothing fetched
Last 24 h: 0 runs, seen 0, new 0, published 0
Alert threshold 192 h
Nothing was fetched at all in the last 24 hours. This is a collection failure, not a quiet week.
Last checked
Grok outage history
Full archive →- October 7, 2026grok.com6 min
- October 6, 2026Enterprise Voice Degraded0 min
- September 22, 2026Outages across API, Grok.com, and Grok Build26 min
- September 10, 2026Enterprise Voice Degraded12 min
- September 3, 2026Models outage3 h 38 min
- September 3, 2026Models outage3 h 35 min
- September 3, 2026Models outage3 h 37 min
- September 3, 2026Models outage3 h 35 min
- September 3, 2026Models outage3 h 36 min
- September 3, 2026Models outage3 h 36 min
- September 3, 2026Models outage3 h 37 min
- September 3, 2026Models outage3 h 39 min
Is Grok down, or just under high demand?
Most of the time it is the latter. Under high demand is a plan limit being reached on your account, not a service failure — the status feed can report every surface as available at the same moment. If the feed above shows every component available and Grok still refuses you, the answer is your allowance, not an outage.
How often does Grok go down?
The incident archive above is the full record since January 2025, each outage on a permanent page with its duration. For the aggregate view, uptime by month shows availability per calendar month — but only for months the archive fully covers, so no figure there is extrapolated.