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


Global Bitcoin nodes by country

175 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Mon Jan 20 19:00:00 2025 EST.

Window size: 90-day

NODES514198
COUNTRIES175
CITIES13288
ASNS3202
SERVICES6
PORT NUMBERS542

Page 1 of 7 (175 countries) Next / Last

RANKCOUNTRYNODES
1United States
107821 (21.93%)
2Germany
91339 (18.58%)
3China
41825 (8.51%)
4Brazil
19844 (4.04%)
5Russian Federation
18628 (3.79%)
6United Kingdom
16575 (3.37%)
7Canada
15977 (3.25%)
8Italy
14620 (2.97%)
9France
12504 (2.54%)
10Australia
10055 (2.04%)
11Netherlands
9505 (1.93%)
12Spain
8853 (1.80%)
13Switzerland
7951 (1.62%)
14Thailand
7668 (1.56%)
15Japan
6288 (1.28%)
16India
4915 (1.00%)
17Mexico
4587 (0.93%)
18Austria
4351 (0.88%)
19Poland
3448 (0.70%)
20Indonesia
3405 (0.69%)
21Singapore
3152 (0.64%)
22Sweden
3108 (0.63%)
23Portugal
3088 (0.63%)
24Belgium
3059 (0.62%)
25Hong Kong
2982 (0.61%)

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