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

Total nodes n/a United States n/a AS14618 AMAZON-AES n/a

Global Bitcoin nodes by city

5911 cities with their respective number of reachable and unreachable IPv4/IPv6 Bitcoin nodes as of Wed Mar 29 20:00:00 2023 EDT.

Window size: 1-day


Page 1 of 119 (5911 cities) Next / Last

1n/a5522 (15.31%)
2Germany Frankfurt am Main684 (1.90%)
3United States Ashburn640 (1.77%)
4Finland Helsinki546 (1.51%)
5United Kingdom London526 (1.46%)
6Netherlands Amsterdam459 (1.27%)
7Japan Tokyo410 (1.14%)
8Russia Moscow369 (1.02%)
9Australia Sydney297 (0.82%)
10Switzerland Zurich284 (0.79%)
11Ireland Dublin277 (0.77%)
12Germany Berlin259 (0.72%)
13Germany Nuremberg253 (0.70%)
14Hong Kong Central249 (0.69%)
15United States Columbus248 (0.69%)
16Canada Toronto244 (0.68%)
17United States Boardman230 (0.64%)
18United States Los Angeles226 (0.63%)
19Canada Montreal203 (0.56%)
20France Paris193 (0.53%)
21United States New York190 (0.53%)
22United States San Jose187 (0.52%)
23United States Council Bluffs186 (0.52%)
23United States North Bergen186 (0.52%)
24United States Santa Clara172 (0.48%)
25United States Chicago168 (0.47%)
26United States Seattle166 (0.46%)
27Sweden Stockholm165 (0.46%)
28Brazil São Paulo158 (0.44%)
29Netherlands Naaldwijk154 (0.43%)
30United States Miami148 (0.41%)
31China Beijing146 (0.40%)
32Russia St Petersburg145 (0.40%)
33Germany Gunzenhausen143 (0.40%)
34Czechia Prague142 (0.39%)
35Austria Vienna139 (0.39%)
35Belgium Brussels139 (0.39%)
36Germany Munich138 (0.38%)
37Germany Brandenburg134 (0.37%)
38United States Dallas121 (0.34%)
39China Shenzhen119 (0.33%)
40Germany Düsseldorf115 (0.32%)
40United States Austin115 (0.32%)
41China Tianjin114 (0.32%)
42Australia Melbourne111 (0.31%)
43Spain Madrid110 (0.30%)
43Thailand Bangkok110 (0.30%)
44South Korea Incheon108 (0.30%)
45Poland Warsaw103 (0.29%)
46Australia Brisbane102 (0.28%)

Page 1 of 119 (5911 cities) Next / Last

This page reports the estimated size of the Bitcoin peer-to-peer network including both reachable and unreachable 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.