Groq uptime

From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.

98.94%free of major or critical incidents, last 30 days*

98.94%free of major or critical incidents, last 90 days*

98.82%free of any incident, last 90 days

3incidents started, last 90 days

* Our archive of Groq’s status page starts Oct 9, so the window is shorter.

Last 90 days, by UTC day

Aug 7today

no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive

Last 7 days, by hour

Oct 28, 01:00now

Numbers

Window	Free of major/critical	Free of any incident	Outage time	Incident time	Incidents
Last 30 days*	98.94%	98.82%	6 h 23 min	7 h 7 min	3
Last 90 days*	98.94%	98.82%	6 h 23 min	7 h 7 min	3

This is what Groq itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed 6 minutes ago.

See the incidents: Groq status history · last 90 days · Groq status page (opens in new tab) · Markdown

GGroq uptime

Last 90 days, by UTC day

Last 7 days, by hour

Numbers

Groq uptime