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


Global Bitcoin nodes by country

184 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Tue May 13 20:00:00 2025 EDT.

Window size: 90-day

NODES559735
COUNTRIES184
CITIES13449
ASNS3785
SERVICES6
PORT NUMBERS621

Page 1 of 8 (184 countries) Next / Last

RANKCOUNTRYNODES
1United States
122821 (22.92%)
2Germany
105409 (19.67%)
3China
38067 (7.11%)
4Brazil
19824 (3.70%)
5Canada
18239 (3.40%)
6Italy
17976 (3.36%)
7Russian Federation
17109 (3.19%)
8United Kingdom
16894 (3.15%)
9France
13777 (2.57%)
10Australia
11760 (2.19%)
11Netherlands
10768 (2.01%)
12Spain
10081 (1.88%)
13Thailand
8449 (1.58%)
14Switzerland
7993 (1.49%)
15Japan
6076 (1.13%)
16India
5597 (1.04%)
17Austria
5555 (1.04%)
18Mexico
5421 (1.01%)
19Portugal
4054 (0.76%)
20Poland
3689 (0.69%)
21Sweden
3585 (0.67%)
22Belgium
3184 (0.59%)
23Indonesia
3180 (0.59%)
24Finland
3149 (0.59%)
25Hong Kong
2922 (0.55%)

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