Live / Groq / Incident
Groq: meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance
Groq · groq.comMinor incidentResolved2026-01-27 01:11 UTC
Public — what happened
Summary
Groq reported a minor problem with its meta-llama/llama-4-scout-17b-16e-instruct model beginning at 23:17 UTC on January 26, 2026, saying users might see more errors or slower responses while its other models kept working normally. The company said a first fix at 00:06 UTC did not fully restore performance, and it did not state a cause. A second fix, which Groq said also covered groq/compound, improved performance by 00:29 UTC. Groq marked the incident resolved at 01:11 UTC on January 27.
Timeline
- Started — 2026-01-26 23:17 UTC
- Investigating — 2026-01-26 23:17 UTC
- Identified — 2026-01-27 00:06 UTC
- Monitoring — 2026-01-27 00:29 UTC
- Resolved — 2026-01-27 01:11 UTC · 1h 54m 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