Estate watchdog · Hosts
VPS health
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
VPS health is degraded.
CPU 18% · RAM 61% · disk 91% · load 1.38 · in this state since 2026-11-19 09:42.
Watchdog itself
- Collection interval
- Every minute
- Stale after
- 10 minutes
- Last check
- 2026-11-19 10:42 (84s ago)
- Next check
- within one minute
- Kind
- host
- Group
- Hosts
Schedule
When it last ran and when it runs next
- Schedule
- Event driven - no fixed schedule
- Previous run
- 2026-11-19 10:42 - Partial (-)
- Next run
- Next run unknown. The scheduler has not published it.
- Last successful run
- 2026-11-19 09:37 (67m ago)
- Heartbeat
- 84s 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.
- 99% 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 |
|---|---|---|
| Monitor evidence freshness | pass | last check 84s ago; stale after 5 minutes |
Recent runs
Last terminal runs
| Started | Duration | Trigger | Status | Work done | Error |
|---|---|---|---|---|---|
| 2026-11-19 10:42 | - | schedule | Partial | CPU 18% · RAM 61% · disk 91% · load 1.38 | CPU 18% · RAM 61% · disk 91% · load 1.38 |
| 2026-11-19 10:37 | - | schedule | Partial | CPU 8% · RAM 61% · disk 91% · load 1.73 | CPU 8% · RAM 61% · disk 91% · load 1.73 |
| 2026-11-19 10:32 | - | schedule | Partial | CPU 10% · RAM 62% · disk 91% · load 3.70 | CPU 10% · RAM 62% · disk 91% · load 3.70 |
| 2026-11-19 10:27 | - | schedule | Partial | CPU 85% · RAM 60% · disk 91% · load 2.13 | CPU 85% · RAM 60% · disk 91% · load 2.13 |
| 2026-11-19 10:22 | - | schedule | Partial | CPU 20% · RAM 60% · disk 91% · load 1.76 | CPU 20% · RAM 60% · disk 91% · load 1.76 |
| 2026-11-19 10:17 | - | schedule | Partial | CPU 100% · RAM 59% · disk 91% · load 2.58 | CPU 100% · RAM 59% · disk 91% · load 2.58 |
| 2026-11-19 10:12 | - | schedule | Partial | CPU 90% · RAM 60% · disk 91% · load 4.05 | CPU 90% · RAM 60% · disk 91% · load 4.05 |
| 2026-11-19 10:07 | - | schedule | Partial | CPU 100% · RAM 59% · disk 91% · load 4.14 | CPU 100% · RAM 59% · disk 91% · load 4.14 |
| 2026-11-19 10:02 | - | schedule | Partial | CPU 100% · RAM 58% · disk 91% · load 3.23 | CPU 100% · RAM 58% · disk 91% · load 3.23 |
| 2026-11-19 09:57 | - | schedule | Partial | CPU 100% · RAM 66% · disk 91% · load 5.09 | CPU 100% · RAM 66% · disk 91% · load 5.09 |
Uptime
Measured availability
- 24 hours
- 100.0%
- 7 days
- 99.8%
- 30 days
- 99.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 host reachability and the heartbeat the host sends. Does not cover every process on the host.
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.