Service status and data coverage per source (public)

status is ok or degraded, HTTP 200 in both cases. reasons lists the failed checks as codes: dma_stale (no new dma day for too long), digitraffic_stale (no digitraffic data written for too long), writer_error, disk_warning, coverage_error, live_heartbeat (live collection unhealthy), live_replica_stale (live data on this API is not current: the live collector is unreachable), privacy_registry_missing (private vessels are excluded by a stricter interim rule until the registry is rebuilt; vessel lookups may return no results meanwhile). Each coverage entry carries available_until: the time up to which that source can be queried, never later than the embargo cutoff. With an API key the cutoff is your plan's (available_until is null on plans with live data) and live gives the live view: included, sources, state (syncing, live or stale) and stale_s.