$ uprouter probe --history --provider mx-236600-xyz
236600 — uptime & latency history
Independent, best-effort probes of mx.236600.xyz run from Uprouter’s own network. Current status: down · 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
0%
avg latency
112ms
p95 latency
219ms
incident days
4
daily_status (worst per day)
Oct 19Oct 25
hover a bar for per-day detail
latency_per_day (avg + min–max band)72–219ms
raw_probe_log (latest 31)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-24 00:07 | down | 219ms |
| 2026-10-23 00:06 | down | 72ms |
| 2026-10-21 00:07 | down | 81ms |
| 2026-10-20 00:07 | down | 74ms |
| 2026-10-18 00:07 | down | 72ms |
| 2026-10-17 00:07 | down | 210ms |
| 2026-10-15 00:07 | down | 442ms |
| 2026-10-14 00:06 | down | 270ms |
| 2026-10-12 00:33 | down | 222ms |
| 2026-10-11 00:34 | down | 205ms |
| 2026-10-11 00:00 | down | 221ms |
| 2026-10-10 00:00 | down | 236ms |
| 2026-10-09 00:33 | down | 233ms |
| 2026-10-08 00:34 | down | 256ms |
| 2026-10-08 00:00 | down | 223ms |
| 2026-10-07 00:00 | down | 230ms |
| 2026-10-06 00:33 | down | 279ms |
| 2026-10-05 00:34 | down | 231ms |
| 2026-10-05 00:00 | down | 227ms |
| 2026-10-04 00:00 | down | 85ms |
| 2026-10-03 00:33 | down | 83ms |
| 2026-10-02 00:33 | down | 244ms |
| 2026-10-01 00:34 | down | 219ms |
| 2026-10-01 00:00 | down | 81ms |
| 2026-09-30 00:00 | down | 16ms |
| 2026-09-29 00:00 | down | 237ms |
| 2026-09-28 00:33 | down | 257ms |
| 2026-09-27 00:34 | down | 95ms |
| 2026-09-27 00:00 | down | 244ms |
| 2026-09-26 00:00 | down | 78ms |
| 2026-09-25 00:33 | down | 257ms |