Skip to content

Outage tracker / Groq

Is Groq down?

I'm having a problem

Vendor reports no incidentWhat Groq reports

Groq reports no incident on its status page.

As of the last successful poll, 2026-11-05 13:53 UTC.

Groq's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Groq pass from all 10 regions we check.

As of Nov 5, 2026, 2:04 PM UTC, RealUptime's checks of Groq passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:04 PM UTC
US-East254 msChecks passing
US-West583 msChecks passing
Europe604 msChecks passing
Asia-Pacific747 msChecks passing
US-Central364 msChecks passing
Canada671 msChecks passing
UK297 msChecks passing
Southeast Asia490 msChecks passing
Australia1310 msChecks passing
South America1058 msChecks passing
their status pagetheir claim, not our reading

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

from Groq's own status page, checked Nov 5, 2026, 1:57 PM UTC
Groq's own status page shows no incident, and our checks of Groq pass right now.

Groq's own component breakdown, as they publish it

  • APIOperational
  • llama-3.1-8b-instantOperational
  • llama-3.3-70b-versatileOperational
  • openai/gpt-oss-120bOperational
  • openai/gpt-oss-20bOperational
  • whisper-large-v3Operational
  • whisper-large-v3-turboOperational
  • Canopy Labs Orpheus Arabic SaudiOperational
  • Canopy Labs Orpheus EnglishOperational
  • meta-llama/llama-prompt-guard-2-22mOperational
  • meta-llama/llama-prompt-guard-2-86mOperational
  • openai/gpt-oss-safeguard-20bOperational
  • minimaxai/minimax-m2.7Operational
  • qwen/qwen3.8-27bOperational
  • 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
797msp95 · 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-10-07 UTC: p95 317ms2026-10-08 UTC: p95 409ms2026-10-09 UTC: p95 396ms2026-10-10 UTC: p95 331ms2026-10-11 UTC: p95 170ms2026-10-12 UTC: p95 360ms2026-10-13 UTC: p95 385ms2026-10-14 UTC: p95 477ms2026-10-15 UTC: p95 456ms2026-10-16 UTC: p95 505ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 959ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 862ms2026-10-23 UTC: p95 981ms2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1s2026-10-29 UTC: p95 888ms2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 845ms2026-11-04 UTC: p95 736ms2026-11-05 UTC: p95 797ms
Oct 7Oct 21Nov 5
US-West
1.2sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 240ms2026-10-08 UTC: p95 343ms2026-10-09 UTC: p95 353ms2026-10-10 UTC: p95 302ms2026-10-11 UTC: p95 178ms2026-10-12 UTC: p95 518ms2026-10-13 UTC: p95 400ms2026-10-14 UTC: p95 532ms2026-10-15 UTC: p95 444ms2026-10-16 UTC: p95 497ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 878ms2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Europe
1.1sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 403ms2026-10-08 UTC: p95 416ms2026-10-09 UTC: p95 476ms2026-10-10 UTC: p95 507ms2026-10-11 UTC: p95 438ms2026-10-12 UTC: p95 468ms2026-10-13 UTC: p95 371ms2026-10-14 UTC: p95 513ms2026-10-15 UTC: p95 378ms2026-10-16 UTC: p95 426ms2026-10-17 UTC: p95 602ms2026-10-18 UTC: p95 679ms2026-10-19 UTC: p95 788ms2026-10-20 UTC: p95 740ms2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 819ms2026-10-23 UTC: p95 703ms2026-10-24 UTC: p95 650ms2026-10-25 UTC: p95 641ms2026-10-26 UTC: p95 719ms2026-10-27 UTC: p95 792ms2026-10-28 UTC: p95 714ms2026-10-29 UTC: p95 859ms2026-10-30 UTC: p95 910ms2026-10-31 UTC: p95 816ms2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 785ms2026-11-03 UTC: p95 857ms2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Asia-Pacific
1.7sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 546ms2026-10-08 UTC: p95 481ms2026-10-09 UTC: p95 680ms2026-10-10 UTC: p95 471ms2026-10-11 UTC: p95 567ms2026-10-12 UTC: p95 732ms2026-10-13 UTC: p95 622ms2026-10-14 UTC: p95 506ms2026-10-15 UTC: p95 582ms2026-10-16 UTC: p95 518ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 765ms2026-10-26 UTC: p95 757ms2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 890ms2026-11-01 UTC: p95 972ms2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
US-Central
1.0sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 380ms2026-10-08 UTC: p95 392ms2026-10-09 UTC: p95 452ms2026-10-10 UTC: p95 352ms2026-10-11 UTC: p95 433ms2026-10-12 UTC: p95 398ms2026-10-13 UTC: p95 195ms2026-10-14 UTC: p95 250ms2026-10-15 UTC: p95 282ms2026-10-16 UTC: p95 580ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 631ms2026-10-23 UTC: p95 673ms2026-10-24 UTC: p95 662ms2026-10-25 UTC: p95 504ms2026-10-26 UTC: p95 464ms2026-10-27 UTC: p95 553ms2026-10-28 UTC: p95 914ms2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 835ms2026-11-04 UTC: p95 842ms2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Canada
663msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 405ms2026-10-08 UTC: p95 404ms2026-10-09 UTC: p95 397ms2026-10-10 UTC: p95 375ms2026-10-11 UTC: p95 209ms2026-10-12 UTC: p95 356ms2026-10-13 UTC: p95 357ms2026-10-14 UTC: p95 230ms2026-10-15 UTC: p95 200ms2026-10-16 UTC: p95 402ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 922ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 893ms2026-11-05 UTC: p95 663ms
Oct 7Oct 21Nov 5
UK
501msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 465ms2026-10-08 UTC: p95 432ms2026-10-09 UTC: p95 585ms2026-10-10 UTC: p95 413ms2026-10-11 UTC: p95 400ms2026-10-12 UTC: p95 506ms2026-10-13 UTC: p95 576ms2026-10-14 UTC: p95 497ms2026-10-15 UTC: p95 663ms2026-10-16 UTC: p95 408ms2026-10-17 UTC: p95 654ms2026-10-18 UTC: p95 680ms2026-10-19 UTC: p95 699ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 770ms2026-10-23 UTC: p95 798ms2026-10-24 UTC: p95 776ms2026-10-25 UTC: p95 969ms2026-10-26 UTC: p95 937ms2026-10-27 UTC: p95 804ms2026-10-28 UTC: p95 706ms2026-10-29 UTC: p95 697ms2026-10-30 UTC: p95 638ms2026-10-31 UTC: p95 722ms2026-11-01 UTC: p95 699ms2026-11-02 UTC: p95 840ms2026-11-03 UTC: p95 753ms2026-11-04 UTC: p95 574ms2026-11-05 UTC: p95 501ms
Oct 7Oct 21Nov 5
Southeast Asia
1.6sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 744ms2026-10-08 UTC: p95 863ms2026-10-09 UTC: p95 775ms2026-10-10 UTC: p95 695ms2026-10-11 UTC: p95 514ms2026-10-12 UTC: p95 729ms2026-10-13 UTC: p95 462ms2026-10-14 UTC: p95 767ms2026-10-15 UTC: p95 936ms2026-10-16 UTC: p95 994ms2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
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-10-07 UTC: p95 877ms2026-10-08 UTC: p95 994ms2026-10-09 UTC: p95 812ms2026-10-10 UTC: p95 678ms2026-10-11 UTC: p95 562ms2026-10-12 UTC: p95 666ms2026-10-13 UTC: p95 691ms2026-10-14 UTC: p95 666ms2026-10-16 UTC: p95 541ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 981ms2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
South America
1.6sp95 · latest
20s10s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 918ms2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 917ms2026-10-10 UTC: p95 940ms2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 718ms2026-10-13 UTC: p95 479ms2026-10-14 UTC: p95 712ms2026-10-15 UTC: p95 562ms2026-10-16 UTC: p95 978ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 988ms2026-10-23 UTC: p95 10.1s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5

Check your own site while you wait on Groq

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Groq reports an incident on its status page, and again when it reports it resolved.

Get an email when Groq reports an incident

Email me when Groq reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Groq's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 254msstatus code: 401checked: Nov 5, 2026, 1:54 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
      Checks passinglatency: 583msstatus code: 401checked: Nov 5, 2026, 2:00 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
      Checks passinglatency: 364msstatus code: 401checked: Nov 5, 2026, 1:53 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
      Checks passinglatency: 671msstatus code: 401checked: Nov 5, 2026, 1:51 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
    Checks passinglatency: 1058msstatus code: 401checked: Nov 5, 2026, 2:04 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 604msstatus code: 401checked: Nov 5, 2026, 1:59 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
      Checks passinglatency: 297msstatus code: 401checked: Nov 5, 2026, 1:53 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 747msstatus code: 401checked: Nov 5, 2026, 1:46 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
      Checks passinglatency: 490msstatus code: 401checked: Nov 5, 2026, 1:44 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
      Checks passinglatency: 1310msstatus code: 401checked: Nov 5, 2026, 1:46 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 probe events

Model Performance or Availability Issue, 18mdeclared on their status page2026-10-12
GroqCloud Console Errors Affecting Multiple Regions, 23mdeclared on their status page2026-10-12
Model Performance or Availability Issue - minimaxai/minimax-m2.7, 6h 5mdeclared on their status page2026-10-10
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

check 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 check readings and Groq's own claim at the time, side by side.

Full check history for Groq: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Groq uptime by RealUptime's checksLive, from this page's own readings.
[![Groq uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Groq down?", https://realuptime.io/outages/groq. The readings change with every check, so give the date you read them.

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

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.groq.com

RealUptime is not affiliated with Groq; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.