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


Global Bitcoin nodes by city

7113 cities with their respective number of global IPv4/IPv6 Bitcoin nodes as of Sat Feb 22 19:00:00 2025 EST.

Window size: 1-day

NODES64477
COUNTRIES141
CITIES7113
ASNS2390
SERVICES6
PORT NUMBERS244

Page 1 of 285 (7113 cities) Next / Last

RANKCITYNODES
1 n/a 7331 (14.79%)
2Germany Falkenstein
800 (1.61%)
3Germany Frankfurt am Main
757 (1.53%)
4Finland Helsinki
739 (1.49%)
5Singapore Singapore
511 (1.03%)
6United States Ashburn
494 (1.00%)
7Canada Toronto
487 (0.98%)
8The Netherlands Amsterdam
472 (0.95%)
9Germany Düsseldorf
452 (0.91%)
10Switzerland Zurich
440 (0.89%)
11Japan Tokyo
419 (0.85%)
12United Kingdom London
418 (0.84%)
13Germany Nuremberg
379 (0.76%)
14Germany Berlin
377 (0.76%)
15Australia Sydney
350 (0.71%)
16United States Los Angeles
297 (0.60%)
17United States Columbus
273 (0.55%)
18Ireland Dublin
269 (0.54%)
19Russia Moscow
263 (0.53%)
19United States Atlanta
263 (0.53%)
20Austria Vienna
251 (0.51%)
21United States New York
247 (0.50%)
22France Paris
240 (0.48%)
23United States Chicago
235 (0.47%)
24Canada Montreal
228 (0.46%)

Page 1 of 285 (7113 cities) 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.