XMRLIST
home / tools / remote nodes

Monero remote nodes, checked live

Public nodes you can point your wallet at. Green means it answered, is on mainnet and has the latest blocks.

Updated · onion nodes 24 min ago
Clearnet online
172 / 176
synced right now
Tor (.onion) online
134 / 135
.onion nodes
Network tip
3,808,494
block height
Valid HTTPS
68
synced, trusted cert
Web-wallet ready
45
CORS enabled

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

NodeStatusHeightUptime 24hLatencyFeatures
65.108.235.49:18089 synced 3,808,494
100%
1 ms
node.chaoswg.dev:443 synced 3,808,494
100%
30 ms HTTPS
tor-exit-223.for-privacy.net:18081 synced 3,808,494
100%
41 ms
91.224.92.48:18089 synced 3,808,494
100%
47 ms
xmr.saxemberg.com:18089 synced 3,808,494
100%
49 ms
xmr.ducks.party:443 synced 3,808,494
100%
51 ms HTTPS CORS
82.149.227.116:18081 synced 3,808,494
100%
66 ms
185.220.101.223:18081 synced 3,808,494
100%
67 ms
xmr.izvne.com:18089 synced 3,808,494
100%
76 ms
185.220.101.63:18081 synced 3,808,494
100%
79 ms
xmr.carlslab.de:443 synced 3,808,494
100%
90 ms HTTPS
188.166.192.175:18081 synced 3,808,494
100%
91 ms
xmr-in-berlin-2.boldsuck.org:18081 synced 3,808,494
100%
91 ms
152.53.150.12:18081 synced 3,808,494
100%
92 ms
45.142.176.163:18089 synced 3,808,494
100%
97 ms
xmr.carlslab.de:443 synced 3,808,494
100%
98 ms HTTPS
152.53.95.190:18089 synced 3,808,494
100%
99 ms
176.123.6.130:18081 synced 3,808,494
100%
103 ms
corny.cc:443 synced 3,808,494
100%
105 ms HTTPS
141.98.153.205:18089 synced 3,808,494
100%
112 ms
xmr-berlin.privacyfirst.digital:18089 synced 3,808,494
100%
112 ms
46.32.46.171:18081 synced 3,808,494
100%
116 ms
corny.cc:443 synced 3,808,494
100%
117 ms
185.66.143.190:18081 synced 3,808,494
100%
120 ms
xmr.0xrpc.io:443 synced 3,808,494
100%
122 ms HTTPS CORS
5.189.143.209:18089 synced 3,808,494
100%
122 ms
185.132.45.117:18089 synced 3,808,494
100%
129 ms
195.16.73.12:18089 synced 3,808,494
100%
129 ms
node1-eu.monero.love:18089 synced 3,808,494
100%
132 ms
88.80.150.48:3389 synced 3,808,494
100%
133 ms
xmr.ducks.party:18081 synced 3,808,494
100%
136 ms
82.67.7.32:18089 synced 3,808,494
100%
137 ms
node0.eu.monero.love:18089 synced 3,808,494
100%
143 ms
xmr-de.boldsuck.org:18081 synced 3,808,494
100%
146 ms
monero.definitelynotafed.com:443 synced 3,808,494
100%
146 ms HTTPS CORS
88.3.210.198:18081 synced 3,808,494
100%
147 ms
xmr-de-2.boldsuck.org:18081 synced 3,808,494
100%
162 ms
node2.monerodevs.org:18089 synced 3,808,494
100%
164 ms
monero.konku.rs:18089 synced 3,808,494
100%
164 ms
xmr.vidaliafarms.com:18089 synced 3,808,494
100%
165 ms
owl.lc:18089 synced 3,808,494
100%
167 ms
monero-rpc.cheems.de.box.skhron.com.ua:18089 synced 3,808,494
100%
167 ms HTTPS CORS
xmr5.doggett.tech:18089 synced 3,808,494
100%
167 ms HTTPS CORS
atm.rabbithole2.net:18089 synced 3,808,494
100%
169 ms
89.125.187.247:18089 synced 3,808,494
100%
178 ms
proxmox.izvne.com:18089 synced 3,808,494
100%
179 ms
193.168.141.4:18081 synced 3,808,494
100%
182 ms
193.168.143.9:18081 synced 3,808,494
100%
186 ms
monero-rpc.cheems.de.box.skhron.com.ua:443 synced 3,808,494
100%
187 ms HTTPS CORS
xmr-node.cakewallet.com:18081 synced 3,808,494
100%
191 ms HTTPS CORS
xmrnode.shork.ch:443 synced 3,808,494
100%
193 ms HTTPS
xmr.hostingwire.net:443 synced 3,808,494
100%
195 ms HTTPS CORS
monero.konku.rs:18089 synced 3,808,494
100%
204 ms HTTPS CORS
xmr.apschneider-it.eu:443 synced 3,808,494
100%
214 ms HTTPS
captrondo.onthewifi.com:18089 synced 3,808,494
100%
215 ms
node.monerosafe.com:443 synced 3,808,494
100%
222 ms HTTPS CORS
xmr.cryptostorm.is:443 synced 3,808,494
100%
231 ms HTTPS CORS
monero.anycolo.net:18081 synced 3,808,494
100%
242 ms
109.199.98.74:18081 synced 3,808,494
100%
242 ms
kowalski.fiatfaucet.com:443 synced 3,808,494
100%
245 ms HTTPS CORS
dewitte.fiatfaucet.com:443 synced 3,808,494
100%
245 ms HTTPS CORS
xmr.litepay.ch:18081 synced 3,808,494
100%
246 ms
node.chaoswg.dev:443 synced 3,808,494
100%
246 ms HTTPS
xmr.jel.gay:18081 synced 3,808,494
100%
246 ms
xmr-node.cakewallet.com:18081 synced 3,808,494
100%
247 ms
connect.xmr-node.org:443 synced 3,808,494
100%
258 ms HTTPS CORS
xmr-gra.tari.com:443 synced 3,808,494
100%
262 ms HTTPS
xmr-full.p2pool.uk:18089 synced 3,808,494
100%
263 ms
xmr.diyarciftci.xyz:18089 synced 3,808,494
100%
263 ms HTTPS
node.monerodevs.org:18089 synced 3,808,494
100%
265 ms
nodes.hashvault.pro:18081 synced 3,808,494
100%
270 ms
monero.ceo:18089 synced 3,808,494
100%
270 ms
opennode.xmr-tw.org:18089 synced 3,808,494
100%
271 ms
xmr-lim.tari.com:443 synced 3,808,494
100%
274 ms HTTPS
connect.xmr-node.org:443 synced 3,808,494
100%
275 ms HTTPS CORS
154.12.229.22:18081 synced 3,808,494
100%
277 ms
monero.mullvad.net:18081 synced 3,808,494
100%
284 ms
xmr.jayjonkman.nl:18089 synced 3,808,494
100%
293 ms HTTPS CORS
xmr.diyarciftci.xyz:18081 synced 3,808,494
100%
296 ms
xmr-node.rbmpool.com:18089 synced 3,808,494
100%
297 ms

Latency is indicative and depends on your location. 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?
Each node is queried regularly. 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 depends on your location, so yours will differ.

The XMRList newsletter

New verified merchants, scam warnings and Monero tool updates. About once a month, nothing else.

Double opt-in. No tracking pixels, no ads, never shared. Unsubscribe in one click.