- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2025-12-17 07:11 UTC and 2025-12-14 13:30 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 4
- investigating
We are currently investigating a potential network issue at our DMM1 that is impacting system capacity. Users may experience slower response times or intermittent failures due to reduced resources. Our engineering team is working to identify the root cause and remediate the problem.
provider
- identified
We have identified a failure in our DMM1 infrastructure that is causing reduced capacity and network latency. The team has isolated the cause to the Salam link confirmed down and the Mobily link operating at full capacity, resulting in significant packet loss and is working on restoring capacity. Users continue to see Network latency.
provider
- monitoring
We have restored capacity in DMM 1 and services are beginning to recover. Users should gradually see network performance return to normal. We’re now monitoring the infrastructure to ensure stability.
provider
- resolved
**The data center capacity issue has been resolved. All services are operating at normal capacity. The incident was caused by a failed ARP entry on the network gateway device caused the Salam network link to go down in the DMM1 data center, which has been addressed. We apologize for the disruption and appreciate 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-0b0bedeec1
Is Groq still down?
No, this incident was resolved 2025-12-14 13:30 UTC. For Groq's live state, see https://down.guide/groq.
How long did it last?
0m, from 2025-12-17 07:11 UTC to 2025-12-14 13:30 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.