$ uprouter probe --history --provider lzjapi-cloud
LZJAPI — uptime & latency history
Independent, best-effort probes of lzjapi.cloud run from Uprouter’s own network. Current status: down · last probe 16h 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
211ms
p95 latency
265ms
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)91–265ms
raw_probe_log (latest 31)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-25 00:06 | down | 91ms |
| 2026-10-23 00:07 | down | 265ms |
| 2026-10-22 00:06 | down | 252ms |
| 2026-10-20 00:07 | down | 240ms |
| 2026-10-19 00:06 | down | 209ms |
| 2026-10-17 00:07 | down | 166ms |
| 2026-10-16 00:06 | down | 78ms |
| 2026-10-14 00:07 | down | 283ms |
| 2026-10-12 00:34 | down | 241ms |
| 2026-10-12 00:00 | down | 76ms |
| 2026-10-11 00:00 | down | 237ms |
| 2026-10-10 00:33 | down | 259ms |
| 2026-10-09 00:33 | down | 228ms |
| 2026-10-09 00:00 | down | 95ms |
| 2026-10-08 00:00 | down | 91ms |
| 2026-10-07 00:00 | down | 328ms |
| 2026-10-06 00:33 | down | 18ms |
| 2026-10-05 00:34 | down | 315ms |
| 2026-10-05 00:00 | down | 101ms |
| 2026-10-04 00:00 | down | 90ms |
| 2026-10-03 00:33 | down | 86ms |
| 2026-10-02 00:34 | down | 96ms |
| 2026-10-02 00:00 | down | 237ms |
| 2026-10-01 00:00 | down | 267ms |
| 2026-09-30 00:00 | down | 106ms |
| 2026-09-29 00:33 | down | 243ms |
| 2026-09-28 00:33 | down | 236ms |
| 2026-09-27 00:34 | down | 25ms |
| 2026-09-27 00:00 | down | 240ms |
| 2026-09-26 00:00 | down | 152ms |
| 2026-09-25 00:33 | down | 103ms |