MiniMax: MiniMax M3.1 Flash Performance
Try MiniMax M3.1 Flash on us. Starter credit covers your first requests, then one key reaches all 12 provider routes with automatic failover.
minimax/minimax-m3.1-flash
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), effective throughput, and success rate for MiniMax: MiniMax M3.1 Flash. 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 |
|---|---|---|---|---|---|---|
| together | 594 ms | 594 ms | — | 100.00% | — | 1 |
| minimax | 1423 ms | 1918 ms | — | 100.00% | — | 8 |
| boundless | 2011 ms | 2381 ms | — | 100.00% | — | 2 |
| gmi | 2221 ms | 3165 ms | — | 100.00% | — | 5 |
| featherless | 5195 ms | 5195 ms | — | 100.00% | — | 1 |
| nvidia-nim | — | — | — | 0.00% | — | 1 |
| zro | — | — | — | — | 3 provider_auth_config |
0 |
Full provider & model leaderboard.
12 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.