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 35 min ago
Clearnet online
188 / 194
synced right now
Tor (.onion) online
112 / 120
checked through Tor
Network tip
3,775,998
block height
Valid HTTPS
73
synced, trusted cert
Web-wallet ready
42
CORS enabled

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

NodeStatusHeightUptime 24hLatencyFeatures
65.108.235.49:18089 synced 3,775,998
100%
 1 ms
xmr.mony.st:443 synced 3,775,998
100%
 25 ms HTTPS
185.220.101.223:18081 synced 3,775,998
100%
 39 ms
46.32.46.171:18081 synced 3,775,998
100%
 43 ms
node.chaoswg.dev:443 synced 3,775,998
100%
 48 ms HTTPS
tor-exit-223.for-privacy.net:18081 synced 3,775,998
100%
 49 ms
204.10.194.186:18081 synced 3,775,998
100%
 69 ms
corny.cc:443 synced 3,775,998
100%
 71 ms HTTPS
185.220.101.63:18081 synced 3,775,998
100%
 74 ms
82.149.227.116:18081 synced 3,775,998
100%
 82 ms
91.224.92.48:18089 synced 3,775,998
100%
 84 ms
xmr-de-2.boldsuck.org:18081 synced 3,775,998
100%
 97 ms
185.66.143.190:18081 synced 3,775,998
100%
 97 ms
176.123.6.130:18081 synced 3,775,998
100%
 97 ms
xmr.ducks.party:18081 synced 3,775,998
100%
 105 ms
193.72.32.187:18089 synced 3,775,998
100%
 105 ms
152.53.95.190:18089 synced 3,775,998
100%
 108 ms
monero.konku.rs:18089 synced 3,775,998
100%
 110 ms
152.53.150.12:18081 synced 3,775,998
100%
 119 ms
xmr.ducks.party:443 synced 3,775,998
100%
 123 ms HTTPS
xmr-berlin.privacyfirst.digital:18089 synced 3,775,998
100%
 125 ms
xmr-nl.privateweb.st:18081 synced 3,775,998
100%
 130 ms
nodex.monerujo.io:18081 synced 3,775,998
100%
 131 ms
nodes.hashvault.pro:18081 synced 3,775,998
100%
 132 ms
144.91.121.7:18089 synced 3,775,998
100%
 133 ms
xmr.hostingwire.net:443 synced 3,775,998
100%
 133 ms HTTPS CORS
xmr.saxemberg.com:18089 synced 3,775,998
100%
 136 ms
corny.cc:443 synced 3,775,998
100%
 145 ms
188.166.192.175:18081 synced 3,775,998
100%
 147 ms
owl.lc:18089 synced 3,775,998
100%
 150 ms
195.160.222.168:18081 synced 3,775,998
100%
 152 ms
kowalski.fiatfaucet.com:443 synced 3,775,998
100%
 153 ms HTTPS CORS
45.142.176.163:18089 synced 3,775,998
100%
 153 ms
xmr-de.boldsuck.org:18081 synced 3,775,998
100%
 156 ms
xmr.cryptostorm.is:18081 synced 3,775,998
100%
 164 ms HTTPS CORS
88.80.150.48:3389 synced 3,775,998
100%
 167 ms
185.132.45.117:18089 synced 3,775,998
100%
 169 ms
195.16.73.12:18089 synced 3,775,998
100%
 169 ms
pinodexmr.hopto.org:18081 synced 3,775,998
100%
 172 ms
xmr-gra.tari.com:443 synced 3,775,998
100%
 177 ms HTTPS
xmr.visnova.pl:443 synced 3,775,998
100%
 179 ms HTTPS CORS
xmr-in-berlin-2.boldsuck.org:18081 synced 3,775,998
100%
 180 ms
xmr.carlslab.de:443 synced 3,775,998
100%
 180 ms HTTPS
connect.xmr-node.org:443 synced 3,775,998
100%
 181 ms HTTPS CORS
monero-rpc.cheems.de.box.skhron.com.ua:18089 synced 3,775,998
100%
 182 ms HTTPS CORS
xmr.carlslab.de:443 synced 3,775,998
100%
 184 ms HTTPS
atm.rabbithole2.net:18089 synced 3,775,998
100%
 185 ms
connect.xmr-node.org:443 synced 3,775,998
100%
 189 ms HTTPS CORS
node.monerosafe.com:443 synced 3,775,998
100%
 190 ms HTTPS CORS
monero.konku.rs:18089 synced 3,775,998
100%
 190 ms HTTPS CORS
88.3.210.198:18081 synced 3,775,998
100%
 191 ms
node.mon3ro.com:443 synced 3,775,998
100%
 191 ms HTTPS CORS
109.199.98.74:18081 synced 3,775,998
100%
 201 ms
xmr.ducks.party:443 synced 3,775,998
100%
 205 ms HTTPS
89.125.187.247:18089 synced 3,775,998
100%
 206 ms
193.168.143.9:18081 synced 3,775,998
100%
 207 ms
xmr.hexide.com:80 synced 3,775,998
100%
 209 ms
xmr.cryptostorm.is:443 synced 3,775,998
100%
 210 ms HTTPS CORS
xmr-bhs.tari.com:443 synced 3,775,998
100%
 212 ms HTTPS
204.8.45.35:18081 synced 3,775,998
100%
 215 ms
monero.dyni.net:18081 synced 3,775,998
100%
 221 ms
legalise.it:18089 synced 3,775,998
100%
 221 ms
monero.anycolo.net:18081 synced 3,775,998
100%
 222 ms
82.67.7.32:18089 synced 3,775,998
100%
 229 ms
xmr.mony.st:443 synced 3,775,998
100%
 232 ms HTTPS
rpc.monerosafe.com:443 synced 3,775,998
100%
 234 ms HTTPS CORS
anstee.dev:18081 synced 3,775,998
100%
 235 ms HTTPS
dewitte.fiatfaucet.com:443 synced 3,775,998
100%
 235 ms HTTPS CORS
194.163.176.218:18089 synced 3,775,998
100%
 238 ms
xmr-lim.tari.com:443 synced 3,775,998
100%
 239 ms HTTPS
xmr-node.cakewallet.com:18081 synced 3,775,998
100%
 240 ms HTTPS CORS
hantaan.fullm00n.de:18089 synced 3,775,998
100%
 241 ms
node.monerodevs.org:18089 synced 3,775,998
100%
 241 ms
xmr.cryptostorm.is:443 synced 3,775,998
100%
 243 ms HTTPS CORS
monero.kaythomas.dev:18089 synced 3,775,998
100%
 244 ms
xmr-node.ddns.net:18081 synced 3,775,998
100%
 249 ms
node.xmr.indst.eu:443 synced 3,775,998
100%
 251 ms HTTPS
xmr.diyarciftci.xyz:18081 synced 3,775,998
100%
 253 ms
0x255.xyz:18081 synced 3,775,998
100%
 257 ms
static.63.34.245.188.clients.your-server.de:18089 synced 3,775,998
100%
 260 ms

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· Cake Wallet· Bitgolder· Coincards· GhostSwap· MoneroDice· SageSwap· xChange.me