Skip to content

Most Reliable Qwen2.5 VL 72B Instruct Inference Providers

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

Nebius currently ranks first at 99.94% via nebius/fp8.

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

Highest uptime endpoint ranking

Most Reliable Qwen2.5 VL 72B Instruct Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
#1Provider / route
Nebiusnebius/fp8
Uptime (last 30 min)99.94%Speed measurements
500-token response
27.15 s
Response starts
0.83 s
Output speed
19.0 tok/s
Endpoint details
Input price
$0.25 / 1M tokens
Output price
$0.75 / 1M tokens
Uptime (30 min)
99.94%
Context
32K
#2Provider / route
Parasailparasail/fp8
Uptime (last 30 min)99.89%Speed measurements
500-token response
17.65 s
Response starts
0.98 s
Output speed
30.0 tok/s
Endpoint details
Input price
$0.8 / 1M tokens
Output price
$1 / 1M tokens
Uptime (30 min)
99.89%
Context
128K

Endpoint data fetched .

Qwen2.5 VL 72B Instruct endpoint guide

How to interpret the Most Reliable Qwen2.5 VL 72B Instruct Inference Providers

2 of 2 Qwen2.5 VL 72B Instruct endpoints currently have the published data required for this ranking. Nebius leads at 99.94% via nebius/fp8. 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 Nebius with the next option

Parasail currently ranks second at 99.89%. 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.

Use the route, not only the provider name

Qwen2.5 VL 72B Instruct 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.