RPCsUpdated

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, 85 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 85 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.

  • Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
  • Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Mantle-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain="mantle". Provider coverage: 3 no-key public-read endpoints live today, each listed with its URL in the endpoints table on this page. Exclusions follow the cluster-wide rules documented on the parent benchmark.

Results: 3 free public Mantle RPC endpoints ranked by p50 latency (24h, 3 regions)

Mantle RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1PublicNodeAllnodes-operated, 70+ chains, archive on most85 ms99 ms224 ms100.00% (n=4320)
2TenderlyMulti-chain public gateway, 9 chains, no key104 ms111 ms117 ms100.00% (n=4320)
3dRPCDecentralized RPC mesh, consensus-checked248 ms401 ms1.56 s60.82% (n=4320)

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.

  • PublicNode logoPublicNodehttps://mantle-rpc.publicnode.com85 ms100.0%
  • Tenderly logoTenderlyhttps://gateway.tenderly.co/public/mantle104 ms100.0%
  • dRPC logodRPChttps://mantle.drpc.org248 ms60.8%

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