On schedule
Published data is on its expected schedule and the evidence quality behind the label is strong.
Policy: Expected ~1d · soft warning > 2d · hard fail > 4d
- As of
- 2026-05-28
- Observed lag
- 1d
- Confidence
- 0.896
- Band
- Good
URD ATLAS
Account
Status shows whether the latest published rows are current enough for operational use, and whether confidence is strong enough for the published label to be read normally. No price data. No forecasts. No recommendations.
Freshness relative to the chain-specific publication policy. BTC and ETH are expected roughly daily. ARB and BASE are expected roughly weekly.
Evidence quality for the published label. A row can be current and still degraded, or delayed and still internally coherent.
Published data is on its expected schedule and the evidence quality behind the label is strong.
Published data is current, but evidence quality is moderate rather than strong. The row is usable, with more caution in interpretation.
Published data is current, but evidence quality is moderate rather than strong. The row is usable, with more caution in interpretation.
Published data is on its expected schedule and the evidence quality behind the label is strong.
Public provenance anchors: date, updated_through, methodology_version, published revision, and regime.determinism_hash.
Health classification is derived at render time. Confidence is read directly from the latest published meta artifact.
This page answers one question: are the published data files current and usable right now?It does not say anything about what markets are doing or what a subscriber should do.
Each chain shows two separate things that are easy to confuse.
Health is derived at render time from lag versus the chain-specific publication policy. Confidence is read from the latest published meta artifact and measures the evidentiary strength behind the label.
These dimensions are orthogonal. A chain can be delayed but internally coherent, or fresh but epistemically weak. Both are shown to keep operational freshness from masking evidence quality and vice versa.
confidence.lag_days_vs_utc_todayconfidence.confidence_scoreDifferent chains publish at different speeds by design. That means lag must always be interpreted relative to policy.
The operational pipeline generally checks for new upstream data twice daily around 09:00 and 21:00 Europe/Oslo.
BTC and ETH use a daily cadence policy: expected 1 day, soft warning above 2 days, hard fail above 4 days. ARB and BASE use a weekly cadence policy: expected 7 days, soft warning above 10 days, hard fail above 15 days.
This is why the same absolute lag value can be normal for one chain and anomalous for another.
Confidence measures how strongly the available data supports the published label.
Confidence is shown here as an operational diagnostic, not as a market signal. It indicates how well the evidence surface distinguishes the published label from adjacent labels.
A degraded score means the row may still be published for traceability, but the label should be treated as low-trust.