🟢 Operational
Model Performance or Availability Issue
Resolved
- Started
- 2026-10-12 18:17 UTC
25 days ago - Last update
- 2026-10-12 18:36 UTC
25 days ago - Duration
- 18m
Timeline
-
12 Oct · 18:36 UTC
🟠 Resolved
atom
Status: Resolved
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.
Affected components
minimaxai/minimax-m2.7 (Operational) -
12 Oct · 18:17 UTC
🟠 Identified
atom
Status: Identified
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.
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.