Live from relay · Refreshes every 15s

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.

Connecting to relay telemetry…

Quorum Consensus

—

nodes agreeing on the tip

Tip Height

—

Active Upstreams

—

healthy of listed in pool

Our Request Rate

—

requests / second, aggregate

Node Host	Status	Height	Latency	Our Rate	Our Cap	Verified	Faults
Waiting for relay response…

Cryptographic Fault Log

Auto-Ejection: 3 / hr

Responses that failed verification (hash mismatch, unparseable payload, or timeout). Three faults within an hour automatically ejects a node for 24 hours. No client query information is ever logged.

—

Operator Opt-Outs

Well-Known File Protocol

Nodes 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.

—

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 01

This live page, our homepage, and every HTTP User-Agent disclose exactly what mnr is and where requests originate.

2. Contribute

Rule 02

mnr operates its own high-throughput dedicated Monero nodes. Our nodes carry the heaviest load and absorb sync surges.

3. Strict Self-Capping

Rule 03

We 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 04

Every 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 05

Publish /.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 06

No client IP addresses, bearer tokens, or view keys are ever forwarded. Public nodes only receive sanitized RPC method bodies.

7. Restricted RPC Only

Rule 07

We 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?

mnr discovers public Monero nodes broadcasting open RPC services (ports 18081 and 18089) on the Monero P2P network. We distribute read-only verification queries across multiple nodes to establish quorum consensus.

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 scanner polls 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.