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


Global Bitcoin nodes by country

170 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Fri Jun 20 03:00:00 2025 EEST.

Window size: 30-day

NODES279144
COUNTRIES170
CITIES10986
ASNS2980
SERVICES6
PORT NUMBERS461

Page 1 of 7 (170 countries) Next / Last

RANKCOUNTRYNODES
1United States
63067 (24.35%)
2Germany
45809 (17.69%)
3China
16831 (6.50%)
4Canada
9631 (3.72%)
5United Kingdom
9034 (3.49%)
6Italy
8609 (3.32%)
7Brazil
8211 (3.17%)
8France
7370 (2.85%)
9Russian Federation
7257 (2.80%)
10Australia
6784 (2.62%)
11Netherlands
6257 (2.42%)
12Spain
4399 (1.70%)
13Switzerland
4216 (1.63%)
14Thailand
3555 (1.37%)
15India
3096 (1.20%)
15Japan
3096 (1.20%)
16Austria
2755 (1.06%)
17Mexico
2481 (0.96%)
18Portugal
2210 (0.85%)
19Sweden
2108 (0.81%)
20Hong Kong
1857 (0.72%)
21Belgium
1747 (0.67%)
22Finland
1743 (0.67%)
23Singapore
1706 (0.66%)
24Czechia
1649 (0.64%)

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