$ uprouter probe --history --provider sss-jumped-cc-cd
Jumped — uptime & latency history
Independent, best-effort probes of sss.jumped.cc.cd run from Uprouter’s own network. Current status: down · last probe 18h 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
0%
avg latency
6002ms
p95 latency
6002ms
incident days
5
daily_status (worst per day)
Oct 19Oct 25
hover a bar for per-day detail
latency_per_day (avg + min–max band)6001–6002ms
raw_probe_log (latest 32)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-25 00:06 | down | 6001ms |
| 2026-10-23 00:07 | down | 6002ms |
| 2026-10-22 00:06 | down | 6001ms |
| 2026-10-20 00:07 | down | 6002ms |
| 2026-10-19 00:06 | down | 6002ms |
| 2026-10-17 00:07 | down | 6002ms |
| 2026-10-16 00:06 | down | 6002ms |
| 2026-10-14 00:07 | down | 6001ms |
| 2026-10-12 00:34 | down | 6001ms |
| 2026-10-12 00:00 | down | 6001ms |
| 2026-10-11 00:00 | down | 6000ms |
| 2026-10-10 00:33 | down | 6001ms |
| 2026-10-09 00:34 | down | 6001ms |
| 2026-10-09 00:00 | down | 6001ms |
| 2026-10-08 00:00 | down | 6001ms |
| 2026-10-07 00:33 | down | 6002ms |
| 2026-10-06 00:33 | down | 6001ms |
| 2026-10-06 00:00 | down | 6005ms |
| 2026-10-05 00:00 | down | 6001ms |
| 2026-10-04 00:33 | down | 6005ms |
| 2026-10-03 00:33 | down | 6001ms |
| 2026-10-02 00:34 | down | 6002ms |
| 2026-10-02 00:00 | down | 6002ms |
| 2026-10-01 00:00 | down | 6002ms |
| 2026-09-30 00:00 | down | 6000ms |
| 2026-09-29 00:33 | down | 6000ms |
| 2026-09-28 00:34 | down | 6001ms |
| 2026-09-28 00:00 | down | 6002ms |
| 2026-09-27 00:00 | down | 6002ms |
| 2026-09-26 00:33 | down | 6005ms |
| 2026-09-25 00:33 | down | 6001ms |
| 2026-09-25 00:00 | down | 6003ms |