Sonic RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Sonic RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 4 free public Sonic RPC endpoints measured, 71 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/sonic-rpc. Chain ID 146. 4 public endpoints, no key: sonic-rpc.publicnode.com, gateway.tenderly.co, rpc.soniclabs.com, sonic.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 →
Sonic ties Gnosis for the largest cohort in the long-tail expansion: 4 no-key providers, including Sonic Labs' own `rpc.soniclabs.com` and the only keyless Lava endpoint outside Ethereum and Arbitrum, `sonic.lava.build` answers no-key while every other Lava subdomain 403s without an API key. Every provider gets the identical `eth_getBlockByNumber` probe every 60 seconds from us-east, eu-west and Singapore, with stale-head detection against the cross-provider tip.
Methodology
Sonic: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 71 ms; the chain-official endpoint measures 112 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Sonic 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 Sonic-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Sonic RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 71 ms | 80 ms | 229 ms | 100.00% |
| 2 | Tenderly | 107 ms | 113 ms | 122 ms | 100.00% |
| 3 | Sonic Labs | 112 ms | 113 ms | 2.31 s | 100.00% |
| 4 | dRPC | 179 ms | 350 ms | 455 ms | 99.33% |
Public Sonic RPC endpoints measured
Chain ID 146, currency S. 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.
PublicNodehttps://sonic-rpc.publicnode.com71 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/sonic107 ms100.0%
Sonic Labshttps://rpc.soniclabs.com112 ms100.0%
dRPChttps://sonic.drpc.org179 ms99.3%
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 Sonic 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.
Why does Lava appear on Sonic but on no other long-tail chain?
Lava publishes `*.lava.build` subdomains for many chains, but nearly all of them return 403 without an API key. `sonic.lava.build` is the exception: it passed our no-key verification (eth_chainId match plus sustained probing) and has held the 60-second cadence since. Every (provider, chain) pair in this cluster is admitted on measured behavior, not on a provider's published chain list.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities