Live / Groq / Incident
Groq: Data Center Failure Impacting Model Latency - SYD
Groq · groq.comMinor incidentResolved2026-01-24 07:23 UTC
Public — what happened
Summary
Groq reported a minor incident at its Sydney, Australia data center that slowed model responses for customers in that region, beginning at 04:53 UTC on January 24, 2026. The company said it had traced the problem to a network fault and kept working on it through the morning. By 07:06 UTC Groq said a fix was in place and models were gradually recovering, and it marked the incident resolved at 07:23 UTC.
Timeline
- Started — 2026-01-24 04:53 UTC
- Identified — 2026-01-24 04:53 UTC (2 updates)
- Monitoring — 2026-01-24 07:06 UTC (2 updates)
- Resolved — 2026-01-24 07:23 UTC · 2h 31m 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