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


Global Bitcoin nodes by country

180 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Thu Dec 5 19:00:00 2024 EST.

Window size: 90-day

NODES487350
COUNTRIES180
CITIES12730
ASNS3278
SERVICES6
PORT NUMBERS530

Page 1 of 8 (180 countries) Next / Last

RANKCOUNTRYNODES
1United States
105328 (22.60%)
2Germany
85320 (18.31%)
3China
34346 (7.37%)
4Brazil
18429 (3.95%)
5Russian Federation
18271 (3.92%)
6United Kingdom
15150 (3.25%)
7Italy
14857 (3.19%)
8Canada
14290 (3.07%)
9France
11927 (2.56%)
10Australia
9911 (2.13%)
11Netherlands
9073 (1.95%)
12Spain
7820 (1.68%)
13Switzerland
7666 (1.65%)
14Thailand
7017 (1.51%)
15Japan
6229 (1.34%)
16India
4871 (1.05%)
17Mexico
4822 (1.03%)
18Austria
4317 (0.93%)
19Singapore
3666 (0.79%)
20Indonesia
3638 (0.78%)
21Sweden
3139 (0.67%)
22Poland
3070 (0.66%)
23Belgium
3057 (0.66%)
24Finland
2991 (0.64%)
25Hong Kong
2890 (0.62%)

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