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

1d7d30d90d

Global Bitcoin nodes by port number

269 port numbers with their respective number of global Bitcoin nodes as of Fri Jun 20 03:00:00 2025 EEST.

Window size: 1-day

NODES65682
COUNTRIES153
CITIES7438
ASNS2434
SERVICES6
PORT NUMBERS269

Page 1 of 11 (269 port numbers) Next / Last

RANKPORT NUMBERNODES
18333
62818 (95.64%)
239388
1880 (2.86%)
38332
134 (0.20%)
412333
54 (0.08%)
58303
52 (0.08%)
58335
52 (0.08%)
68334
39 (0.06%)
79333
36 (0.05%)
718333
36 (0.05%)
87335
22 (0.03%)
88433
22 (0.03%)
920008
16 (0.02%)
1010001
15 (0.02%)
118331
14 (0.02%)
128330
12 (0.02%)
1331270
11 (0.02%)
147333
10 (0.02%)
148336
10 (0.02%)
1550001
9 (0.01%)
168343
8 (0.01%)
1630268
8 (0.01%)
1648332
8 (0.01%)
178444
7 (0.01%)
1711333
7 (0.01%)
1718332
7 (0.01%)

Page 1 of 11 (269 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.