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, 76 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`. Lava's keyless `sonic.lava.build` answered until 2026; it returns 410 Gone and left the cohort on 2026-10-19. 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 76 ms; the chain-official endpoint measures 114 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.
- 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 Sonic-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain="sonic". Provider coverage: 4 no-key public-read endpoints live today, each listed with its URL in the endpoints table on this page. Exclusions follow the cluster-wide rules documented on the parent benchmark.
Results: 4 free public Sonic RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNodeAllnodes-operated, 70+ chains, archive on most | 76 ms | 89 ms | 208 ms | 99.98% (n=4319) |
| 2 | TenderlyMulti-chain public gateway, no key | 106 ms | 113 ms | 122 ms | 100.00% (n=4319) |
| 3 | Sonic LabsSonic Labs public RPC, Sonic mainnet only | 114 ms | 131 ms | 138 ms | 100.00% (n=4320) |
| 4 | dRPCDecentralized RPC mesh, consensus-checked | 163 ms | 288 ms | 484 ms | 99.79% (n=4318) |
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.com76 ms100.0%Tenderly
https://gateway.tenderly.co/public/sonic106 ms100.0%
Sonic Labshttps://rpc.soniclabs.com114 ms100.0%
dRPChttps://sonic.drpc.org163 ms99.8%
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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities