ASN Health

This page reports network metrics and statistics for reachable ASNs, which are autonomous systems that contain at least one reachable IPv4 or IPv6 Bitcoin node. Data points are refreshed whenever a new network snapshot is available.

A diverse set of ASNs helps the Bitcoin peer-to-peer network stay resilient because node reachability is not concentrated behind a single routing or hosting provider.

Reachable nodes as of ...

BROWSE

Reachable ASNs

Terminology

Reachable ASN

ASN that contains at least one reachable IPv4 or IPv6 Bitcoin node.

RTT 50%

50th percentile (median) ping message round-trip time in milliseconds.

Uptime 50%

50th percentile (median) uptime in hours from persistent connections.

Block 50%

50th percentile (median) latest block inv propagation time in milliseconds.

Height 50%

50th percentile (median) block height delta from consensus height.

IPv4 ROA %

Percentage of IPv4 nodes covered by Route Origin Authorization IPv4 prefixes for the ASN.

IPv6 ROA %

Percentage of IPv6 nodes covered by Route Origin Authorization IPv6 prefixes for the ASN.

Adjacent peers

Adjacent peering ASNs that contain at least one reachable Bitcoin node.

SRC

This ASN is originating an IP prefix owned by another ASN during the past hour.

DST

Another ASN is originating an IP prefix owned by this ASN during the past hour.

BGP Alert

Source or destination route-origin alert from a BGP/RPKI monitoring feed. Standalone deployments show this as unavailable unless that feed is integrated.

BGP Alert Methodology

Border Gateway Protocol (BGP) hijacking can redirect traffic intended for a Bitcoin node to a malicious node under the attacker's control. Bitcoin traffic is unencrypted by default, so suspicious routing changes are relevant to both the source AS and the destination ASes of a node's peers.

[BN1]        [BN2]
  |            ^
  v            |
[AS1]---x--->[AS2]
                ^
                |
[AS3]----------+

[BN1]        [BN2]
  |            ^
  v            |
[AS1]---x--->[AS2]
  |
  |
  +--------->[AS4]
                |
                v
              [BN4]

Hosted btcnodes.io uses rpki-client to fetch Route Origin Authorizations from the five Regional Internet Registries, then stores validated ROA payloads for route-origin checks. It receives live BGP announcement messages from RIPE RIS Live and validates announced prefixes against those ROAs.

If a route validation outcome is invalid, the reachable ASN on the origin AS end is labeled SRC, and the reachable ASN on the ROA owner end is labeled DST, for up to one hour from the last invalid validation. These labels are signals for additional analysis, not automatic proof of an attack.

This standalone UI does not fabricate external BGP or RPKI alerts. It reports live snapshot-derived ASN health and marks BGP alert status as unavailable unless a deployment provides that data source.