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 , OnFinality is the only free public Moonbeam RPC endpoint measured, at 56 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 3 no-key public endpoints that sustain continuous probing. The cohort was rebuilt on 2026-10-09: PublicNode stopped serving the chain and answers 404 on every hostname it published, Tenderly's public gateway answers 404, and the Foundation endpoint refuses the TLS handshake from two independent client stacks. OnFinality and UnitedBloc took their place, each verified on the same head as dRPC before inclusion; UnitedBloc's host has answered 502 since and left on 2026-10-19. 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. OnFinality leads at 56 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.
- 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 on this page 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 Moonbeam-scoped view of the same harness, with the same exclusion rules.
- Cohort rebuilt 2026-10-09. Dropped: PublicNode and Tenderly, both 404, and the Foundation endpoint, which refuses the TLS handshake from two independent client stacks (LibreSSL 3.3.6 and OpenSSL 3.5.5), so it cannot be measured from here whatever the cause. Added: OnFinality and UnitedBloc, each probed with `eth_getBlockByNumber` and kept only after returning dRPC's head on 10 of 10 tries.
Results: 1 free public Moonbeam RPC endpoint ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | OnFinalityOnFinality shared node service public endpoint | 56 ms | 1.77 s | 6.92 s | 93.96% (n=4320) |
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities