STATUS

AI service status

Official status and recent incidents for the four upstream providers: OpenAI, Claude, Gemini and Grok. Upstream hiccups are usually amplified at the relay layer — check here first to tell an upstream outage apart from a broken relay.

Status unavailable for some providers

Updated 8/14/2026, 09:32:11 · Results are cached for 60 seconds; reload later to fetch again.

OpenAI

Operational

All Systems Operational

All 25 services operational

Official status pageOfficial status page ↗

Claude

Unknown

Could not reach the official status page — please check it directly.

Official status pageOfficial status page ↗

Gemini

Operational

All 3 services operational

Official status pageOfficial status page ↗

Grok

Operational

No per-component status published

Official status pageOfficial status page ↗

Why does an upstream outage look like a broken relay?

A relay doesn't generate answers itself — it forwards your request to the official endpoints of OpenAI, Anthropic, Google or xAI. The moment an upstream provider rate-limits, degrades or goes down, all the relay sees is timeouts, 429s and 5xx. Its retries, queueing and multi-channel failover then amplify that blip into longer latency, truncated responses, or even a silent switch to a different model — which looks almost exactly like the relay diluting your traffic.

Telling the two apart takes two steps. First check whether the provider on this page is having an incident right now: if the time window lines up, it is almost certainly upstream and will clear on its own. If it doesn't line up, run a fidelity check with the same key — when tokenizer fingerprints, thinking signatures or the identity echo don't match, this isn't upstream turbulence, it's the relay swapping models on you.

  1. 7/7/2026, 15:40:26GrokResolved[API (us-west-2.api.x.ai)] Imagine Video 1.5 is experiencing lower success rate and higher latency
  2. 7/7/2026, 15:36:32GrokResolved[API (eu-west-1.api.x.ai)] Imagine Video 1.5 is experiencing lower success rate and higher latency
  3. 7/7/2026, 15:35:34GrokResolved[API (us-east-1.api.x.ai)] Imagine Video 1.5 is experiencing lower success rate and higher latency
  4. 7/2/2026, 00:44:20GrokResolved[API (us-east-1.api.x.ai)] Grok Build 0.1 unavailable
  5. 6/17/2026, 12:13:15GrokResolved[API (eu-west-1.api.x.ai)] Increased Error rate on Image Generation Endpoint
  6. 6/17/2026, 12:12:07GrokResolved[API (us-east-1.api.x.ai)] Increased Error rate on Image Generation Endpoint
  7. 6/3/2026, 10:16:29GrokResolved[API (us-east-1.api.x.ai)] Increased Failure Rate of Image Generation and Editing
  8. 6/3/2026, 10:16:29GrokResolved[API (eu-west-1.api.x.ai)] Increased Failure Rate of Image Generation and Editing
  9. 5/26/2026, 15:10:45GrokResolved[API Console] Grok Build Caching broken
  10. 5/18/2026, 01:58:00GrokResolved[API Console] Console not loading

Incident titles are quoted verbatim from each provider.

Disclaimer

This page only relays status information published by each provider. It may lag or omit events and is not an availability guarantee — the official status pages take precedence.