Public RPC
Last scan:
3 days ago
| # | Endpoint * | Height | Moniker | VP | Indexer | Version | Country | Provider |
|---|---|---|---|---|---|---|---|---|
| 1 | 93.189.30.120:26657 | 0 - 29,272,378 | dankuzone_rpc | 0 | on | v25.2.0 | 🇦🇹 Austria | IPAX GmbH |
| 2 | 40.160.**.***:***** | 0 - 29,272,380 | infstones | 436.58K | on | v25.2.0 | 🇺🇸 United States | OVH SAS |
| 3 | 37.120.245.41:26657 | 0 - 29,272,392 | sentry | 0 | on | v25.2.0 | 🇷🇴 Romania | M247 Europe SRL |
| 4 | 67.213.***.***:***** | 0 - 29,272,407 | DELIGHT | 2.42K | on | v25.2.0 | 🇺🇸 United States | Latitude.sh |
| 5 | 65.108.23.183:29657 | 0 - 29,272,424 | cryptonode.tool... | 0 | on | HEAD-6e74cf647f60ef59f4dfade16bd41ff890539fb0 | 🇫🇮 Finland | Hetzner Online GmbH |
| 6 | 188.214.130.113:26657 | 0 - 29,272,428 | range-cosmos-ma... | 0 | on | v25.2.0 | 🇱🇹 Lithuania | UAB Cherry Servers |
| 7 | 65.108.197.163:29657 | 0 - 29,272,439 | n0ok | 0 | on | v25.2.0 | 🇫🇮 Finland | Hetzner Online GmbH |
| 8 | 88.198.**.***:***** | 24,365,999 - 29,272,371 | colossus-node5 | 519.41K | on | v25.2.0 | 🇩🇪 Germany | Hetzner Online GmbH |
| 9 | 54.177.181.170:26657 | 25,290,001 - 29,272,394 | aws-nc-atom1 | 0 | on | v25.2.0 | 🇺🇸 United States | Amazon.com, Inc. |
| 10 | 140.235.158.24:26657 | 28,830,001 - 29,272,403 | one | 0 | on | v25.2.0 | 🇨🇦 Canada | Hypha Worker Co oper... |
| 11 | 138.201.82.234:29657 | 29,271,999 - 29,272,442 | hello-aries | 0 | off | v25.2.0 | 🇩🇪 Germany | Hetzner Online GmbH |
* Validators should configure a firewall to block all incoming traffic except for traffic that is explicitly allowed.
It helps to protect validators from attack. When we see a validator that is not using a firewall, we mark it with a warning symbol in the Validator column to indicate that it is more vulnerable to attack.
It helps to protect validators from attack. When we see a validator that is not using a firewall, we mark it with a warning symbol in the Validator column to indicate that it is more vulnerable to attack.
RPC nodes are a way to access information about the blockchain through HTTP requests. We scan the network to find and list all RPC nodes that have published their endpoints. RPC endpoints are scanned automatically every 6 hours.