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


Global Bitcoin nodes by country

165 countries with their respective number of global IPv4/IPv6 Bitcoin nodes as of Fri Sep 5 20:00:00 2025 EDT.

Window size: 7-day

NODES127670
COUNTRIES165
CITIES9430
ASNS2766
SERVICES6
PORT NUMBERS337

First / Prev Page 4 of 7 (165 countries) Next / Last

RANKCOUNTRYNODES
74Nigeria
52 (0.05%)
74Zimbabwe
52 (0.05%)
75Malta
51 (0.05%)
75Peru
51 (0.05%)
76Georgia
50 (0.05%)
77Morocco
49 (0.05%)
78Paraguay
48 (0.04%)
79Bolivia
45 (0.04%)
79Algeria
45 (0.04%)
80Cyprus
44 (0.04%)
81Greenland
41 (0.04%)
81Guatemala
41 (0.04%)
81Liechtenstein
41 (0.04%)
82Bosnia and Herzegovina
38 (0.03%)
82Uzbekistan
38 (0.03%)
83 n/a 36 (0.03%)
83Panama
36 (0.03%)
84Qatar
31 (0.03%)
85Armenia
30 (0.03%)
85Guam
30 (0.03%)
85Isle of Man
30 (0.03%)
85North Macedonia
30 (0.03%)
86Myanmar
29 (0.03%)
86Nepal
29 (0.03%)
87Jamaica
28 (0.03%)

First / Prev Page 4 of 7 (165 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.