Groq Cloud Outage History

Groq Cloud is up right now

Pingoru has recorded 20 incidents for Groq Cloud: 15 in the last 12 months and 3 in the last 90 days.

Source: groqstatus.com

20incidents recorded

15last 12 months

3last 90 days

106 minutestypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Groq Cloud in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Month	Incidents	Hours with an open incident
April 2026	0	0 of 720 (0%)
May 2026	0	0 of 744 (0%)
June 2026	0	0 of 720 (0%)
July 2026	1	1 of 744 (0%)
August 2026	0	0 of 744 (0%)
September 2026	0	0 of 720 (0%)
October 2026	3	7 of 744 (1%)
November 2026	0	0 of 208 (0%)

Incidents, newest first

Major October 12, 2026 Model Performance or Availability Issue 18m Preview Models (minimaxai/minimax-m2.7)

Started Oct 12, 2026, 06:17 PM UTC· resolved Oct 12, 2026, 06:36 PM UTC

identified Oct 12, 2026, 06:17 PM UTC

We have identified the problem affecting the minimaxai/minimax-m2.7 service. The issue was traced to hardware connectivity issues. A fix is in progress. Users may still see API failures until the fix completes.
resolved Oct 12, 2026, 06:36 PM UTC

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.

Read the full incident report →

Minor October 12, 2026 GroqCloud Console Errors Affecting Multiple Regions 21m Website, API

Started Oct 12, 2026, 03:17 AM UTC· resolved Oct 12, 2026, 03:38 AM UTC

investigating Oct 12, 2026, 03:37 AM UTC

We are currently investigating increased error rates on our GroqCloud console (including metrics, /models API endpoints, and API key creation). Users may receive 500 errors when making requests to console.groq.com. Our engineers are isolating the issue.
monitoring Oct 12, 2026, 03:47 AM UTC

We've mitigated the errors on the GroqCloud console and functionality has been restored. Inference API requests are not affected, and we will provide additional updates here.
resolved Oct 12, 2026, 04:00 AM UTC

The Groqcloud console issue has been resolved. All services are operating normally. We apologize for the disruption and appreciate your patience.

Read the full incident report →

Major October 10, 2026 Model Performance or Availability Issue - minimaxai/minimax-m2.7 6h 5m Preview Models (minimaxai/minimax-m2.7)

Started Oct 10, 2026, 10:09 AM UTC· resolved Oct 10, 2026, 04:14 PM UTC

identified Oct 10, 2026, 10:09 AM UTC

We have identified the problem affecting the enterprise-only minimaxai/minimax-m2.7 model. The issue was traced to hardware issues in our data center. A fix is in progress. Users may still see failed requests until the fix completes.
resolved Oct 10, 2026, 04:14 PM UTC

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.

Read the full incident report →

Minor July 1, 2026 Data Center Failure Impacting Capacity 46m Production (openai/gpt-oss-20b), Production (llama-3.3-70b-versatile)

Started Jul 01, 2026, 11:01 PM UTC· resolved Jul 01, 2026, 11:48 PM UTC

investigating Jul 01, 2026, 11:01 PM UTC

We are currently investigating a potential issue at one of our US Central data centers that is impacting system capacity. Users may experience higher latencies due to reduced resources. Our engineering team is working to identify the root cause and remediate the problem.
identified Jul 01, 2026, 11:11 PM UTC

We have identified a cooling system failure at one of our US Central data centers that is causing reduced capacity. The team is working on restoring capacity. Users continue to see elevated latencies for specific models.
identified Jul 01, 2026, 11:27 PM UTC

A power loss issue at approximately 22:20pm UTC led to a subsequent cooling system failure at one of our US Central data centers that is causing reduced capacity, primarily for the openai/gpt-oss-20b model. The team is working on restoring capacity.
monitoring Jul 01, 2026, 11:48 PM UTC

We have redistributed and allocated more capacity to production models in the US Central region. Users should see performance return to normal. We’re now monitoring the infrastructure to ensure stability.
resolved Jul 02, 2026, 12:35 AM UTC

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.

Read the full incident report →

Minor March 19, 2026 openai/gpt-oss-120b Performance Issue 32m

Started Mar 19, 2026, 12:51 PM UTC· resolved Mar 19, 2026, 01:23 PM UTC

identified Mar 19, 2026, 12:51 PM UTC

We have identified the problem affecting the openai/gpt-oss-120b model. The issue has been traced to malicious traffic patterns. A fix is in progress, we are working to block the source of these requests. Users may still see degraded performance from requests made to openai/gpt-oss-120b as we identify and block the orgs from which this traffic is originating.
monitoring Mar 19, 2026, 01:23 PM UTC

We have implemented a fix for openai/gpt-oss-120b and performance is improving. We’re now monitoring the model to ensure stability persists. If all remains normal, we will resolve the incident in the next update.
resolved Mar 19, 2026, 01:50 PM UTC

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 patience.

Read the full incident report →

Minor February 7, 2026 meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance 1h 32m meta-llama/llama-4-scout-17b-16e-instruct

Started Feb 07, 2026, 10:02 AM UTC· resolved Feb 07, 2026, 11:34 AM UTC

investigating Feb 07, 2026, 10:02 AM UTC

We are currently investigating reports of an issue with meta-llama/llama-4-scout-17b-16e-instruct. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing logs and infrastructure to identify the cause.
investigating Feb 07, 2026, 10:36 AM UTC

We are continuing to investigating an issue with meta-llama/llama-4-scout-17b-16e-instruct. Users may be experiencing elevated error rates or slow response time. Other models remain operational. Our team is continuing to analyze logs and infrastructure to identify the cause.
identified Feb 07, 2026, 10:59 AM UTC

We have implemented a fix for meta-llama/llama-4-scout-17b-16e-instruct however performance is still degraded. We’re continuing to investigate the models to determine the cause of the issues.
monitoring Feb 07, 2026, 11:13 AM UTC

We have implemented a new fix for meta-llama/llama-4-scout-17b-16e-instruct & groq/compound and performance has improved. We’re continuing monitor the models to ensure stability persists. If all remains normal, we will resolve the incident in the next update.
resolved Feb 07, 2026, 11:34 AM UTC

This incident has been resolved. Thank you for your patience.

Read the full incident report →

Minor February 5, 2026 meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance 23m meta-llama/llama-4-scout-17b-16e-instruct

Started Feb 05, 2026, 06:09 PM UTC· resolved Feb 05, 2026, 06:32 PM UTC

investigating Feb 05, 2026, 06:09 PM UTC

We are currently investigating reports of an issue with meta-llama/llama-4-scout-17b-16e-instruct. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing logs and infrastructure to identify the cause.
monitoring Feb 05, 2026, 06:21 PM UTC

meta-llama/llama-4-scout-17b-16e-instruct and performance is improving. We’re now monitoring the model to ensure stability. If all remains normal, we will resolve the incident in the next update.
resolved Feb 05, 2026, 06:32 PM UTC

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.

Read the full incident report →

Minor February 5, 2026 meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance 1h 44m meta-llama/llama-4-scout-17b-16e-instruct

Started Feb 05, 2026, 01:23 PM UTC· resolved Feb 05, 2026, 03:07 PM UTC

investigating Feb 05, 2026, 01:23 PM UTC

We are currently investigating reports of an issue with meta-llama/llama-4-scout-17b-16e-instruct. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing logs and infrastructure to identify the cause.
identified Feb 05, 2026, 01:33 PM UTC

We have identified the problem affecting the meta-llama/llama-4-scout-17b-16e-instruct. A fix is in progress, users may still see delayed responses and errors from Scout until the fix completes.
monitoring Feb 05, 2026, 01:43 PM UTC

We have implemented a fix for meta-llama/llama-4-scout-17b-16e-instruct and performance is improving. We’re now monitoring the model to ensure stability. If all remains normal, we will resolve the incident in the next update.
monitoring Feb 05, 2026, 02:47 PM UTC

We’re continuing to monitor the scout model to ensure stability persists. If all remains normal, we will resolve the incident in the next update.
resolved Feb 05, 2026, 03:07 PM UTC

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.

Read the full incident report →

Minor January 26, 2026 meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance 1h 53m meta-llama/llama-4-scout-17b-16e-instruct

Started Jan 26, 2026, 11:17 PM UTC· resolved Jan 27, 2026, 01:11 AM UTC

investigating Jan 26, 2026, 11:17 PM UTC

We are currently investigating an issue with meta-llama/llama-4-scout-17b-16e-instruct. Users may be experiencing elevated error rates or slow response time. Other models remain operational. Our team is analyzing logs and infrastructure to identify the cause.
identified Jan 27, 2026, 12:06 AM UTC

We have implemented a fix for meta-llama/llama-4-scout-17b-16e-instruct however performance is still degraded. We’re continuing to investigate the models to determine the cause of the issues.
monitoring Jan 27, 2026, 12:29 AM UTC

We have implemented a new fix for meta-llama/llama-4-scout-17b-16e-instruct & groq/compound and performance has improved. We’re continuing monitor the models to ensure stability persists. If all remains normal, we will resolve the incident in the next update.
resolved Jan 27, 2026, 01:11 AM UTC

This incident has been resolved. Thank you for your patience.