Model Performance or Availability Issue
major- Started
- Oct 12, 2:17 PM EDT
- Resolved
- Oct 12, 2:36 PM EDT
- Duration
- 18 min
Groq's updates (2)
- identified · Oct 12, 2:17 PM EDT
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.
- resolved · Oct 12, 2:36 PM EDT
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.
What our checks recorded
We checked Groq 4 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 43 ms, against 73 ms over the 24 hours before. Groq posted the incident at Oct 12, 2:17 PM EDT.
Updates are Groq's own words from its status page (status: resolved); we never add an inferred cause.