Bitnodes estimates the relative size of the Bitcoin peer-to-peer network by finding all of its reachable nodes.


This page reports network health data for reachable ASNs, which are ASNs that have at least one reachable IPv4/IPv6 Bitcoin node. Data points are collected whenever a new network snapshot is available, which occurs approximately every 10 minutes. BGP alerts are promptly displayed within 10 seconds of detection and will be automatically cleared after 1 hour if they are not persistent.

Each autonomous system (AS) is associated with a unique autonomous system number (ASN) and consists of a group of IP prefixes that fall under the control of a single administrative entity, such as an Internet Service Provider (ISP). ASNs are crucial for determining the most efficient routes for network traffic using Border Gateway Protocol (BGP), which enables the Internet to operate as a global, interconnected network.

A diverse range of ASNs is essential for the Bitcoin peer-to-peer network to maintain its decentralized nature, a key characteristic that sets it apart from traditional financial systems. This diversity also enhances the network's resiliency against potential threats, making it more difficult for bad actors to disrupt the network by targeting a single point of weakness.

Page is updated automatically on new snapshot. Time since last snapshot: 0s

AS24961 ADJACENT PEERSSelectel JSC (AS49505), Emirates Telecommunications Group Company (etisalat Group) Pjsc (AS8966), Vectra S.A. (AS29314), Nte Telekom As (AS34087), myNet GmbH (AS31543), Verein zur Foerderung eines Deutschen Forschungsnetzes e.V. (AS680), 31173 Services AB (AS39351), AS-CHOOPA (AS20473), Datacamp Limited (AS60068), Aruba S.p.A. (AS31034), EWE-Tel GmbH (AS9145), UK-2 Limited (AS13213), Emirates Integrated Telecommunications Company PJSC (AS15802), Wind Tre S.p.A. (AS1267), Telekom Slovenije, d.d. (AS5603), Gigahost AS (AS56655), Administracion Nacional de Telecomunicaciones (AS6057), Digi Romania S.A. (AS8708), HVC-AS (AS29802), Consortium GARR (AS137), HURRICANE (AS6939), AMAZON-02 (AS16509), ecotel communication ag (AS12312), 1&1 Versatel Deutschland GmbH (AS8881), Deutsche Telekom AG (AS3320), TENET Scientific Production Enterprise LLC (AS6876), Telefonica Germany (AS6805), TM TECHNOLOGY SERVICES SDN. BHD. (AS4788), Tele2 SWIPnet (AS1257), Partner Communications Ltd. (AS12400), Hong Kong Broadband Network Ltd. (AS9269), Orange Romania S.A. (AS9050), M247 Europe SRL (AS9009), Init7 (Switzerland) Ltd. (AS13030), Cyprus Telecommunications Authority (AS6866), Contabo GmbH (AS51167), Voxility LLP (AS3223), Telekom Austria (AS8447), Revolution Provider Srl (AS41720), OVH SAS (AS16276), HGC Global Communications Limited (AS9304), Telia Lietuva, AB (AS8764), Rostelecom (AS12389), Serbia BroadBand-Srpske Kablovske mreze d.o.o. (AS31042), Data Communication Business Group (AS3462), NetAssist LLC (AS8772), IQWeb FZ-LLC (AS59692), Melbikomas UAB (AS56630), NetCom BW GmbH (AS41998), UAB Bite Lietuva (AS13194), MTS PJSC (AS8359), Serverius Holding B.V. (AS50673), TELEKOM SRBIJA a.d. (AS8400), Ooredoo Q.S.C. (AS8781), Societatea mixta pe actiuni de tip inchis Interdnestrcom (AS1547), IONOS SE (AS8560), ESCOM Ltd. - Haskovo (AS25374), Bezeq- THE ISRAEL TELECOMMUNICATION CORP. LTD. (AS6810), SWAN, a.s. (AS5578), Cellcom Fixed Line Communication L.P (AS1680), Bulsatcom EOOD (AS43205), MICROSOFT-CORP-MSN-AS-BLOCK (AS8075), TENET-1 (AS2018), SK Broadband Co Ltd (AS9318), Inetcom Carrier LLC (AS35598), GANDI SAS (AS29169), DOKOM Gesellschaft fuer Telekommunikation mbH (AS15763), inexio Informationstechnologie und Telekommunikation Gmbh (AS42652), Host Europe GmbH (AS20773), TDC Holding A/S (AS3292), Societe Francaise Du Radiotelephone - SFR SA (AS15557), Selectel JSC (AS50340), oneCorp GmbH (AS204035), SWITCH (AS559), Vodafone GmbH (AS3209), PACKET (AS54825), Fonira Telekom GmbH (AS51184), TimeWeb Ltd. (AS9123), Eir Broadband (AS5466), Tencent Building, Kejizhongyi Avenue (AS132203), CLOUDFLARENET (AS13335), CETIN Ltd. Belgrade (AS15958), VNPT Corp (AS45899), GOOGLE (AS15169), Quantcom, a.s. (AS29208), Vivacom Bulgaria EAD (AS8866), Neterra Ltd. (AS34224), Equinix (EMEA) Acquisition Enterprises B.V. (AS15830), Fastweb (AS12874), Bluewin (AS3303)


Reachable ASNASN that contains at least 1 reachable Bitcoin node.
Latency 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 ROA (Route Origin Authorization) IPv4 prefixes for the ASN.
IPv6 ROA %Percentage of IPv6 nodes covered by ROA (Route Origin Authorization) IPv6 prefixes for the ASN.
Adjacent peersAdjacent peering ASNs that contain at least 1 reachable Bitcoin node.
BGP alertThis ASN is originating an IP prefix owned by another ASN during the past hour.
BGP alertAnother ASN is originating an IP prefix owned by this ASN during the past hour.


One threat to the Bitcoin peer-to-peer network's security that is often overlooked is Border Gateway Protocol (BGP) hijacking. In a BGP hijacking attack, an attacker manipulates BGP routes to redirect traffic intended for a Bitcoin node to a malicious node under the attacker's control. This can lead to the interception and manipulation of Bitcoin block or transaction messages, potentially resulting in financial losses. Adding to this risk, Bitcoin traffic is unencrypted by default, making it susceptible to interception and manipulation by attackers who gain access to the network traffic.

BGP hijacking attacks can occur anywhere along the path between a Bitcoin node and its peers, so it is important for Bitcoin node operators to be able to monitor for any suspicious routing changes, both within their own autonomous system (AS) and in the ASes of their peers.

A BGP hijack in the operator's own AS1 (Fig. 1) could redirect traffic away from the legitimate Bitcoin node ₿1 while a hijack in the destination AS2 (Fig. 2) could redirect traffic intended for the Bitcoin node ₿2 to a malicious node under the attacker's control.

To mitigate the risk of BGP hijacking attacks, it is important to have monitoring tools in place that can detect and alert network operators to any unusual routing changes. However, existing monitoring tools may not be suitable for Bitcoin node operators as they are primarily designed for general network operations. Hence, a specialized monitoring tool, such as Bitnodes BGP alert, is necessary in surfacing possible BGP hijacking attacks affecting the Bitcoin network.

Bitnodes uses rpki-client to periodically (hourly) fetch the latest Route Origin Authorizations (ROAs) from each of the five Regional Internet Registries (RIRs), i.e. AFRINIC, APNIC, ARIN, LACNIC, RIPE, and consolidate them into a single JSON file:

    "metadata": {.., "buildtime": "2023-01-01T00:00:00Z", ..},
    "roas": [
        {"asn": "AS14061", "prefix": "", "maxLength": 24},

All IP prefixes from the JSON file are stored in a database and treated as Validated ROA Payload (VRP) for up to 24 hours. Bitnodes uses RIPE Routing Information Service Live (RIS Live) to receive live BGP announcement messages. For each announcement message:

    'peer': '', 'peer_asn': '133210',
    'path': [133210, 9498, 14061],
    'announcements': [{'next_hop': '', 'prefixes': ['']}], ..

Bitnodes queries its VRP database to validate each of the prefixes in the message:

Query outputOutcome
Prefix in the message matches a VRP record. The match can be equal or prefix being more specific with its prefix length no greater than the matching VRP's max. length.VALID
Origin AS in the message did not match the matching VRP record or prefix in the message is more specific than the matching VRP's max. length.INVALID
No matching VRPs.UNKNOWN

If the validation outcome is marked as INVALID, the reachable ASN on the origin AS end will trigger an alert labeled as BGP alert, and the reachable ASN on the VRP's AS end will trigger an alert labeled as BGP alert, for a duration of up to one hour from the time of the last INVALID validation. It is important to note that the presence of these alerts should not automatically be interpreted as indicative of a BGP hijack. They could potentially result from temporary misconfigurations or other benign causes. Additional analysis is almost always warranted, including but not limited to monitoring for anomalous changes in ping latency, block propagation time, or an increase in block height delta from consensus height.

Join the Network

Be part of the Bitcoin network by running a Bitcoin full node, e.g. Bitcoin Core.

Use this tool to check if your Bitcoin client is currently accepting incoming connections from other nodes. Port must be between 1024 and 65535.