BlockAlt status
Live checks run by the API itself each time this page loads.
All checks are passing
2 of 2 checks passing
Checked
Live checks
Run on this requestVerification database
OperationalToken verification, issuance and the console can read and write their data.
Script delivery
OperationalThe browser script and its manifest are served by this server.
- Version
- 0.3.0
- Size
- 4,640 bytes gzip
- Path
/v1/assets/blockalt.c8b2d9539dbbc932999adb0f51a36bddd4e99899f543e1505818841878cf9813.js
What to do while something is down
Your server decides
While a check fails, verification and issuance fail closed. The official server SDK refuses the action with
service_unavailableon a timeout, a network error or a 5xx: ask the visitor to try again. Failure policyLow-risk actions may fail open
You may accept a low-risk action without a decision, but log it and alert on it, so an outage is not mistaken for quiet traffic.
Check from outside
This page runs on the API it describes. Poll /readyz from your own monitoring to see an outage this page cannot show.
Independent monitoring
This page is served by the same API it describes, so it cannot report an outage of the API, the server or the network in front of it. It is a live check, not an uptime record or a service level.
No independent probe results are published yet.
The independent monitor runs from a separate host and alerts the operator directly; its history will be published on a separately hosted status page.
The independent probe loads the readiness endpoint and the browser script, and, with a dedicated canary site, verifies the signed configuration, solves the work, has one token accepted and checks that a replay of it is refused. Operators set it up as described in the README section “Independent monitoring” (ops/blockalt-monitor.service on a different host).