KituwaStudio
Admin sign in Start a build

Estate watchdog · Websites

Rewind MODE
watchdog.

What is running, when it last checked in, and what failed. Generated at 2026-11-20 12:08; refresh the page for a new check. This is not a screenshot and nothing here is hardcoded.

Current state

Rewind MODE is healthy.

Healthy

HTTP 200 in 340 ms · in this state since 2026-11-18 00:23.

Healthyoverall
3/3checks passing
100.0%service uptime, 24 h
5m agolast successful run
100%success rate, 7 days

Watchdog itself

Collection interval
Every minute
Stale after
10 minutes
Last check
2026-11-20 12:03 (5m 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-20 12:03 - OK (339 ms)
Next run
Next run unknown. The scheduler has not published it.
Last successful run
2026-11-20 12:03 (5m ago)
Heartbeat
5m ago
Tracking since
2026-11-13 11:23 (7 days)
Longest gap, 24 h
5m

Weekly progress

Has this been working all week?

Success rate, 7 days: 100% across 4761 checks.

  1. 100% Sat
  2. 100% Sun
  3. 100% Mon
  4. 100% Tue
  5. 100% Wed
  6. 100% Thu
  7. 100% Fri

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

CheckStateEvidence
Reachability pass HTTP 200 in 340 ms · checked 5m ago
HTTP response pass HTTP 200 in 340 ms
Monitor evidence freshness pass last check 5m ago; stale after 5 minutes

Recent runs

Last terminal runs

StartedDurationTriggerStatusWork doneError
2026-11-20 12:03 339 ms schedule OK HTTP 200 in 340 ms —
2026-11-20 11:58 286 ms schedule OK HTTP 200 in 287 ms —
2026-11-20 11:53 334 ms schedule OK HTTP 200 in 335 ms —
2026-11-20 11:48 228 ms schedule OK HTTP 200 in 228 ms —
2026-11-20 11:43 233 ms schedule OK HTTP 200 in 233 ms —
2026-11-20 11:38 402 ms schedule OK HTTP 200 in 402 ms —
2026-11-20 11:33 213 ms schedule OK HTTP 200 in 214 ms —
2026-11-20 11:28 341 ms schedule OK HTTP 200 in 341 ms —
2026-11-20 11:23 326 ms schedule OK HTTP 200 in 326 ms —
2026-11-20 11:18 276 ms schedule OK HTTP 200 in 276 ms —

Uptime

Measured availability

24 hours
100.0%
7 days
100.0%
30 days
100.0%
24 h samples
289

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.