Upstream Monero Nodes
The live Monero node pool behind mnr: verified community nodes and dedicated infrastructure. Every request sent by our relay identifies as mnr-relay/0.x in its User-Agent, caps itself to prevent node exhaustion, and verifies answers against cryptographic consensus.
Operational · Quorum consensus active (15 of 15 nodes healthy)
relay v0.1.17 · commit 0d679add7b7a · up 24h · self-reported
| Node Host | Status | Height | Latency | Up 24h | Our Rate | Our Cap | Requests | WU | Verified | Faults |
|---|---|---|---|---|---|---|---|---|---|---|
| own-1ourshttprestricted rpc | on tip | 3,757,137 | 663 ms | 99.4% | 0.54/s | 500/s · 32 streams | 37,524 | 372,235 | 4,412 | 1 |
| stackwallethttprestricted rpc | on tip | 3,757,137 | 65 ms | 99.9% | 0.42/s | 5/s · 2 streams | 32,989 | 28,163 | 22,844 | 1 |
| xmr-supporthttprestricted rpc | on tip | 3,757,137 | 35 ms | 99.7% | 0.44/s | 5/s · 2 streams | 28,593 | 27,423 | 17,696 | 1 |
| cakewallethttpsrestricted rpc | on tip | 3,757,137 | 57 ms | 98.8% | 0.38/s | 5/s · 2 streams | 21,070 | 14,793 | 11,337 | 0 |
| sethforprivacyhttprestricted rpc | on tip | 3,757,137 | 150 ms | 98.6% | 0.05/s | 5/s · 2 streams | 19,566 | 12,629 | 10,342 | 0 |
| xmr-tw-1httprestricted rpc | on tip | 3,757,137 | 148 ms | 99.8% | 0.00/s | 5/s · 2 streams | 14,042 | 7,102 | 4,677 | 0 |
| privacyxhttpsrestricted rpc | on tip | 3,757,137 | 184 ms | 99.7% | 0.00/s | 5/s · 2 streams | 11,475 | 4,535 | 1,765 | 0 |
| monerodevs-2httprestricted rpc | on tip | 3,757,137 | 183 ms | 99.4% | 0.00/s | 5/s · 2 streams | 10,890 | 4,173 | 1,903 | 0 |
| boldsuck-dehttprestricted rpc | on tip | 3,757,137 | 162 ms | 100.0% | 0.00/s | 5/s · 2 streams | 10,014 | 3,074 | 993 | 0 |
| stormycloudhttprestricted rpc | on tip | 3,757,137 | 1110 ms | 85.7% | 0.00/s | 5/s · 2 streams | 10,575 | 3,636 | 1,571 | 0 |
| monerujohttprestricted rpc | on tip | 3,757,137 | 330 ms | 99.4% | 0.00/s | 5/s · 2 streams | 10,481 | 3,541 | 1,557 | 0 |
| hashvaulthttprestricted rpc | on tip | 3,757,137 | 208 ms | 99.9% | 0.00/s | 5/s · 2 streams | 9,672 | 2,732 | 850 | 0 |
| boldsuck-berlinhttprestricted rpc | on tip | 3,757,137 | 169 ms | 99.8% | 0.00/s | 5/s · 2 streams | 9,299 | 2,359 | 528 | 0 |
| monerodevs-3httprestricted rpc | on tip | 3,757,137 | 166 ms | 99.9% | 0.00/s | 5/s · 2 streams | 3,733 | 26 | 19 | 0 |
| cryptostormhttpsrestricted rpc | on tip | 3,757,137 | 575 ms | 61.7% | 0.00/s | 5/s · 2 streams | 10,640 | 3,700 | 1,483 | 0 |
Cryptographic Fault Log
Auto-Ejection: 3 / hrResponses that failed verification against block and transaction hashes, our header chain, or the answers other nodes gave. Three faults within an hour automatically ejects a node for 24 hours. No client query information is ever logged.
No active faults. All consensus nodes verified on tip height 3,756,973.
Operator Opt-Outs
Well-Known File ProtocolNodes whose operators opted out. Nodes leave rotation immediately upon serving /.well-known/mnr-optout (any HTTP 200) on port 80/443, or via email to dev@mnr.network.
No active opt-outs. All 15 community nodes in voluntary rotation.
The seven ethical proxy rules
Public Monero nodes are voluntary community infrastructure. mnr operates under strict, transparent principles to ensure zero disruption and absolute privacy.
1. Disclose
Rule 01This live page, our homepage, and every HTTP User-Agent disclose exactly what mnr is and where requests originate.
2. Contribute
Rule 02mnr operates its own high-throughput dedicated Monero nodes. Our nodes carry the heaviest load and absorb sync surges.
3. Strict Self-Capping
Rule 03We hard-cap ourselves at 5 light requests/second, 2 wallet sync streams, and 10 MB/s to any public node. Caps are enforced before transmission.
4. Identify
Rule 04Every single request carries mnr-relay/0.x (+https://mnr.network/upstreams) so operators can easily grep our traffic in daemon logs.
5. Honor Opt-Outs
Rule 05Publish /.well-known/mnr-optout on your web port or write to dev@mnr.network. Nodes are removed from rotation within 24 hours.
6. Zero Client Identity
Rule 06No client IP addresses, bearer tokens, or view keys are ever forwarded. Public nodes only receive sanitized RPC method bodies.
7. Restricted RPC Only
Rule 07We enforce a strict method allow-list at the edge. Administrative commands (stop_daemon, start_mining) are dropped instantly.
Node operator FAQ
Why does mnr query my node?
We do not scan the network. mnr's upstream pool is a small curated list built from the well-known public node lists (monero.fail, the wallet-maintained lists) plus a full node we run ourselves, and every operator we can identify is told before their node is used. We distribute read-only verification queries across the pool to establish quorum consensus, staying within the published per-node caps.
What about privacy-sensitive requests?
The queries that reveal what a wallet is looking at — outputs, transactions, key images — are routed to our own node first, so a third-party node does not see them while our node is up. The honest limits of that are on the privacy page.
How can I inspect mnr's traffic in my logs?
Filter your daemon access or web reverse-proxy logs by User-Agent: mnr-relay/0.*. You will see light, evenly paced queries adhering strictly to our published request caps.
How does the automated opt-out work?
If you host a web server on the same IP or domain, configure it to return HTTP 200 for /.well-known/mnr-optout. Our relay checks this daily and immediately drops your node from rotation.
What raw telemetry API is available?
The live data powering this dashboard is available as JSON at rpc.mnr.network/upstreams.json, including per-node RTT, verification counters, and fault details.