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


Global Bitcoin nodes by country

161 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Sun Jun 8 20:00:00 2025 EDT.

Window size: 7-day

NODES125973
COUNTRIES161
CITIES9150
ASNS2747
SERVICES6
PORT NUMBERS339

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

RANKCOUNTRYNODES
26Hong Kong
754 (0.69%)
27Korea (the Republic of)
655 (0.60%)
28Ireland
632 (0.58%)
29Indonesia
547 (0.50%)
30Ukraine
535 (0.49%)
31Argentina
462 (0.42%)
32Norway
460 (0.42%)
33Romania
457 (0.42%)
34Taiwan
437 (0.40%)
35Hungary
410 (0.38%)
36Israel
399 (0.37%)
37New Zealand
395 (0.36%)
38Malaysia
384 (0.35%)
39Greece
370 (0.34%)
40United Arab Emirates
346 (0.32%)
41South Africa
335 (0.31%)
42Vietnam
270 (0.25%)
43Bulgaria
264 (0.24%)
44Slovakia
247 (0.23%)
45Saudi Arabia
245 (0.22%)
46Croatia
220 (0.20%)
47Colombia
214 (0.20%)
48Türkiye
203 (0.19%)
49Uruguay
200 (0.18%)
50Iran (Islamic Republic of)
196 (0.18%)

First / Prev Page 2 of 7 (161 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.