Skip to main content

groq · 212d ago

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

Resolved

Yes — groq had a problem on February 5, 2026, and groq has since marked it resolved. groq's latest word: “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.”

See groq's live status →

Timeline

Started: 2/5/2026, 1:23:22 PM

Last update: 3/12/2026, 6:22:51 PM

Resolved: 2/5/2026, 3:07:23 PM

Updates

  • resolved

    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.

    2/5/2026, 3:07:23 PM

  • monitoring

    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.

    2/5/2026, 2:47:32 PM

  • monitoring

    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.

    2/5/2026, 1:43:52 PM

  • identified

    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.

    2/5/2026, 1:33:31 PM

  • investigating

    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/5/2026, 1:23:22 PM

More groq incidents

Is groq down right now?All outage history →