·Status

Live status, on a third-party dead-man’s switch.

Per-component health for the surfaces you depend on. Our servers probe each component and report the result to independent third-party infrastructure (healthchecks.io), which renders the badges shown here and flips one red on its own if our pings stop arriving — so we can fail to report, but we can’t publish a green light we didn’t send. While monitors are still being connected, the affected component says so plainly; this page never shows a green light it didn’t receive.

01Components

Four components, one badge each.

Component list (no-JavaScript view)

This page renders its badges with a small same-origin script. Without JavaScript, here is the component list; the first two health endpoints are public and you can open them directly:

Anchor API — app.satsignal.cloud/healthz
Public verify — proof.satsignal.cloud/healthz
Landing — satsignal.cloud (you are reading it)
Broadcast path — heartbeat reported from our infrastructure; no public endpoint

The first two components also expose their raw health endpoints publicly — /healthz on each host returns ok — so you can always probe them yourself rather than trust a badge.

02What an outage does not touch

Already-anchored proofs don’t need us to be up.

If you downloaded your .mbnt bundle, verification is independent of every component on this page: the bundle’s internal integrity checks fully offline, and the “is it really on the chain?” step runs against any public Bitcoin SV block explorer — not through Satsignal. The verifier itself is a single static HTML file you can save and run offline — its checks are embedded in the page; the one on-demand fetch is the PDF text-extraction library, used only when re-deriving a PDF’s content fingerprint.

What an outage does affect: anchoring new proofs, downloading bundles still in server-side retention, sealed-mode reveals via /unseal, and /lookup_hash re-binding for holders who never downloaded their bundle. Details and the per-mode breakdown are on the availability page and in the docs durability table.