What the ingestion pipeline did last, and how old the freshest reading is. Published rather than hidden: a site built around someone else’s data should be able to tell you when it last heard from them.
Newest reading
just now
| Source | Result | When | Rows |
|---|---|---|---|
| NOAA CO-OPS (tide, water level) | ok | Nov 13, 9:42 am | 2,237 |
| NDBC latest_obs (current conditions) | ok | Nov 13, 9:40 am | 0 |
| NDBC realtime2 (history, water temp) | ok | Nov 13, 4:41 am | 10,560 |
| Station | Live metrics | Newest |
|---|---|---|
| Crescent City | 9 | just now |
| San Francisco | 9 | just now |
| Monterey | 10 | just now |
| Port San Luis | 10 | just now |
| Santa Monica | 6 | just now |
| La Jolla | 6 | just now |
This page is not the alarm. A status page nobody opens is exactly how a scheduled job fails unnoticed for a month. A separate scheduled check asserts freshness and exits non-zero when it is wrong, which is the part that actually gets anyone’s attention.