Start typing to search.
Ranks providers by estimated time to return 500 tokens, combining the wait for the first token with output speed.
Alibaba Cloud Int. currently ranks first at 6.67 s via alibaba.
| Rank | Provider / route | Estimated response time | Speed measurements | Endpoint details |
|---|---|---|---|---|
| #1 | Provider / route Alibaba Cloud Int. alibaba | Estimated response time6.67 s | Speed measurements
| Endpoint details
|
| #2 | Provider / route Phala phala | Estimated response time6.71 s | Speed measurements
| Endpoint details
|
| #3 | Provider / route DekaLLM dekallm | Estimated response time6.96 s | Speed measurements
| Endpoint details
|
| #4 | Provider / route Nebius nebius/fp8 | Estimated response time7.39 s | Speed measurements
| Endpoint details
|
| #5 | Provider / route Weights & Biases wandb/bf16 | Estimated response time8.30 s | Speed measurements
| Endpoint details
|
| #6 | Provider / route StreamLake streamlake | Estimated response time12.95 s | Speed measurements
| Endpoint details
|
| #7 | Provider / route SiliconFlow siliconflow/fp8 | Estimated response time25.92 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. Alibaba Cloud Int. leads at 6.67 s via alibaba. 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.
Phala currently ranks second at 6.71 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.
