Start typing to search.
Ranks providers by the uptime OpenRouter measured during the latest 30-minute window.
| Rank | Provider / route | Uptime (last 30 min) | Speed measurements | Endpoint details |
|---|---|---|---|---|
| — | Provider / route MiniMax minimax/fp8 | Uptime (last 30 min)Insufficient recent data | Speed measurements
| Endpoint details
|
| — | Provider / route Google Vertex google-vertex | Uptime (last 30 min)Insufficient recent data | Speed measurements
| Endpoint details
|
| — | Provider / route NovitaAI novita/fp8 | Uptime (last 30 min)Insufficient recent data | Speed measurements
| Endpoint details
|
Endpoint data fetched .
MiniMax M2 endpoint guide
0 of 3 MiniMax M2 endpoints currently have the published data required for this ranking. No endpoint currently has enough data to receive first place. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
The reliability ranking uses the published 30-minute endpoint uptime measurement. This short operational window can reveal current instability, but it is not a service-level agreement or a substitute for longer-term availability monitoring.
Only 0 routes currently qualifies, so the rank alone provides limited choice. Review every visible endpoint for price, speed, uptime, context length, and route-specific configuration.
MiniMax M2 has 3 published provider options, and performance data is matched to each exact OpenRouter routing tag. Different quantization, context, regional deployment, or provider configuration can change price and behavior even when the underlying model name is identical.
