GroktrackerIT'S NOT YOU. IT'S GROK.

Components

API — us-east-1 incident history

The last recorded incident affecting API — us-east-1 started on September 3, 2026. Every figure on this page is computed from our archive of SpaceXAI's public incident reporting.

ASK
Incidents (archive)
10
Last 30 days
0
Median duration
2 h 5 min
Total incident time
2737 h 32 min

By month

  • September 20261 · 3 h 37 min
  • July 20261 · 26 min
  • January 20264 · 4 h 40 min
  • October 20251 · 2617 h 30 min
  • May 20252 · 18 h 19 min
  • January 20251 · 93 h

Incidents affecting API — us-east-1

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.