Live / Groq / Incident
Groq: openai/gpt-oss-120b Performance Issue
Groq · groq.comMinor incidentResolved2026-03-19 13:50 UTC
Public — what happened
Summary
Groq reported a minor incident on March 19, 2026, in which users sending requests to its openai/gpt-oss-120b model could see slower or degraded performance, beginning at 12:51 UTC. Groq said it had linked the problem to malicious traffic and was working to block the organizations sending it. By 13:23 UTC the company said a fix was in place and performance was getting better. It declared the issue resolved at 13:50 UTC, saying it had cancelled billing plans and limited the verification status of organizations it said were involved in coordinated abuse.
Timeline
- Started — 2026-03-19 12:51 UTC
- Identified — 2026-03-19 12:51 UTC
- Monitoring — 2026-03-19 13:23 UTC
- Resolved — 2026-03-19 13:50 UTC · 59 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