MegaETH RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public MegaETH RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , MegaETH Official has the lowest median latency of the 3 free public MegaETH RPC endpoints measured, 28 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/megaeth-rpc. Chain ID 4326. 3 public endpoints, no key: mainnet.megaeth.com, megaeth.drpc.org, megaeth.gateway.tenderly.co. 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 →
MegaETH markets itself as the real-time Ethereum L2. 10 ms mini-blocks batched into 1 s EVM blocks, data availability on EigenDA and ZK fraud proofs via Kailua, live on mainnet since February 2026. Marketing aside, builders still reach it through ordinary JSON-RPC, and the free tier of that surface is what this page measures. the official mainnet.megaeth.com endpoint plus dRPC and Tenderly Gateway, probed every 60 seconds from three regions with the cluster's anti-cache payload. The chain's 10 ms story lives on its WebSocket realtime API; the HTTP numbers below are what a wallet, indexer or bot actually experiences when polling.
Methodology
MegaETH: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. MegaETH Official leads at 28 ms; the chain-official endpoint measures 28 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public MegaETH endpoint that sustains continuous probing, 3 providers, every 30 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 MegaETH-scoped answer with per-region breakdowns first-class.
Results: 3 free public MegaETH RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | MegaETH Official | 28 ms | 45 ms | 108 ms | 100.00% |
| 2 | dRPC | 86 ms | 117 ms | 183 ms | 99.75% |
| 3 | Tenderly Gateway | 106 ms | 113 ms | 129 ms | 100.00% |
Public MegaETH RPC endpoints measured
Chain ID 4326, currency ETH. 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.
MegaETH Officialhttps://mainnet.megaeth.com/rpc28 ms100.0%
dRPChttps://megaeth.drpc.org86 ms99.7%
Tenderly Gatewayhttps://megaeth.gateway.tenderly.co106 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 MegaETH RPCs work without an API key in 2026?
3 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.
Does this page measure MegaETH's 10 ms real-time claim?
No, and deliberately so. The 10 ms figure refers to sequencer mini-blocks delivered over the WebSocket realtime API; this page measures the plain HTTP JSON-RPC surface that wallets, indexers and most tooling actually poll. Both numbers are real, they describe different transport layers. A WebSocket-level benchmark is a separate methodology.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities