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

456 port numbers with their respective number of global Bitcoin nodes as of Sun Apr 27 20:00:00 2025 EDT.

Window size: 30-day

NODES249935
COUNTRIES165
CITIES10607
ASNS2947
SERVICES6
PORT NUMBERS456

Page 1 of 19 (456 port numbers) Next / Last

RANKPORT NUMBERNODES
18333
244690 (97.90%)
239388
2708 (1.08%)
38335
253 (0.10%)
48332
252 (0.10%)
512333
201 (0.08%)
69333
172 (0.07%)
78334
147 (0.06%)
818333
67 (0.03%)
98331
66 (0.03%)
108303
62 (0.02%)
1024081
62 (0.02%)
1158976
55 (0.02%)
128433
39 (0.02%)
1320008
38 (0.02%)
148337
34 (0.01%)
158330
31 (0.01%)
1660938
30 (0.01%)
178444
28 (0.01%)
188555
27 (0.01%)
188833
27 (0.01%)
1810001
27 (0.01%)
198343
26 (0.01%)
208338
20 (0.01%)
218033
19 (0.01%)
228336
16 (0.01%)

Page 1 of 19 (456 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.