AI API status /

Is the Groq API reachable right now?

A live probe of api.groq.com from NetOkay’s edge, a test from your own browser, and why a fast provider makes your own network’s behaviour easier to spot.

In short: The card below shows the latest probe of api.groq.com from eight Cloudflare regions: one GET for /openai/v1/models with a placeholder token. Groq answers in its own JSON: 401 for an invalid key, or 403 Forbidden within milliseconds where Groq refuses the request on policy, for example a region it does not serve. Either is Groq answering, not an outage. Because Groq streams tokens quickly, a stream that arrives “all at once” for you almost always means buffering on your path.

Last updated

Where is api.groq.com reachable from?

Checking…

Loading the latest round from every region…

Loading the latest observation of api.groq.com…

From this browser

—

Not run. One request from your browser, sent only when you ask.

What this proves, and what it does not

Loading…

Groq specifics

API host
api.groq.com, with the OpenAI‑compatible surface under /openai/v1/. Clients built for OpenAI usually only change the base URL and key.
Streaming
OpenAI‑style server-sent events: data: JSON chunks ending with data: [DONE]. Groq’s chunks arrive fast enough that a proxy which buffers a few kilobytes before flushing can turn a stream into a single burst at the end.
What fast delivery reveals
If the homepage SSE check reports events arriving close together, and Groq responses also arrive in one block, the buffering is on your path, not at Groq. The idle stream check tells you whether that path also drops silent connections.
Official status
groqstatus.com publishes incidents for the API and console.
Client defaults
The Groq Python SDK waits only 60 seconds per request (5-second connect) and retries twice; the TypeScript SDK uses 1 minute and 2 retries. That is the shortest default of the providers here, so a slow first token on a queued request can hit the SDK timeout, not only your proxy.

What Groq status codes mean

Code Sent by Meaning
403 API application Policy refusal in Groq’s own JSON (Forbidden): a region Groq does not serve, or a key without permission. Answered within milliseconds at the front door, so it proves reachability, not that your request would succeed.
401 API application Key missing or invalid. The API application produced this answer.
429 API application Rate limit, with retry-after when Groq expects you to wait.
503 API application Capacity: the model is unavailable right now. Retry with backoff.
Every row is an HTTP answer: the host was reached and the request was refused or served. None of them means api.groq.com is unreachable.

Reachable here but failing for you?

  1. Run the homepage SSE check from the network where your app fails. Events arriving close together means something on your path buffers streams, which is what turns Groq’s fast stream into one block. Run the streaming check →
  2. Run the 30‑second idle stream. Closed during the silence points at an idle limit under 30 seconds; fixes for both cases are in the streaming guide. Fixes in the streaming guide →
  3. Compare environments if this browser passes but a container, server or agent fails, then run the CLI from the failing environment against api.groq.com. Compare environments →

Groq API status FAQ

Groq is supposed to be fast. Why is my first token slow?

Time to first token includes your own path: DNS, TLS, any corporate proxy and the request queue at Groq. Compare the response time in the probe above with what your client measures; a large gap is on your side.

I get 401 or 403 from my app. Is that what the probe sees?

The probe carries a placeholder token, so Groq answering 401 is expected, and a 403 Forbidden in Groq’s own JSON within milliseconds is a policy refusal for the Cloudflare location that served you. If your app gets 401 or 403 with a key set, check the header name, the key’s organization and whether Groq serves your region; the probe cannot tell you that.

Does this page tell me whether Groq is down globally?

No. It is one observation from one Cloudflare location, refreshed at most once a minute. Use groqstatus.com for incidents.