$ uprouter probe --history --provider chutes-ai
Chutes — uptime & latency history
Independent, best-effort probes of chutes.ai run from Uprouter’s own network. Current status: up · last probe 4h 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
268ms
p95 latency
439ms
incident days
0
daily_status (worst per day)
Oct 20Oct 26
hover a bar for per-day detail
latency_per_day (avg + min–max band)142–439ms
raw_probe_log (latest 31)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-26 00:06 | up | 142ms |
| 2026-10-24 00:07 | up | 232ms |
| 2026-10-23 00:06 | up | 439ms |
| 2026-10-21 00:07 | up | 353ms |
| 2026-10-20 00:06 | up | 176ms |
| 2026-10-18 00:07 | up | 191ms |
| 2026-10-17 00:06 | up | 276ms |
| 2026-10-15 00:07 | up | 166ms |
| 2026-10-13 00:07 | up | 116ms |
| 2026-10-12 00:33 | up | 126ms |
| 2026-10-11 00:34 | up | 273ms |
| 2026-10-11 00:00 | up | 193ms |
| 2026-10-10 00:00 | up | 168ms |
| 2026-10-09 00:01 | up | 167ms |
| 2026-10-08 00:33 | up | 151ms |
| 2026-10-07 00:34 | up | 124ms |
| 2026-10-07 00:00 | up | 183ms |
| 2026-10-06 00:00 | up | 222ms |
| 2026-10-05 00:33 | up | 183ms |
| 2026-10-04 00:34 | up | 236ms |
| 2026-10-04 00:00 | up | 207ms |
| 2026-10-03 00:00 | up | 136ms |
| 2026-10-02 00:33 | up | 163ms |
| 2026-10-01 00:33 | up | 125ms |
| 2026-09-30 00:34 | up | 199ms |
| 2026-09-30 00:00 | up | 172ms |
| 2026-09-29 00:00 | up | 141ms |
| 2026-09-28 00:00 | up | 165ms |
| 2026-09-27 00:33 | up | 198ms |
| 2026-09-26 00:34 | up | 203ms |
| 2026-09-26 00:00 | up | 135ms |