Skip to content

Most Reliable ReMM SLERP 13B Inference Providers

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

NextBit currently ranks first at 96.95% via nextbit/bf16.

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

Highest uptime endpoint ranking

Most Reliable ReMM SLERP 13B Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
#1Provider / route
NextBitnextbit/bf16
Uptime (last 30 min)96.95%Speed measurements
500-token response
31.17 s
Response starts
1.76 s
Output speed
17.0 tok/s
Endpoint details
Input price
$0.45 / 1M tokens
Output price
$0.65 / 1M tokens
Uptime (30 min)
96.95%
Context
6.1K
Provider / route
Mancermancer/fp8
Uptime (last 30 min)Insufficient recent dataSpeed measurements
500-token response
15.82 s
Response starts
0.90 s
Output speed
33.5 tok/s
Endpoint details
Input price
$0.5 / 1M tokens
Output price
$0.75 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
6.1K

Endpoint data fetched .

ReMM SLERP 13B endpoint guide

How to interpret the Most Reliable ReMM SLERP 13B Inference Providers

1 of 2 ReMM SLERP 13B endpoints currently have the published data required for this ranking. NextBit leads at 96.95% via nextbit/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 NextBit with the next option

Only 1 route 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

ReMM SLERP 13B 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.