Monero remote node picker
Health data for public Monero nodes, probed from our server. Sort by latency, height lag or uptime to find one worth using; the height and fee checks flag nodes serving stale or wrong data.
| Node | Net | Height | Response | Uptime | Web (CORS) | |
|---|---|---|---|---|---|---|
| Loading node health… | ||||||
How to use one
Copy a node's host:port and paste it into your wallet's remote node setting:
- Official GUI: Settings → Node → Remote → enter the address and port.
- CLI: monero-wallet-cli --daemon-address host:port (add --trusted-daemon only for your own node).
- Feather / Cake / Monerujo: Settings → Node → add a custom node as host:port.
The Web (CORS) column marks nodes that browser-based wallets (like the web wallet) can reach. Rotate nodes now and then — it's good privacy hygiene.
How we check them
A background prober contacts each clearnet node through Tor, roughly every 30–60 minutes, with an identifying user-agent. Routing over Tor keeps our own server's IP private and means a bad node can't log where the checks come from. For each node we record:
- Height lag — blocks behind our own synced node. 0 is perfectly in sync; a large lag means stale (or dishonest) data.
- Response — round-trip time to /get_height over Tor. It shows a node is reachable and responsive, but includes Tor's overhead, so treat it as a rough signal, not the node's raw speed.
- Uptime — share of recent checks the node answered correctly (the bar shows the last ~30 checks, newest on the right).
- Fee canary — we periodically compare the node's fee estimate to the network's; a value far off the norm suggests a node trying to overcharge.
Tor and I2P nodes are listed from public directories but not yet health-checked from here — this host has no Tor relay, so they appear without latency or uptime data.