Skip to content

Most Reliable Qwen3 VL 235B A22B Thinking Inference Providers

Ranks providers by the uptime OpenRouter measured during the latest 30-minute window.

Alibaba Cloud Int. currently ranks first at 89.57% via alibaba.

Provider options:
2
Ranked:
1
Metric:
Uptime (last 30 min)

Highest uptime endpoint ranking

Most Reliable Qwen3 VL 235B A22B Thinking Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
#1Provider / route
Uptime (last 30 min)89.57%Speed measurements
500-token response
9.51 s
Response starts
0.89 s
Output speed
58.0 tok/s
Endpoint details
Input price
$0.26 / 1M
Output price
$2.6 / 1M
Uptime (30 min)
89.57%
Context
131.1K
Provider / route
NovitaAInovita/bf16
Uptime (last 30 min)Insufficient recent dataSpeed measurements
500-token response
13.95 s
Response starts
2.04 s
Output speed
42.0 tok/s
Endpoint details
Input price
$0.98 / 1M
Output price
$3.95 / 1M
Uptime (30 min)
Insufficient recent data
Context
131.1K

Endpoint data fetched .

Qwen3 VL 235B A22B Thinking endpoint guide

How to interpret the Most Reliable Qwen3 VL 235B A22B Thinking Inference Providers

1 of 2 Qwen3 VL 235B A22B Thinking endpoints currently have the published data required for this ranking. Alibaba Cloud Int. leads at 89.57% via alibaba. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.

How recent uptime is ranked

The reliability ranking uses the published 30-minute endpoint uptime measurement. This short operational window can reveal current instability, but it is not a service-level agreement or a substitute for longer-term availability monitoring.

Compare Alibaba Cloud Int. with the next option

Only 1 route currently qualifies, so the rank alone provides limited choice. Review every visible endpoint for price, speed, uptime, context length, and route-specific configuration.

Use the route, not only the provider name

Qwen3 VL 235B A22B Thinking has 2 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.