Live / Groq / Incident
Groq: meta-llama/llama-4-scout-17b-16e-instruct & groq/compound Degraded Performance
Groq · groq.comMinor incidentResolved2025-10-14 23:18 UTC
Public — what happened
Summary
Groq said that starting at 21:16 UTC on October 14, 2025, its meta-llama/llama-4-scout-17b-16e-instruct model was having problems, with users possibly seeing more errors than usual or sluggish replies; the incident title also listed groq/compound. The company said its other models kept working normally while engineers looked into the problem and added extra logging to track it down. Groq did not publicly name a cause, but reported putting a fix in place at 22:50 UTC, after which performance got better. It declared the incident resolved at 23:18 UTC, saying the model was back to normal.
Timeline
- Started — 2025-10-14 21:16 UTC
- Investigating — 2025-10-14 21:16 UTC (3 updates)
- Monitoring — 2025-10-14 22:50 UTC
- Resolved — 2025-10-14 23:18 UTC · 2h 02m 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