Groq Outage History

27 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Groq status99.95% uptime history

Every Recorded Groq Incident

Groq incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 1, 2026Data Center Failure Impacting CapacityThe **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…1h 33mResolved
Mar 19, 2026openai/gpt-oss-120b Performance IssueThe 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…59 minResolved
Feb 7, 2026meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceThis incident has been resolved. Thank you for your patience.1h 32mResolved
Feb 5, 2026meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceThe 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.23 minResolved
Feb 5, 2026meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceThe 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.1h 44mResolved
Jan 26, 2026meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceThis incident has been resolved. Thank you for your patience.1h 53mResolved
Jan 24, 2026Data Center Failure Impacting Model Latency - SYDThis incident is now resolved.2h 30mResolved
Dec 24, 2025Model Performance or Availability Issue: llama-3.3-70b-versatileThe 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.1h 15mResolved
Dec 17, 2025Data Center Failure Impacting Capacity - DMM1**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…-3941 minResolved
Dec 6, 2025meta-llama/llama-4-scout-17b-16e-instruct Degraded PerformanceThe 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…1h 25mResolved
Dec 2, 2025meta-llama/llama-4-scout-17b-16e-instruct & groq/compound Degraded PerformanceThe 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.2h 25mResolved
Nov 18, 2025Console, Website, & API Availability Issues: Global Cloudflare OutageWe 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…3h 33mResolved
Nov 5, 2025Cloud API DegradationThe issues causing degraded performance have been **resolved**. All models are now operating normally. Upon investigation we learned the issue was scoped to an internal feature yet to be released that is still in…34 minResolved
Nov 4, 2025Model Performance Issue: llama-3.1-8b-instantThe issues affecting llama-3.1-8b-instant have been **resolved**. The model is operating normally. Root cause: Two recent changes to the inference-engine-instances repository that were contributing to the elevated Orion…36 minResolved
Oct 24, 2025Planned Maintenance: meta-llama/llama-4-maverick-17b-128e-instruct (me-central-1) **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…—Scheduled
Oct 22, 2025openai/gpt-oss-120b Degraded PerformanceThe latency issues affecting openai/gpt-oss-120b have been resolved. The model is now operating normally and latency has returned to expected ranges. We apologize for the disruption and thank you for your patience.2h 8mResolved
Oct 21, 2025openai/gpt-oss-120b Degraded PerformanceThe issues affecting openai/gpt-oss-120b have been **resolved**. The model is operating normally. We apologize for the disruption and thank you for your patience.1h 53mResolved
Oct 14, 2025meta-llama/llama-4-scout-17b-16e-instruct & groq/compound Degraded PerformanceThe issues affecting meta-llama/llama-4-scout-17b-16e-instruct have been **resolved**. The model is operating normally. We apologize for the disruption and thank you for your patience.2h 2mResolved
Oct 6, 2025 Llama-3.1-8b-instant model Degraded PerformanceThe issues affecting llama-3.1-8b-instant have been resolved. The model is operating normally. Thank you for your patience.49 minResolved
Oct 6, 2025llama-3.3-70b-versatile and llama-3.1-8b-instant Degraded PerformanceThe issues affecting llama-3.3-70b-versatile and llama-3.1-8b-instant have been **resolved**. The models are operating normally. We apologize for the disruption and thank you for your patience.48 minResolved
Sep 18, 2025Degraded login via VercelVercel‑initiated login is operating normally. Other login methods were unaffected. This incident is now resolved.16h 7mResolved
Sep 10, 2025Elevated Latency on Search Tooling This issue has been resolved.40 minResolved
Sep 8, 2025llama-3.3-70b-versatile Performance IssueThis incident has been resolved.1h 52mResolved
Sep 5, 2025moonshotai/kimi-k2-instruct Unavailable or Degraded PerformanceThe issues affecting moonshotai/kimi-k2-instruct have been **resolved**. The model is operating normally. We apologize for the disruption and thank you for your patience.37 minResolved
Sep 4, 2025me-central-1 Data Center Failure Impacting CapacityWe have **fully resolved** the failure in our me-central-1 region. All services are operating at normal capacity. The incident was caused by a **network failure**, which has been corrected. We apologize for the…1h 35mResolved
Sep 3, 2025API Errors Affecting Multiple RegionsThe authentication issue impacting multiple regions has been fully resolved. Services are operating normally, and error rates remain stable.41 minResolved
Aug 25, 2025Latency Issues Across Various ModelsThis incident has been resolved.1h 29mResolved

How to Read This Groq Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Groq acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Groq outage in this window ran 16h 7m, against a mean recovery of 2h 3m. If you depend on Groq in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.