MoonshotAI: Kimi K2.5 Performance
Try Kimi K2.5 on us. Starter credit covers your first requests, then one key reaches all 10 provider routes with automatic failover.
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 |
|---|---|---|---|---|---|---|
| telnyx | 861 ms | 861 ms | — | 100.00% | — | 1 |
| atlas-cloud | 1471 ms | 1471 ms | — | 100.00% | — | 1 |
| siliconflow | 1776 ms | 1942 ms | — | 100.00% | — | 2 |
| alibaba | 2248 ms | 2309 ms | — | 100.00% | — | 2 |
| azure | 2507 ms | 2507 ms | — | 100.00% | — | 1 |
| nscale | 3788 ms | 3788 ms | — | 100.00% | — | 1 |
Full provider & model leaderboard.
10 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.