Start typing to search.
Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.
Google Vertex currently ranks first at 3.96 s via google-vertex/us-west2.
| Rank | Provider / route | Estimated response time | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Google Vertex google-vertex/us-west2 | Estimated response time3.96 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route SambaNova sambanova/fp8 | Estimated response time10.21 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route Weights & Biases wandb/fp8 | Estimated response time11.00 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route MARA mara | Estimated response time13.17 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route SiliconFlow siliconflow/fp8 | Estimated response time29.40 s | Speed measurements
| Endpoint details
|
| #6 | Provider / route NovitaAI novita/fp8 | Estimated response time29.51 s | Speed measurements
| Endpoint details
|
| #7 | Provider / route DeepInfra deepinfra/fp4 | Estimated response time56.59 s | Speed measurements
| Endpoint details
|
| #8 | Provider / route AtlasCloud atlas-cloud/fp8 | Estimated response time126.46 s | Speed measurements
| Endpoint details
|
Endpoint data fetched .
DeepSeek V3.1 endpoint guide
8 of 8 DeepSeek V3.1 endpoints currently have the published data required for this ranking. Google Vertex leads at 3.96 s via google-vertex/us-west2. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
The fastest ranking estimates a 500-token answer by adding the recent median first-token wait to 500 divided by median output throughput. It represents an example complete response, not a guarantee for every prompt or request size.
SambaNova currently ranks second at 10.21 s. Compare that gap with input and output price, response-start time, output speed, 30-minute uptime, context length, and the exact route before deciding whether first place is meaningful for your workload.
DeepSeek V3.1 has 8 published provider options, and performance data is matched to each exact OpenRouter routing tag. Different quantization, context, regional deployment, or provider configuration can change price and behavior even when the underlying model name is identical.
