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, 30 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 and OnFinality (bloXroute's public host stopped resolving and left on 2026-10-19), 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 30 ms; the chain-official endpoint measures 30 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.
- 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 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 Monad-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain="monad" (chain id 143, mainnet since November 2025). Provider coverage: 4 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: 4 free public Monad RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | MonadFoundation endpoint (rpc.monad.xyz, Quicknode-backed, 25 rps) | 30 ms | 45 ms | 83 ms | 99.79% (n=4315) |
| 2 | OnFinalityPublic endpoint, 80+ networks | 86 ms | 258 ms | 1.94 s | 100.00% (n=4321) |
| 3 | Tenderly GatewayPublic gateway by Tenderly | 106 ms | 114 ms | 152 ms | 100.00% (n=4319) |
| 4 | dRPCDecentralized RPC mesh, consensus-checked | 142 ms | 160 ms | 210 ms | 100.00% (n=4319) |
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.xyz30 ms99.8%
OnFinalityhttps://monad-mainnet.api.onfinality.io/public86 ms100.0%Tenderly Gateway
https://monad.gateway.tenderly.co106 ms100.0%
dRPChttps://monad-mainnet.drpc.org142 ms100.0%
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?
4 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