Groq

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-12 18:17 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.

2. resolved 2026-10-12 18:36 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.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-12 03:37 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.

2. monitoring 2026-10-12 03:47 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.

3. resolved 2026-10-12 04:00 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-10 10:09 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.

2. resolved 2026-10-10 16:14 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.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-01 23:01 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.

2. identified 2026-07-01 23:11 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**.

3. identified 2026-07-01 23:27 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**.

4. monitoring 2026-07-01 23:48 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.

5. resolved 2026-07-02 00:35 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**.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-19 12:51 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...

2. monitoring 2026-03-19 13:23 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.

3. resolved 2026-03-19 13:50 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...

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-07 10:02 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.

2. investigating 2026-02-07 10:36 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.

3. identified 2026-02-07 10:59 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.

4. monitoring 2026-02-07 11:13 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.

5. resolved 2026-02-07 11:34 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-05 18:09 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.

2. monitoring 2026-02-05 18:21 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.

3. resolved 2026-02-05 18:32 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.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-05 13:23 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.

2. identified 2026-02-05 13:33 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.

3. monitoring 2026-02-05 13:43 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.

4. monitoring 2026-02-05 14:47 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.

5. resolved 2026-02-05 15:07 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.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-26 23:17 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.

2. identified 2026-01-27 00:06 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.

3. monitoring 2026-01-27 00:29 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.

4. resolved 2026-01-27 01:11 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-24 04:53 UTC

   We have **identified an issue in our Sydney, AUS data center** that may be causing some latency for customers in this region. The issue was traced to **a network issue**. Users may still see latency until the fix completes.

2. identified 2026-01-24 05:26 UTC

   The team is still working to resolve the issue at our SYD Data Center. Customers in the area may still be experiencing some model latency. We will provide further updates at they are available.

3. monitoring 2026-01-24 07:06 UTC

   The issue impacting our SYD data center has been fixed. Users should gradually see performance return to normal as we continue to recover all models. We will continue to monitor.

4. monitoring 2026-01-24 07:14 UTC

   This issue is now resolved. All services are operating normally. We will continue to monitor for stability and resolve this incident shortly. Thank you for your patience.

5. resolved 2026-01-24 07:23 UTC

   This incident is now resolved.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-24 23:01 UTC

   We’ve identified an issue causing 503s for the `llama-3.3-70b-versatile` production model. We’ve started mitigation. Error rates are improving, but some requests may still fail while we continue tuning and monitoring.

2. monitoring 2025-12-25 00:04 UTC

   We have **implemented a fix** for **llama-3.3-70b-versatile** and performance is improving. The team is continuing to work the issue and we hope to have it resolved shortly.

3. resolved 2025-12-25 00:16 UTC

   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.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-14 09:46 UTC

   We are currently investigating a potential network issue at our DMM1 that is impacting system capacity. Users may experience slower response times or intermittent failures due to reduced resources. Our engineering team is working to identify the root cause and remediate the...

2. identified 2025-12-14 10:12 UTC

   We have identified a failure in our DMM1 infrastructure that is causing reduced capacity and network latency. The team has isolated the cause to the Salam link confirmed down and the Mobily link operating at full capacity, resulting in significant packet loss and is working on...

3. monitoring 2025-12-14 10:30 UTC

   We have restored capacity in DMM 1 and services are beginning to recover. Users should gradually see network performance return to normal. We’re now monitoring the infrastructure to ensure stability.

4. resolved 2025-12-14 13:30 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-06 18:58 UTC

   We are currently investigating reports of an issue with our meta-llama/llama-4-scout-17b-16e-instruct & groq/compound models. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing logs and infrastructure to...

2. investigating 2025-12-06 19:32 UTC

   We are now seeing similar degradation on meta-llama/llama-4-maverick-17b-128e-instruct. The team is still investigating the issue and working to resolve.

3. investigating 2025-12-06 19:59 UTC

   We are no longer seeing issues on meta-llama/llama-4-maverick-17b-128e-instruct. However, the team is still troubleshooting errors and latency issues with meta-llama/llama-4-scout-17b-16e-instruct.

4. monitoring 2025-12-06 20:16 UTC

   We have implemented a new fix for meta-llama/llama-4-scout-17b-16e-instruct and performance and have observed improvement over the last 15 minutes. We’re continuing monitor to ensure stability persists. If all remains normal, we will resolve the incident in the next update. In...

5. resolved 2025-12-06 20:23 UTC

   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.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-02 17:36 UTC

   We are currently investigating reports of an issue with our meta-llama/llama-4-scout-17b-16e-instruct & groq/compound models. Users may be experiencing **elevated error rates and or slow responses**. Other models remain operational. Our team is analyzing logs and infrastructure...

2. monitoring 2025-12-02 17:51 UTC

   We have **implemented a fix** for meta-llama/llama-4-scout-17b-16e-instruct & groq/compound and performance is improving. We’re now **monitoring** the models to ensure stability. If all remains normal, we will resolve the incident in the next update.

3. investigating 2025-12-02 18:06 UTC

   We have implemented a fix for meta-llama/llama-4-scout-17b-16e-instruct & groq/compound however performance is still degraded. We’re continuing to investigate the models to determine the cause of the issues.

4. monitoring 2025-12-02 18:31 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.

5. resolved 2025-12-02 20:02 UTC

   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.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 11:52 UTC

   We are currently investigating an issue with our services that we believe is impacting customer experiences. Our team is has identified that is due to a [global cloudflare outage](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "global cloudflare outage") and is working...

2. monitoring 2025-11-18 12:15 UTC

   We are currently monitoring an issue with our services that is impacting customer experiences. Our team is has identified that is due to an ongoing [global cloudflare outage](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "global cloudflare outage") and is working to...

3. monitoring 2025-11-18 12:31 UTC

   We are continuing to monitor an issue with our services that is impacting customer experiences. Our team is has identified that is due to an ongoing [global cloudflare outage](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "global cloudflare outage") and they've...

4. monitoring 2025-11-18 13:04 UTC

   We are continuing to monitor an issue with our services that is impacting customer experiences due to an ongoing [global cloudflare outage](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "global cloudflare outage"). Cloudflare recently shared that "The are continuing to...

5. monitoring 2025-11-18 13:35 UTC

   We are continuing to monitor an issue with our services that is impacting customer experiences due to an ongoing [global cloudflare outage](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "global cloudflare outage"). Cloudflare recently shared that "We are continuing to...

6. monitoring 2025-11-18 14:09 UTC

   We are continuing to monitor an issue with our services that is impacting customer experiences due to an ongoing [global cloudflare outage](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "global cloudflare outage"). Cloudflare previously shared that "We are continuing...

7. monitoring 2025-11-18 14:48 UTC

   We are continuing to monitor an issue with our services that is impacting customer experiences due to an ongoing [global cloudflare outage](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 "global cloudflare outage"). Cloudflare has just shared that "A fix has been...

8. resolved 2025-11-18 15:26 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-05 20:03 UTC

   We are currently investigating an issue resulting in a performance degradation of our Cloud API. Users may be experiencing **elevated error rates and or slow responses**. Our team is analyzing logs and infrastructure to identify the cause and implement a fix as soon as possible.

2. identified 2025-11-05 20:13 UTC

   We have **identified the problem** causing performance degradation of our Cloud API. A fix is in progress, users may still see elevated error rates and or slow responses until the fix completes. Our team is working on getting this fix rolled out as soon as possible.

3. monitoring 2025-11-05 20:24 UTC

   We have **implemented a fix** for the performance degradation of our Cloud API and performance is improving. We’re now **monitoring** the fix to ensure stability persists. If all remains normal, we will resolve the incident in the next update.

4. resolved 2025-11-05 20:37 UTC

   The 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 development. At this time we don't believe there was any customer...

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-04 02:11 UTC

   We have **identified an issue** affecting the lama-3.1-8b-instant service. A fix is in progress. Users may still experience latency until the fix completes.

2. monitoring 2025-11-04 02:33 UTC

   We have **implemented a fix** for llama-3.1-8b-instant service 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.

3. resolved 2025-11-04 02:47 UTC

   The 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 LoRA latencies were reverted . We apologize for the...

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-22 15:51 UTC

   We are currently investigating reports of an issue with ouropenai/gpt-oss-120b. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing traces, logs and infrastructure to identify the cause.

2. investigating 2025-10-22 16:22 UTC

   We are continuing to investigate issues with our openai/gpt-oss-120b model. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing traces, logs and infrastructure to identify the cause.

3. investigating 2025-10-22 17:17 UTC

   We are continuing to investigate issues with our openai/gpt-oss-120b model. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing traces, logs and infrastructure to identify the cause.

4. investigating 2025-10-22 17:46 UTC

   We are continuing to investigate issues with our openai/gpt-oss-120b model. Users may be experiencing or slow responses. Other models remain operational. Our team is analyzing traces, logs and infrastructure to identify the cause.

5. resolved 2025-10-22 17:59 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-21 15:19 UTC

   We are currently investigating reports of an issue with our openai/gpt-oss-120b model. 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.

2. identified 2025-10-21 15:45 UTC

   We have **identified a problem** affecting the openai/gpt-oss-120b service. The issue was traced to . A fix is in progress, which may take some time to implement. Users may still see elevated error rates or delayed responses until the fix is in place.

3. monitoring 2025-10-21 16:47 UTC

   We are actively implementing a fix for openai/gpt-oss-120b and we expect performance to begin improving shortly. We’ll be monitoring the model to ensure stability as this fix rolls out. If all remains normal, we will resolve the incident in the next update.

4. resolved 2025-10-21 17:12 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-14 21:16 UTC

   We are currently investigating reports of an issue with our meta-llama/llama-4-scout-17b-16e-instruct model. Users may be experiencing **elevated error rates and or slow responses**. Other models remain operational. Our team is analyzing metrics and logs to identify the cause.

2. investigating 2025-10-14 21:48 UTC

   We are continuing to investigate an issue with our meta-llama/llama-4-scout-17b-16e-instruct model. Users may be experiencing **elevated error rates and or slow responses**. Other models remain operational.

3. investigating 2025-10-14 22:30 UTC

   We are still working to identify the root cause of the issue with our meta-llama/llama-4-scout-17b-16e-instruct model. As part of the investigation our team has implemented additional logging to pinpoint the issue. Users may still be experiencing elevated error rates and or slow...

4. monitoring 2025-10-14 22:50 UTC

   We have implemented a fix for the issue impacting our meta-llama/llama-4-scout-17b-16e-instruct model and performance has improved. We’re now **monitoring** the model to ensure stability. If all remains normal, we will resolve the incident in the next update.

5. resolved 2025-10-14 23:18 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-06 23:58 UTC

   We are currently investigating reports of an issue with the llama-3.1-8b-instant model. Users may be experiencing repeated performance degradation, with significant spikes in response times and increased 503 errors across several regions. The team is investigating.

2. identified 2025-10-07 00:07 UTC

   We have identified the problem affecting the llama-3.1-8b-instant service. A fix is in progress. Users may still see impact until the fix completes.

3. monitoring 2025-10-07 00:16 UTC

   We have fix 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.

4. resolved 2025-10-07 00:48 UTC

   The issues affecting llama-3.1-8b-instant have been resolved. The model is operating normally. Thank you for your patience.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-06 18:53 UTC

   We are currently investigating reports of an issue with our **[**llama-3.3-70b-versatile and llama-3.1-8b-instant models. Users may be experiencing **elevated error rates and or slow responses**. Other models remain operational. Our team is analyzing logs and infrastructure to...

2. monitoring 2025-10-06 19:08 UTC

   We have **implemented a fix** for the llama-3.3-70b-versatile and llama-3.1-8b-instant models 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.

3. resolved 2025-10-06 19:42 UTC

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

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-18 01:38 UTC

   Following the login system upgrade earlier today, we’ve identified an issue with Vercel-initiated logins. Users starting login from Vercel may see an error. Other login methods are unaffected. The team is working to identify the cause to remediate. **Workaround:** Log in...

2. monitoring 2025-09-18 02:32 UTC

   A small number of Vercel‑initiated logins may error. Direct login at the Groq console works normally. We are coordinating on a fix with our identity provider. We will update this page if impact or timeline changes.

3. resolved 2025-09-18 17:45 UTC

   Vercel‑initiated login is operating normally. Other login methods were unaffected. This incident is now resolved.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-10 17:04 UTC

   We are investigating an issue causing elevated latency on search tooling affecting the **groq/compound, groq/compound-mini, openai/gpt-oss-120b and openai/gpt-oss-20b** models. The team is working to identify the cause and remediate.

2. monitoring 2025-09-10 17:37 UTC

   A fix has been implemented and performance is improving. We’re now monitoring the models to ensure stability. If all remains normal, we will resolve the incident in the next update.

3. resolved 2025-09-10 17:45 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Groq's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-08 21:08 UTC

   We have identified an issue where a small portion of requests against llama-3.3-70b-versatile are returning degraded output. A fix is in progress, Users may still see the issue until the fix is fully deployed.

2. monitoring 2025-09-08 22:56 UTC

   We have implemented a fix and are no longer seeing degraded output from llama-3.3-70b. The team is monitoring this model to ensure continued performance.

3. resolved 2025-09-08 23:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Groq's status page.