$ uprouter probe --history --provider platform-kimi-com
Kimi — uptime & latency history
Independent, best-effort probes of platform.kimi.com run from Uprouter’s own network. Current status: up · last probe 16h ago. This is not a guarantee — results depend on our network location and cadence; for production always cross-check the provider’s own status page.
// uptime_historyprobe cadence: best-effort
5/7 days w/ probe data · 5 checks
uptime
100%
avg latency
739ms
p95 latency
765ms
incident days
0
daily_status (worst per day)
Oct 19Oct 25
hover a bar for per-day detail
latency_per_day (avg + min–max band)726–765ms
raw_probe_log (latest 32)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-25 00:07 | up | 731ms |
| 2026-10-24 00:06 | up | 765ms |
| 2026-10-22 00:07 | up | 731ms |
| 2026-10-21 00:06 | up | 726ms |
| 2026-10-19 00:07 | up | 741ms |
| 2026-10-18 00:07 | up | 732ms |
| 2026-10-16 00:07 | up | 737ms |
| 2026-10-15 00:06 | up | 810ms |
| 2026-10-13 00:07 | up | 739ms |
| 2026-10-12 00:00 | up | 726ms |
| 2026-10-11 00:33 | up | 769ms |
| 2026-10-10 00:34 | up | 767ms |
| 2026-10-10 00:00 | up | 774ms |
| 2026-10-09 00:00 | up | 768ms |
| 2026-10-08 00:33 | up | 734ms |
| 2026-10-07 00:34 | up | 748ms |
| 2026-10-07 00:00 | up | 946ms |
| 2026-10-06 00:00 | up | 735ms |
| 2026-10-05 00:33 | up | 1128ms |
| 2026-10-04 00:33 | up | 732ms |
| 2026-10-04 00:00 | up | 974ms |
| 2026-10-03 00:00 | up | 760ms |
| 2026-10-02 00:00 | up | 732ms |
| 2026-10-01 00:33 | up | 759ms |
| 2026-09-30 00:33 | up | 780ms |
| 2026-09-29 00:34 | up | 741ms |
| 2026-09-29 00:00 | up | 729ms |
| 2026-09-28 00:00 | up | 729ms |
| 2026-09-27 00:33 | up | 1023ms |
| 2026-09-26 00:33 | up | 731ms |
| 2026-09-26 00:00 | up | 1116ms |
| 2026-09-25 00:00 | up | 731ms |