MiniMax M2
minimax/minimax-m2InputOutput
Compare its 3 providersIncident RSSCompare with MiniMax M2-her, MiniMax M2.1, MiniMax M2.5
CompareMiniMax M2
- No data24h 97.51%
- 7d
- 100%
- 30d
- 99.28%
- p50
- 335ms
- p99
- 2.11s
- Throughput
- 111 tps
- Context
- 197K
- $/Mtok
- $0.300 / $1.20
google-vertex - No data24h 99.93%
- 7d
- 99.93%
- 30d
- 99.90%
- p50
- 1.14s
- p99
- 6.02s
- Throughput
- 44 tps
- Context
- 205K
- $/Mtok
- $0.255 / $1.02
minimax/fp8fp8 - No data24h 99.77%
- 7d
- 100%
- 30d
- 100%
- p50
- 1.26s
- p99
- 1.74s
- Throughput
- 69 tps
- Context
- 205K
- $/Mtok
- $0.300 / $1.20
novita/fp8fp8
Measured 3m ago. Latency and throughput are OpenRouter's rolling 30-minute windows.
History
Availability
Axis starts at 90% so small differences stay visible; it expands to 0 when an endpoint falls below.
Time to first token
Logarithmic axis — the fleet spans two orders of magnitude. P50 is OpenRouter's rolling 30-minute window.
Throughput
Median tokens per second.
Daily availability
One row per endpoint · one dot per day · last 90 days.
worst hour ≥ 95%90–95%< 90%no data
Colour by each endpoint's worst hour of each UTC day · 3 endpoints · 46 days with data, 2 endpoint-days below 90%.