Live / Groq / Incident
Groq: meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance
Groq · groq.comMinor incidentResolved2026-02-07 11:34 UTC
Public — what happened
Summary
Groq said that on February 7, 2026, starting at 10:02 UTC, people using its meta-llama/llama-4-scout-17b-16e-instruct model might see more errors than usual or sluggish replies, while its other models kept working normally. An initial fix applied around 10:59 UTC did not fully restore performance, and Groq did not say what caused the problem. At 11:13 UTC the company reported a second fix, which also covered groq/compound, had improved things, and it marked the incident resolved at 11:34 UTC.
Timeline
- Started — 2026-02-07 10:02 UTC
- Investigating — 2026-02-07 10:02 UTC (2 updates)
- Identified — 2026-02-07 10:59 UTC
- Monitoring — 2026-02-07 11:13 UTC
- Resolved — 2026-02-07 11:34 UTC · 1h 33m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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