Changes / Groq / Model Performance or Availability Issue - minimaxai/minimax-m2.7
Groq: Major incident: Model Performance or Availability Issue - minimaxai/minimax-m2.7
Summary
Groq reported a major incident affecting the enterprise-only minimaxai/minimax-m2.7 model, with users potentially seeing failed requests due to data center hardware issues. It started at 2026-10-10 10:09 UTC and was resolved at 2026-10-10 16:14 UTC, lasting 6 h 5 min; Groq confirmed normal operation.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Model Performance or Availability Issue - minimaxai/minimax-m2.7
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-10-10 10:09 UTC
Before: not present
After: 2026-10-10 16:14 UTC
Before: not present
After: We have identified the problem affecting the enterprise-only minimaxai/minimax-m2.7 model. The issue was traced to hardware issues in our data center. A fix is in progress. Users may still see failed requests 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: Data center hardware 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 - minimaxai/minimax-m2.7 (this change) Groq reported a major incident affecting the enterprise-only minimaxai/minimax-m2.7 model, with users potentially seeing failed requests due to data center hardware issues. It started at 2026-10-10 10:09 UTC and was resolved at 2026-10-10 16:14 UTC, lasting 6 h 5 min; Groq confirmed normal operation. | Major incident |