Groq status
Is Groq down? This is Groq’s current status, its components and its recent incidents, read from Groq’s official status page and refreshed every 2 minutes.
All Systems Operational
As reported by Groq’s status page, read Oct 24, 2026, 18:07 UTC.
Scheduled maintenance
- Planned Maintenance: meta-llama/llama-4-maverick-17b-128e-instruct (me-central-1) · Oct 24, 2025, 18:25 UTC · scheduled, maintenance impact
Components
| Component | Status |
|---|---|
| API | Operational |
| llama-3.1-8b-instant | Operational |
| llama-3.3-70b-versatile | Operational |
| openai/gpt-oss-120b | Operational |
| openai/gpt-oss-20b | Operational |
| whisper-large-v3 | Operational |
| whisper-large-v3-turbo | Operational |
| Canopy Labs Orpheus Arabic Saudi | Operational |
| Canopy Labs Orpheus English | Operational |
| meta-llama/llama-prompt-guard-2-22m | Operational |
| meta-llama/llama-prompt-guard-2-86m | Operational |
| openai/gpt-oss-safeguard-20b | Operational |
| minimaxai/minimax-m2.7 | Operational |
| qwen/qwen3.8-27b | Operational |
| Website | Operational |
What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.
Recent Groq incidents
- Model Performance or Availability Issue · Oct 12, 2026, 18:17 UTC · resolved, major impact, lasted 18 min
The issues affecting **minimaxai/minimax-m2.7** have been **resolved**. The model is operating normally. Root cause: **hardware connectivity issues**. We apologize for the disruption and thank you for your patience.
- GroqCloud Console Errors Affecting Multiple Regions · Oct 12, 2026, 03:37 UTC · resolved, minor impact, lasted 23 min
The **Groqcloud console issue has been resolved**. All services are operating normally. We apologize for the disruption and **appreciate your patience**.
- Model Performance or Availability Issue - minimaxai/minimax-m2.7 · Oct 10, 2026, 10:09 UTC · resolved, minor impact, lasted 6 h 5 min
The issues affecting **minimaxai/minimax-m2.7** have been **resolved**. The model is operating normally. Root cause: **Data center hardware issues**. We apologize for the disruption and thank you for your patience.
- Data Center Failure Impacting Capacity · Jul 1, 2026, 23:01 UTC · resolved, minor impact, lasted 1 h 34 min
The **capacity issue has been resolved**. All services are operating at normal capacity. The incident was caused by a **power loss issue that led to a cooling system failure at one of our US Central data centers**. We apologize for any disruption and **appreciate your patience**.
- openai/gpt-oss-120b Performance Issue · Mar 19, 2026, 12:51 UTC · resolved, minor impact, lasted 59 min
The issues affecting openai/gpt-oss-120b have been **resolved**. The model is operating normally. Actions were taken to cancel billing plans and restrict verification status of organizations engaged in coordinated abuse. We apologize for the disruption and thank you for your…
- meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance · Feb 7, 2026, 10:02 UTC · resolved, minor impact, lasted 1 h 33 min
This incident has been resolved. Thank you for your patience.
- meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance · Feb 5, 2026, 18:09 UTC · resolved, minor impact, lasted 23 min
The issues affecting meta-llama/llama-4-scout-17b-16e-instruct have been **resolved**. The model is once again operating normally. We apologize for the disruption and thank you for your patience.
- meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance · Feb 5, 2026, 13:23 UTC · resolved, minor impact, lasted 1 h 44 min
The issues affecting meta-llama/llama-4-scout-17b-16e-instruct have been fully **resolved**. The model is operating normally. We apologize for the disruption and thank you for your patience.
- meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance · Jan 26, 2026, 23:17 UTC · resolved, minor impact, lasted 1 h 54 min
This incident has been resolved. Thank you for your patience.
- Data Center Failure Impacting Model Latency - SYD · Jan 24, 2026, 04:53 UTC · resolved, minor impact, lasted 2 h 31 min
This incident is now resolved.
- Model Performance or Availability Issue: llama-3.3-70b-versatile · Dec 24, 2025, 23:01 UTC · resolved, minor impact, lasted 1 h 15 min
The issues affecting **llama-3.3-70b-versatile** have been **resolved**. The model is operating normally. We apologize for the disruption and thank you for your patience.
- Data Center Failure Impacting Capacity - DMM1 · Dec 17, 2025, 07:11 UTC · resolved, minor impact
**The data center capacity issue has been resolved. All services are operating at normal capacity. The incident was caused by a failed ARP entry on the network gateway device caused the Salam network link to go down in the DMM1 data center, which has been addressed. We apologize…
- meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance · Dec 6, 2025, 18:58 UTC · resolved, minor impact, lasted 1 h 25 min
The issues affecting meta-llama/llama-4-scout-17b-16e-instruct , meta-llama/llama-4-maverick-17b-128e-instruct, & groq/compound have been **resolved**. The models are operating normally. We apologize for the disruption and thank you for your patience.
- meta-llama/llama-4-scout-17b-16e-instruct & groq/compound Degraded Performance · Dec 2, 2025, 17:36 UTC · resolved, minor impact, lasted 2 h 26 min
The issues affecting meta-llama/llama-4-scout-17b-16e-instruct & groq/compound have been **resolved**. Both of the models are operating normally. We apologize for the disruption and thank you for your patience.
- Console, Website, & API Availability Issues: Global Cloudflare Outage · Nov 18, 2025, 11:52 UTC · resolved, major impact, lasted 3 h 33 min
We are resolving this incident as we have now observed ~30 minutes of normalized service availability and customer traffic. We will continue to closely monitor our systems for any signs of regression as [Cloudflare's statuspage incident remains active…
Source: Groq Status: Real-Time Visibility Into GroqCloud's System Health and , Groq’s public status page, read Oct 24, 2026, 18:07 UTC. Uptimely is not affiliated with Groq; incident text is Groq’s own.
Is it down for you, or for everyone?
A status page shows what the vendor has confirmed, which often lags what users see. Run a live check of groq.com to see whether it answers right now.
Get alerted when Groq has an incident
Uptimely’s External Status Page monitor watches Groq’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services.
Status of similar services
Is Groq down right now?
The status at the top of this page is Groq's own, read from its public status page every couple of minutes. It shows what Groq's team has confirmed. For an independent check of whether groq.com answers right now, use the live check on the is-it-down page.
Where is Groq's official status page?
Groq publishes its status at https://groqstatus.com. This page shows the same data with the recent incident history in one place, and links each incident to Groq's own write-up.
Why does Groq not work for me when its status says operational?
A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause.
How can I get alerted when Groq has an incident?
Add an External Status Page monitor in Uptimely pointed at https://groqstatus.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when Groq reports a problem, beside the monitors for your own services.