Skip to content

Most Reliable Llama 3 8B Lunaris Inference Providers

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

NovitaAI currently ranks first at 100.00% via novita/bf16.

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

Highest uptime endpoint ranking

Most Reliable Llama 3 8B Lunaris Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
#1Provider / route
NovitaAInovita/bf16
Uptime (last 30 min)100.00%Speed measurements
500-token response
7.65 s
Response starts
0.30 s
Output speed
68.0 tok/s
Endpoint details
Input price
$0.05 / 1M tokens
Output price
$0.05 / 1M tokens
Uptime (30 min)
100.00%
Context
8.2K
#2Provider / route
DeepInfradeepinfra/turbo
Uptime (last 30 min)99.97%Speed measurements
500-token response
7.20 s
Response starts
0.16 s
Output speed
71.0 tok/s
Endpoint details
Input price
$0.04 / 1M tokens
Output price
$0.05 / 1M tokens
Uptime (30 min)
99.97%
Context
8.2K

Endpoint data fetched .

Llama 3 8B Lunaris endpoint guide

How to interpret the Most Reliable Llama 3 8B Lunaris Inference Providers

2 of 2 Llama 3 8B Lunaris endpoints currently have the published data required for this ranking. NovitaAI leads at 100.00% via novita/bf16. 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 NovitaAI with the next option

DeepInfra currently ranks second at 99.97%. 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

Llama 3 8B Lunaris 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.