Estate watchdog · Websites
OhioMotoCrashes
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
OhioMotoCrashes is healthy.
HTTP 200 in 86 ms · in this state since 2026-11-16 22:48.
Watchdog itself
- Collection interval
- Every minute
- Stale after
- 10 minutes
- Last check
- 2026-11-19 10:42 (2m 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 (86 ms)
- Next run
- Next run unknown. The scheduler has not published it.
- Last successful run
- 2026-11-19 10:42 (2m ago)
- Heartbeat
- 2m 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.
- 100% 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 |
|---|---|---|
| Reachability | pass | HTTP 200 in 86 ms · checked 2m ago |
| HTTP response | pass | HTTP 200 in 86 ms |
| Monitor evidence freshness | pass | last check 2m ago; stale after 5 minutes |
Recent runs
Last terminal runs
| Started | Duration | Trigger | Status | Work done | Error |
|---|---|---|---|---|---|
| 2026-11-19 10:42 | 86 ms | schedule | OK | HTTP 200 in 86 ms | — |
| 2026-11-19 10:37 | 64 ms | schedule | OK | HTTP 200 in 64 ms | — |
| 2026-11-19 10:32 | 29 ms | schedule | OK | HTTP 200 in 29 ms | — |
| 2026-11-19 10:27 | 30 ms | schedule | OK | HTTP 200 in 31 ms | — |
| 2026-11-19 10:22 | 39 ms | schedule | OK | HTTP 200 in 39 ms | — |
| 2026-11-19 10:17 | 41 ms | schedule | OK | HTTP 200 in 42 ms | — |
| 2026-11-19 10:12 | 44 ms | schedule | OK | HTTP 200 in 45 ms | — |
| 2026-11-19 10:07 | 127 ms | schedule | OK | HTTP 200 in 127 ms | — |
| 2026-11-19 10:02 | 75 ms | schedule | OK | HTTP 200 in 76 ms | — |
| 2026-11-19 09:57 | 41 ms | schedule | OK | HTTP 200 in 41 ms | — |
Uptime
Measured availability
- 24 hours
- 100.0%
- 7 days
- 99.9%
- 30 days
- 99.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
| Started | Duration | Severity | Summary | Resolution |
|---|---|---|---|---|
| 2026-11-16 17:18 | 5m | critical | unavailable | 2026-11-16 17:23 |
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.