Skip to content

Most Reliable Kimi K2 0905 Inference Providers

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

Groq currently ranks first at 99.97% via groq.

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

Highest uptime endpoint ranking

Most Reliable Kimi K2 0905 Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
#1Provider / route
Groqgroq
Uptime (last 30 min)99.97%Speed measurements
500-token response
7.50 s
Response starts
0.35 s
Output speed
70.0 tok/s
Endpoint details
Input price
$1 / 1M tokens
Output price
$3 / 1M tokens
Uptime (30 min)
99.97%
Context
262.1K
#2Provider / route
NovitaAInovita/fp8
Uptime (last 30 min)98.94%Speed measurements
500-token response
36.79 s
Response starts
1.08 s
Output speed
14.0 tok/s
Endpoint details
Input price
$0.6 / 1M tokens
Output price
$2.5 / 1M tokens
Uptime (30 min)
98.94%
Context
262.1K

Endpoint data fetched .

Kimi K2 0905 endpoint guide

How to interpret the Most Reliable Kimi K2 0905 Inference Providers

2 of 2 Kimi K2 0905 endpoints currently have the published data required for this ranking. Groq leads at 99.97% via groq. 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 Groq with the next option

NovitaAI currently ranks second at 98.94%. 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

Kimi K2 0905 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.