New Multi-region uptime checks and custom-domain status pages

Groq Outage History

Daily provider-status observations and published incident history for Groq.

Operational

Groq is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Groq for future changes.

96.4% of 56 verified observed days had no reported provider issue

90-Day Trend

Jul 24Oct 21

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 23 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

2 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

July 2026
Data Center Failure Impacting Capacity
minor Source not attested
Last archived state: resolved
View archived record details
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.
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**.
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**.
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.
March 2026
Model Performance or Availability Issue
Source not attested
Last archived state: resolved
View archived record details
monitoring
identified