Groq Cloud Outage History

Groq Cloud is up right now

Groq Cloud had 21 outages in the last 2 years totaling 39h 48m of downtime — averaging 0.9 incidents per month.

There were 21 Groq Cloud outages since August 25, 2025 totaling 39h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://groqstatus.com

Minor July 2, 2026

Data Center Failure Impacting Capacity

Detected by Pingoru
Jul 02, 2026, 12:35 AM UTC
Resolved
Jul 02, 2026, 12:35 AM UTC
Duration
—
Affected: openai/gpt-oss-20bllama-3.3-70b-versatile
Timeline · 5 updates
  1. investigating Jul 01, 2026, 11:01 PM UTC

    Status: 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. Affected components openai/gpt-oss-20b (Degraded performance) llama-3.3-70b-versatile (Degraded performance)

  2. identified Jul 01, 2026, 11:11 PM UTC

    Status: 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. Affected components openai/gpt-oss-20b (Degraded performance) llama-3.3-70b-versatile (Degraded performance)

  3. identified Jul 01, 2026, 11:27 PM UTC

    Status: 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. Affected components openai/gpt-oss-20b (Degraded performance) llama-3.3-70b-versatile (Operational)

  4. monitoring Jul 01, 2026, 11:48 PM UTC

    Status: 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. Affected components openai/gpt-oss-20b (Operational) llama-3.3-70b-versatile (Operational)

  5. resolved Jul 02, 2026, 12:35 AM UTC

    Status: 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. Affected components openai/gpt-oss-20b (Operational) llama-3.3-70b-versatile (Operational)

Read the full incident report →

Minor March 19, 2026

openai/gpt-oss-120b Performance Issue

Detected by Pingoru
Mar 19, 2026, 01:50 PM UTC
Resolved
Mar 19, 2026, 01:50 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 19, 2026, 12:51 PM UTC

    Status: Identified We have identified the problem affecting the openai/gpt-oss-120b model. The issue has been traced to malicious traffic patterns. A fix is in progress, we are working to block the source of these requests. Users may still see degraded performance from requests made to openai/gpt-oss-120b as we identify and block the orgs from which this traffic is originating.

  2. monitoring Mar 19, 2026, 01:23 PM UTC

    Status: Monitoring We have implemented a fix for openai/gpt-oss-120b and performance is improving. We’re now monitoring the model to ensure stability persists. If all remains normal, we will resolve the incident in the next update.

  3. resolved Mar 19, 2026, 01:50 PM UTC

    Status: Resolved The issues affecting openai/gpt-oss-120b have been resolved. The model is operating normally. Actions were taken to cancel billing plans and restrict verification status of organizations engaged in coordinated abuse. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Minor February 7, 2026

meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance

Detected by Pingoru
Feb 07, 2026, 11:34 AM UTC
Resolved
Feb 07, 2026, 11:34 AM UTC
Duration
—
Affected: meta-llama/llama-4-scout-17b-16e-instruct
Timeline · 5 updates
  1. investigating Feb 07, 2026, 10:02 AM UTC

    Status: Investigating We are currently investigating reports of an issue with meta-llama/llama-4-scout-17b-16e-instruct. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing logs and infrastructure to identify the cause. Affected components meta-llama/llama-4-scout-17b-16e-instruct (Degraded performance)

  2. investigating Feb 07, 2026, 10:36 AM UTC

    Status: Investigating We are continuing to investigating an issue with meta-llama/llama-4-scout-17b-16e-instruct. Users may be experiencing elevated error rates or slow response time. Other models remain operational. Our team is continuing to analyze logs and infrastructure to identify the cause. Affected components meta-llama/llama-4-scout-17b-16e-instruct (Degraded performance)

  3. identified Feb 07, 2026, 10:59 AM UTC

    Status: Identified We have implemented a fix for meta-llama/llama-4-scout-17b-16e-instruct however performance is still degraded. We’re continuing to investigate the models to determine the cause of the issues. Affected components meta-llama/llama-4-scout-17b-16e-instruct (Degraded performance)

  4. monitoring Feb 07, 2026, 11:13 AM UTC

    Status: Monitoring We have implemented a new fix for meta-llama/llama-4-scout-17b-16e-instruct & groq/compound and performance has improved. We’re continuing monitor the models to ensure stability persists. If all remains normal, we will resolve the incident in the next update. Affected components meta-llama/llama-4-scout-17b-16e-instruct (Operational)

  5. resolved Feb 07, 2026, 11:34 AM UTC

    Status: Resolved This incident has been resolved. Thank you for your patience. Affected components meta-llama/llama-4-scout-17b-16e-instruct (Operational)

Read the full incident report →