$ uprouter probe --history --provider requesty-ai
Requesty — uptime & latency history
Independent, best-effort probes of requesty.ai run from Uprouter’s own network. Current status: up · 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
100%
avg latency
127ms
p95 latency
157ms
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)100–157ms
raw_probe_log (latest 32)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-25 00:07 | up | 100ms |
| 2026-10-24 00:06 | up | 142ms |
| 2026-10-22 00:07 | up | 157ms |
| 2026-10-21 00:07 | up | 120ms |
| 2026-10-19 00:07 | up | 118ms |
| 2026-10-18 00:07 | up | 128ms |
| 2026-10-16 00:07 | up | 121ms |
| 2026-10-15 00:06 | up | 130ms |
| 2026-10-13 00:07 | up | 82ms |
| 2026-10-12 00:00 | up | 105ms |
| 2026-10-11 00:33 | up | 117ms |
| 2026-10-10 00:34 | up | 81ms |
| 2026-10-10 00:00 | up | 128ms |
| 2026-10-09 00:00 | up | 190ms |
| 2026-10-08 00:33 | up | 137ms |
| 2026-10-07 00:34 | up | 91ms |
| 2026-10-07 00:00 | up | 131ms |
| 2026-10-06 00:00 | up | 146ms |
| 2026-10-05 00:33 | up | 113ms |
| 2026-10-04 00:33 | up | 118ms |
| 2026-10-04 00:00 | up | 130ms |
| 2026-10-03 00:00 | up | 89ms |
| 2026-10-02 00:00 | up | 130ms |
| 2026-10-01 00:33 | up | 102ms |
| 2026-09-30 00:33 | up | 119ms |
| 2026-09-29 00:34 | up | 153ms |
| 2026-09-29 00:00 | up | 155ms |
| 2026-09-28 00:00 | up | 161ms |
| 2026-09-27 00:33 | up | 95ms |
| 2026-09-26 00:33 | up | 145ms |
| 2026-09-26 00:00 | up | 141ms |
| 2026-09-25 00:00 | up | 101ms |