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 Sep 3 20:00:00 2025 EDT.

Window size: 1-day

NODES67852
COUNTRIES154
CITIES7780
ASNS2489
SERVICES6
PORT NUMBERS285

Page 1 of 7 (154 countries) Next / Last

RANKCOUNTRYNODES
1United States
15371 (30.03%)
2Germany
7049 (13.77%)
3Canada
2246 (4.39%)
4France
2104 (4.11%)
5United Kingdom
1811 (3.54%)
6Netherlands
1810 (3.54%)
7China
1457 (2.85%)
8Australia
1305 (2.55%)
9Russian Federation
1289 (2.52%)
10Switzerland
1221 (2.39%)
11Brazil
1092 (2.13%)
12Italy
1055 (2.06%)
13Spain
1001 (1.96%)
14Finland
903 (1.76%)
15Japan
719 (1.40%)
16Sweden
630 (1.23%)
17Korea (the Republic of)
603 (1.18%)
18Austria
575 (1.12%)
19Singapore
554 (1.08%)
20Czechia
477 (0.93%)
21Hong Kong
376 (0.73%)
22Thailand
368 (0.72%)
23Belgium
359 (0.70%)
24Portugal
352 (0.69%)
25Poland
336 (0.66%)

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.