Testnet Mode — switch back to Production in the menuheader when you're done.
Checks of the scanner, its gateways and the ledger nodes, run from your browser every 30 seconds while this tab is open.
Checking systems…
Scanner API
This site's own backend (search, history, wallet routes).
Checking…
Indexing
How recently the scanner stored a ledger event. A quiet ledger also reads as old.
Checking…
Gateways
Checked from your browser. One gateway up is enough; the scanner uses the best.
Checking…
Gateway 1
Checking…
Gateway 2
Checking…
Gateway 3
Checking…
Gateway 4
Checking…
Ledger nodes
Checked from your browser. 3 of 4 must be up to reach consensus.
Checking…
Node 1
Checking…
Node 2
Checking…
Node 3
Checking…
Node 4
Checking…
Email delivery
How recently the scanner sent an alert or confirmation email. A quiet spell also reads as old.
Checking…
How far our deposit scanners have read each chain. They stay behind the tip on purpose: a deposit is credited to the ledger only once its block is final enough, and each chain shows the gap to expect. Your browser reads the tip from a public node. Informational only; it doesn't change the status above.
Ethereum Sepolia
Checking…
expected: 3 blocks, ~36 s
Tron Nile
Checking…
expected: at the tip
BNB Smart Chain Testnet
Checking…
expected: 6 blocks, ~3 s
Base Sepolia
Checking…
expected: safe, ~3 min
Arbitrum Sepolia
Checking…
expected: safe, ~15 min
Polygon Amoy
Checking…
expected: finalized − 32 blocks, ~2 min
Bitcoin Testnet4
Checking…
expected: 6 blocks, ~1 h
testnet4 is currently mined mostly by bots that use its 20-minute minimum-difficulty rule to make empty blocks, so transactions can wait a long time to confirm. This is a testnet4 problem, not a Varnir one, so Varnir has paused testnet4 deposits and sends until it is reliable; Bitcoin Signet is live and confirms normally.
Bitcoin Signet
Checking…
expected: 3 blocks, ~30 min
No incidents in the last 90 days.
The checks run from your browser, so a fault in your own connection can show here too. Blockchains compares each chain's tip, read from a public node, with how far our deposit scanners have read; it is informational and doesn't set the overall status. Recovery emails, sent by the gateways, aren't checked. This page runs on the same Cloudflare account as the scanner: if the scanner is fully down, so is this page. An independent uptime monitor, run from outside our infrastructure, is planned.