Public Monero Remote Nodes List
Monero remote node is a device on the internet running the Monero software with a full copy of the Monero blockchain that does not operate on the same local machine where the Monero wallet is located.
- The MRL and DNS ban list features are still experimental and data is provided by Rucknium's Monero Network Scan and Boog900's Monero Ban List.
- Using a remote node with both MRL and DNS ban list enabled is better than using a remote node that does not have MRL and DNS ban list enabled.
- MRL and DNS ban list information currently applies only to mainnet nodes using IPv4.
- If you find it difficult to choose a remote node from the list below, using the remote node used by Feather Wallet is a good choice.
- If you are a node operator, Monero Research Lab (MRL) recommends enabling the ban list of suspected spy node IP addresses (see the ban_list.txt file). And, don't forget to use
--enable-dns-blocklistflag (orenable-dns-blocklist=1if using config file) when startingmonerod👌.
| Host:Port | Nettype | Protocol | Spy Node | Ban List Enabled | Country | Status | Estimate Fee | Uptime ▴▾ | Check ▴ | |
|---|---|---|---|---|---|---|---|---|---|---|
.i2p:2266 I2P | mainnet 3756984 | http | N/A | N/A | N/A | Offline ••••• | 20000 | 80.88% [Logs] | 12s ago | |
.i2p:2266 I2P | mainnet 3756984 | http | N/A | N/A | N/A | Online ••••• | 20000 | 80% [Logs] | 26s ago | |
.i2p:18081 I2P | mainnet 3757312 | http | N/A | N/A | N/A | Online ••••• | 20000 | 72.63% [Logs] | 26s ago | |
.onion:18089 TOR | mainnet 3753491 | http | N/A | N/A | N/A | Online ••••• | 20000 | 94.63% [Logs] | 32s ago | |
.i2p:2266 I2P | mainnet 3756984 | http | N/A | N/A | N/A | Offline ••••• | 20000 | 86.29% [Logs] | 40s ago | |
.onion:18081 TOR | mainnet 3757178 | http | N/A | N/A | N/A | Online ••••• | 20000 | 93.59% [Logs] | 43s ago | |
.onion:18081 TOR | mainnet 3757177 | http | N/A | N/A | N/A | Online ••••• | 20000 | 95.7% [Logs] | 51s ago | |
.i2p:18081 I2P | mainnet 3741955 | http | N/A | N/A | N/A | Offline ••••• | 20000 | 26.64% [Logs] | 52s ago | |
.i2p:2266 I2P | mainnet 3757312 | http | N/A | N/A | N/A | Online ••••• | 20000 | 77.78% [Logs] | 57s ago | |
.i2p:18081 I2P | mainnet 3742107 | http | N/A | N/A | N/A | Offline ••••• | 20000 | 24.18% [Logs] | 59s ago | |
1 - 10 / 2487
Info
- If you find any remote nodes that are strange or suspicious, please open an issue on GitHub for removal.
- Uptime percentage calculated is the last 1 month uptime.
- Est. Fee here is just fee estimation / byte from
get_fee_estimateRPC call method. - Malicious actors who are running remote nodes can still return a high fee if you are about to create a transaction..
- The best and safest way is running your own node!
- Nodes with 0% uptime with more than 50 check attempts will be archived. You can always add your node again later.
- You can filter remote nodes by selecting nettype, protocol, country, tor, and online-status options.
- If you want to add more remote nodes, you can do so on the /add-node page.
- I deliberately cut the long Tor and I2P addresses, click the 👁 hostname... to open more detailed information about the Node.
- You can find larger remote nodes database from monero.fail.
- If you’re a developer or power user who’d like to fetch the Monero remote nodes above in JSON format, see our Public API Monero Remote Node List blog post for more detailed information.
Remote nodes can be used by individuals who, for various reasons (usually due to hardware requirements, disk space, or technical abilities), cannot or do not want to run their own node and prefer to rely on one that is publicly available on the Monero network.
Using an open node allows for instantaneous transactions without the need to download the blockchain and sync with the Monero network first, but it comes at the cost of control over your privacy. The Monero community suggests always running and using your own node to achieve the maximum possible privacy and to help decentralize the network.