Model Performance or Availability Issue - minimaxai/minimax-m2.7
Groq · Last saved provider status: identified
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- identified
- Provider impact
- major
- Provider record created
- 10 Oct 2026, 10:09:21 UTC
- Provider record updated
- 10 Oct 2026, 10:09:21 UTC
- Explicit provider start
- Not available
- Explicit provider end
- Not available
Affected components reported by the provider
Component associations were not provided or have not been recovered for this saved revision.
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
GroqCloud's official production and preview model components and website; individual account availability can vary.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- 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.
Seen in a saved revision at 10 Oct 2026, 10:10:24 UTC