Status
ReserveBeat publishes this self-check so the board is held to the standard it applies to issuers. The page reports, live, whether the public API is answering, whether the pre-publication review covers the served methodology, when the registry chain was last anchored, and how recently reserve data was captured.
01Self-check
Live self-check
Every line below is read from the running system at the moment this page is requested. Nothing here is cached, scheduled, or hand-maintained.
- public API
- Answering
GET /healthz -> 200 - coverage board
- Serving figures review CURRENT
- hourly supply snapshot
- Current · 17m late after 3 h
What this page does not claim
This page states current conditions only. ReserveBeat publishes no uptime percentage and no availability history: the reachability probe its operator runs is an internal dead-man, not a measurement offered to readers.
02Review
Pre-publication review
- state
- CURRENT
- reviewed at
- 2026-10-10 19:30 UTC
- reviewer
- ReserveBeat
- methodology sha256
01d1de5ec2…3a9c0cc5- review anchor
- ANCHORED
The board serves figures only while a recorded pre-publication review covers the exact methodology document being served. When those diverge, every figure route answers with a withholding notice instead of a number, and this line says so.
03Anchor
Latest registry anchor
- kind
- DAILY
- state
- ANCHORED
- cadence
- CURRENT
- covers to
- 2026-10-19
- anchored at
- 2026-10-19 03:33 UTC
- merkle root
2532aaa806…36a6f6a9
The registry evidence chain is committed to a Merkle root and timestamped externally. A pending or late anchor is shown as such; absence of an anchor is stated, never filled in.
04Freshness
Data freshness
- latest supply snapshot
- 2026-10-19 10:17 UTC · 17m ago
- latest attestation parsed
- 2026-10-12 21:18 UTC
- that report’s period
- 2026-08
Freshness timestamps describe the underlying data — when a supply snapshot was captured, when an attestation report was parsed — never when this page was rendered.
The recorder takes a supply snapshot every hour. The verdict above reads Snapshot late whenever the newest snapshot on the board is older than the stated threshold, measured by the database clock at request time — the same clock the board applies when it calls an issuer's attestation Stale. A late snapshot is shown as late, never relabelled fresh.
05Trust