Own data · network crawler

Bitcoin nodes worldwide

We currently reach 14,527 Bitcoin nodes across 94 countries, most of them in the United States (20%). Every dot on the map is a computer that checks every block against Bitcoin's rules itself. The numbers come from our own network crawler.

Reachable nodes
14,527
59% of known hosts
Countries
94
Top: US 20%
Clearnet
7,082
49% · IPv4
Tor
7,445
51% of all nodes

Live world map

Every dot is a reachable node at its approximate location (from the IP address). The lines are illustrative: they show the network's global interconnection, not specific links. Which node talks to which is not publicly available.

Loading nodes…
scroll/buttons = zoom · drag = pan · click = IP

Dots = reachable nodes · lines = illustrative. The map shows the 7,082 clearnet nodes (IPv4); the 7,445 Tor nodes are counted but have no location and cannot be mapped.

By country

US · United States
2,930
20.2 %
DE · Germany
788
5.4 %
GB · United Kingdom
326
2.2 %
CA · Canada
326
2.2 %
FR · France
250
1.7 %
NL · Netherlands
222
1.5 %
CH · Switzerland
150
1.0 %
AU · Australia
146
1.0 %
RU · Russia
138
0.9 %
KR · South Korea
109
0.8 %
ES · Spain
101
0.7 %
SE · Sweden
90
0.6 %

Client versions

Core 32
3,201
22.0 %
Core 31
3,445
23.7 %
Core 30
782
5.4 %
Core 29
1,793
12.3 %
Core 28
1,138
7.8 %
Core ≤27
2,245
15.5 %
Knots
1,922
13.2 %
Other
56
0.4 %

Counted by major release. Knots announces itself as "Satoshi:…/Knots:…" and all its builds share one bar; Core builds with a suffix count to their release, pre-releases to other.

▸ Top 25 exact user agents
Core 32.1.0
3,041
20.9 %
Core 31.1.0
1,758
12.1 %
Core 31.2.0
787
5.4 %
Core 31.0.0
764
5.3 %
Knots 20260507 (Core 29.3.0)
608
4.2 %
Core 28.1.0
507
3.5 %
Core 29.2.0
499
3.4 %
Core 26.0.0
389
2.7 %
Core 29.0.0
388
2.7 %
Core 30.2.0
356
2.5 %
Core 28.1.0(FutureBit-Apollo-Node)
338
2.3 %
Core 25.1.0
335
2.3 %
Core 29.3.0
307
2.1 %
Core 30.0.0
293
2.0 %
Core 25.0.0
292
2.0 %
Core 27.0.0
278
1.9 %
Knots 20260508 (Core 29.5.0)
271
1.9 %
Core 29.5.0
253
1.7 %
Core 27.1.0
251
1.7 %
Core 28.0.0
207
1.4 %
Knots 20260508 (Core 29.4.3)
188
1.3 %
Knots 20260508 (Core 29.4.0)
142
1.0 %
Core 29.4.0
123
0.8 %
Core 29.1.0
110
0.8 %
Knots 20260210 (Core 29.3.0)
102
0.7 %

Over time

Reachable nodes per crawl cycle

13,34313,97314,60411/1611/17

Node explorer

Every reachable node, searchable by IP, client version or city.

NodeCountryVersionTypeLast
0 nodes
1 / 1

Methodology & data

Our crawler walks the Bitcoin P2P network via protocol handshakes and getaddr requests (continuously, one cycle after another). Clearnet nodes (IPv4) are geolocated offline; we reach Tor nodes (.onion) through a Tor proxy and count them as well. They have no geographic location, though, so they do not appear on the map. We count only publicly reachable (listening) nodes; nodes behind NAT/firewall cannot be counted directly. The crawler does not currently cover IPv6 nodes, because our server has no IPv6 connectivity; nodes reachable only over IPv6 are therefore missing from the count. Locations are IP-based and approximate. Last updated: Nov 17, 2026, 12:46 PM.

Frequently asked questions

01What is a Bitcoin node?

A node is a computer that holds the full Bitcoin blockchain and independently checks every transaction and block against the consensus rules. The more nodes there are, the less the network depends on individual operators and the harder it is to censor.

02How many Bitcoin nodes are there?

We currently reach 14,527 nodes across 94 countries. These are the publicly reachable (listening) nodes. The true total is higher, because many nodes behind firewalls accept no inbound connections and so cannot be counted directly. The crawler does not currently cover IPv6 nodes, because our server has no IPv6 connectivity; nodes reachable only over IPv6 are therefore missing from the count.

03Where does the data come from?

It comes from our own crawler, which walks the Bitcoin P2P network the way Bitnodes used to: it connects to nodes, asks them over the protocol for their known peers and works through the entire reachable network. It runs continuously: each cycle starts shortly after the previous one ends.

04What does "reachable" mean?

A node counts as reachable when our crawler could complete a full protocol handshake. Nodes that only make outbound connections (behind NAT/firewall) are not counted.

05Are Tor nodes included?

Yes. We reach Tor nodes (.onion) through a Tor proxy and count them. They are often the majority of reachable nodes. But by design they have no geographic location, so they appear only in the totals and the network-type figures, not on the map. I2P/CJDNS nodes are not covered yet.