Skip to content

Most Reliable Nova Pro 1.0 Inference Providers

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

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

Highest uptime endpoint ranking

Most Reliable Nova Pro 1.0 Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
Provider / route
Amazon Bedrockamazon-bedrock/eu-west-1
Uptime (last 30 min)Insufficient recent dataSpeed measurements
500-token response
4.91 s
Response starts
0.46 s
Output speed
112.5 tok/s
Endpoint details
Input price
$0.8 / 1M tokens
Output price
$3.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
300K
Provider / route
Amazon Bedrockamazon-bedrock
Uptime (last 30 min)Insufficient recent dataSpeed measurements
500-token response
4.90 s
Response starts
0.55 s
Output speed
115.0 tok/s
Endpoint details
Input price
$0.8 / 1M tokens
Output price
$3.2 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
300K

Endpoint data fetched .

Nova Pro 1.0 endpoint guide

How to interpret the Most Reliable Nova Pro 1.0 Inference Providers

0 of 2 Nova Pro 1.0 endpoints currently have the published data required for this ranking. No endpoint currently has enough data to receive first place. 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 all available routes

Only 0 routes 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

Nova Pro 1.0 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.