Chain liveness
Whether each chain we watch is producing blocks, measured at the moment we asked — and every halt we have recorded since this archive began. A chain we could not read is not green.
| Chain | Now | Height | Lag at reading | Halts recorded | Total halted |
|---|---|---|---|---|---|
| BitcoinBTCread 2m ago | producing19:52since last read | 970,382 | 5m | none recorded | — |
| EthereumETHread 2m ago | producing19:57since last read | 26,142,748 | 0s | none recorded | — |
| SolanaSOLread 2m ago | producing19:57since last read | 454,323,054 | 5s | none recorded | — |
| XRP LedgerXRPread 2m ago | producing19:57since last read | 107,501,113 | 0s | none recorded | — |
| Avalanche C-ChainAVAXread 2m ago | producing19:57since last read | 96,980,167 | 0s | none recorded | — |
| NEAR ProtocolNEARnot currently watched, so a halt on this chain would not be detected here | disabled | — | — | none recorded | — |
| SuiSUIread 2m ago | producing19:57since last read | 331,425,877 | 0s | none recorded | — |
How complete is this?
1 recorded gap(s) in the last 14 days, totalling 3 minutes when this site was not looking.
One row per chain we watch, as it stands now. The coverage windows below are our own: while we were not looking, a halt could have started and ended without ever reaching this record.
When we were not looking
- 3 min Chain slowdowns and recoverieswe were not reading this while the window was open
Days that are not a day’s worth
This dataset is not a continuous record: a day with nothing on it is a quiet day in the world rather than a gap in ours, so no per-day expectation is stated.
What produced these rows
- bitcoin 1 row(s)https://mempool.space/api
- ethereum 1 row(s)https://ethereum-rpc.publicnode.com
- solana 1 row(s)https://api.mainnet-beta.solana.com
- xrp 1 row(s)https://xrplcluster.com/
- avalanche 1 row(s)https://api.avax.network/ext/bc/C/rpc
- near 1 row(s)https://free.rpc.fastnear.com — not currently watched
- sui 1 row(s)https://graphql.mainnet.sui.io/graphql
Corrections
None issued against this dataset.
Our own downtime, inside this window
- 38 min degraded · The wire wrote no ledger row for 38 minutes (stage 'budget') not written up yet
- 44 min degraded · The wire wrote no ledger row for 44 minutes (stage 'budget') not written up yet
- 107 min degraded · The wire wrote no ledger row for 107 minutes (stage 'budget') not written up yet
- 47 min degraded · The wire wrote no ledger row for 47 minutes (stage 'budget') not written up yet
- 39 min degraded · The wire wrote no ledger row for 39 minutes (stage 'budget') not written up yet
- 46 min degraded · The wire wrote no ledger row for 46 minutes (stage 'budget') not written up yet
- 65 min degraded · The wire wrote no ledger row for 65 minutes (stage 'budget') not written up yet
- 57 min degraded · The wire wrote no ledger row for 57 minutes (stage 'budget') not written up yet
- 44 min degraded · The wire wrote no ledger row for 44 minutes (stage 'budget') not written up yet
- 39 min degraded · The wire wrote no ledger row for 39 minutes (stage 'budget') not written up yet
- 37 min degraded · The wire wrote no ledger row for 37 minutes (stage 'budget') not written up yet
- 31 min degraded · The wire wrote no ledger row for 31 minutes (stage 'budget') not written up yet
- 31 min degraded · The wire wrote no ledger row for 31 minutes (stage 'budget') not written up yet
- 31 min degraded · The wire wrote no ledger row for 31 minutes (stage 'budget') not written up yet
Anything known to be wrong?
5 problems are open in this site’s own checks; none of them is about this dataset.
Assembled from records this site already keeps — the gap ledgers, the corrections record, the incident record and the gate’s own tally. It adds no new collection. The same report ships with the download as /api/v1/chain-liveness.integrity.txt and inside the JSON. What this site cannot see at all.
Heights are read from public endpoints at our own polling interval. We record what we measured; a gap in the record is a gap in our watching, and is shown as one.