Estate watchdog · Websites

Matomo analytics
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

Matomo analytics is healthy.

Healthy

HTTP 200 in 323 ms · in this state since 2026-11-18 06:18.

Healthyoverall
4/4checks passing
100.0%service uptime, 24 h
78s agolast successful run
94%success rate, 7 days

Watchdog itself

Collection interval
Every minute
Stale after
10 minutes
Last check
2026-11-19 10:42 (77s 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 (322 ms)
Next run
Next run unknown. The scheduler has not published it.
Last successful run
2026-11-19 10:42 (78s ago)
Heartbeat
77s 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.

  1. 80% Fri
  2. 100% Sat
  3. 100% Sun
  4. 95% Mon
  5. 100% Tue
  6. 100% Wed
  7. 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

CheckStateEvidence
Reachability pass HTTP 200 in 323 ms · checked 77s ago
HTTP response pass HTTP 200 in 323 ms
Upstream uptime sample pass 100.00% over 24 h from Uptime Kuma
Monitor evidence freshness pass last check 77s ago; stale after 5 minutes

Recent runs

Last terminal runs

StartedDurationTriggerStatusWork doneError
2026-11-19 10:42 322 ms schedule OK HTTP 200 in 323 ms —
2026-11-19 10:37 392 ms schedule OK HTTP 200 in 393 ms —
2026-11-19 10:32 256 ms schedule OK HTTP 200 in 256 ms —
2026-11-19 10:27 314 ms schedule OK HTTP 200 in 314 ms —
2026-11-19 10:22 262 ms schedule OK HTTP 200 in 262 ms —
2026-11-19 10:17 322 ms schedule OK HTTP 200 in 323 ms —
2026-11-19 10:12 257 ms schedule OK HTTP 200 in 258 ms —
2026-11-19 10:07 265 ms schedule OK HTTP 200 in 265 ms —
2026-11-19 10:02 296 ms schedule OK HTTP 200 in 296 ms —
2026-11-19 09:57 339 ms schedule OK HTTP 200 in 339 ms —

Uptime

Measured availability

24 hours
100.0%
7 days
94.9%
30 days
94.9%
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

StartedDurationSeveritySummaryResolution
2026-11-16 13:18 55m warning unavailable 2026-11-16 14:13
2026-11-16 12:28 40m warning unavailable 2026-11-16 13:08

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.