- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Groq. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 15m it lasted.
Anything that failed between 2025-12-24 23:01 UTC and 2025-12-25 00:16 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’ve identified an issue causing 503s for the `llama-3.3-70b-versatile` production model. We’ve started mitigation. Error rates are improving, but some requests may still fail while we continue tuning and monitoring.
provider
- monitoring
We have **implemented a fix** for **llama-3.3-70b-versatile** and performance is improving. The team is continuing to work the issue and we hope to have it resolved shortly.
provider
- resolved
The issues affecting **llama-3.3-70b-versatile** have been **resolved**. The model is operating normally. We apologize for the disruption and thank you for your patience.
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-6a264f9327
Is Groq still down?
No, this incident was resolved 2025-12-25 00:16 UTC. For Groq's live state, see https://down.guide/groq.
How long did it last?
1h 15m, from 2025-12-24 23:01 UTC to 2025-12-25 00:16 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.