Public RPC
| # | Endpoint * | Height | Moniker | VP | Indexer | Country | Provider | Scan Time |
|---|---|---|---|---|---|---|---|---|
| 1 | 34.162.141.12:26657 | 1 - 760,350 | hippo | 0 | on | 🇺🇸 United States | Google LLC | 1 hour ago |
| 2 | 44.226.74.246:26657 | 1 - 760,351 | hippo | 0 | on | 🇺🇸 United States | Amazon.com, Inc. | 1 hour ago |
| 3 | 54.180.207.159:26657 | 1 - 760,352 | hippo | 0 | on | 🇰🇷 South Korea | Amazon.com, Inc. | 1 hour ago |
| 4 | 135.181.117.37:46657 | 366,001 - 760,360 | 6DFA2huPi6d63rn... | 0 | on | 🇫🇮 Finland | Hetzner Online GmbH | 1 hour ago |
| 5 | 167.235.13.19:28657 | 759,001 - 760,357 | hello-taurus | 0 | off | 🇩🇪 Germany | Hetzner Online GmbH | 1 hour ago |
* 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.