$ uprouter probe --history --provider docode-cc
Docode — uptime & latency history
Independent, best-effort probes of docode.cc 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
440ms
p95 latency
449ms
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)428–449ms
raw_probe_log (latest 31)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-24 00:07 | up | 442ms |
| 2026-10-23 00:06 | up | 428ms |
| 2026-10-21 00:07 | up | 439ms |
| 2026-10-20 00:06 | up | 449ms |
| 2026-10-18 00:07 | up | 417ms |
| 2026-10-17 00:06 | up | 432ms |
| 2026-10-15 00:07 | up | 427ms |
| 2026-10-13 00:07 | up | 432ms |
| 2026-10-12 00:33 | up | 452ms |
| 2026-10-11 00:34 | up | 463ms |
| 2026-10-11 00:00 | up | 453ms |
| 2026-10-10 00:00 | up | 408ms |
| 2026-10-09 00:33 | up | 423ms |
| 2026-10-08 00:33 | up | 423ms |
| 2026-10-08 00:00 | up | 427ms |
| 2026-10-07 00:00 | up | 432ms |
| 2026-10-06 00:01 | up | 430ms |
| 2026-10-05 00:33 | up | 441ms |
| 2026-10-04 00:34 | up | 428ms |
| 2026-10-04 00:00 | up | 460ms |
| 2026-10-03 00:00 | up | 427ms |
| 2026-10-02 00:33 | up | 439ms |
| 2026-10-01 00:33 | up | 472ms |
| 2026-09-30 00:34 | up | 428ms |
| 2026-09-30 00:00 | up | 434ms |
| 2026-09-29 00:00 | up | 435ms |
| 2026-09-28 00:33 | up | 427ms |
| 2026-09-27 00:33 | up | 438ms |
| 2026-09-26 00:34 | up | 426ms |
| 2026-09-26 00:00 | up | 430ms |
| 2026-09-25 00:33 | up | 422ms |