Skip to main content
ReserveBeat
Get alertsGet an API key

Updates

Changelog

The ReserveBeat changelog records changes to this site and its data API that are already live. Each entry carries the date the change shipped and what it affected. Nothing here describes planned work: an entry appears only after the change is running in production and readers can see it.

This log records only changes that are already live on this site. It is not a roadmap, it does not describe work in progress, and an entry is added only once the change it describes is running.

RSS feed

  1. Shipped

    Nightly backups and host hardening

    The production host moved to a hardened posture with a nightly database backup and a documented restore path, so the evidence behind the published figures survives the loss of a machine.

  2. Shipped

    Subscription confirmation limits

    Coverage-alert signup gained a two-sided rate limit, so neither a single address nor a single sender can be used to generate confirmation mail in volume.

  3. Shipped

    ReserveBeat published

    The coverage board and everything around it became publicly readable at reservebeat.com, and the site was registered with search engines the same day.

Questions

Common questions

What counts as a change worth listing here?

A change to what readers or API callers can see or do: a new page or endpoint, a change to how a figure is derived or labelled, a change to published limits, or a change to how the site's evidence is retained. Internal work that leaves the published surface unchanged is not listed.

Does this log include planned work?

No. An entry appears only after the change is live. There is no roadmap on this page, and no entry describes something that has not shipped.

What date does an entry carry?

The date the change went live on this site, taken from the deployment record. It is not the date the work started or the date the entry was written.

Does a changed figure appear here?

No. Figures change as issuers publish and as chains are read, and a correction to an already-published figure is recorded on the revisions page, which keeps both the superseded record and the one that replaced it. This log covers changes to the site and the API themselves.