Monad RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Monad RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Monad has the lowest median latency of the 4 free public Monad RPC endpoints measured, 7 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/monad-rpc. Chain ID 143. 4 public endpoints, no key: rpc.monad.xyz, monad-mainnet.api.onfinality.io, monad.gateway.tenderly.co, monad-mainnet.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 →
Monad shipped its parallel-execution EVM mainnet in November 2025 with 400 ms blocks and MonadBFT finality around 800 ms, and its free RPC story is unusually rich for a chain this young. the Foundation runs five official mirrors behind different infra vendors (QuickNode, Alchemy, Goldsky, Ankr and its own nodes), and the multi-chain gateways followed within weeks. We probe the primary official endpoint plus dRPC, Tenderly Gateway, bloXroute and OnFinality, every 60 seconds from three regions, with the same anti-cache payload as every chain in the cluster. If you are building on Monad and pasting a free RPC URL into your dapp, this page is the live answer to which one deserves it.
Methodology
Monad: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Monad leads at 7 ms; the chain-official endpoint measures 7 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Monad endpoint that sustains continuous probing, 4 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) 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 Monad-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Monad RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Monad | 7 ms | 8 ms | 18 ms | 100.00% |
| 2 | OnFinality | 89 ms | 353 ms | 1.15 s | 92.85% |
| 3 | Tenderly Gateway | 106 ms | 114 ms | 132 ms | 100.00% |
| 4 | dRPC | 137 ms | 151 ms | 227 ms | 97.41% |
Public Monad RPC endpoints measured
Chain ID 143, currency MON. The 4 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.
Monadhttps://rpc.monad.xyz7 ms100.0%
OnFinalityhttps://monad-mainnet.api.onfinality.io/public89 ms92.8%
Tenderly Gatewayhttps://monad.gateway.tenderly.co106 ms100.0%
dRPChttps://monad-mainnet.drpc.org137 ms97.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 Monad RPCs work without an API key in 2026?
5 endpoints are probed on this chain; each is listed with its URL, 24h median and success rate in the endpoints table on this page, and the list changes as providers come and go.
How is Monad RPC latency measured on OpenChainBench?
One identical JSON-RPC POST (eth_getBlockByNumber latest, rotating request id) every 60 seconds against each provider from each of 3 regions, with the same plain HTTP client. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus quantile_over_time over 24 hours. Responses are classified so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities