Service status
Self-reported checks from our own monitoring. This is not an independent availability audit or a service-level guarantee.
Loading observations…
Current components
Data feed freshness
Daymark reads published FMCSA files. This table shows when each daily file last published a new version, from our nightly landing records. A daily feed is marked delayed when its newest publication is more than two days old, or when our most recent check of that feed failed. The carrier census is read live from the publisher each time a lookup runs, so it has no stored publication time here; unknown means we do not have a recorded time, not that the feed is empty.
| Feed | Last published | Expected updates | Status |
|---|---|---|---|
| No observations loaded. | |||
Publication times are the publisher's own timestamps (UTC). Source: FMCSA data via data.transportation.gov.
90-day observation history
Each day shows the worst observed component state. Gray means no observations. Missing time is not counted as uptime; sampled checks do not measure continuous availability.
Legend: green = operational; amber = degraded; red = down; gray = no observations. Focus a day for its text label.
API: HTTP 200 and health JSON, including a database query. Lookup: HTML reachability only, not a live carrier lookup. Ingestion: latest completed job must succeed within 30 hours; over 48 hours is down. Missing run evidence is degraded. Snapshots older than 30 minutes are stale; displayed components become degraded until fresh observations arrive.