Grok for Android incident history
The last recorded incident affecting Grok for Android started on September 3, 2026. Every figure on this page is computed from our archive of SpaceXAI's public incident reporting.
- Incidents (archive)
- 13
- Last 30 days
- 0
- Median duration
- 1 h 45 min
- Total incident time
- 34 h 36 min
By month
- September 20261 · 3 h 35 min
- March 20262 · 3 h 6 min
- February 20262 · 1 h 25 min
- January 20265 · 13 h 26 min
- August 20251 · 1 h 45 min
- April 20251 · 29 min
- March 20251 · 10 h 50 min
Incidents affecting Grok for Android
- September 3, 2026Models outageMajor · 3 h 35 min
- March 10, 2026Grok is Temporarily UnavailableMajor · 2 h 24 min
- March 2, 2026Grok on Android is Temporarily Unavailable.Major · 42 min
- February 12, 2026Grok is Temporarily Unavailable.Major · 50 min
- February 5, 2026grok-code-fast-1 outageMajor · 35 min
- January 27, 2026Grok is Temporarily UnavailableMajor · 7 h 26 min
- January 27, 2026Grok is Temporarily UnavailableMajor · 15 min
- January 27, 2026Grok.com is Temporarily UnavailableMajor · 18 min
- January 26, 2026Grok is Temporarily Unavailable.Major · 2 h 51 min
- January 24, 2026Grok is Temporarily Unavailable.Major · 2 h 36 min
- August 14, 2025Grok Imagine Response is UnavailableMajor · 1 h 45 min
- April 3, 2025Responses are Temporarily UnavailableMajor · 29 min
- March 10, 2025Partial Outage of Grok Android AppMajor · 10 h 50 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.