Estate watchdog · Websites
Kituwa landing
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 landing is healthy.
HTTP 200 in 160 ms · in this state since 2026-11-17 23:38.
Watchdog itself
- Collection interval
- Every minute
- Stale after
- 10 minutes
- Last check
- 2026-11-19 10:42 (89s 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 (160 ms)
- Next run
- Next run unknown. The scheduler has not published it.
- Last successful run
- 2026-11-19 10:42 (89s ago)
- Heartbeat
- 89s 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: 54% across 5863 checks.
- 92% Fri
- 0% Sat
- 19% Sun
- 100% Mon
- 99% 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 200 in 160 ms · checked 89s ago |
| HTTP response | pass | HTTP 200 in 160 ms |
| Monitor evidence freshness | pass | last check 89s ago; stale after 5 minutes |
Recent runs
Last terminal runs
| Started | Duration | Trigger | Status | Work done | Error |
|---|---|---|---|---|---|
| 2026-11-19 10:42 | 160 ms | schedule | OK | HTTP 200 in 160 ms | — |
| 2026-11-19 10:37 | 223 ms | schedule | OK | HTTP 200 in 224 ms | — |
| 2026-11-19 10:32 | 631 ms | schedule | OK | HTTP 200 in 631 ms | — |
| 2026-11-19 10:27 | 116 ms | schedule | OK | HTTP 200 in 116 ms | — |
| 2026-11-19 10:22 | 122 ms | schedule | OK | HTTP 200 in 122 ms | — |
| 2026-11-19 10:17 | 176 ms | schedule | OK | HTTP 200 in 176 ms | — |
| 2026-11-19 10:12 | 77 ms | schedule | OK | HTTP 200 in 77 ms | — |
| 2026-11-19 10:07 | 175 ms | schedule | OK | HTTP 200 in 175 ms | — |
| 2026-11-19 10:02 | 267 ms | schedule | OK | HTTP 200 in 267 ms | — |
| 2026-11-19 09:57 | 1091 ms | schedule | OK | HTTP 200 in 1091 ms | — |
Uptime
Measured availability
- 24 hours
- 100.0%
- 7 days
- 59.1%
- 30 days
- 59.3%
- 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.