Every dated figure on this site is a claim that a pipeline ran. This page is that claim’s audit trail: what ran, when, what it attempted, what succeeded, and what failed. A data vendor cannot publish this page about itself. We can, so we do.
The last 40 runs, newest first. Failures are rows, not footnotes.
Last successful write per dataset, read from the data store itself rather than from the run log, so pipelines that predate run-level recording still appear here. A dataset in this table but absent from the pipelines table above is exactly that case, stated rather than hidden.
What this page is, and is not
It is the record behind every “as of” label on the site: when each pipeline ran, what it attempted, and whether it succeeded, with failures shown as rows rather than summarised away. When an ingest fails, the house rule is that it refuses to write, so the pages keep serving the previous good data under its original date. A failure here plus an older date there is the system working.
It is not a service-level promise, and it does not cover cache warmers, alert deliveries or AI generation jobs, which write no dataset a page reads. Run-level recording arrived in stages, so a few older pipelines appear only in the freshness table; that boundary shrinks as instrumentation catches up, and it is stated here rather than papered over. Educational information, not investment advice. Back to the methodology.
Ingestion ledger FAQ
Why publish pipeline failures?
Because a run log that only shows successes is marketing. Every dated figure on this site is a claim that a pipeline ran; this page is where that claim can be checked. A commercial data vendor cannot publish its own failure record without undermining what it sells. We are not selling reliability, so we can, and a log with visible failures is the only kind worth trusting.
What does a failed run mean for the data I see?
Usually nothing visible. The house rule is that a failed ingest refuses to write, so pages keep serving the previous good snapshot with its original date. A failure here plus a stale date on a page is the system working as designed: showing you older data honestly rather than newer data invented.
Why do some datasets appear only in the freshness table?
Run-level recording arrived in stages, and some older pipelines write their dataset without writing a run record yet. Freshness is observed from the data itself, so the freshness table has no coverage gap; the run log covers the pipelines that record runs, and the gap between the two lists is stated rather than hidden.
What is not on this page?
Cache warmers, email and alert deliveries, and AI generation jobs. This ledger covers pipelines that write the datasets pages read. It also is not a service-level promise: it is a record of what happened, not a guarantee of what will.