Is Groq down right now?
Authenticated API inference - 2 models monitored · How we classify outages
Groq is currently operational - 337ms HTTP response. Last checked . 90-day uptime: 97.5%. Groq API: all 2 models responding - fastest TTFT 226ms.
Stay informed
Follow @tickerr_ai
We post when tier 1 LLM APIs go down - before the official status page updates.
Follow on X →Or get the weekly reliability digest:
Add a status badge
Show live Groq status on your site, README, or docs.
HTTP uptime (90d)
97.5%
20 incidents (90d)
HTTP response now
337ms
HTTP p50 (7d)
385ms
median ping response
HTTP p95 (7d)
1606ms
tail ping response
API Inference Monitoring
Live · every 5 minBest TTFT (p50)
226ms
time to first token
Best throughput
1579tok/s
output tokens/sec (24h avg)
Min success rate
100%
worst model (24h)
P50 = typical speed. P95 = worst case 95% of the time. Measured by Tickerr's independent inference checks. Requires ≥10 checks to display.
TTFT over 24 hours
ⓘ Authenticated streaming API calls via native fetch. TTFT = milliseconds from request start to first streamed token chunk. Throughput = output tokens ÷ generation time. Checks run from Vercel us-east-1. Independent of the provider's official status page.
Agent monitoring active · 2 agents reporting · Powered by Tickerr MCP
HTTP endpoint response time (7 days)
p50 385ms·p95 1606msⓘ HTTP response times to Groq's status endpoint - measures infrastructure availability, not API inference speed. For TTFT and model-level API status, see the Groq API Status section above.
90-day uptime
Incident history
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 4.1× above the rolling p50 baseline (1600ms vs p50 391ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 13× above the rolling p50 baseline (5376ms vs p50 415ms). The service is responding …
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 5.3× above the rolling p50 baseline (1920ms vs p50 359ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 2.1× above the rolling p50 baseline (886ms vs p50 419ms). The service is responding …
llama-3.3-70b-versatile API Latency Degraded
Independent monitoring detected elevated API latency for llama-3.3-70b-versatile. Current TTFT is 6.1× above the rolling p50 baseline (1425ms vs p50 233ms). The service is responding but slower than n…
Status: Identified We have identified a cooling system failure at one of our US Central data centers that is causing reduced capacity. The team is working on restoring capacity. Users continue to see …
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 2.2× above the rolling p50 baseline (831ms vs p50 379ms). The service is responding …
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 3.1× above the rolling p50 baseline (1040ms vs p50 332ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 2.8× above the rolling p50 baseline (1107ms vs p50 392ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 2.5× above the rolling p50 baseline (1022ms vs p50 404ms). The service is responding…
llama-3.3-70b-versatile API Latency Degraded
Independent monitoring detected elevated API latency for llama-3.3-70b-versatile. Current TTFT is 7.7× above the rolling p50 baseline (1838ms vs p50 240ms). The service is responding but slower than n…
llama-3.3-70b-versatile API Latency Degraded
Independent monitoring detected elevated API latency for llama-3.3-70b-versatile. Current TTFT is 6.9× above the rolling p50 baseline (1661ms vs p50 241ms). The service is responding but slower than n…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 3.9× above the rolling p50 baseline (3633ms vs p50 941ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 2.2× above the rolling p50 baseline (1331ms vs p50 606ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 4.8× above the rolling p50 baseline (4263ms vs p50 889ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 3.7× above the rolling p50 baseline (1922ms vs p50 524ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 7.1× above the rolling p50 baseline (5046ms vs p50 710ms). The service is responding…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 3.8× above the rolling p50 baseline (1512ms vs p50 394ms). The service is responding…
llama-3.3-70b-versatile API Latency Degraded
Independent monitoring detected elevated API latency for llama-3.3-70b-versatile. Current TTFT is 2.3× above the rolling p50 baseline (516ms vs p50 227ms). The service is responding but slower than no…
meta-llama/llama-4-scout-17b-16e-instruct API Latency Degraded
Independent monitoring detected elevated API latency for meta-llama/llama-4-scout-17b-16e-instruct. Current TTFT is 5.2× above the rolling p50 baseline (2158ms vs p50 414ms). The service is responding…
Related pages
Groq API not working? Common error codes
If Groq's API is returning errors, the table below explains what each code means and how to fix it. If errors are widespread, check the live status above - a service incident will appear there within minutes.
| Error | What it means & what to do |
|---|---|
| HTTP 429 | Rate limit hit - check x-ratelimit-remaining headers; free tier is 30 RPM |
| HTTP 503 | Service overloaded - Groq queues fill fast under heavy load; retry |
Note: Tickerr monitors Groq's status endpoint, not individual API calls. An HTTP 429 or 500 in your app may be specific to your account tier - check the rate limits page for plan-specific thresholds.
About Groq status
Groq is an AI inference provider offering extremely fast LLM inference using custom LPU hardware. Groq downtime is rare due to their hardware architecture but can affect API users building latency-sensitive apps. Groq offers free and paid tiers with separate rate limits.