Is Groq down?
For agents
proceed
Proceed.
GET upbutler.com/status/groq/status.agent.json
MCP: upstream_status {"service":"groq"}
Low-latency inference for open models. Capacity incidents show as 503 and queueing rather than hard downtime.
What Groq reports
Operational
Taken as is from Groq's own status page API. Incident titles and component names below are theirs.
Open groqstatus.comUpButler's independent probe
API edge is answeringHTTP 401 · 211 ms
One request without credentials to api.groq.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
Open at Groq
- Planned Maintenance: meta-llama/llama-4-maverick-17b-128e-instruct (me-central-1)scheduled maintenance
Starts
When: Monday, Nov 3, 2025 • 00:00 to 03:00 UTC (Sunday, Nov 2, 16:00 to 19:00 PT) What • We’re performing planned maintenance on the me-central-1 deployment of meta-llama/llama-4-maverick-17b-128e-instruct to keep systems current. Other regions remain available. Impact • No customer action required. • Requests that explicitly target the me-central-1 endpoint for this model will be unavailable for approximately 2 hours within the window, possibly longer if troubleshooting is required. • Requests…
Text written by Groq, shown unchanged.
Groq components
16 operational
- 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
- moonshotai/kimi-k2-instruct-0905Operational
- openai/gpt-oss-safeguard-20bOperational
- minimaxai/minimax-m2.7Operational
- qwen/qwen3.8-27bOperational
- WebsiteOperational
Groq incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Groq publishes for 90 days from the day it starts tracking a service.
Tell your outage from Groq's
Declare that your project depends on Groq. When one of your monitors fails while Groq has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- groqcurl -s https://upbutler.com/status/groq/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "groq",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Groq down right now?
- No. As of 2026-10-10 05:12 UTC, Groq is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Groq's own status page API at https://groqstatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Groq's words.
- What does UpButler's own Groq check prove?
- Every two minutes UpButler sends one request without credentials to the Groq API edge (api.groq.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Groq reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Groq status?
- Fetch https://upbutler.com/status/groq/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"groq"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Groq's?
- Add "groq" to the dependencies of your UpButler workspace. When one of your monitors fails while Groq has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in ai models and tooling
UpButler is not affiliated with Groq. Status and incident text belong to Groq and are read from their public status source; the probe result is UpButler's own measurement.