🟢 Operational
Model Performance or Availability Issue - minimaxai/minimax-m2.7
Resolved
- Started
- 2026-10-10 10:09 UTC
27 days ago - Last update
- 2026-10-10 16:14 UTC
27 days ago - Duration
- 6h 5m
Timeline
-
10 Oct · 16:14 UTC
🟠 Resolved
atom
Status: Resolved
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.
Affected components
minimaxai/minimax-m2.7 (Operational) -
10 Oct · 10:09 UTC
🟠 Identified
atom
Status: Identified
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.
Affected components
minimaxai/minimax-m2.7 (Partial outage)
Source
Official Groq status — view original incident ↗
IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.