DeepSeek: DeepSeek V3.2 Performance
Try DeepSeek V3.2 on us. Starter credit covers your first requests, then one key reaches all 7 provider routes with automatic failover.
deepseek/deepseek-v3.2
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), 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 | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|
| amazon-bedrock | 1463 ms | 1463 ms | — | 100.00% | — | 1 |
| io-net | 1541 ms | 1732 ms | — | 100.00% | — | 2 |
| digitalocean | 2423 ms | 2542 ms | — | 75.00% | 1 provider_error |
4 |
| chutes | — | — | — | — | 1 provider_error |
0 |
| venice | — | — | — | — | 1 provider_error |
0 |
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.