Total nodes Loading
bitnodesBitnodes estimates the relative size of the Bitcoin peer-to-peer network by finding all of its reachable nodes.
2931 ASNs with their respective number of global IPv4/IPv6 Bitcoin nodes as of Thu Jan 16 19:00:00 2025 EST.
Window size: 30-day
| RANK | ASN | NODES |
|---|---|---|
| 319 | AS36666 GTCOMM | 5 (0.01%) |
| 319 | AS37002 Reunicable | 5 (0.01%) |
| 319 | AS37153 xneelo | 5 (0.01%) |
| 319 | AS395570 FIBRESTREAM | 5 (0.01%) |
| 319 | AS395662 OZARKSGO | 5 (0.01%) |
| 319 | AS398113 GATEWAY-FIBER | 5 (0.01%) |
| 319 | AS398337 COMMUNITY-INTERNET-PROVIDERS | 5 (0.01%) |
| 319 | AS40065 CNSERVERS | 5 (0.01%) |
| 319 | AS40545 EMPIRE-40545 | 5 (0.01%) |
| 319 | AS41230 ASK4 Limited | 5 (0.01%) |
| 319 | AS41268 LANTA Ltd | 5 (0.01%) |
| 319 | AS41822 MTS PJSC | 5 (0.01%) |
| 319 | AS41843 JSC ER-Telecom Holding | 5 (0.01%) |
| 319 | AS42668 Nevalink, LLC | 5 (0.01%) |
| 319 | AS42916 IT Ltd. | 5 (0.01%) |
| 319 | AS43529 ViDaNet Cabletelevision Provider Ltd. | 5 (0.01%) |
| 319 | AS43667 Vermont-IT Limited Liability Company | 5 (0.01%) |
| 319 | AS44592 SkyLink Data Center BV | 5 (0.01%) |
| 319 | AS44709 O.m.c. Computers & Communications Ltd | 5 (0.01%) |
| 319 | AS44923 Saint-Petersburg Computer Networks Ltd. | 5 (0.01%) |
| 319 | AS44927 LLC Telecom MPK | 5 (0.01%) |
| 319 | AS45179 SiteHost New Zealand | 5 (0.01%) |
| 319 | AS47066 PRGMR | 5 (0.01%) |
| 319 | AS47589 Kuwait Telecommunication Company (Under Association) | 5 (0.01%) |
| 319 | AS48004 PE Tsibrankov Konstantin Igorevich | 5 (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.