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


Global Bitcoin nodes by country

154 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Wed May 28 20:00:00 2025 EDT.

Window size: 1-day

NODES65199
COUNTRIES154
CITIES7507
ASNS2450
SERVICES6
PORT NUMBERS257

Page 1 of 7 (154 countries) Next / Last

RANKCOUNTRYNODES
1United States
14672 (29.32%)
2Germany
6755 (13.50%)
3Canada
2721 (5.44%)
4United Kingdom
2000 (4.00%)
5France
1996 (3.99%)
6Netherlands
1725 (3.45%)
7China
1543 (3.08%)
8Russian Federation
1259 (2.52%)
9Australia
1173 (2.34%)
10Switzerland
1154 (2.31%)
11Brazil
1126 (2.25%)
12Italy
1056 (2.11%)
13Spain
1036 (2.07%)
14Finland
849 (1.70%)
15Japan
755 (1.51%)
16Sweden
653 (1.30%)
17Singapore
552 (1.10%)
18Korea (the Republic of)
536 (1.07%)
19Austria
508 (1.02%)
20Czechia
485 (0.97%)
21Portugal
394 (0.79%)
22Hong Kong
369 (0.74%)
23Belgium
357 (0.71%)
24Poland
347 (0.69%)
25Ireland
336 (0.67%)

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