Network Snapshot
Snapshot of reachable Bitcoin nodes as of Sat May 10 00:41:31 2025 EDT.
Previous snapshot /
Next snapshot /
JSON API
21556
Nodes
6247
IPv4 @ 28.98%
1232
IPv6 @ 5.72%
14077
.onion @ 65.30%
19754
Full nodes @ 91.64%
1791
Pruned nodes @ 8.31%
+64/-676
Churn
896059
Height
Top 10 user agents with their respective number of reachable nodes.
| RANK | USER AGENT | NODES |
|---|---|---|
| 1 | Satoshi:28.1.0 | 6035 (28.00%) |
| 2 | Satoshi:27.1.0 | 2645 (12.27%) |
| 3 | Satoshi:26.0.0 | 2618 (12.15%) |
| 4 | Satoshi:28.0.0 | 2139 (9.92%) |
| 5 | Satoshi:27.0.0 | 1635 (7.58%) |
| 6 | Satoshi:29.0.0 | 1468 (6.81%) |
| 7 | Satoshi:25.0.0 | 1148 (5.33%) |
| 8 | Satoshi:25.1.0 | 842 (3.91%) |
| 9 | Satoshi:22.0.0 | 636 (2.95%) |
| 10 | Satoshi:24.0.1 | 471 (2.19%) |
| All (86) | ||
Top 10 countries with their respective number of reachable nodes.
| RANK | COUNTRY | NODES |
|---|---|---|
| 1 | n/a | 14078 (65.31%) |
| 2 | United States | 2216 (10.28%) |
| 3 | Germany | 1198 (5.56%) |
| 4 | France | 570 (2.64%) |
| 5 | Canada | 371 (1.72%) |
| 6 | Finland | 354 (1.64%) |
| 7 | Netherlands | 335 (1.55%) |
| 8 | United Kingdom | 271 (1.26%) |
| 9 | Switzerland | 214 (0.99%) |
| 10 | Russian Federation | 195 (0.90%) |
| All (94) | ||
Top 10 networks with their respective number of reachable nodes.
| RANK | NETWORK | NODES |
|---|---|---|
| 1 | Tor network (TOR) | 14077 (65.30%) |
| 2 | Hetzner Online GmbH (AS24940) | 821 (3.81%) |
| 3 | OVH SAS (AS16276) | 438 (2.03%) |
| 4 | COMCAST-7922 (AS7922) | 325 (1.51%) |
| 5 | AMAZON-02 (AS16509) | 222 (1.03%) |
| 6 | DIGITALOCEAN-ASN (AS14061) | 212 (0.98%) |
| 7 | ATT-INTERNET4 (AS7018) | 196 (0.91%) |
| 8 | Contabo GmbH (AS51167) | 163 (0.76%) |
| 9 | UUNET (AS701) | 150 (0.70%) |
| 10 | Deutsche Telekom AG (AS3320) | 136 (0.63%) |
| All (1106) | ||
| NODE | ADDRESS | USER AGENT | HEIGHT | LOCATION | NETWORK |
|---|---|---|---|---|---|
| 95.191.130.100:8333 Since 1 month, 2 weeks ago /Satoshi:0.21.1/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) 896058 Tomsk, Russian Federation Asia/Tomsk Rostelecom (AS12389) | 95.191.130.100:8333 Since 1 month, 2 weeks ago | /Satoshi:0.21.1/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) | 896058 | Tomsk, Russian Federation Asia/Tomsk | Rostelecom (AS12389) |
| 109.184.254.244:8333 109-184-254-244.dynamic.mts-nn.ru Since 2 weeks, 1 day ago /Satoshi:27.1.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 896059 Nizhniy Novgorod, Russian Federation Europe/Moscow Rostelecom (AS12389) | 109.184.254.244:8333 109-184-254-244.dynamic.mts-nn.ru Since 2 weeks, 1 day ago | /Satoshi:27.1.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 896059 | Nizhniy Novgorod, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 178.70.129.37:8333 Since 1 week, 3 days ago /Satoshi:25.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) 896059 St Petersburg, Russian Federation Europe/Moscow Rostelecom (AS12389) | 178.70.129.37:8333 Since 1 week, 3 days ago | /Satoshi:25.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED (1033) | 896059 | St Petersburg, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 109.172.13.218:8333 Since 6 days, 20 hours ago /Satoshi:28.1.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 896059 Russian Federation Europe/Moscow Rostelecom (AS12389) | 109.172.13.218:8333 Since 6 days, 20 hours ago | /Satoshi:28.1.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 896059 | Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 95.167.180.230:8333 Since 4 days, 16 hours ago /Satoshi:28.1.0/ NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) 896059 Kyzyl, Russian Federation Asia/Krasnoyarsk Rostelecom (AS12389) | 95.167.180.230:8333 Since 4 days, 16 hours ago | /Satoshi:28.1.0/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) | 896059 | Kyzyl, Russian Federation Asia/Krasnoyarsk | Rostelecom (AS12389) |
| 83.171.72.203:8333 Since 4 days, 6 hours ago /Satoshi:28.1.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 896059 Russian Federation Europe/Moscow Rostelecom (AS12389) | 83.171.72.203:8333 Since 4 days, 6 hours ago | /Satoshi:28.1.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 896059 | Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 94.28.204.134:8333 node-134-204-28-94.domolink.tula.net Since 2 days, 18 hours ago /Satoshi:28.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 896059 Tula, Russian Federation Europe/Moscow Rostelecom (AS12389) | 94.28.204.134:8333 node-134-204-28-94.domolink.tula.net Since 2 days, 18 hours ago | /Satoshi:28.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 896059 | Tula, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 90.188.248.101:8333 Since 2 days, 13 hours ago /Satoshi:29.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_COMPACT_FILTERS, NODE_P2P_V2 (3145) 896059 Irkutsk, Russian Federation Asia/Irkutsk Rostelecom (AS12389) | 90.188.248.101:8333 Since 2 days, 13 hours ago | /Satoshi:29.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_COMPACT_FILTERS, NODE_P2P_V2 (3145) | 896059 | Irkutsk, Russian Federation Asia/Irkutsk | Rostelecom (AS12389) |
| 90.189.194.61:8333 Since 2 days, 10 hours ago /Satoshi:24.0.1/ NODE_WITNESS, NODE_NETWORK_LIMITED (1032) 896059 Novosibirsk, Russian Federation Asia/Novosibirsk Rostelecom (AS12389) | 90.189.194.61:8333 Since 2 days, 10 hours ago | /Satoshi:24.0.1/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED (1032) | 896059 | Novosibirsk, Russian Federation Asia/Novosibirsk | Rostelecom (AS12389) |
| 91.122.105.234:8333 Since 2 days, 1 hour ago /Satoshi:26.99.0/ NODE_WITNESS, NODE_NETWORK_LIMITED (1032) 896057 St Petersburg, Russian Federation Europe/Moscow Rostelecom (AS12389) | 91.122.105.234:8333 Since 2 days, 1 hour ago | /Satoshi:26.99.0/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED (1032) | 896057 | St Petersburg, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 95.55.22.3:8333 Since 1 day, 12 hours ago /Satoshi:28.99.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 896059 St Petersburg, Russian Federation Europe/Moscow Rostelecom (AS12389) | 95.55.22.3:8333 Since 1 day, 12 hours ago | /Satoshi:28.99.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 896059 | St Petersburg, Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 77.34.3.65:8333 Since 20 hours ago /Satoshi:29.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 896059 Russian Federation Europe/Moscow Rostelecom (AS12389) | 77.34.3.65:8333 Since 20 hours ago | /Satoshi:29.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 896059 | Russian Federation Europe/Moscow | Rostelecom (AS12389) |
| 90.188.112.251:8333 Since 19 hours ago /Satoshi:27.0.0/ NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) 896058 Tomsk, Russian Federation Asia/Tomsk Rostelecom (AS12389) | 90.188.112.251:8333 Since 19 hours ago | /Satoshi:27.0.0/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) | 896058 | Tomsk, Russian Federation Asia/Tomsk | Rostelecom (AS12389) |
| 37.79.255.74:8333 Since 19 hours ago /Satoshi:28.1.0/ NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) 896059 Perm, Russian Federation Asia/Yekaterinburg Rostelecom (AS12389) | 37.79.255.74:8333 Since 19 hours ago | /Satoshi:28.1.0/ (70016) NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3080) | 896059 | Perm, Russian Federation Asia/Yekaterinburg | Rostelecom (AS12389) |
| 37.21.27.64:8333 Since 17 hours ago /Satoshi:27.0.0/ NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) 896059 Tomsk, Russian Federation Asia/Tomsk Rostelecom (AS12389) | 37.21.27.64:8333 Since 17 hours ago | /Satoshi:27.0.0/ (70016) NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, NODE_P2P_V2 (3081) | 896059 | Tomsk, Russian Federation Asia/Tomsk | Rostelecom (AS12389) |
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.