Total nodes Loading
bitnodesBitnodes estimates the relative size of the Bitcoin peer-to-peer network by finding all of its reachable nodes.
Support Bitnodes project and enjoy ad-free experience. Sign up and upgrade today.
2892 ASNs with their respective number of global IPv4/IPv6 Bitcoin nodes as of Fri Oct 4 20:00:00 2024 EDT.
Window size: 90-day
RANK | ASN | NODES |
---|---|---|
443 | AS56668 FOP Demchuk Sergiy Olexandrovuch | 2 (0.01%) |
443 | AS56689 Elitel Telecom Group Ltd | 2 (0.01%) |
443 | AS56985 RUSTEL LLC | 2 (0.01%) |
443 | AS57184 kt Mazllc | 2 (0.01%) |
443 | AS57271 BitWeb LLC | 2 (0.01%) |
443 | AS57293 AG Telekom MMC. | 2 (0.01%) |
443 | AS57672 Daniel James Austin | 2 (0.01%) |
443 | AS57707 Greendata s.r.o. | 2 (0.01%) |
443 | AS57814 Cloud 9 Ltd. | 2 (0.01%) |
443 | AS58256 Rayaneh Gostar Farzanegan Ahwaz Company LTD. | 2 (0.01%) |
443 | AS58294 CloudWall Ltd. | 2 (0.01%) |
443 | AS58369 PT. Fiber Networks Indonesia | 2 (0.01%) |
443 | AS58965 ANJANI BROADBAND SOLUTIONS PVT.LTD. | 2 (0.01%) |
443 | AS59108 KATCH NETWORK INC. | 2 (0.01%) |
443 | AS59668 Turon Media XK | 2 (0.01%) |
443 | AS59684 Hoster kg, Ltd. | 2 (0.01%) |
443 | AS59692 IQWeb FZ-LLC | 2 (0.01%) |
443 | AS59845 Top 21 Systemhaus GmbH | 2 (0.01%) |
443 | AS60131 High5! B.V. | 2 (0.01%) |
443 | AS60631 Pars Parva System LLC | 2 (0.01%) |
443 | AS61942 TURBONET TELECOM LTDA | 2 (0.01%) |
443 | AS62064 Closeness S.L. | 2 (0.01%) |
443 | AS62098 Espix Network SPRL | 2 (0.01%) |
443 | AS62365 SachsenGigaBit GmbH | 2 (0.01%) |
443 | AS62728 VGPE-ASN1 | 2 (0.01%) |
This page reports the estimated size of the Bitcoin peer-to-peer network including both reachable and unreachable nodes, i.e. global nodes. Unlike the low churn rate estimation method for reachable nodes (see the latest snapshot here), the method for this report can only provide a rough estimation and does not filter out potentially spurious nodes that may be gossiped by non-standard/spam/malicious peers.
Bitnodes crawler captures these nodes from the addr messages returned by all the reachable nodes. Each snapshot or data point in this report represents a rolling window. A snapshot with window size of 1 day will include all nodes by IP addresses with timestamps less than 1 day old. The timestamp for a node here refers to the time when its peer last connects to it. If you turn on your Bitcoin node for only a few minutes anytime during the last 24 hours, it will be included in the latest snapshot with a window size of 1 day.
Multiple nodes from the same IP address, but different port numbers are counted as one node in this report. A larger window size may increase the likelihood of the same node being counted more than once due to e.g. IP lease renewal.
A Bitcoin node may be unreachable for several reasons. It may be configured by the operator to only attempt to make outgoing connections or it may be located behind corporate/ISP firewalls or NAT. A node could also become temporarily unreachable if it has hit its maximum allowed connections or if it is in the process of syncing up to the latest blocks. As it is impossible to connect to an unreachable node directly, we cannot reliably confirm the true existence of an unreachable node, hence the rough estimation.
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.