MiniMax: MiniMax M2.7 Performance
Compare measured TTFT, throughput, uptime, and route health for MiniMax: MiniMax M2.7 across TrustedRouter providers using metadata-only production probes.
minimax/minimax-m2.7
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), effective throughput, and success rate for MiniMax: MiniMax M2.7. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime, and no prompt or output content is stored.
| Provider | p50 TTFT | p95 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|
| morph | 1836 ms | 7111 ms | — | 66.67% | — | 3 |
| minimax | 2857 ms | 4099 ms | — | 100.00% | — | 7 |
| novita | 2866 ms | 2866 ms | — | 100.00% | — | 1 |
| sambanova | 3665 ms | 6149 ms | — | 100.00% | — | 4 |
| atlas-cloud | 3752 ms | 3752 ms | — | 100.00% | — | 1 |
| telnyx | 3968 ms | 3968 ms | — | 100.00% | — | 1 |
Full provider & model leaderboard.
7 routes.
More routes give the auto router more room to fail over around provider 429 and 5xx responses.
Gateway overhead is measured separately.
Public status separates TLS/health overhead from full model latency so slow LLMs do not inflate the router metric.
Metadata rollups.
Status samples store latency, outcome, provider, model, route, cost, and region metadata only.
View public status or inspect provider routes.