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


Global Bitcoin nodes by city

7439 cities with their respective number of global IPv4/IPv6 Bitcoin nodes as of Sat Jun 21 03:00:00 2025 EEST.

Window size: 1-day

NODES65675
COUNTRIES153
CITIES7439
ASNS2442
SERVICES6
PORT NUMBERS265

Page 1 of 298 (7439 cities) Next / Last

RANKCITYNODES
1 n/a 4627 (9.22%)
2Germany Falkenstein
820 (1.63%)
3Finland Helsinki
726 (1.45%)
4Germany Frankfurt am Main
713 (1.42%)
5The Netherlands Amsterdam
532 (1.06%)
6United States Ashburn
516 (1.03%)
7Singapore Singapore
507 (1.01%)
8Canada Toronto
473 (0.94%)
9Switzerland Zurich
461 (0.92%)
10Australia Sydney
447 (0.89%)
11Germany Berlin
433 (0.86%)
12Japan Tokyo
380 (0.76%)
13Germany Nuremberg
371 (0.74%)
14United States Atlanta
320 (0.64%)
15United Kingdom London
316 (0.63%)
16Ireland Dublin
305 (0.61%)
16United States Los Angeles
305 (0.61%)
17Russia Moscow
303 (0.60%)
18Austria Vienna
273 (0.54%)
18United States Dallas
273 (0.54%)
19United States Chicago
259 (0.52%)
20Australia Melbourne
253 (0.50%)
20Germany Düsseldorf
253 (0.50%)
20United States New York
253 (0.50%)
21France Paris
251 (0.50%)

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