Skip to content

Most Reliable Ministral 3 14B 2512 Inference Providers

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

NextBit currently ranks first at 100.00% via nextbit/fp8.

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

Highest uptime endpoint ranking

Most Reliable Ministral 3 14B 2512 Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
#1Provider / route
NextBitnextbit/fp8
Uptime (last 30 min)100.00%Speed measurements
500-token response
22.45 s
Response starts
0.71 s
Output speed
23.0 tok/s
Endpoint details
Input price
$0.35 / 1M tokens
Output price
$0.35 / 1M tokens
Uptime (30 min)
100.00%
Context
262.1K
#2Provider / route
Mistralmistral
Uptime (last 30 min)99.94%Speed measurements
500-token response
13.14 s
Response starts
0.32 s
Output speed
39.0 tok/s
Endpoint details
Input price
$0.2 / 1M tokens
Output price
$0.2 / 1M tokens
Uptime (30 min)
99.94%
Context
262.1K

Endpoint data fetched .

Ministral 3 14B 2512 endpoint guide

How to interpret the Most Reliable Ministral 3 14B 2512 Inference Providers

2 of 2 Ministral 3 14B 2512 endpoints currently have the published data required for this ranking. NextBit leads at 100.00% via nextbit/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 NextBit with the next option

Mistral currently ranks second at 99.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

Ministral 3 14B 2512 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.