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

What to do

• Check whether your product depends on Groq. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 54m it lasted.

  Anything that failed between 2026-01-26 23:17 UTC and 2026-01-27 01:11 UTC may need a replay.

• Subscribe to Groq's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=groq works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Groq 4

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

   provider

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

   provider

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

   provider

4. resolvedJan 27, 2026, 1:11 AM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.