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


Global Bitcoin nodes by country

157 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Tue May 13 19:00:00 2025 CDT.

Window size: 7-day

NODES123296
COUNTRIES157
CITIES8962
ASNS2709
SERVICES6
PORT NUMBERS336

Page 1 of 7 (157 countries) Next / Last

RANKCOUNTRYNODES
1United States
28194 (26.52%)
2Germany
16619 (15.63%)
3China
5304 (4.99%)
4Canada
4497 (4.23%)
5France
3725 (3.50%)
6United Kingdom
3686 (3.47%)
7Netherlands
3121 (2.94%)
8Russian Federation
3040 (2.86%)
9Brazil
2935 (2.76%)
10Italy
2643 (2.49%)
11Australia
2415 (2.27%)
12Switzerland
2125 (2.00%)
13Spain
2070 (1.95%)
14Japan
1465 (1.38%)
15Austria
1308 (1.23%)
16Thailand
1151 (1.08%)
17Sweden
1111 (1.04%)
18Finland
1106 (1.04%)
19Portugal
1094 (1.03%)
20India
898 (0.84%)
21Singapore
894 (0.84%)
22Mexico
883 (0.83%)
23Hong Kong
872 (0.82%)
24Czechia
753 (0.71%)
25Belgium
743 (0.70%)

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