Skip to main content
Groq

Elevated Latency on Search Tooling

Degraded Lasted 40m · started · Groq's page

Level
confirmed
Worst impact
Degraded
Down Index
16of 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 40m it lasted.

    Anything that failed between 2025-09-10 17:04 UTC and 2025-09-10 17:45 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

  1. investigating

    We are investigating an issue causing elevated latency on search tooling affecting the **groq/compound, groq/compound-mini, openai/gpt-oss-120b and openai/gpt-oss-20b** models. The team is working to identify the cause and remediate.

    provider

  2. monitoring

    A fix has been implemented and performance is improving. We’re now monitoring the models to ensure stability. If all remains normal, we will resolve the incident in the next update.

    provider

  3. resolved

    This issue 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-288340199a

Is Groq still down?

No, this incident was resolved 2025-09-10 17:45 UTC. For Groq's live state, see https://down.guide/groq.

How long did it last?

40m, from 2025-09-10 17:04 UTC to 2025-09-10 17:45 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.