DeepSeek: DeepSeek V4 Flash 0731 Performance
Compare measured TTFT, throughput, uptime, and route health for DeepSeek V4 Flash 0731 across TrustedRouter providers using metadata-only production probes.
deepseek/deepseek-v4-flash-0731
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), effective throughput, and success rate for DeepSeek: DeepSeek V4 Flash 0731. 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 |
|---|---|---|---|---|---|---|
| relace | 1784 ms | 4043 ms | — | 94.12% | — | 17 |
| baseten | 2112 ms | 4900 ms | — | 100.00% | — | 455 |
| confidential-ai | 3641 ms | 4564 ms | 244 tok/s n=2 | 100.00% | — | 14 |
| nebius | 4185 ms | 8166 ms | — | 99.59% | — | 485 |
| mancer | 1382 ms | 6329 ms | — | 100.00% | — | 4 |
| io-net | 1512 ms | 1512 ms | — | 100.00% | — | 1 |
| pearl | 1538 ms | 3526 ms | 152 tok/s n=2 | 100.00% | — | 9 |
| fireworks | 1541 ms | 1541 ms | 12 tok/s n=1 | 100.00% | — | 1 |
| scaleway | 1580 ms | 4073 ms | — | 100.00% | — | 6 |
| sail-research | 1643 ms | 2140 ms | — | 100.00% | — | 3 |
| telnyx | 1837 ms | 1837 ms | — | 100.00% | — | 1 |
| alibaba | 2212 ms | 2611 ms | — | 100.00% | — | 2 |
| nextbit | 2415 ms | 4113 ms | 124 tok/s n=1 | 100.00% | — | 3 |
| siliconflow | 2456 ms | 4365 ms | — | 100.00% | — | 3 |
| featherless | 2593 ms | 3647 ms | — | 100.00% | — | 2 |
| engy | 3153 ms | 5648 ms | — | 100.00% | — | 5 |
| inceptron | 4123 ms | 10217 ms | — | 75.00% | — | 4 |
| nvidia-nim | 11204 ms | 11204 ms | — | 33.33% | — | 3 |
Full provider & model leaderboard.
24 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.