Skip to content

Outage tracker / Groq

Is Groq down?

I'm having a problem

Awaiting datachecked 3 minutes ago

We reached Groq from 9 of the 10 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

Functional endpoints verified

No outage recorded in the 14 days we have measured Groq (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:05 AM UTC
US-East177 msOperational
US-West289 msOperational
Europe344 msOperational
Asia-Pacific171 msOperational
US-Central326 msAwaiting data
Canada160 msOperational
UK334 msOperational
Southeast Asia403 msOperational
Australia872 msOperational
South America781 msOperational
their status pagetheir claim, not our reading

Groq reports: All systems operational (“All Systems Operational”)

from Groq's own status page, checked Sep 5, 2026, 1:50 AM UTC

Groq's own component breakdown, as they publish it

  • openai/gpt-oss-20bOperational
  • meta-llama/llama-guard-4-12bOperational
  • groq/compound-miniOperational
  • Canopy Labs Orpheus Arabic SaudiOperational
  • meta-llama/llama-4-scout-17b-16e-instructOperational
  • meta-llama/llama-prompt-guard-2-86mOperational
  • moonshotai/kimi-k2-instruct-0905Operational
  • openai/gpt-oss-safeguard-20bOperational
  • qwen/qwen3-32bOperational
  • WebsiteOperational
  • llama-3.1-8b-instantOperational
  • APIOperational
  • Canopy Labs Orpheus EnglishOperational
  • meta-llama/llama-prompt-guard-2-22mOperational
  • whisper-large-v3Operational
  • groq/compoundOperational
  • whisper-large-v3-turboOperational
  • openai/gpt-oss-120bOperational
  • meta-llama/llama-4-maverick-17b-128e-instructOperational
  • llama-3.3-70b-versatileOperational

These are Groq's components, named and scored by Groq. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Groq's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Groq response time, by region

US-East
208msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.4s2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 1.6s2026-08-25 UTC: p95 1.6s2026-08-26 UTC: p95 1.5s2026-08-27 UTC: p95 890ms2026-08-28 UTC: p95 713ms2026-08-29 UTC: p95 629ms2026-08-30 UTC: p95 680ms2026-08-31 UTC: p95 716ms2026-09-01 UTC: p95 868ms2026-09-02 UTC: p95 942ms2026-09-03 UTC: p95 822ms2026-09-04 UTC: p95 493ms2026-09-05 UTC: p95 208ms
Aug 7Aug 21Sep 5
US-West
317msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 293ms2026-08-23 UTC: p95 330ms2026-08-24 UTC: p95 482ms2026-08-25 UTC: p95 561ms2026-08-26 UTC: p95 351ms2026-08-27 UTC: p95 628ms2026-08-28 UTC: p95 450ms2026-08-29 UTC: p95 615ms2026-08-30 UTC: p95 600ms2026-08-31 UTC: p95 439ms2026-09-01 UTC: p95 282ms2026-09-02 UTC: p95 525ms2026-09-03 UTC: p95 420ms2026-09-04 UTC: p95 346ms2026-09-05 UTC: p95 317ms
Aug 7Aug 21Sep 5
Europe
366msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 253ms2026-08-23 UTC: p95 461ms2026-08-24 UTC: p95 548ms2026-08-25 UTC: p95 448ms2026-08-26 UTC: p95 520ms2026-08-27 UTC: p95 585ms2026-08-28 UTC: p95 517ms2026-08-29 UTC: p95 596ms2026-08-30 UTC: p95 434ms2026-08-31 UTC: p95 440ms2026-09-01 UTC: p95 612ms2026-09-02 UTC: p95 562ms2026-09-03 UTC: p95 547ms2026-09-04 UTC: p95 413ms2026-09-05 UTC: p95 366ms
Aug 7Aug 21Sep 5
Asia-Pacific
362msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 635ms2026-08-23 UTC: p95 612ms2026-08-24 UTC: p95 696ms2026-08-25 UTC: p95 657ms2026-08-26 UTC: p95 675ms2026-08-27 UTC: p95 765ms2026-08-28 UTC: p95 820ms2026-08-29 UTC: p95 596ms2026-08-30 UTC: p95 587ms2026-08-31 UTC: p95 614ms2026-09-01 UTC: p95 729ms2026-09-02 UTC: p95 795ms2026-09-03 UTC: p95 960ms2026-09-04 UTC: p95 318ms2026-09-05 UTC: p95 362ms
Aug 7Aug 21Sep 5
US-Central
437msp95 · latest
500ms250ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 394ms2026-09-04 UTC: p95 437ms
Aug 7Aug 21Sep 5
Canada
318msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 514ms2026-09-04 UTC: p95 340ms2026-09-05 UTC: p95 318ms
Aug 7Aug 21Sep 5
UK
402msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 524ms2026-09-04 UTC: p95 527ms2026-09-05 UTC: p95 402ms
Aug 7Aug 21Sep 5
Southeast Asia
760msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 837ms2026-09-05 UTC: p95 760ms
Aug 7Aug 21Sep 5
Australia
824msp95 · latest
1s500ms0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 799ms2026-09-04 UTC: p95 687ms2026-09-05 UTC: p95 824ms
Aug 7Aug 21Sep 5
South America
707msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 707ms
Aug 7Aug 21Sep 5
Why some readings show as awaiting data. 1 of 20 readings for Groq came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 406, 429 or 451, a redirect loop, or a timeout we could rule out as a real outage using a second endpoint) rather than a normal success or failure. That tells us about our own probe's reception, not about Groq's actual health, so we publish no verdict for those readings rather than guessing in either direction. 1 of those reading received an actual response: we confirmed the connection, the TLS handshake, and the edge all answered, with a real measured latency. That is a positive result, we verified reachability, just not through the specific path automated checks are filtered on. Read how we tell the difference.

Is it Groq, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Groq -- it cannot diagnose Groq's own systems.

What we measured, function by function

Groq answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Awaiting dataCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    Awaiting dataUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 177msstatus code: 401checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Groq normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 289msstatus code: 401checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Groq normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Awaiting datalatency: 326msstatus code: 403reachable: automated verification filteredchecked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayGroq refused our US-Central probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from US-Central to say anything on their own.
    • Canada
      Operationallatency: 160msstatus code: 401checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Groq normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 781msstatus code: 401checked: Sep 5, 2026, 2:00 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Groq normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 344msstatus code: 401checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Groq normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 334msstatus code: 401checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Groq normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 171msstatus code: 401checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Groq normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 403msstatus code: 401checked: Sep 5, 2026, 1:47 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Groq normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 872msstatus code: 401checked: Sep 5, 2026, 1:59 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Groq normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Groq, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Groq yet, which is not evidence that nothing is wrong.

Recent outages

Data Center Failure Impacting Capacity, 1h 34mdeclared on their status page2026-07-01
openai/gpt-oss-120b Performance Issue, 59mdeclared on their status page2026-03-19
meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance, 1h 33mdeclared on their status page2026-02-07
meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance, 23mdeclared on their status page2026-02-05
meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance, 1h 44mdeclared on their status page2026-02-05
meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance, 1h 54mdeclared on their status page2026-01-26
Data Center Failure Impacting Model Latency - SYD, 2h 31mdeclared on their status page2026-01-24
Model Performance or Availability Issue: llama-3.3-70b-versatile, 1h 15mdeclared on their status page2025-12-24

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Groq since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Groq covering any window you pick, with our measurements and Groq's own claim at the time, side by side.

Full availability history for Groq: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Groq, and again when they can reach it again. That is our own measurement from ten regions, not Groq's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Groq uptime measured by RealUptimeLive, from this page's own readings.
[![Groq uptime measured by RealUptime](https://realuptime.io/outages/groq/badge.svg?days=30)](https://realuptime.io/outages/groq)
<a href="https://realuptime.io/outages/groq"><img src="https://realuptime.io/outages/groq/badge.svg?days=30" alt="Groq uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Groq's SLA implies, from our measurement

At or above your target

We measured none of downtime for Groq over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Groq's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.groq.com/openai/v1/models
secondary
https://groq.com/
secondary
https://groqstatus.com/api/v2/status.json
RealUptime is not affiliated with Groq; the name identifies what we measured, and nothing here speaks for Groq's own team. We send a single web request to Groq from 10 regions on our own schedule and time the response. We do not see inside Groq's systems, do not use an account or real transaction, and are not the same signal Groq's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Groq is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.