Skip to content

Outage tracker / Groq

Is Groq down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Groq from all 10 regions we check.

As of Oct 6, 2026, 9:58 PM UTC, Groq answered RealUptime's probes in all 10 regions that returned a reading.

Groq's last published incident: "Data Center Failure Impacting Capacity", Jul 1, 2026, 1h 34m. their claim, not our reading

Functional endpoints verified

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

our independent probeslive · checked Oct 6, 2026, 9:58 PM UTC
US-East212 msOperational
US-West254 msOperational
Europe325 msOperational
Asia-Pacific223 msOperational
US-Central259 msOperational
Canada290 msOperational
UK419 msOperational
Southeast Asia584 msOperational
Australia838 msOperational
South America751 msOperational
their status pagetheir claim, not our reading

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

from Groq's own status page, checked Oct 6, 2026, 9:58 PM UTC
Our probes and Groq's own status page agree: both show Groq as reachable right now.

Groq's own component breakdown, as they publish it

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

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
391msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 288ms2026-09-08 UTC: p95 261ms2026-09-09 UTC: p95 310ms2026-09-10 UTC: p95 377ms2026-09-11 UTC: p95 524ms2026-09-12 UTC: p95 396ms2026-09-13 UTC: p95 331ms2026-09-14 UTC: p95 349ms2026-09-15 UTC: p95 341ms2026-09-16 UTC: p95 410ms2026-09-17 UTC: p95 428ms2026-09-18 UTC: p95 443ms2026-09-19 UTC: p95 353ms2026-09-20 UTC: p95 384ms2026-09-21 UTC: p95 400ms2026-09-22 UTC: p95 478ms2026-09-23 UTC: p95 528ms2026-09-24 UTC: p95 582ms2026-09-25 UTC: p95 557ms2026-09-26 UTC: p95 492ms2026-09-27 UTC: p95 568ms2026-09-28 UTC: p95 549ms2026-09-29 UTC: p95 373ms2026-09-30 UTC: p95 353ms2026-10-01 UTC: p95 286ms2026-10-02 UTC: p95 300ms2026-10-03 UTC: p95 289ms2026-10-04 UTC: p95 381ms2026-10-05 UTC: p95 417ms2026-10-06 UTC: p95 391ms
Sep 7Sep 21Oct 6
US-West
434msp95 · 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-09-07 UTC: p95 249ms2026-09-08 UTC: p95 260ms2026-09-09 UTC: p95 183ms2026-09-10 UTC: p95 234ms2026-09-11 UTC: p95 207ms2026-09-12 UTC: p95 149ms2026-09-13 UTC: p95 190ms2026-09-14 UTC: p95 174ms2026-09-15 UTC: p95 393ms2026-09-16 UTC: p95 394ms2026-09-17 UTC: p95 435ms2026-09-18 UTC: p95 441ms2026-09-19 UTC: p95 463ms2026-09-20 UTC: p95 500ms2026-09-21 UTC: p95 493ms2026-09-22 UTC: p95 519ms2026-09-23 UTC: p95 504ms2026-09-24 UTC: p95 497ms2026-09-25 UTC: p95 538ms2026-09-26 UTC: p95 398ms2026-09-27 UTC: p95 398ms2026-09-28 UTC: p95 453ms2026-09-29 UTC: p95 333ms2026-09-30 UTC: p95 340ms2026-10-01 UTC: p95 382ms2026-10-02 UTC: p95 362ms2026-10-03 UTC: p95 361ms2026-10-04 UTC: p95 341ms2026-10-05 UTC: p95 381ms2026-10-06 UTC: p95 434ms
Sep 7Sep 21Oct 6
Europe
378msp95 · 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-09-07 UTC: p95 553ms2026-09-08 UTC: p95 555ms2026-09-09 UTC: p95 476ms2026-09-10 UTC: p95 361ms2026-09-11 UTC: p95 358ms2026-09-12 UTC: p95 351ms2026-09-13 UTC: p95 336ms2026-09-14 UTC: p95 349ms2026-09-15 UTC: p95 348ms2026-09-16 UTC: p95 445ms2026-09-17 UTC: p95 449ms2026-09-18 UTC: p95 398ms2026-09-19 UTC: p95 451ms2026-09-20 UTC: p95 421ms2026-09-21 UTC: p95 456ms2026-09-22 UTC: p95 540ms2026-09-23 UTC: p95 473ms2026-09-24 UTC: p95 518ms2026-09-25 UTC: p95 450ms2026-09-26 UTC: p95 401ms2026-09-27 UTC: p95 398ms2026-09-28 UTC: p95 401ms2026-09-29 UTC: p95 418ms2026-09-30 UTC: p95 447ms2026-10-01 UTC: p95 395ms2026-10-02 UTC: p95 443ms2026-10-03 UTC: p95 368ms2026-10-04 UTC: p95 365ms2026-10-05 UTC: p95 428ms2026-10-06 UTC: p95 378ms
Sep 7Sep 21Oct 6
Asia-Pacific
502msp95 · 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-09-07 UTC: p95 386ms2026-09-08 UTC: p95 439ms2026-09-09 UTC: p95 426ms2026-09-10 UTC: p95 389ms2026-09-11 UTC: p95 398ms2026-09-12 UTC: p95 350ms2026-09-13 UTC: p95 410ms2026-09-14 UTC: p95 424ms2026-09-15 UTC: p95 394ms2026-09-16 UTC: p95 470ms2026-09-17 UTC: p95 512ms2026-09-18 UTC: p95 466ms2026-09-19 UTC: p95 502ms2026-09-20 UTC: p95 493ms2026-09-21 UTC: p95 454ms2026-09-22 UTC: p95 502ms2026-09-23 UTC: p95 585ms2026-09-24 UTC: p95 571ms2026-09-25 UTC: p95 547ms2026-09-26 UTC: p95 512ms2026-09-27 UTC: p95 628ms2026-09-28 UTC: p95 568ms2026-09-29 UTC: p95 461ms2026-09-30 UTC: p95 524ms2026-10-01 UTC: p95 450ms2026-10-02 UTC: p95 466ms2026-10-03 UTC: p95 509ms2026-10-04 UTC: p95 468ms2026-10-05 UTC: p95 499ms2026-10-06 UTC: p95 502ms
Sep 7Sep 21Oct 6
US-Central
314msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 415ms2026-09-08 UTC: p95 400ms2026-09-09 UTC: p95 457ms2026-09-10 UTC: p95 483ms2026-09-11 UTC: p95 534ms2026-09-12 UTC: p95 469ms2026-09-13 UTC: p95 456ms2026-09-14 UTC: p95 576ms2026-09-15 UTC: p95 506ms2026-09-16 UTC: p95 448ms2026-09-17 UTC: p95 419ms2026-09-18 UTC: p95 469ms2026-09-19 UTC: p95 513ms2026-09-20 UTC: p95 446ms2026-09-21 UTC: p95 476ms2026-09-22 UTC: p95 479ms2026-09-23 UTC: p95 403ms2026-09-24 UTC: p95 443ms2026-09-25 UTC: p95 329ms2026-09-26 UTC: p95 419ms2026-09-27 UTC: p95 416ms2026-09-28 UTC: p95 394ms2026-09-29 UTC: p95 469ms2026-09-30 UTC: p95 420ms2026-10-01 UTC: p95 362ms2026-10-02 UTC: p95 270ms2026-10-03 UTC: p95 399ms2026-10-04 UTC: p95 386ms2026-10-05 UTC: p95 342ms2026-10-06 UTC: p95 314ms
Sep 7Sep 21Oct 6
Canada
452msp95 · 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-07 UTC: p95 302ms2026-09-08 UTC: p95 436ms2026-09-09 UTC: p95 511ms2026-09-10 UTC: p95 706ms2026-09-11 UTC: p95 775ms2026-09-12 UTC: p95 328ms2026-09-13 UTC: p95 393ms2026-09-14 UTC: p95 373ms2026-09-15 UTC: p95 402ms2026-09-16 UTC: p95 362ms2026-09-17 UTC: p95 424ms2026-09-18 UTC: p95 412ms2026-09-19 UTC: p95 349ms2026-09-20 UTC: p95 316ms2026-09-21 UTC: p95 367ms2026-09-22 UTC: p95 379ms2026-09-23 UTC: p95 270ms2026-09-24 UTC: p95 281ms2026-09-25 UTC: p95 255ms2026-09-26 UTC: p95 424ms2026-09-27 UTC: p95 381ms2026-09-28 UTC: p95 393ms2026-09-29 UTC: p95 416ms2026-09-30 UTC: p95 497ms2026-10-01 UTC: p95 404ms2026-10-02 UTC: p95 355ms2026-10-03 UTC: p95 359ms2026-10-04 UTC: p95 371ms2026-10-05 UTC: p95 352ms2026-10-06 UTC: p95 452ms
Sep 7Sep 21Oct 6
UK
474msp95 · 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-07 UTC: p95 478ms2026-09-08 UTC: p95 381ms2026-09-09 UTC: p95 289ms2026-09-10 UTC: p95 369ms2026-09-11 UTC: p95 247ms2026-09-12 UTC: p95 273ms2026-09-13 UTC: p95 252ms2026-09-14 UTC: p95 266ms2026-09-15 UTC: p95 303ms2026-09-16 UTC: p95 544ms2026-09-17 UTC: p95 453ms2026-09-18 UTC: p95 399ms2026-09-19 UTC: p95 464ms2026-09-20 UTC: p95 391ms2026-09-21 UTC: p95 453ms2026-09-22 UTC: p95 544ms2026-09-23 UTC: p95 605ms2026-09-24 UTC: p95 612ms2026-09-25 UTC: p95 644ms2026-09-26 UTC: p95 450ms2026-09-27 UTC: p95 384ms2026-09-28 UTC: p95 383ms2026-09-29 UTC: p95 378ms2026-09-30 UTC: p95 368ms2026-10-01 UTC: p95 500ms2026-10-02 UTC: p95 396ms2026-10-03 UTC: p95 420ms2026-10-04 UTC: p95 437ms2026-10-05 UTC: p95 496ms2026-10-06 UTC: p95 474ms
Sep 7Sep 21Oct 6
Southeast Asia
794msp95 · 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-07 UTC: p95 711ms2026-09-08 UTC: p95 840ms2026-09-09 UTC: p95 767ms2026-09-10 UTC: p95 673ms2026-09-11 UTC: p95 965ms2026-09-12 UTC: p95 783ms2026-09-13 UTC: p95 628ms2026-09-14 UTC: p95 630ms2026-09-15 UTC: p95 737ms2026-09-16 UTC: p95 810ms2026-09-17 UTC: p95 896ms2026-09-18 UTC: p95 860ms2026-09-19 UTC: p95 793ms2026-09-20 UTC: p95 992ms2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 903ms2026-09-30 UTC: p95 941ms2026-10-01 UTC: p95 820ms2026-10-02 UTC: p95 749ms2026-10-03 UTC: p95 766ms2026-10-04 UTC: p95 804ms2026-10-05 UTC: p95 776ms2026-10-06 UTC: p95 794ms
Sep 7Sep 21Oct 6
Australia
1.1sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 735ms2026-09-08 UTC: p95 674ms2026-09-09 UTC: p95 733ms2026-09-10 UTC: p95 660ms2026-09-11 UTC: p95 679ms2026-09-12 UTC: p95 616ms2026-09-13 UTC: p95 602ms2026-09-14 UTC: p95 694ms2026-09-15 UTC: p95 842ms2026-09-16 UTC: p95 779ms2026-09-17 UTC: p95 869ms2026-09-18 UTC: p95 743ms2026-09-19 UTC: p95 580ms2026-09-20 UTC: p95 531ms2026-09-21 UTC: p95 648ms2026-09-22 UTC: p95 615ms2026-09-23 UTC: p95 934ms2026-09-24 UTC: p95 962ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 805ms2026-09-27 UTC: p95 735ms2026-09-28 UTC: p95 811ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 924ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.1s
Sep 7Sep 21Oct 6
South America
1.2sp95 · 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-07 UTC: p95 690ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 890ms2026-09-14 UTC: p95 841ms2026-09-15 UTC: p95 862ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 856ms2026-09-19 UTC: p95 851ms2026-09-20 UTC: p95 876ms2026-09-21 UTC: p95 854ms2026-09-22 UTC: p95 990ms2026-09-23 UTC: p95 895ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 989ms2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 955ms2026-10-02 UTC: p95 908ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 951ms2026-10-06 UTC: p95 1.2s
Sep 7Sep 21Oct 6

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: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Groq go down, and when it is back

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.

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
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 212msstatus code: 401checked: Oct 6, 2026, 9:53 PM 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: 254msstatus code: 401checked: Oct 6, 2026, 9:53 PM 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
      Operationallatency: 259msstatus code: 401checked: Oct 6, 2026, 9:48 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Groq normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 290msstatus code: 401checked: Oct 6, 2026, 9:48 PM 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: 751msstatus code: 401checked: Oct 6, 2026, 9:53 PM 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: 325msstatus code: 401checked: Oct 6, 2026, 9:58 PM 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: 419msstatus code: 401checked: Oct 6, 2026, 9:44 PM 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: 223msstatus code: 401checked: Oct 6, 2026, 9:52 PM 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: 584msstatus code: 401checked: Oct 6, 2026, 9:42 PM 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: 838msstatus code: 401checked: Oct 6, 2026, 9:40 PM 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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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.