Skip to content

Most Reliable Nex-N2-Pro Inference Providers

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

Nex AGI currently ranks first at 99.65% via nex-agi/fp8.

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

Highest uptime endpoint ranking

Most Reliable Nex-N2-Pro Inference Providers
RankProvider / routeUptime (last 30 min)Speed measurementsEndpoint details
#1Provider / route
Nex AGInex-agi/fp8
Uptime (last 30 min)99.65%Speed measurements
500-token response
9.45 s
Response starts
0.98 s
Output speed
59.0 tok/s
Endpoint details
Input price
$0.25 / 1M tokens
Output price
$1 / 1M tokens
Uptime (30 min)
99.65%
Context
262.1K
Provider / route
SiliconFlowsiliconflow
Uptime (last 30 min)Insufficient recent dataSpeed measurements
500-token response
9.89 s
Response starts
2.43 s
Output speed
67.0 tok/s
Endpoint details
Input price
$0.5 / 1M tokens
Output price
$2.5 / 1M tokens
Uptime (30 min)
Insufficient recent data
Context
262.1K

Endpoint data fetched .

Nex-N2-Pro endpoint guide

How to interpret the Most Reliable Nex-N2-Pro Inference Providers

1 of 2 Nex-N2-Pro endpoints currently have the published data required for this ranking. Nex AGI leads at 99.65% via nex-agi/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 Nex AGI 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

Nex-N2-Pro 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.