Outage recap · Groq

Groq outage — February 7, 2026

On February 7, 2026, Groq had a reported incident on Groq's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance

minor
Started
Feb 7, 5:02 AM EST
Resolved
Feb 7, 6:34 AM EST
Duration
1h 33m

Groq's updates (5)

  1. investigating · Feb 7, 5:02 AM EST

    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 · Feb 7, 5:36 AM EST

    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 · Feb 7, 5:59 AM EST

    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 · Feb 7, 6:13 AM EST

    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 · Feb 7, 6:34 AM EST

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

Updates are Groq's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Groq. This recap summarizes incidents published on Groq's official status page.