Live / Groq / Incident
Groq: Cloud API Degradation
Groq · groq.comMinor incidentResolved2025-11-05 20:37 UTC
Public — what happened
Summary
Groq reported a minor performance problem with its Cloud API starting at 20:03 UTC on November 5, 2025, warning that users might see more errors than usual or sluggish responses. The company said it pinpointed the problem by 20:13 UTC and had a fix in place by 20:24 UTC, after which it watched for stability. Groq marked the incident resolved at 20:37 UTC, saying the problem was limited to an unreleased internal feature still in development and that it did not believe customers were directly affected.
Timeline
- Started — 2025-11-05 20:03 UTC
- Investigating — 2025-11-05 20:03 UTC
- Identified — 2025-11-05 20:13 UTC
- Monitoring — 2025-11-05 20:24 UTC
- Resolved — 2025-11-05 20:37 UTC · 35 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