Live / Groq / Incident
Groq: Llama-3.1-8b-instant model Degraded Performance
Groq · groq.comMinor incidentResolved2025-10-07 00:48 UTC
Public — what happened
Summary
Groq reported a minor incident affecting its llama-3.1-8b-instant model, beginning at 23:58 UTC on October 6, 2025, with users in several regions possibly seeing much slower responses and more 503 errors. About nine minutes later, Groq said it had pinpointed the problem and was working on a fix, though it did not describe the cause publicly. By 00:16 UTC the company said a fix was in place and performance was getting better. Groq marked the incident resolved at 00:48 UTC on October 7, saying the model was working normally again.
Timeline
- Started — 2025-10-06 23:58 UTC
- Investigating — 2025-10-06 23:58 UTC
- Identified — 2025-10-07 00:07 UTC
- Monitoring — 2025-10-07 00:16 UTC
- Resolved — 2025-10-07 00:48 UTC · 49 min 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