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 Sat Nov 1 20:00:00 2025 EDT.

Window size: 1-day

NODES67204
COUNTRIES157
CITIES7830
ASNS2431
SERVICES6
PORT NUMBERS295

Page 1 of 7 (157 countries) Next / Last

RANKCOUNTRYNODES
1United States
15254 (30.32%)
2Germany
6873 (13.66%)
3France
2331 (4.63%)
4Canada
2269 (4.51%)
5United Kingdom
1822 (3.62%)
6Netherlands
1696 (3.37%)
7China
1467 (2.92%)
8Australia
1340 (2.66%)
9Switzerland
1179 (2.34%)
10Spain
1111 (2.21%)
11Russian Federation
1106 (2.20%)
12Italy
1047 (2.08%)
13Brazil
941 (1.87%)
14Finland
862 (1.71%)
15Japan
721 (1.43%)
16Korea (the Republic of)
644 (1.28%)
17Sweden
576 (1.14%)
18Austria
559 (1.11%)
19Singapore
547 (1.09%)
20Czechia
486 (0.97%)
21Thailand
414 (0.82%)
22Belgium
371 (0.74%)
23Hong Kong
366 (0.73%)
24Portugal
361 (0.72%)
25Ireland
312 (0.62%)

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.