Is Grok down?
Live xAI (Grok) API status, pulled from the official status page. If it's green here, the API is up — so the problem is probably on your side.
Is it Grok or is it you?
Before assuming an outage, check the error you're getting — most "Grok not working" reports are client-side:
- 429 Too Many Requests — a rate limit. Your side. Back off and retry with exponential backoff, or request a higher tier.
- 401 / 403 — an invalid or expired API key, or wrong org/project. Your side.
- 400 — a malformed request (bad model string, oversized prompt). Your side — check the model reference.
- 500 / 502 / 503 / timeouts across all calls — usually xAI (Grok)'s side. Confirm on the status page.
What to do during a Grok outage
- Fail over. Route to another provider — compare drop-in alternatives by price and capability.
- Retry smart. Exponential backoff with jitter; don't hammer a recovering API.
- Queue non-urgent work and replay it once the status page goes green.
- Subscribe to the xAI (Grok) status page for incident updates.
xAI (Grok) models & pricing
If you're switching or planning a fallback, here's what xAI (Grok) offers.
| Model | Input /1M | Output /1M | Cost / call* | Context | Type |
|---|---|---|---|---|---|
| Grok 3 mini | $0.100 | $0.300 | $0.0004 | 128K | Fast / cheap |
| Grok 4 Fast 2M context | $0.200 | $0.500 | $0.0007 | 2M | Fast / cheap |
| Grok Code Fast 1 Code-specialised | $0.200 | $1.50 | $0.0017 | 256K | Balanced |
| Grok 4 Flagship | $3.00 | $15.00 | $0.018 | 256K | Flagship |
*Reference cost of one call with 1,000 input + 1,000 output tokens — a neutral yardstick. Use the calculator for your real usage. Cheapest row highlighted.
Is Grok down — FAQ
Is Grok down right now?
Check the live status above — it reads xAI (Grok)'s official status page (https://status.x.ai). Green means all systems operational; amber or red means a degradation or outage on xAI (Grok)'s side, not yours.
How do I know if it's Grok or my own code?
A 429 means you hit a rate limit (your side — back off and retry). 401/403 is an auth or API-key problem (your side). Widespread 500/502/503 errors or timeouts usually mean xAI (Grok) is having an incident — confirm on the status page.
Where is the official xAI (Grok) status page?
https://status.x.ai — it lists current incidents, per-component status (API, console, etc.) and a history of past outages with timelines.
What should I do during a Grok outage?
Fail over to another model or provider if your app supports it (compare alternatives here on AI API Prices), queue non-urgent requests, retry with exponential backoff, and subscribe to the status page for updates.