Status · measured now, not promised

Every probe passed — measured 2026-10-20 11:45:21 UTC

Four real probes ran when you opened this page, each under a 4,000 ms timeout · nothing is stored, nothing is averaged : this page is the probe

Machine-readable JSON →Sign in

All probes pass

the worst probe decides · kernel · database · catalogue · deployment

slowest database · 277 msdeployment 9a17991 · iad1catalogue seal c9d5c71a3fa13ecf…

probes

4 / 4

ok · none degraded · none down

kernel

16 ms

compute → sign → verify · chainLadderReserve

database

277 ms

one bounded read · receipts

deployment

9a17991

iad1 · production · rendered 2026-10-20 11:45:21 UTC

intelligence · detect → adapt → verify

detectfour probes ran this second, each with its own timeout : the kernel computed, signed and verified the sealed beachhead preset in-process · the database answered one bounded read · the catalogue seal was recomputed · the deployment named itself — the worst of the four is the verdictmeasured now

adaptNothing to do. Point your monitor at /api/status (200 when every probe passes, 503 when one is down, never cached) ; when a probe is down, write to support with the timestamp above and the failing probe's words.Write to support →

verifyno history is kept and no percentage is derived — reload and the probes run again ; curl -i /api/status returns the same report as JSON · the Terms page's Uptime row says « measured, not promised » and links hereno history · no SLA

Probes · this requesttimeout 4,000 ms each · degraded past 1,500 ms

Kernelokcomputed chainLadderReserve on its sealed preset, signed it with a throwaway probe key and verified the bundle — 6 / 6 checks, seal matches the live catalogue16 ms
Databaseokone bounded read on receipts through the service role answered — nothing is shown, nothing is written277 ms
Catalogueokthe manifest loaded and sealed — 5 engines, seal c9d5c71a3fa13ecf… (the value every new receipt pins)2 ms
Deploymentokcommit 9a17991 · region iad1 · production · rendered 2026-10-20 11:45:21 UTC0 ms

What this page is, and is notthe same words on the Terms page

It measures the moment you open it.Four probes, real, with timeouts. Reload : they run again. Nothing is cached.
It keeps no history and promises no number.No uptime percentage, no 90-day bar, no SLA — a figure would be fabricated, because nothing stores the past yet. The Terms page says « measured, not promised » and links here.
Your monitor gets the same truth.GET /api/status → the same report as JSON, 200 when every probe passes, 503 when one is down, Cache-Control: no-store.