MoonshotAI: Kimi K2.5 Performance
TrustedRouter performance signals and provider route posture for MoonshotAI: Kimi K2.5.
moonshotai/kimi-k2.5
Measured performance
Continuously sampled p50/p95 time-to-first-token (TTFT), time-to-first-byte (TTFB), 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 | p50 TTFB | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|---|---|
| deepinfra | 1188 ms | 3251 ms | 1188 ms | — | 100.00% | — | 2 |
| novita | 1243 ms | 1243 ms | 1243 ms | — | 100.00% | — | 1 |
| digitalocean | 1624 ms | 7628 ms | 1623 ms | — | 100.00% | — | 4 |
| telnyx | 2712 ms | 3900 ms | 2711 ms | — | 100.00% | — | 7 |
| alibaba | 2959 ms | 2959 ms | 2959 ms | — | 100.00% | — | 1 |
| kimi | 2972 ms | 14565 ms | 2972 ms | — | 100.00% | — | 7 |
Full provider & model leaderboard.
15 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.