$ uprouter probe --history --provider cun-ai
Cun.ai — uptime & latency history
Independent, best-effort probes of cun.ai run from Uprouter’s own network. Current status: up · last probe 1d 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
4/7 days w/ probe data · 4 checks
uptime
100%
avg latency
616ms
p95 latency
657ms
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)529–657ms
raw_probe_log (latest 31)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-24 00:07 | up | 529ms |
| 2026-10-23 00:06 | up | 657ms |
| 2026-10-21 00:07 | up | 648ms |
| 2026-10-20 00:06 | up | 629ms |
| 2026-10-18 00:07 | up | 617ms |
| 2026-10-17 00:06 | up | 570ms |
| 2026-10-15 00:07 | up | 522ms |
| 2026-10-13 00:07 | up | 604ms |
| 2026-10-12 00:33 | up | 577ms |
| 2026-10-11 00:34 | up | 542ms |
| 2026-10-11 00:00 | up | 575ms |
| 2026-10-10 00:00 | up | 661ms |
| 2026-10-09 00:33 | up | 616ms |
| 2026-10-08 00:33 | up | 606ms |
| 2026-10-07 00:34 | up | 619ms |
| 2026-10-07 00:00 | up | 640ms |
| 2026-10-06 00:00 | up | 614ms |
| 2026-10-05 00:33 | up | 582ms |
| 2026-10-04 00:34 | up | 581ms |
| 2026-10-04 00:00 | up | 599ms |
| 2026-10-03 00:00 | up | 588ms |
| 2026-10-02 00:33 | up | 601ms |
| 2026-10-01 00:33 | up | 597ms |
| 2026-09-30 00:34 | up | 657ms |
| 2026-09-30 00:00 | up | 685ms |
| 2026-09-29 00:00 | up | 671ms |
| 2026-09-28 00:00 | up | 629ms |
| 2026-09-27 00:33 | up | 629ms |
| 2026-09-26 00:34 | up | 587ms |
| 2026-09-26 00:00 | up | 618ms |
| 2026-09-25 00:00 | up | 631ms |