Mantle RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Mantle RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 3 free public Mantle RPC endpoints measured, 70 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/mantle-rpc. Chain ID 5000. 3 public endpoints, no key: mantle-rpc.publicnode.com, gateway.tenderly.co, mantle.drpc.org. Full URLs with their 24h median are listed below.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Mantle rounds out the cluster's long tail with 3 qualifying no-key providers, all multi-chain gateways. Like every chain in the family, the number that matters is a sustained median, the same `eth_getBlockByNumber` call every 60 seconds from three regions over a rolling 24 hours, not a one-off marketing burst, and archive-depth support is audited separately every 5 minutes.
Methodology
Mantle: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 70 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Mantle endpoint that sustains continuous probing, 3 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness also classifies every response (ok / http_err / jsonrpc_err / stale / timeout) and audits archive depth every 5 minutes, so the leaderboard rewards sustained, honest availability rather than a fast error message. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Mantle-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public Mantle RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 70 ms | 85 ms | 244 ms | 100.00% |
| 2 | Tenderly | 102 ms | 108 ms | 116 ms | 100.00% |
| 3 | dRPC | 445 ms | 642 ms | 948 ms | 98.44% |
Public Mantle RPC endpoints measured
Chain ID 5000, currency MNT. The 3 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
PublicNodehttps://mantle-rpc.publicnode.com70 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/mantle102 ms100.0%
dRPChttps://mantle.drpc.org445 ms98.4%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Frequently asked
Which Mantle RPCs work without an API key?
The 3 providers on this page are listed with their URLs in the endpoints table above. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.
Are free Mantle RPCs reliable enough to build on?
The 3 qualifying gateways all maintain high measured success rates on Mantle, but a 3-provider field means less redundancy if one degrades. Use the current leader as primary and the runner-up as fallback, and re-check this page after incidents, the ranking is live and the honest answer moves.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities