Site status

Status

One status dashboard for every configured network: 4 of 4 networks have a node answering. Each chain line uses the same rule as that network's /healthz.

Is the stack OK?

Summary

Errors since process start

Bitcoin Cash MainnetReachable
Tip
972,857
Lag
One node reporting
Errors
41.5%2,212 / 5,324
/healthz answers ok: 1 of 1 probed node answering.
mainnet-node-1Preferred127.0.0.1:1235Reachable
Tip
972,857
Lag
At tip
Errors
41.5%2,212 / 5,324
OK · unified API reachable; index readiness not probed

Tip agreement, this probe

One node reporting: lag is not measured against another node.

Bitcoin Cash ChipnetTestnetReachable
Tip
327,879
Lag
One node reporting
Errors
0.4%11 / 3,066
/healthz answers ok: 1 of 1 probed node answering.
chipnet-node-1Preferred127.0.0.1:41235Reachable
Tip
327,879
Lag
At tip
Errors
0.4%11 / 3,066
OK · unified API reachable; index readiness not probed

Tip agreement, this probe

One node reporting: lag is not measured against another node.

Bitcoin Cash Testnet3TestnetReachable
Tip
1,732,390
Lag
One node reporting
Errors
1.8%14 / 794
/healthz answers ok: 1 of 1 probed node answering.
testnet3-node-1Preferred127.0.0.1:11235Reachable
Tip
1,732,390
Lag
At tip
Errors
1.8%14 / 794
OK · unified API reachable; index readiness not probed

Tip agreement, this probe

One node reporting: lag is not measured against another node.

Bitcoin Cash Testnet4TestnetReachable
Tip
327,860
Lag
One node reporting
Errors
1.6%12 / 736
/healthz answers ok: 1 of 1 probed node answering.
testnet4-node-1Preferred127.0.0.1:21235Reachable
Tip
327,860
Lag
At tip
Errors
1.6%12 / 736
OK · unified API reachable; index readiness not probed

Tip agreement, this probe

One node reporting: lag is not measured against another node.

A node is reachable when it answered the status probe. A chain is reachable when at least one probed node is, which is exactly when its /healthz answers ok; otherwise it is degraded and /healthz answers 503. Lag is how far a node's tip is behind the highest tip in the same probe. Error rates count every backend call to the node since the explorer process started; there is no rolling window.

Node diagnostics for every network

Bitcoin Cash Mainnet

Rank	Node	Endpoint	Reachable	Cooldown	Chain	Best height	Indexed tip	Latency	Successes	Failures	Last success	Last failure	Message
1	mainnet-node-1 Inspect node	127.0.0.1:1235 Pool 8/8 active Open sessions 8 to backend Busy 0 · Reserved fast 1	Up	Ready	main	972,857	—	10 ms	3,112	2,212	2026-10-14 19:06:44 UTC	2026-10-14 19:06:42 UTC	OK · unified API reachable; index readiness not probed

Bitcoin Cash Chipnet

Rank	Node	Endpoint	Reachable	Cooldown	Chain	Best height	Indexed tip	Latency	Successes	Failures	Last success	Last failure	Message
1	chipnet-node-1 Inspect node	127.0.0.1:41235 Pool 8/8 active Open sessions 4 to backend Busy 0 · Reserved fast 1	Up	Ready	chip	327,879	—	10 ms	3,055	11	2026-10-14 19:06:44 UTC	2026-10-14 18:19:26 UTC	OK · unified API reachable; index readiness not probed

Bitcoin Cash Testnet3

Rank	Node	Endpoint	Reachable	Cooldown	Chain	Best height	Indexed tip	Latency	Successes	Failures	Last success	Last failure	Message
1	testnet3-node-1 Inspect node	127.0.0.1:11235 Pool 8/8 active Open sessions 4 to backend Busy 0 · Reserved fast 1	Up	Ready	test	1,732,390	—	10 ms	780	14	2026-10-14 19:06:44 UTC	2026-10-14 18:45:27 UTC	OK · unified API reachable; index readiness not probed

Bitcoin Cash Testnet4

Rank	Node	Endpoint	Reachable	Cooldown	Chain	Best height	Indexed tip	Latency	Successes	Failures	Last success	Last failure	Message
1	testnet4-node-1 Inspect node	127.0.0.1:21235 Pool 8/8 active Open sessions 3 to backend Busy 0 · Reserved fast 1	Up	Ready	test4	327,860	—	10 ms	724	12	2026-10-14 19:06:44 UTC	2026-10-14 19:05:35 UTC	OK · unified API reachable; index readiness not probed