Mezo public RPC endpoints, tested
Every keyless Mezo (chain ID 31612) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: does it answer on the right chain, how fast, how far behind the best head, how large an eth_getLogs range it accepts, whether it keeps archive state, and whether its WebSocket actually streams. 5 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://mezo.drpc.org | 23 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://mainnet.mezo.public.validationcloud.io | 32 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/mezo (SwiftNodes, keyless: 2 req/s) | 92 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://mezo-mainnet.boar.network | 126 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://rpc-internal.mezo.org | 137 ms | 0 blocks | 10,000+ | archive (1M+) |
Order: endpoints within 3 blocks of the best head first, then by median latency. Latency is measured from one server, so yours will differ by region; lag and limits do not.
WebSocket endpoints
- streams
rpc-ws-internal.mezo.org: first head after 1819 ms - streams
mainnet.mezo.public.validationcloud.io: first head after 1933 ms - streams
mezo-mainnet.boar.network: first head after 2106 ms - streams
mezo.drpc.org: first head after 2997 ms - does not stream
ws_evm-mezo.imperator.co: connection failed (connect) - does not stream
rpc.swiftnodes.io/ws/mezo(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc_evm-mezo.imperator.co: no answer (HTTP 405)lb.routeme.sh/rpc/evm/31612: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Mezo endpoint, limits and status: Mezo RPC, uptime history.