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 23m it lasted.

  Anything that failed between 2026-02-05 18:09 UTC and 2026-02-05 18:32 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 3

1. investigatingFeb 5, 2026, 6: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.

   provider

2. monitoringFeb 5, 2026, 6: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.

   provider

3. resolvedFeb 5, 2026, 6: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.

   provider

Corrections

None so far.

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