Start typing to search.
Ranks providers by how quickly the first generated token appears. Providers without enough recent data remain visible after ranked rows.
Weights & Biases currently ranks first at 0.24 s via wandb/bf16.
| Rank | Provider / route | Time to first token | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Weights & Biases wandb/bf16 | Time to first token0.24 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route Alibaba Cloud Int. alibaba | Time to first token0.34 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route Nebius nebius/fp8 | Time to first token0.34 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route DekaLLM dekallm | Time to first token0.47 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route Phala phala | Time to first token1.13 s | Speed measurements
| Endpoint details
|
| #6 | Provider / route StreamLake streamlake | Time to first token2.08 s | Speed measurements
| Endpoint details
|
| #7 | Provider / route SiliconFlow siliconflow/fp8 | Time to first token2.11 s | Speed measurements
| Endpoint details
|
Endpoint data fetched .
Qwen3 30B A3B Instruct 2507 endpoint guide
7 of 7 Qwen3 30B A3B Instruct 2507 endpoints currently have the published data required for this ranking. Weights & Biases leads at 0.24 s via wandb/bf16. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.
The first-token ranking orders endpoints by the recent median time before output begins. This is useful for interactive applications, but it should be read alongside throughput because the first provider to start is not always the first to finish a long answer.
Alibaba Cloud Int. currently ranks second at 0.34 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.
Qwen3 30B A3B Instruct 2507 has 7 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.
