DeepSeek: DeepSeek V3.2 Performance
TrustedRouter performance signals and provider route posture for DeepSeek: DeepSeek V3.2.
deepseek/deepseek-v3.2
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), time-to-first-byte (TTFB), effective throughput, and success rate for DeepSeek: DeepSeek V3.2. 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 | p50 TTFB | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|---|
| digitalocean | 1596 ms | 3431 ms | 1596 ms | — | 100.00% | — | 3 |
| siliconflow | 2517 ms | 3994 ms | 2516 ms | — | 100.00% | 1 unsupported_route |
3 |
| friendli | 2869 ms | 7092 ms | 2869 ms | — | 100.00% | — | 7 |
| atlas-cloud | 3980 ms | 3980 ms | 3980 ms | — | 100.00% | — | 1 |
| chutes | 4166 ms | 6378 ms | 4166 ms | — | 100.00% | — | 7 |
Full provider & model leaderboard.
15 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.