Our own record

This page holds us to the standard we hold everyone else to. A bureau that publishes other people's intervals and not its own is asking for a trust it has not offered to earn.

The figures on this page are the real published chain, and every one of them is checkable at its source without taking our word for it. That was worth saying even when the endpoint records elsewhere on this site were not yet real, and it is worth saying now that they are: this page measures us, and it is the one page where a flattering number would be the easiest to write and the least defensible.

What we aim for, stated as an aim

The intended cadence is daily. That is an intention, not a guarantee and not a service level. We are not promising a number here, because a promise we have not been held to for long enough to test is worth nothing, and because the interval table below is the honest version of the same claim.

When observations are taken is deliberately not published. Knowing when a record looks is knowing when to look good, and a record that can be timed can be gamed. The intervals between published snapshots are a different matter: each snapshot publishes its own capture time as part of what it commits to, so anyone holding two entries can already subtract them. Restating them here gives away nothing that is not already in the reader's hands.

Every interval so far

Intervals between consecutive published snapshots, as of 2026-08-20. Both capture times are shown, so the rounded figure can be checked against them.
BetweenIntervalFromTo
REL-SNAP-001 → REL-SNAP-0024h 21m
REL-SNAP-002 → REL-SNAP-00314h 55m
REL-SNAP-003 → REL-SNAP-00425h 40m — longest to date
REL-SNAP-004 → REL-SNAP-00522h 36m
REL-SNAP-005 → REL-SNAP-00624h 0m
REL-SNAP-006 → REL-SNAP-00724h 0m
REL-SNAP-007 → REL-SNAP-00824h 0m
REL-SNAP-008 → REL-SNAP-00924h 0m
REL-SNAP-009 → REL-SNAP-01024h 0m
REL-SNAP-010 → REL-SNAP-01124h 0m
REL-SNAP-011 → REL-SNAP-01224h 0m
REL-SNAP-012 → REL-SNAP-01324h 4m
REL-SNAP-013 → REL-SNAP-01423h 56m
REL-SNAP-014 → REL-SNAP-01524h 0m
REL-SNAP-015 → REL-SNAP-01624h 0m

The longest interval, and what happened during it

25h 40m — between REL-SNAP-003 and REL-SNAP-004.

The scheduled run produced no snapshot. Nothing reported the silence — a person noticed, and the snapshot was captured and published by hand.

The next scheduled run produced a snapshot with no intervention.

Nothing was missing from the record. Both snapshots were published, and the later one names the earlier one's root, so the sequence has no break in it. What went wrong was that the capture did not happen on its own and nothing said so — the silence had to be noticed by a person rather than reported by the system. That is a worse property than a long interval, and it is the part worth writing down.

We would describe a third party's record in exactly these terms: what was observed, when, and what is not known. Applying a softer standard to ourselves would make every other page on this site worth less.

Why there is no status indicator on this page

This page is built, not queried. Any reassuring summary of the present moment would be true when the page was built and would quietly stop being true afterwards, with no way to correct itself between builds. An indicator that goes stale without looking stale is worse than no indicator at all — it is most confidently green exactly when nobody has checked.

So this page publishes only facts that stay true: intervals that have already happened, stamped as of 2026-08-20. The chain itself is the live source. If you are reading this later, there are very likely more snapshots than are listed here, and verifying the chain is how you find out rather than trusting this page's date.

If you think a record about your server is wrong

How corrections work — including why a published snapshot is never rewritten. If you would rather not appear here at all, delisting explains what we can and cannot do.