Groq status — and how to poll it yourself

Snapshot: Aug 31, 2026 9:30 AM ET · Statuses shown are build-time snapshots — they refresh on each site rebuild. Live auto-refresh ships post-launch.

At this snapshot, 8 of the 9 providers on our status board reported fully operational. Here is where Groq stood, and how to get the same answer from its status API without a browser.

Status pagehttps://groqstatus.com
Snapshot statusOperational All Systems Operational (as of Aug 31, 2026 9:30 AM ET)
Components20/20
Status API formatstatuspage-v2
JSON endpointhttps://groqstatus.com/api/v2/status.json
Gotchastatus.groq.com redirects to groqstatus.com; fetch the API on groqstatus.com
Verificationverified — live fetch on 2026-08-31

The 20 components Groq reports status for

When Groq says "operational", this is the granularity behind the claim — the component list its own status feed publishes, fetched 2026-08-31. All were reported operational at snapshot time. If an incident hits, these are the names its status page will scope it to.

Polling Groq's status programmatically

Atlassian Statuspage v2. GET /api/v2/status.json returns status.indicator (none | minor | major | critical) and a human description; GET /api/v2/components.json returns per-component state.

curl -s https://groqstatus.com/api/v2/status.json

Gotcha (verified 2026-08-31): status.groq.com redirects to groqstatus.com; fetch the API on groqstatus.com

Everything above was verified against the live endpoint on 2026-08-31 — nothing is inferred from platform defaults. If the endpoint moved, tell us.

Model retirements — Groq

Our 129-row deprecations table tracks the providers that publish dated, citable retirement schedules (OpenAI, Anthropic, Google Vertex AI and Azure OpenAI). Groq publishes no dated model-retirement schedule we could verify against its own docs — absence here means absence of a published schedule, not a no-deprecation guarantee. Pin model versions and watch the provider's changelog either way.

Other providers