$ uprouter probe --history --provider unity2-ai
Unity2 — uptime & latency history
Independent, best-effort probes of unity2.ai 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
29ms
p95 latency
43ms
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)24–43ms
raw_probe_log (latest 31)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-24 00:07 | down | 24ms |
| 2026-10-23 00:06 | down | 24ms |
| 2026-10-21 00:07 | down | 43ms |
| 2026-10-20 00:06 | down | 25ms |
| 2026-10-18 00:07 | down | 23ms |
| 2026-10-17 00:06 | down | 44ms |
| 2026-10-15 00:07 | down | 26ms |
| 2026-10-13 00:07 | down | 24ms |
| 2026-10-12 00:33 | down | 42ms |
| 2026-10-11 00:34 | down | 22ms |
| 2026-10-11 00:00 | down | 45ms |
| 2026-10-10 00:00 | down | 28ms |
| 2026-10-09 00:33 | down | 28ms |
| 2026-10-08 00:33 | down | 26ms |
| 2026-10-07 00:34 | down | 25ms |
| 2026-10-07 00:00 | down | 29ms |
| 2026-10-06 00:00 | down | 23ms |
| 2026-10-05 00:33 | down | 42ms |
| 2026-10-04 00:34 | down | 26ms |
| 2026-10-04 00:00 | down | 22ms |
| 2026-10-03 00:00 | down | 22ms |
| 2026-10-02 00:33 | down | 26ms |
| 2026-10-01 00:33 | down | 22ms |
| 2026-09-30 00:34 | down | 35ms |
| 2026-09-30 00:00 | down | 44ms |
| 2026-09-29 00:00 | down | 51ms |
| 2026-09-28 00:00 | down | 48ms |
| 2026-09-27 00:33 | down | 48ms |
| 2026-09-26 00:34 | down | 27ms |
| 2026-09-26 00:00 | down | 29ms |
| 2026-09-25 00:00 | down | 29ms |