Live  /  Groq  /  Incident

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

Groq · groq.comMinor incidentResolved2026-02-05 15:07 UTC
Public — what happened

Summary

Groq reported a minor incident on February 5, 2026, starting at 13:23 UTC, in which its meta-llama/llama-4-scout-17b-16e-instruct model was returning more errors and responding slowly for some users, while its other models kept working. About ten minutes later, Groq said it had pinpointed the problem, though it did not describe what it was, and by 13:43 UTC it reported a fix was in place and performance was getting better. After a period of monitoring, Groq marked the incident resolved at 15:07 UTC and said the model was running normally again.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Groq against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Groq: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Groq report →

More from Groq

The full archive is on the Groq status & history page.

Related: Groq status & history. SquidGrid is not affiliated with Groq.