$ uprouter probe --history --provider jucodex-com
JuCodex — uptime & latency history
Independent, best-effort probes of jucodex.com 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
807ms
p95 latency
1018ms
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)660–1018ms
raw_probe_log (latest 31)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-24 00:07 | up | 709ms |
| 2026-10-23 00:06 | up | 840ms |
| 2026-10-21 00:07 | up | 660ms |
| 2026-10-20 00:07 | up | 1018ms |
| 2026-10-18 00:07 | up | 681ms |
| 2026-10-17 00:07 | up | 692ms |
| 2026-10-15 00:07 | up | 679ms |
| 2026-10-13 00:07 | up | 758ms |
| 2026-10-12 00:33 | up | 673ms |
| 2026-10-11 00:34 | up | 702ms |
| 2026-10-11 00:00 | up | 611ms |
| 2026-10-10 00:00 | up | 665ms |
| 2026-10-09 00:33 | up | 625ms |
| 2026-10-08 00:34 | up | 687ms |
| 2026-10-08 00:00 | up | 722ms |
| 2026-10-07 00:00 | up | 762ms |
| 2026-10-06 00:33 | up | 727ms |
| 2026-10-05 00:33 | up | 644ms |
| 2026-10-05 00:00 | up | 645ms |
| 2026-10-04 00:00 | up | 643ms |
| 2026-10-03 00:00 | up | 631ms |
| 2026-10-02 00:33 | up | 716ms |
| 2026-10-01 00:34 | up | 672ms |
| 2026-09-30 00:34 | up | 620ms |
| 2026-09-30 00:00 | up | 693ms |
| 2026-09-29 00:00 | up | 633ms |
| 2026-09-28 00:33 | up | 634ms |
| 2026-09-27 00:33 | up | 622ms |
| 2026-09-26 00:34 | up | 650ms |
| 2026-09-26 00:00 | up | 623ms |
| 2026-09-25 00:33 | up | 641ms |