Estate watchdog · Websites
Kituwa metrics admin
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
Kituwa metrics admin is healthy.
HTTP 200 in 462 ms · in this state since 2026-11-18 23:33.
Watchdog itself
- Collection interval
- Every minute
- Stale after
- 10 minutes
- Last check
- 2026-11-19 10:42 (87s 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 (461 ms)
- Next run
- Next run unknown. The scheduler has not published it.
- Last successful run
- 2026-11-19 10:42 (87s ago)
- Heartbeat
- 87s 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: 100% across 5863 checks.
- 98% Fri
- 100% Sat
- 100% Sun
- 100% Mon
- 100% Tue
- 99% 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 200 in 462 ms · checked 87s ago |
| HTTP response | pass | HTTP 200 in 462 ms |
| Monitor evidence freshness | pass | last check 87s ago; stale after 5 minutes |
Recent runs
Last terminal runs
| Started | Duration | Trigger | Status | Work done | Error |
|---|---|---|---|---|---|
| 2026-11-19 10:42 | 461 ms | schedule | OK | HTTP 200 in 462 ms | — |
| 2026-11-19 10:37 | 935 ms | schedule | OK | HTTP 200 in 935 ms | — |
| 2026-11-19 10:32 | 963 ms | schedule | OK | HTTP 200 in 964 ms | — |
| 2026-11-19 10:27 | 433 ms | schedule | OK | HTTP 200 in 434 ms | — |
| 2026-11-19 10:22 | 644 ms | schedule | OK | HTTP 200 in 644 ms | — |
| 2026-11-19 10:17 | 670 ms | schedule | OK | HTTP 200 in 671 ms | — |
| 2026-11-19 10:12 | 520 ms | schedule | OK | HTTP 200 in 520 ms | — |
| 2026-11-19 10:07 | 467 ms | schedule | OK | HTTP 200 in 468 ms | — |
| 2026-11-19 10:02 | 739 ms | schedule | OK | HTTP 200 in 740 ms | — |
| 2026-11-19 09:57 | 1258 ms | schedule | OK | HTTP 200 in 1258 ms | — |
Uptime
Measured availability
- 24 hours
- 99.3%
- 7 days
- 98.5%
- 30 days
- 98.4%
- 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.