Skip to main content
Groq

Data Center Failure Impacting Capacity

Degraded Lasted 1h 34m · started · Groq's page

Level
confirmed
Worst impact
Degraded
Regions
us
Down Index
22of 100

What to do

  • Check whether you use Groq in us. 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 34m it lasted.

    Anything that failed between 2026-07-01 23:01 UTC and 2026-07-02 00:35 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 5

  1. investigating

    We are currently investigating a potential issue at one of our US Central data centers that is impacting system capacity. Users **may experience higher latencies** due to reduced resources. Our engineering team is working to identify the root cause and remediate the problem.

    provider

  2. identified

    We have **identified a cooling system failure** at one of our **US Central** data centers that is causing **reduced capacity**. The team is **working on restoring capacity**. Users **continue to see elevated latencies for specific models**.

    provider

  3. identified

    A power loss issue at approximately 22:20pm UTC led to a subsequent **cooling system failure** at one of our **US Central** data centers that is causing **reduced capacity**, primarily for the `openai/gpt-oss-20b` model. The team is **working on restoring capacity**.

    provider

  4. monitoring

    We have **redistributed and allocated more capacity to production models** in **the US Central region.** Users should **see performance return to normal**. We’re now **monitoring** the infrastructure to ensure stability.

    provider

  5. resolved

    The **capacity issue has been resolved**. All services are operating at normal capacity. The incident was caused by a **power loss issue that led to a cooling system failure at one of our US Central data centers**. We apologize for any 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-89d7c85f34

Is Groq still down?

No, this incident was resolved 2026-07-02 00:35 UTC. For Groq's live state, see https://down.guide/groq.

How long did it last?

1h 34m, from 2026-07-01 23:01 UTC to 2026-07-02 00:35 UTC, by the times Groq posted.

What was affected?

Groq named in us.

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.