$ uprouter probe --history --provider aws-amazon-com
Amazon Bedrock — uptime & latency history
Independent, best-effort probes of aws.amazon.com 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
69ms
p95 latency
79ms
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)58–79ms
raw_probe_log (latest 32)
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-25 00:07 | up | 67ms |
| 2026-10-23 00:07 | up | 72ms |
| 2026-10-22 00:07 | up | 58ms |
| 2026-10-20 00:07 | up | 79ms |
| 2026-10-19 00:07 | up | 67ms |
| 2026-10-17 00:07 | up | 64ms |
| 2026-10-16 00:07 | up | 191ms |
| 2026-10-14 00:07 | up | 62ms |
| 2026-10-13 00:06 | up | 72ms |
| 2026-10-12 00:00 | up | 75ms |
| 2026-10-11 00:33 | up | 63ms |
| 2026-10-10 00:33 | up | 78ms |
| 2026-10-09 00:34 | up | 64ms |
| 2026-10-09 00:00 | up | 65ms |
| 2026-10-08 00:00 | up | 72ms |
| 2026-10-07 00:33 | up | 78ms |
| 2026-10-06 00:34 | up | 136ms |
| 2026-10-06 00:00 | up | 75ms |
| 2026-10-05 00:00 | up | 69ms |
| 2026-10-04 00:33 | up | 63ms |
| 2026-10-03 00:34 | up | 64ms |
| 2026-10-03 00:00 | up | 64ms |
| 2026-10-02 00:00 | up | 66ms |
| 2026-10-01 00:00 | up | 66ms |
| 2026-09-30 00:33 | up | 65ms |
| 2026-09-29 00:33 | up | 75ms |
| 2026-09-28 00:34 | up | 71ms |
| 2026-09-28 00:00 | up | 72ms |
| 2026-09-27 00:00 | up | 75ms |
| 2026-09-26 00:33 | up | 83ms |
| 2026-09-25 00:34 | up | 87ms |
| 2026-09-25 00:00 | up | 67ms |