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


Global Bitcoin nodes by port number

659 port numbers with their respective number of global Bitcoin nodes as of Tue Oct 21 20:00:00 2025 EDT.

Window size: 90-day

NODES665657
COUNTRIES192
CITIES14098
ASNS3353
SERVICES6
PORT NUMBERS659

Page 1 of 27 (659 port numbers) Next / Last

RANKPORT NUMBERNODES
18333
636426 (95.61%)
29333
17886 (2.69%)
339388
4618 (0.69%)
48335
850 (0.13%)
58332
763 (0.11%)
68555
677 (0.10%)
78334
583 (0.09%)
87335
289 (0.04%)
912333
214 (0.03%)
1018333
162 (0.02%)
1058976
162 (0.02%)
1124081
147 (0.02%)
1242069
141 (0.02%)
135119
114 (0.02%)
148331
93 (0.01%)
158303
87 (0.01%)
168338
85 (0.01%)
178433
73 (0.01%)
188330
58 (0.01%)
1920008
57 (0.01%)
1938333
57 (0.01%)
208340
52 (0.01%)
2125502
47 (0.01%)
2250912
45 (0.01%)
238833
43 (0.01%)

Page 1 of 27 (659 port numbers) 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.