Grok in X incident history
The last recorded incident affecting Grok in X started on September 3, 2026. Every figure on this page is computed from our archive of SpaceXAI's public incident reporting.
- Incidents (archive)
- 6
- Last 30 days
- 0
- Median duration
- 2 h 37 min
- Total incident time
- 18 h 36 min
By month
- September 20261 · 3 h 36 min
- March 20261 · 2 h 23 min
- February 20261 · 51 min
- January 20263 · 11 h 46 min
Incidents affecting Grok in X
- September 3, 2026Models outageMajor · 3 h 36 min
- March 10, 2026Grok in X is Temporarily UnavailableMajor · 2 h 23 min
- February 12, 2026Grok is Temporarily Unavailable.Major · 51 min
- January 27, 2026Grok is Temporarily Unavailable in XMajor · 6 h 32 min
- January 26, 2026Grok is Temporarily Unavailable in XMajor · 2 h 51 min
- January 24, 2026Grok is Temporarily Unavailable in XMajor · 2 h 23 min
How this is counted
- Source. SpaceXAI's public incident reporting for Grok. We do not probe, ping or measure the services ourselves, so nothing here is an availability measurement.
- What we count. Minutes of the month that fell inside a recorded incident window for that component — from the reported start to the reported resolution, clipped to the month.
- What we do not count. Severity is ignored: an incident logged as degraded performance counts the same as a full outage. Unreported disruption, regional differences and per-user impact are invisible to us. An incident window is not the same thing as downtime.
- Overlaps. Figures are per component only, never aggregated into one service-level number. Within a component, overlapping incidents count the shared minutes once; the same minute can appear under several components when an incident affected several.
Computed from our incident archive, which starts on — 638 days deep.