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


Global Bitcoin nodes by country

151 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Wed Aug 6 20:00:00 2025 EDT.

Window size: 1-day

NODES69153
COUNTRIES151
CITIES7773
ASNS2451
SERVICES6
PORT NUMBERS258

Page 1 of 7 (151 countries) Next / Last

RANKCOUNTRYNODES
1United States
15888 (30.14%)
2Germany
7275 (13.80%)
3Canada
2993 (5.68%)
4France
2044 (3.88%)
5United Kingdom
1846 (3.50%)
6Netherlands
1806 (3.43%)
7China
1484 (2.82%)
8Australia
1248 (2.37%)
9Russian Federation
1219 (2.31%)
10Switzerland
1202 (2.28%)
11Brazil
1169 (2.22%)
12Spain
1077 (2.04%)
13Italy
1050 (1.99%)
14Finland
899 (1.71%)
15Japan
824 (1.56%)
16Sweden
631 (1.20%)
17Korea (the Republic of)
592 (1.12%)
18Singapore
589 (1.12%)
19Austria
547 (1.04%)
20Czechia
487 (0.92%)
21Thailand
376 (0.71%)
22Hong Kong
372 (0.71%)
23Belgium
365 (0.69%)
24Poland
342 (0.65%)
25Ireland
331 (0.63%)

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