MiniMax M2
minimax/minimax-m2InputOutput
Compare its 3 providersIncident RSSCompare with MiniMax M2-her, MiniMax M2.1, MiniMax M2.5
Showing only the google-vertex provider · show all 3
CompareMiniMax M2
| State | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
Googlegoogle-vertex | No data | — | 95.47% | 100% | 99.31% | 384ms | 2.97s | 65 tps | 197K | $0.300 / $1.20 |
- No data24h 95.47%
- 7d
- 100%
- 30d
- 99.31%
- p50
- 384ms
- p99
- 2.97s
- Throughput
- 65 tps
- Context
- 197K
- $/Mtok
- $0.300 / $1.20
google-vertex
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 · 48 days with data, 2 endpoint-days below 90%. Tables and charts above are filtered to google-vertex.