Changes / Groq / Model Performance or Availability Issue
Groq: Major incident: Model Performance or Availability Issue
Summary
Groq reported a major incident affecting minimaxai/minimax-m2.7, with users potentially seeing API failures due to hardware connectivity issues. It started at 2026-10-12 18:17 UTC and was resolved at 2026-10-12 18:36 UTC; the computed duration was 18 min, and Groq confirmed normal model operation.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Model Performance or Availability Issue
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-10-12 18:17 UTC
Before: not present
After: 2026-10-12 18:36 UTC
Before: not present
After: We have identified the problem affecting the minimaxai/minimax-m2.7 service. The issue was traced to hardware connectivity issues. A fix is in progress. Users may still see API failures until the fix completes.
Before: not present
After: The issues affecting minimaxai/minimax-m2.7 have been resolved. The model is operating normally. Root cause: hardware connectivity issues. We apologize for the disruption and thank you for your patience.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Model Performance or Availability Issue (this change) Groq reported a major incident affecting minimaxai/minimax-m2.7, with users potentially seeing API failures due to hardware connectivity issues. It started at 2026-10-12 18:17 UTC and was resolved at 2026-10-12 18:36 UTC; the computed duration was 18 min, and Groq confirmed normal model operation. | Major incident |