Groq: GroqCloud Console Errors Affecting Multiple Regions

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 23m it lasted.
Anything that failed between 2026-10-12 03:37 UTC and 2026-10-12 04:00 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.

investigatingOct 12, 2026, 3:37 AM UTC
We are currently investigating increased error rates on our GroqCloud console (including metrics, /models API endpoints, and API key creation). Users may receive 500 errors when making requests to console.groq.com. Our engineers are isolating the issue.
provider
monitoringOct 12, 2026, 3:47 AM UTC
We've mitigated the errors on the GroqCloud console and functionality has been restored. Inference API requests are not affected, and we will provide additional updates here.
provider
resolvedOct 12, 2026, 4:00 AM UTC
The Groqcloud console issue has been resolved. All services are operating normally. We apologize for the disruption and appreciate your patience.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Groq still down?

No, this incident was resolved 2026-10-12 04:00 UTC. For Groq's live state, see https://down.guide/providers/groq.

How long did it last?

23m, from 2026-10-12 03:37 UTC to 2026-10-12 04:00 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.