Live  /  Groq  /  Incident

Groq: API Errors Affecting Multiple Regions

Groq · groq.comMinor incidentResolved2025-09-03 16:40 UTC
Public — what happened

Summary

Groq reported a minor incident beginning at 15:58 UTC on September 3, 2025, initially describing reduced capacity in its me-central-1 region that could cause more failed requests for users. By 16:13 UTC, Groq said the problem had spread to infrastructure in several regions, with API requests returning higher error rates and wrongly rejected as unauthorized (401 errors), and that it had traced the cause to an authentication problem. The company said a fix was in place by 16:37 UTC with error rates back to normal, and it declared the incident resolved at 16:40 UTC.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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

The full archive is on the Groq status & history page.

Related: Groq status & history. SquidGrid is not affiliated with Groq.