Skip to content

Outage tracker

Groq: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, Groq's declared record, and how the two compare.

← Back to Groq's live status

We started measuring Groq on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Groq's own status page declared. Below it, any public chatter we saw about Groq and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Groq's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Groq in the last 24 hours, which is not evidence that nothing is wrong.
Groq's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Groq's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Groq next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%1841
US-West100.00%1834
Europe100.00%1760
Asia-Pacific100.00%1560
US-Central73.14%175
Canada100.00%175
UK100.00%174
Southeast Asia100.00%143
Australia69.50%141
South America100.00%165

Monthly summary

Tracking Groq since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Groq: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Groq's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Groq in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Groq's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Groq since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Groq's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Data Center Failure Impacting CapacityMinor incident
Jul 1, 2026, 11:01 PM UTC to Jul 2, 2026, 12:35 AM UTC (1h 34m)resolved
their latest update (Jul 2, 2026, 12:35 AM UTC): 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**.
openai/gpt-oss-120b Performance IssueMinor incident
Mar 19, 2026, 12:51 PM UTC to Mar 19, 2026, 1:50 PM UTC (59 min)resolved
their latest update (Mar 19, 2026, 1:50 PM UTC): 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 pati…
meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceMinor incident
Feb 7, 2026, 10:02 AM UTC to Feb 7, 2026, 11:34 AM UTC (1h 33m)resolved
their latest update (Feb 7, 2026, 11:34 AM UTC): This incident has been resolved. Thank you for your patience.
meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceMinor incident
Feb 5, 2026, 6:09 PM UTC to Feb 5, 2026, 6:32 PM UTC (23 min)resolved
their latest update (Feb 5, 2026, 6:32 PM UTC): The issues affecting meta-llama/llama-4-scout-17b-16e-instruct have been **resolved**. The model is once again operating normally. We apologize for the disruption and thank you for your patience.
meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceMinor incident
Feb 5, 2026, 1:23 PM UTC to Feb 5, 2026, 3:07 PM UTC (1h 44m)resolved
their latest update (Feb 5, 2026, 3:07 PM UTC): The issues affecting meta-llama/llama-4-scout-17b-16e-instruct have been fully **resolved**. The model is operating normally. We apologize for the disruption and thank you for your patience.
meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceMinor incident
Jan 26, 2026, 11:17 PM UTC to Jan 27, 2026, 1:11 AM UTC (1h 54m)resolved
their latest update (Jan 27, 2026, 1:11 AM UTC): This incident has been resolved. Thank you for your patience.
Data Center Failure Impacting Model Latency - SYDMinor incident
Jan 24, 2026, 4:53 AM UTC to Jan 24, 2026, 7:23 AM UTC (2h 31m)resolved
their latest update (Jan 24, 2026, 7:23 AM UTC): This incident is now resolved.
Model Performance or Availability Issue: llama-3.3-70b-versatileMinor incident
Dec 24, 2025, 11:01 PM UTC to Dec 25, 2025, 12:16 AM UTC (1h 15m)resolved
their latest update (Dec 25, 2025, 12:16 AM UTC): The issues affecting **llama-3.3-70b-versatile** have been **resolved**. The model is operating normally. We apologize for the disruption and thank you for your patience.
Data Center Failure Impacting Capacity - DMM1Minor incident
Dec 17, 2025, 7:11 AM UTC to Dec 14, 2025, 1:30 PM UTC (0 min)resolved
their latest update (Dec 14, 2025, 1:30 PM UTC): **The data center capacity issue has been resolved. All services are operating at normal capacity. The incident was caused by a failed ARP entry on the network gateway device caused the Salam network link to go down in the DMM1 data center, which has been addressed. We apologize …
meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceMinor incident
Dec 6, 2025, 6:58 PM UTC to Dec 6, 2025, 8:23 PM UTC (1h 25m)resolved
their latest update (Dec 6, 2025, 8:23 PM UTC): The issues affecting meta-llama/llama-4-scout-17b-16e-instruct , meta-llama/llama-4-maverick-17b-128e-instruct, & groq/compound have been **resolved**. The models are operating normally. We apologize for the disruption and thank you for your patience.

Showing the 10 most recent of 25 incidents Groq has declared in the history we hold.

These entries are Groq's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Groq's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Groq's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Groq since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Groq decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Groq believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.