XMRLIST
home / tools / remote nodes

Monero remote nodes, checked live

Public nodes you can point your wallet at, re-checked every 10 minutes. Green means it answered, is on mainnet and has the latest blocks.

Updated · onion nodes 45 min ago
Clearnet online
188 / 194
synced right now
Tor (.onion) online
98 / 104
checked through Tor
Network tip
3,783,253
block height
Valid HTTPS
72
synced, trusted cert
Web-wallet ready
43
CORS enabled

Showing the 80 most reliable of 286 nodes · show all 286

NodeStatusHeightUptime 24hLatencyFeatures
65.108.235.49:18089 synced 3,783,253
100%
 1 ms
91.224.92.48:18089 synced 3,783,253
100%
 22 ms
node.chaoswg.dev:443 synced 3,783,253
100%
 30 ms HTTPS
185.220.101.223:18081 synced 3,783,253
100%
 41 ms
xmr-in-berlin-2.boldsuck.org:18081 synced 3,783,253
100%
 41 ms
185.66.143.190:18081 synced 3,783,253
100%
 55 ms
152.53.150.12:18081 synced 3,783,253
100%
 56 ms
xmr-de.boldsuck.org:18081 synced 3,783,253
100%
 72 ms
141.98.153.205:18089 synced 3,783,253
100%
 77 ms
82.149.227.116:18081 synced 3,783,253
100%
 81 ms
185.220.101.63:18081 synced 3,783,253
100%
 81 ms
204.10.194.186:18081 synced 3,783,253
100%
 81 ms
109.199.98.74:18081 synced 3,783,253
100%
 87 ms
195.160.222.168:18081 synced 3,783,253
100%
 103 ms
xmr.unshakled.net:443 synced 3,783,253
100%
 109 ms HTTPS CORS
82.67.7.32:18089 synced 3,783,253
100%
 114 ms
188.166.192.175:18081 synced 3,783,253
100%
 116 ms
109.192.204.136:18081 synced 3,783,253
100%
 119 ms
193.72.32.187:18089 synced 3,783,253
100%
 119 ms
45.142.176.163:18089 synced 3,783,253
100%
 119 ms
xmr-nl.privateweb.st:18081 synced 3,783,253
100%
 120 ms
88.80.150.48:3389 synced 3,783,253
100%
 121 ms
176.123.6.130:18081 synced 3,783,253
100%
 128 ms
152.53.95.190:18089 synced 3,783,253
100%
 129 ms
pinodexmr.hopto.org:18081 synced 3,783,253
100%
 132 ms
monero.definitelynotafed.com:443 synced 3,783,253
100%
 132 ms HTTPS CORS
monero.konku.rs:18089 synced 3,783,253
100%
 139 ms
opennode.xmr-tw.org:18089 synced 3,783,253
100%
 142 ms
xmr.hostingwire.net:443 synced 3,783,253
100%
 142 ms HTTPS CORS
tor-exit-223.for-privacy.net:18081 synced 3,783,253
100%
 149 ms
89.125.187.247:18089 synced 3,783,253
100%
 157 ms
corny.cc:443 synced 3,783,253
100%
 157 ms HTTPS
xmr.ducks.party:443 synced 3,783,253
100%
 164 ms HTTPS
nodex.monerujo.io:18081 synced 3,783,253
100%
 166 ms
node2.monerodevs.org:18089 synced 3,783,253
100%
 168 ms
corny.cc:443 synced 3,783,253
100%
 168 ms
185.132.45.117:18089 synced 3,783,253
100%
 178 ms
xmr.hexide.com:80 synced 3,783,253
100%
 179 ms
195.16.73.12:18089 synced 3,783,253
100%
 188 ms
kowalski.fiatfaucet.com:443 synced 3,783,253
100%
 197 ms HTTPS CORS
nodes.hashvault.pro:18081 synced 3,783,253
100%
 198 ms
monero-rpc.cheems.de.box.skhron.com.ua:443 synced 3,783,253
100%
 205 ms HTTPS CORS
captrondo.onthewifi.com:18089 synced 3,783,253
100%
 209 ms
9x.ddns.net:18081 synced 3,783,253
100%
 211 ms
xmr.0xrpc.io:443 synced 3,783,253
100%
 216 ms HTTPS CORS
rpc.monerosafe.com:443 synced 3,783,253
100%
 223 ms HTTPS CORS
xmr-de-2.boldsuck.org:18081 synced 3,783,253
100%
 226 ms
dewitte.fiatfaucet.com:443 synced 3,783,253
100%
 228 ms HTTPS CORS
xmr.diyarciftci.xyz:18081 synced 3,783,253
100%
 228 ms
xmr-01.tari.com:443 synced 3,783,253
100%
 233 ms HTTPS
xmr.cryptostorm.is:18081 synced 3,783,253
100%
 234 ms HTTPS CORS
node.mon3ro.com:443 synced 3,783,253
100%
 236 ms HTTPS CORS
193.168.143.9:18081 synced 3,783,253
100%
 237 ms
xmr.cryptostorm.is:443 synced 3,783,253
100%
 238 ms HTTPS CORS
xmr-full.p2pool.uk:18089 synced 3,783,253
100%
 239 ms
xmr.visnova.pl:443 synced 3,783,253
100%
 241 ms HTTPS CORS
xmr.litepay.ch:18081 synced 3,783,253
100%
 242 ms
node.monerosafe.com:443 synced 3,783,253
100%
 242 ms HTTPS CORS
alucardxmr.ydns.eu:18081 synced 3,783,253
100%
 243 ms
xmr.ducks.party:18081 synced 3,783,253
100%
 244 ms
edge7.servebeer.com:18089 synced 3,783,253
100%
 245 ms
xmr.ducks.party:443 synced 3,783,253
100%
 250 ms HTTPS
node.chaoswg.dev:443 synced 3,783,253
100%
 252 ms HTTPS
xmr-bhs.tari.com:443 synced 3,783,253
100%
 263 ms HTTPS
69.30.225.138:18089 synced 3,783,253
100%
 273 ms
0x255.xyz:18081 synced 3,783,253
100%
 279 ms
legalise.it:18089 synced 3,783,253
100%
 280 ms
ldn1.derp.anstee.dev:18081 synced 3,783,253
100%
 294 ms
monero.konku.rs:18089 synced 3,783,253
100%
 296 ms HTTPS CORS
node3.monerodevs.org:18089 synced 3,783,253
100%
 297 ms
xmr-gra.tari.com:443 synced 3,783,253
100%
 297 ms HTTPS
anstee.dev:18081 synced 3,783,253
100%
 298 ms HTTPS
xmr.cryptostorm.is:443 synced 3,783,253
100%
 300 ms HTTPS CORS
xmr.apschneider-it.eu:443 synced 3,783,253
100%
 306 ms HTTPS
node.kyc.rip:443 synced 3,783,253
100%
 321 ms HTTPS
monero.kaythomas.dev:18089 synced 3,783,253
100%
 321 ms
88.3.210.198:18081 synced 3,783,253
100%
 324 ms
monero.mullvad.net:18081 synced 3,783,253
100%
 324 ms
204.8.45.35:18081 synced 3,783,253
100%
 329 ms
xmrnode.shork.ch:443 synced 3,783,253
100%
 331 ms HTTPS

Latency is measured from our server in Europe; onion latency includes the Tor circuit. Uptime counts the share of checks in the last 24 hours where the node was synced. Candidates from monero.fail, checks by XMRList. JSON: /tools/nodes.json

01

Connect your wallet to a node

Feather Wallet

Settings → Network → Node → Specify custom node. Paste the address with port. For .onion nodes, turn on Tor in the same section.

Cake Wallet

Settings → Connection and sync → Manage nodes → add a node. Enter the host and port; tick SSL for HTTPS nodes.

Monero GUI

Settings → Node → Remote node → Add remote node. Enter address and port. Start the GUI with Tor running to use .onion nodes.

CLI

monero-wallet-cli --daemon-address host:port. For onion nodes add --proxy 127.0.0.1:9050 with Tor running.

02

What a remote node can see

A remote node cannot see your balance, your keys or who you pay. It can see your IP address, when your wallet broadcasts a transaction, and which blocks you download. Using an .onion node through Tor removes the IP part. Running your own node removes the rest. See our guide to remote nodes and privacy.

?

Questions people ask

Which Monero remote node should I use?
Pick a node marked synced with high 24h uptime. A nearby clearnet node is fastest; an .onion node used through Tor hides your IP address from the node operator. The most private option is still your own node: a pruned node needs about 100 GB of disk.
Is it safe to use a remote node?
Your keys and balance never leave your wallet, so a remote node cannot spend or freeze your funds. It can see your IP address (unless you use Tor), roughly when you send a transaction, and which blocks your wallet downloads. Ring signatures hide which output is really yours, but a malicious node could try to weaken that over many transactions, which is why people rotate nodes or run their own.
Why does my wallet say “daemon not connected” or stay stuck syncing?
Usually the node is offline or still catching up. Switch to a node listed here as synced with a recent check. Also confirm the port: most public nodes answer on 18081 or 18089, HTTPS nodes on 443. A wrong system clock can also stall sync.
What is the difference between port 18081 and 18089?
18081 is the default Monero RPC port. Many operators expose a restricted RPC on 18089 for public use, which blocks admin commands. For a wallet both work the same if the node is public.
How does XMRList check the nodes?
Our server calls /get_info on every node every 10 minutes (onion nodes hourly, through Tor). A node counts as synced when it answers, is on mainnet and is within 3 blocks of the network tip agreed by at least three nodes. The list of candidates comes from monero.fail. Latency is measured from Europe, so yours will differ.
sponsors Apple Bitcoin· Bull Miners· Mullvad· Trocador· CryptoGPUs· Cake Wallet· Bitgolder· Coincards· MoneroDice· Swapnoir· PayAIwithCrypto