AI company founded by Elon Musk. Builds Grok, a general-purpose assistant with real-time access to X (Twitter) content. Positioned as a less-restricted alternative to competing assistants.
Method: a rolling quarter (13 weeks ≈ 91 days). Each cell is one 7-day slice of Statuspage-standard uptime (1 − (critical + 0.3 × major) / window; minors and maintenance excluded; red when the slice dips below the stated SLA).
Grok — Incidents by Day last 30d
MinorMajorCritical
Total 3 incidents
0
0
1
1
1
09-1509-1909-2309-2710-0110-0510-0910-13
Worst Incidents
Ranked by severity-weighted duration (impact × wall-clock). Click any incident for the full update timeline.
Type of Failure
Categorised from the public incident headlines (outage / latency / auth / etc.).
Other
2
67%
Degraded
1
33%
When It Breaks
Incident starts by weekday × hour, UTC. Hover a cell for incident detail.
S
0
M
0
T
Tuesday01:00–02:00 UTC
1incident
1 minor
[Global (api.x.ai)] Outages across API, Grok.com, and Grok BuildSep 22
Tuesday19:00–20:00 UTC
1incident
1 minor
[Voice] Enterprise Voice DegradedOct 6
2
W
Wednesday00:00–01:00 UTC
1incident
1 minor
[grok.com] grok.comOct 7
1
T
0
F
0
S
0
00
06
12
18
HOUR OF DAY · UTC3 incident starts · hover any cell for detail
Hottest hour
Tuesday 01:00 1
Worst day
Tuesday 2
Worst time of day
00:00–01:00 1
How fast they fix things
Distribution of resolution times alongside the 12-week trend so you can see whether they're getting faster or slower.
Typical fix
26m
half of incidents resolve faster
On a bad day
28m
9 in 10 resolve faster than this
Distribution
<15m
1
15m–1h
2
1–4h
0
4–24h
0
24h+
0
+0 ongoing (not counted above)
MTTR Trend (12 weeks)
Are they recovering faster or slower over time? Lower is better.