- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 25of 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 18m it lasted.
Anything that failed between 2026-10-12 18:17 UTC and 2026-10-12 18:36 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.
Root cause
Root cause: **hardware connectivity issues**.Read the postmortem
Updates from Groq 2
- identified
We have **identified the problem** affecting the **minimaxai/minimax-m2.7** service. The issue was traced to **hardware connectivity issues**. A fix is in progress. Users may still see **API failures** until the fix completes.
provider
- resolved
The issues affecting **minimaxai/minimax-m2.7** have been **resolved**. The model is operating normally. Root cause: **hardware connectivity issues**. 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-664202f09b
Is Groq still down?
No, this incident was resolved 2026-10-12 18:36 UTC. For Groq's live state, see https://down.guide/groq.
How long did it last?
18m, from 2026-10-12 18:17 UTC to 2026-10-12 18:36 UTC, by the times Groq posted.
What caused it?
Groq wrote: "Root cause: **hardware connectivity issues**." The postmortem: https://groqstatus.com/incidents/01M4RNBH8R850TCY7FTW0VBJ1T
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.