Soneium RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Soneium RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Soneium has the lowest median latency of the 4 free public Soneium RPC endpoints measured, 42 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/soneium-rpc. Chain ID 1868. 4 public endpoints, no key: rpc.soneium.org, soneium-rpc.publicnode.com, gateway.tenderly.co, soneium.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 →
Soneium, Sony's OP Stack rollup, is the long-tail chain where the official endpoint actually wins: `rpc.soneium.org` measures 42 ms on the 3-region average against 42 ms for the current leader Soneium, distributed official infrastructure that answers near every probe origin while keeping fresh heads in our stale detection. 4 no-key providers, the identical `eth_getBlockByNumber` call every 60 seconds from us-east, eu-west and Singapore.
Methodology
Soneium: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Soneium leads at 42 ms; the chain-official endpoint measures 42 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Soneium endpoint that sustains continuous probing, 4 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 Soneium-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Soneium RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Soneium | 42 ms | 49 ms | 91 ms | 100.00% |
| 2 | PublicNode | 74 ms | 87 ms | 275 ms | 100.00% |
| 3 | Tenderly | 106 ms | 112 ms | 120 ms | 100.00% |
| 4 | dRPC | 254 ms | 312 ms | 475 ms | 77.23% |
Public Soneium RPC endpoints measured
Chain ID 1868, currency ETH. The 4 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.
Soneiumhttps://rpc.soneium.org42 ms100.0%
PublicNodehttps://soneium-rpc.publicnode.com74 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/soneium106 ms100.0%
dRPChttps://soneium.drpc.org254 ms77.2%
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 Soneium RPCs work without an API key?
The 4 providers on this page are listed with their URLs in the endpoints table above. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.
Is the official Soneium RPC actually the best choice?
Currently yes, and that is unusual: across the 12-chain long-tail expansion only two chains resist the gateway tier, and `rpc.soneium.org` is the clearest case, leading the 3-region average at around 17 ms while our stale-head checks stay clean. The usual free-tier caveats (no SLA, shared limits) still apply, so keep dRPC or PublicNode wired as fallback.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities