Loading status…
Loading status…
Groq status · AI & APIs · checked (0s ago)
Also searched as GroqCloud, Groq API.
No — Groq is not down. All Groq systems are reported operational.
According to Groq's official status page, Groq was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Groq's feed reported no outage in 100.00% of our checks.
Everything above is read from Groq's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Groq in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Groq runs open models on its own LPU inference hardware and sells access through GroqCloud and an OpenAI-compatible API. The selling point is latency — very fast token generation — which is also what people notice first when something is wrong.
Groq's status page reports the API and the console. Because Groq's capacity is its own silicon rather than rented GPUs, capacity pressure shows up as rate limiting and queueing more readily than at providers who can scale horizontally, and that is normally posted as degraded performance rather than an outage.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Groq's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Groq was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 0s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Groq's status endpoint.
Groq has published 19 incidents in the last 12 months, newest first. Only what Groq posted itself — not every problem users hit.
resolved · Jul 1, 11:01 PM (80d ago)
resolved · Mar 19, 12:51 PM (184d ago)
resolved · Feb 7, 10:02 AM (224d ago)
resolved · Feb 5, 06:09 PM (226d ago)
resolved · Feb 5, 01:23 PM (226d ago)
resolved · Jan 26, 11:17 PM (236d ago)
resolved · Jan 24, 04:53 AM (239d ago)
resolved · Dec 24, 11:01 PM (269d ago)
resolved · Dec 17, 07:11 AM (276d ago)
resolved · Dec 6, 06:58 PM (287d ago)
resolved · Dec 2, 05:36 PM (291d ago)
resolved · Nov 18, 11:52 AM (305d ago)
resolved · Nov 5, 08:03 PM (318d ago)
resolved · Nov 4, 02:11 AM (320d ago)
resolved · Oct 22, 03:51 PM (332d ago)
resolved · Oct 21, 03:19 PM (333d ago)
resolved · Oct 14, 09:16 PM (340d ago)
resolved · Oct 6, 11:58 PM (348d ago)
resolved · Oct 6, 06:53 PM (348d ago)
Free-tier rate limits are strict and per-model; a 429 is far more likely than an outage. Models are deprecated and removed on a rolling basis, so a request naming a model that no longer exists returns an error that has nothing to do with availability. If throughput is merely slower than usual rather than failing, that is capacity, and Groq does not always post it.
Groq is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.