MoonshotAI: Kimi K2.5 Performance
Compare measured TTFT, throughput, uptime, and route health for MoonshotAI: Kimi K2.5 across TrustedRouter providers using metadata-only production probes.
moonshotai/kimi-k2.5
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), effective throughput, and success rate for MoonshotAI: Kimi K2.5. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime, and no prompt or output content is stored.
| Provider | p50 TTFT | p95 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|
| alibaba | 1820 ms | 1820 ms | — | 100.00% | — | 1 |
| novita | 1832 ms | 1832 ms | — | 100.00% | — | 1 |
| nscale | 1905 ms | 3782 ms | — | 100.00% | — | 4 |
| telnyx | 2075 ms | 2535 ms | — | 100.00% | — | 3 |
| siliconflow | 2275 ms | 2275 ms | — | 100.00% | — | 1 |
| digitalocean | 2356 ms | 2582 ms | — | 100.00% | — | 3 |
| io-net | 2398 ms | 2398 ms | — | 100.00% | — | 1 |
| azure | 3320 ms | 4971 ms | — | 100.00% | — | 3 |
Full provider & model leaderboard.
9 routes.
More routes give the auto router more room to fail over around provider 429 and 5xx responses.
Gateway overhead is measured separately.
Public status separates TLS/health overhead from full model latency so slow LLMs do not inflate the router metric.
Metadata rollups.
Status samples store latency, outcome, provider, model, route, cost, and region metadata only.
View public status or inspect provider routes.