Network Snapshot
Snapshot of reachable Bitcoin nodes as of Mon Sep 15 22:29:10 2025 EDT.
Previous snapshot /
Next snapshot /
JSON API
16056
Nodes
5457
IPv4 @ 33.99%
1113
IPv6 @ 6.93%
9486
.onion @ 59.08%
14452
Full nodes @ 90.01%
1603
Pruned nodes @ 9.98%
+329/-10168
Churn
914888
Height
Top 10 user agents with their respective number of reachable nodes.
| RANK | USER AGENT | NODES |
|---|---|---|
| 1 | Satoshi:28.1.0 | 4418 (27.52%) |
| 2 | Satoshi:29.0.0 | 3046 (18.97%) |
| 3 | Satoshi:29.1.0 | 2064 (12.86%) |
| 4 | Satoshi:26.0.0 | 1430 (8.91%) |
| 5 | Satoshi:27.1.0 | 896 (5.58%) |
| 6 | Satoshi:27.0.0 | 737 (4.59%) |
| 7 | Satoshi:28.0.0 | 713 (4.44%) |
| 8 | Satoshi:25.0.0 | 554 (3.45%) |
| 9 | Satoshi:25.1.0 | 455 (2.83%) |
| 10 | Satoshi:22.0.0 | 308 (1.92%) |
| All (83) | ||
Top 10 countries with their respective number of reachable nodes.
| RANK | COUNTRY | NODES |
|---|---|---|
| 1 | n/a | 9486 (59.08%) |
| 2 | United States | 1817 (11.32%) |
| 3 | Germany | 1105 (6.88%) |
| 4 | France | 506 (3.15%) |
| 5 | Finland | 301 (1.87%) |
| 6 | Canada | 292 (1.82%) |
| 7 | Netherlands | 268 (1.67%) |
| 8 | United Kingdom | 242 (1.51%) |
| 9 | Switzerland | 180 (1.12%) |
| 10 | Russian Federation | 164 (1.02%) |
| All (97) | ||
Top 10 networks with their respective number of reachable nodes.
| RANK | NETWORK | NODES |
|---|---|---|
| 1 | Tor network (TOR) | 9486 (59.08%) |
| 2 | Hetzner Online GmbH (AS24940) | 673 (4.19%) |
| 3 | OVH SAS (AS16276) | 374 (2.33%) |
| 4 | COMCAST-7922 (AS7922) | 243 (1.51%) |
| 5 | DIGITALOCEAN-ASN (AS14061) | 169 (1.05%) |
| 6 | AMAZON-02 (AS16509) | 165 (1.03%) |
| 7 | Contabo GmbH (AS51167) | 162 (1.01%) |
| 8 | ATT-INTERNET4 (AS7018) | 160 (1.00%) |
| 9 | Deutsche Telekom AG (AS3320) | 154 (0.96%) |
| 10 | UUNET (AS701) | 132 (0.82%) |
| All (1031) | ||
Page 1 of 1 (15 nodes/0.09%)
| NODE | ADDRESS | USER AGENT | HEIGHT | LOCATION | NETWORK |
|---|---|---|---|---|---|
| 95.167.180.230:8333 Since 21 hours ago /Satoshi:28.1.0/ NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) 914888 Belgorod, Russian Federation Europe/Moscow Rostelecom (AS12389) | 95.167.180.230:8333 Since 21 hours ago | /Satoshi:28.1.0/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) | 914888 | Belgorod, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 188.17.228.207:8435 Since 21 hours ago /Satoshi:28.1.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 914888 Chelyabinsk, Russian Federation Asia/Yekaterinburg Rostelecom (AS12389) | 188.17.228.207:8435 Since 21 hours ago | /Satoshi:28.1.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 914888 | Chelyabinsk, Russian Federation Asia/Yekaterinburg | Rostelecom (AS12389) |
| 90.189.194.61:8333 Since 21 hours ago /Satoshi:24.0.1/ NODE_WITNESS, NODE_NETWORK_LIMITED (1032) 914888 Novosibirsk, Russian Federation Asia/Novosibirsk Rostelecom (AS12389) | 90.189.194.61:8333 Since 21 hours ago | /Satoshi:24.0.1/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED (1032) | 914888 | Novosibirsk, Russian Federation Asia/Novosibirsk | Rostelecom (AS12389) |
| 178.71.171.78:8333 Since 21 hours ago /Satoshi:25.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) 914888 St Petersburg, Russian Federation Europe/Moscow Rostelecom (AS12389) | 178.71.171.78:8333 Since 21 hours ago | /Satoshi:25.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) | 914888 | St Petersburg, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 77.35.199.152:8333 Since 21 hours ago /Satoshi:22.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) 914888 Vladivostok, Russian Federation Asia/Vladivostok Rostelecom (AS12389) | 77.35.199.152:8333 Since 21 hours ago | /Satoshi:22.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) | 914888 | Vladivostok, Russian Federation Asia/Vladivostok | Rostelecom (AS12389) |
| 92.100.38.142:8333 Since 21 hours ago /Satoshi:25.1.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) 914888 St Petersburg, Russian Federation Europe/Moscow Rostelecom (AS12389) | 92.100.38.142:8333 Since 21 hours ago | /Satoshi:25.1.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) | 914888 | St Petersburg, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 188.19.101.110:8333 Since 21 hours ago /Satoshi:28.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 914888 Perm, Russian Federation Asia/Yekaterinburg Rostelecom (AS12389) | 188.19.101.110:8333 Since 21 hours ago | /Satoshi:28.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 914888 | Perm, Russian Federation Asia/Yekaterinburg | Rostelecom (AS12389) |
| 90.188.248.101:8333 Since 21 hours ago /Satoshi:29.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_COMPACT_FILTERS, NODE_P2P_V2 (3145) 914888 Irkutsk, Russian Federation Asia/Irkutsk Rostelecom (AS12389) | 90.188.248.101:8333 Since 21 hours ago | /Satoshi:29.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_COMPACT_FILTERS, NODE_P2P_V2 (3145) | 914888 | Irkutsk, Russian Federation Asia/Irkutsk | Rostelecom (AS12389) |
| 91.122.105.234:8333 Since 21 hours ago /Satoshi:28.1.0/ NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) 914888 Glazhevo, Russian Federation Europe/Moscow Rostelecom (AS12389) | 91.122.105.234:8333 Since 21 hours ago | /Satoshi:28.1.0/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) | 914888 | Glazhevo, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 178.35.2.126:8333 Since 21 hours ago /Satoshi:29.1.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_COMPACT_FILTERS, NODE_P2P_V2 (3145) 914888 Vladikavkaz, Russian Federation Europe/Moscow Rostelecom (AS12389) | 178.35.2.126:8333 Since 21 hours ago | /Satoshi:29.1.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_COMPACT_FILTERS, NODE_P2P_V2 (3145) | 914888 | Vladikavkaz, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 90.188.251.32:8333 Since 21 hours ago /Satoshi:0.19.1/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) 914888 Irkutsk, Russian Federation Asia/Irkutsk Rostelecom (AS12389) | 90.188.251.32:8333 Since 21 hours ago | /Satoshi:0.19.1/ (70015) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) | 914888 | Irkutsk, Russian Federation Asia/Irkutsk | Rostelecom (AS12389) |
| 77.34.3.65:8333 Since 21 hours ago /Satoshi:29.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 914888 Vladivostok, Russian Federation Asia/Vladivostok Rostelecom (AS12389) | 77.34.3.65:8333 Since 21 hours ago | /Satoshi:29.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 914888 | Vladivostok, Russian Federation Asia/Vladivostok | Rostelecom (AS12389) |
| 90.189.119.69:8333 mail.reflix.ru Since 21 hours ago /Satoshi:28.1.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 914888 Abakan, Russian Federation Asia/Krasnoyarsk Rostelecom (AS12389) | 90.189.119.69:8333 mail.reflix.ru Since 21 hours ago | /Satoshi:28.1.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 914888 | Abakan, Russian Federation Asia/Krasnoyarsk | Rostelecom (AS12389) |
| 77.35.8.78:8333 Since 21 hours ago /Satoshi:29.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 914888 Vladivostok, Russian Federation Asia/Vladivostok Rostelecom (AS12389) | 77.35.8.78:8333 Since 21 hours ago | /Satoshi:29.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 914888 | Vladivostok, Russian Federation Asia/Vladivostok | Rostelecom (AS12389) |
| 37.21.207.78:8333 Since 21 hours ago /Satoshi:27.0.0/ NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) 914888 Krasnoyarka, Russian Federation Asia/Tomsk Rostelecom (AS12389) | 37.21.207.78:8333 Since 21 hours ago | /Satoshi:27.0.0/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) | 914888 | Krasnoyarka, Russian Federation Asia/Tomsk | Rostelecom (AS12389) |
Page 1 of 1 (15 nodes/0.09%)
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.