Moonbeam RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Moonbeam RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , dRPC is the only one of the 2 free public Moonbeam RPC endpoints answering our probes, at 263 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/moonbeam-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Moonbeam, the EVM chain of the Polkadot ecosystem, fields 4 no-key descoped cluster-wide to Ethereum and Arbitrum after its keyless per-IP daily budget proved too tight for continuous multi-chain probing; the remaining cohort covers the multi-chain gateways plus the chain-official endpoint. Probes every 60 seconds from three regions with the cluster's anti-cache payload.
Methodology
Moonbeam: 1 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. dRPC leads at 263 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Moonbeam endpoint that sustains continuous probing, 1 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 Moonbeam-scoped answer with per-region breakdowns as a first-class dimension.
Results: measurement paused since 2026-08-19, last ranking of 1 free public Moonbeam RPC endpoint
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | dRPC | 263 ms | 342 ms | 1.52 s | 91.40% |
Public Moonbeam RPC endpoints measured
Chain ID 1284, currency GLMR. The 1 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.
dRPChttps://moonbeam.drpc.org263 ms91.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.
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.
- Tenderly
https://gateway.tenderly.co/public/moonbeam0.0 % success over 24 h
Frequently asked
What is the fastest free Moonbeam RPC right now?
dRPC currently leads at 263 ms (`eth_getBlockByNumber` p50 over the last 24h), measured against 4 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples, so the answer on this page is the answer right now, not a quarterly snapshot. Use the region tabs to see the leader from the origin closest to your deployment.
Which Moonbeam RPCs work without an API key?
Four endpoints sustain continuous keyless probing: PublicNode, dRPC, Tenderly Gateway and the Moonbeam Foundation's official endpoint. 1RPC was descoped cluster-wide to Ethereum and Arbitrum because its keyless per-IP daily budget cannot sustain continuous multi-chain probing. Every listed endpoint was live-verified (eth_chainId match + anti-cache probe) before inclusion.
Does the fastest Moonbeam RPC change by region?
Frequently. The headline number averages three probe origins (us-east, eu-west, Singapore), but per-region leaders regularly diverge, a gateway that wins from Virginia can lose from Singapore by multiples. The region tabs at the top of the page re-scope every number on the page to a single origin; pick the one closest to where your requests actually originate.
How is Moonbeam RPC latency measured here?
One identical JSON-RPC POST (`eth_getBlockByNumber`) 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 (`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. The harness is open source and every number on this page is a public Prometheus query you can run yourself.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities