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


Global Bitcoin nodes by country

150 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Fri Jul 11 20:00:00 2025 EDT.

Window size: 1-day

NODES66952
COUNTRIES150
CITIES7579
ASNS2457
SERVICES6
PORT NUMBERS270

Page 1 of 6 (150 countries) Next / Last

RANKCOUNTRYNODES
1United States
15095 (29.57%)
2Germany
6961 (13.64%)
3Canada
2730 (5.35%)
4France
2085 (4.08%)
5United Kingdom
2037 (3.99%)
6Netherlands
1816 (3.56%)
7China
1524 (2.99%)
8Russian Federation
1223 (2.40%)
9Australia
1210 (2.37%)
10Switzerland
1165 (2.28%)
11Spain
1093 (2.14%)
12Brazil
1066 (2.09%)
13Italy
1016 (1.99%)
14Finland
867 (1.70%)
15Japan
777 (1.52%)
16Singapore
571 (1.12%)
17Korea (the Republic of)
564 (1.10%)
18Austria
558 (1.09%)
19Sweden
554 (1.09%)
20Czechia
481 (0.94%)
21Portugal
397 (0.78%)
22Belgium
377 (0.74%)
23Poland
366 (0.72%)
24Hong Kong
341 (0.67%)
25Mexico
337 (0.66%)

Page 1 of 6 (150 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.