Moonriver RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public Moonriver EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , OnFinality has the lowest median latency of the 3 free public Moonriver RPC endpoints measured, 55 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/moonriver-rpc. Chain ID 1285. 3 public endpoints, no key: moonriver.api.onfinality.io, moonriver.unitedbloc.com, moonriver.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 →
Moonriver is the Kusama canary network for Moonbeam (chain 1285), a full EVM parachain with Ethereum-compatible tooling, MOVR gas token, ~12 s block time under Nominated Proof of Stake, serving as the staging ground for Moonbeam features before they reach Polkadot. The 2026-10-09 audit confirms 3 clean keyless providers: OnFinality (moonriver.api.onfinality.io/public), dRPC (moonriver.drpc.org) and UnitedBloc (moonriver.unitedbloc.com). The last two were excluded in August, dRPC for having no Moonriver route and UnitedBloc for dead DNS, and both answer again on the current head. Excluded now: the Moonbeam Foundation endpoint (rpc.api.moonriver.moonbeam.network refuses the TLS handshake from two independent client stacks), PublicNode (moonriver-rpc.publicnode.com answers 404, the chain was dropped), Ankr (requires a key for Moonriver).
Methodology
Moonriver: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. OnFinality leads at 55 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public Moonriver endpoint that sustains continuous probing, 3 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Moonriver-scaled staleness gap (20 blocks at Moonriver's ~12 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Moonriver-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 Moonriver-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="moonriver"`. Provider coverage: 3 no-key endpoints. Cohort rebuilt 2026-10-09: the Foundation endpoint and PublicNode dropped, dRPC and UnitedBloc restored after both answered on the current head on 10 of 10 probes.
Results: 3 free public Moonriver RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | OnFinalityOnFinality shared node service public endpoint for Moonriver | 55 ms | 229 ms | 1.05 s | 99.86% (n=4309) |
| 2 | UnitedBlocUnitedBloc community-operated public RPC | 126 ms | 130 ms | 751 ms | 54.61% (n=4326) |
| 3 | dRPCDecentralized RPC mesh, consensus-checked | 198 ms | 380 ms | 1.29 s | 98.01% (n=4327) |
Public Moonriver RPC endpoints measured
Chain ID 1285, currency MOVR. 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.
OnFinalityhttps://moonriver.api.onfinality.io/public55 ms99.9%
UnitedBlochttps://moonriver.unitedbloc.com126 ms54.6%
dRPChttps://moonriver.drpc.org198 ms98.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 Moonriver RPCs work without an API key?
3 endpoints are probed on this chain, each listed with its URL in the endpoints table above.
How is Moonriver 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