Estate watchdog · Websites
Uptime Kuma
watchdog.
What is running, when it last checked in, and what failed. Generated at 2026-11-19 10:44; refresh the page for a new check. This is not a screenshot and nothing here is hardcoded.
Current state
Uptime Kuma is healthy.
HTTP 302 in 42 ms · in this state since 2026-11-16 22:48.
Watchdog itself
- Collection interval
- Every minute
- Stale after
- 10 minutes
- Last check
- 2026-11-19 10:42 (81s ago)
- Next check
- within one minute
- Kind
- http
- Group
- Websites
Schedule
When it last ran and when it runs next
- Schedule
- Event driven - no fixed schedule
- Previous run
- 2026-11-19 10:42 - OK (42 ms)
- Next run
- Next run unknown. The scheduler has not published it.
- Last successful run
- 2026-11-19 10:42 (81s ago)
- Heartbeat
- 81s ago
- Tracking since
- 2026-11-12 10:23 (7 days)
- Longest gap, 24 h
- 5m
Weekly progress
Has this been working all week?
Success rate, 7 days: 94% across 5863 checks.
- 76% Fri
- 100% Sat
- 100% Sun
- 100% Mon
- 100% Tue
- 100% Wed
- 100% Thu
Each tile is one local day: green means at least 90% of checks succeeded, amber 50-89%, red below 50%, grey no attempt. Health is measured from recorded runs, not from a process check, so a frozen worker shows as failed or missing.
Checks
Evidence behind the state
| Check | State | Evidence |
|---|---|---|
| Reachability | pass | HTTP 302 in 42 ms · checked 81s ago |
| HTTP response | pass | HTTP 302 in 42 ms |
| Upstream uptime sample | pass | 100.00% over 24 h from Uptime Kuma |
| Monitor evidence freshness | pass | last check 81s ago; stale after 5 minutes |
Recent runs
Last terminal runs
| Started | Duration | Trigger | Status | Work done | Error |
|---|---|---|---|---|---|
| 2026-11-19 10:42 | 42 ms | schedule | OK | HTTP 302 in 42 ms | — |
| 2026-11-19 10:37 | 165 ms | schedule | OK | HTTP 302 in 165 ms | — |
| 2026-11-19 10:32 | 37 ms | schedule | OK | HTTP 302 in 37 ms | — |
| 2026-11-19 10:27 | 116 ms | schedule | OK | HTTP 302 in 116 ms | — |
| 2026-11-19 10:22 | 175 ms | schedule | OK | HTTP 302 in 175 ms | — |
| 2026-11-19 10:17 | 81 ms | schedule | OK | HTTP 302 in 81 ms | — |
| 2026-11-19 10:12 | 36 ms | schedule | OK | HTTP 302 in 36 ms | — |
| 2026-11-19 10:07 | 43 ms | schedule | OK | HTTP 302 in 43 ms | — |
| 2026-11-19 10:02 | 82 ms | schedule | OK | HTTP 302 in 82 ms | — |
| 2026-11-19 09:57 | 182 ms | schedule | OK | HTTP 302 in 183 ms | — |
Uptime
Measured availability
- 24 hours
- 100.0%
- 7 days
- 94.8%
- 30 days
- 94.8%
- 24 h samples
- 288
Uptime is the share of recorded checks that passed. Gaps reduce coverage; they are never assumed up.
Recent failures
Last 20 incidents
No failures recorded in the last 30 days.
What this covers
Scope and honesty
Covers HTTPS reachability, response code and latency, upstream uptime when available, and monitor freshness. Does not cover product correctness, content accuracy or signed-in flows.
A 200 from a landing page proves reachability, not a working product. Missing data is shown as unknown, never as zero or green. Alerts and silences are evaluated by the same monitor that renders this page.