Skip to content

Most Reliable Nova 2 Lite Inference Providers

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

Amazon Bedrock currently ranks first at 100.00% via amazon-bedrock.

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

Highest uptime endpoint ranking

Most Reliable Nova 2 Lite Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
#1Provider / route
Amazon Bedrockamazon-bedrock
Uptime (last 30 min)100.00%Speed measurements
500-token response
16.56 s
Response starts
0.43 s
Output speed
31.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$2.5 / 1M tokens
Uptime (30 min)
100.00%
Context
1M
#2Provider / route
Amazon Bedrockamazon-bedrock/eu-west-1
Uptime (last 30 min)98.46%Speed measurements
500-token response
5.59 s
Response starts
1.16 s
Output speed
113.0 tok/s
Endpoint details
Input price
$0.3 / 1M tokens
Output price
$2.5 / 1M tokens
Uptime (30 min)
98.46%
Context
1M

Endpoint data fetched .

Nova 2 Lite endpoint guide

How to interpret the Most Reliable Nova 2 Lite Inference Providers

2 of 2 Nova 2 Lite endpoints currently have the published data required for this ranking. Amazon Bedrock leads at 100.00% via amazon-bedrock. 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 Amazon Bedrock with the next option

Amazon Bedrock currently ranks second at 98.46%. 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

Nova 2 Lite 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.