- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Groq. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 53m it lasted.
Anything that failed between 2025-09-08 21:08 UTC and 2025-09-08 23:01 UTC may need a replay.Subscribe to Groq's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=groq works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Groq 3
- identified
We have identified an issue where a small portion of requests against llama-3.3-70b-versatile are returning degraded output. A fix is in progress, Users may still see the issue until the fix is fully deployed.
provider
- monitoring
We have implemented a fix and are no longer seeing degraded output from llama-3.3-70b. The team is monitoring this model to ensure continued performance.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2d6f40e087
Is Groq still down?
No, this incident was resolved 2025-09-08 23:01 UTC. For Groq's live state, see https://down.guide/providers/groq.
How long did it last?
1h 53m, from 2025-09-08 21:08 UTC to 2025-09-08 23:01 UTC, by the times Groq posted.
What caused it?
Groq hasn't published a root cause. If it does, it shows here.
Where does this come from?
Groq's official status page, https://groqstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.