Model Performance or Availability Issue - minimaxai/minimax-m2.7
minor- Started
- Oct 10, 6:09 AM EDT
- Resolved
- Oct 10, 12:14 PM EDT
- Duration
- 6h 5m
Groq's updates (2)
- identified · Oct 10, 6:09 AM EDT
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.
- resolved · Oct 10, 12:14 PM EDT
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.
What our checks recorded
We checked Groq 73 times from Groq's start time to its resolution, once every five minutes. Every one of them reached Groq's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 65 ms, against 79 ms over the 24 hours before. Groq posted the incident at Oct 10, 6:09 AM EDT.
Updates are Groq's own words from its status page (status: resolved); we never add an inferred cause.