Live / Groq / Incident
Groq: Model Performance or Availability Issue
Groq · groq.comMajor incidentResolved2026-10-12 18:36 UTC
Public — what happened
Summary
Groq reported a major problem with its minimaxai/minimax-m2.7 model on 2026-10-12, posting at 18:17 UTC that it had already found the source and was working on a fix. The company said users could run into failed API requests while the repair was underway. Groq attributed the trouble to problems with hardware connections. It marked the issue resolved at 18:36 UTC, saying the model was back to normal operation.
Timeline
- Started — 2026-10-12 18:17 UTC
- Identified — 2026-10-12 18:17 UTC
- Resolved — 2026-10-12 18:36 UTC · 18 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
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.