Mode RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public Mode EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Mode Labs has the lowest median latency of the 2 free public Mode RPC endpoints measured above the 50 % success floor (3 listed), 129 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/mode-rpc. Chain ID 34443. 3 public endpoints, no key: mainnet.mode.network, mode.drpc.org, 1rpc.io. 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 →
Mode is an OP Stack rollup (chain 34443) in the Base / Superchain ecosystem, ETH gas, DeFi + AI-agent positioning, with a 2 s sequencer cadence and standard blob calldata settlement on Ethereum. The 2026-07-03 sweep excluded Mode with 3 providers; the 2026-07-26 re-audit adds Thirdweb which is now live on Mode, bringing the count to 3 clean keyless providers. Excluded by this re-launch: Tenderly public (no `mode` route), Blast API (discontinued), MeowRPC + PublicNode (no `mode` subdomain). Every provider live-verified with 4 consecutive keyless probes.
Methodology
Mode: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Mode Labs leads at 129 ms; the chain-official endpoint measures 129 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public Mode endpoint that sustains continuous probing, 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Mode-scaled staleness gap (25 blocks at Mode's ~2 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Mode-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public Mode RPC endpoints measured, 2 ranked by p50 latency (24h, 3 regions)
Public Mode RPC endpoints measured
Chain ID 34443, currency ETH. The 3 no-key endpoints answering our probes today, with their current 24h median; 1 of them sits below the 50 % success floor and is listed last. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
Mode Labshttps://mainnet.mode.network129 ms100.0%
dRPChttps://mode.drpc.org457 ms91.6%
1RPChttps://1rpc.io/mode203 ms26.6% ▾
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.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://mode.rpc.thirdweb.com1.3 % success over 24 h
Frequently asked
Which Mode RPCs work without an API key?
4 endpoints are probed on this chain. Every listed endpoint was live-verified with a `eth_getBlockByNumber` POST returning a parsable response before inclusion. See the methodology section for the endpoints that were audited and excluded.
How is Mode RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` POST every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. 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 (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) 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