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


Global Bitcoin nodes by country

165 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Sun Aug 31 20:00:00 2025 EDT.

Window size: 7-day

NODES128124
COUNTRIES165
CITIES9382
ASNS2748
SERVICES6
PORT NUMBERS342

First / Prev Page 2 of 7 (165 countries) Next / Last

RANKCOUNTRYNODES
26Belgium
672 (0.62%)
27Poland
657 (0.60%)
28Ireland
643 (0.59%)
29Indonesia
586 (0.54%)
30Argentina
551 (0.50%)
31Romania
535 (0.49%)
32Ukraine
500 (0.46%)
33Norway
491 (0.45%)
34Hungary
475 (0.43%)
35Greece
468 (0.43%)
36Taiwan
455 (0.42%)
37Israel
414 (0.38%)
38New Zealand
410 (0.38%)
39United Arab Emirates
389 (0.36%)
40Vietnam
370 (0.34%)
41Malaysia
355 (0.32%)
42Bulgaria
319 (0.29%)
43South Africa
292 (0.27%)
44Iran (Islamic Republic of)
280 (0.26%)
45Croatia
272 (0.25%)
46Colombia
259 (0.24%)
47Uruguay
242 (0.22%)
48Slovakia
233 (0.21%)
49Türkiye
228 (0.21%)
50Philippines
221 (0.20%)

First / Prev Page 2 of 7 (165 countries) Next / Last

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.


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.