Superseed RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public Superseed EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Superseed has the lowest median latency of the 2 free public Superseed RPC endpoints measured, 138 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/superseed-rpc. 2 public endpoints, no key: mainnet.superseed.xyz, superseed.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 →
Superseed is an OP Stack L2 (chain 5330). The 2026-10-07 sweep found 2 clean keyless endpoints: the Superseed official RPC (mainnet.superseed.xyz), dRPC (superseed.drpc.org) and Thirdweb (5330.rpc.thirdweb.com), all three returning chain id 0x14d2. PublicNode carries no Superseed route, which is worth noting because it serves most OP Stack chains: the absence is the provider's choice, not a measurement failure on our side.
Methodology
Superseed: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Superseed leads at 138 ms; the chain-official endpoint measures 138 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public Superseed endpoint that sustains continuous probing, 2 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Superseed-scaled staleness gap (20 blocks at Superseed's ~2 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Superseed-scoped answer with per-region breakdowns as a first-class dimension.
Results: 2 free public Superseed RPC endpoints ranked by p50 latency (24h, 3 regions)
Public Superseed RPC endpoints measured
The 2 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.
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.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://5330.rpc.thirdweb.com0.7 % success over 24 h
Frequently asked
Which Superseed RPCs work without an API key?
3 endpoints are probed on this chain: Superseed (mainnet.superseed.xyz), dRPC (superseed.drpc.org), Thirdweb (5330.rpc.thirdweb.com). Every listed endpoint was live-verified with a `eth_getBlockByNumber` call returning a parsable response before inclusion.
How is Superseed RPC latency measured here, technically?
One identical `eth_getBlockByNumber` call 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.
Why is PublicNode missing from the Superseed roster?
PublicNode has no Superseed route. It serves most OP Stack L2s, so its absence here is a coverage gap on the provider's side rather than something our probe failed to reach. We list only endpoints that answered a real `eth_getBlockByNumber` POST without a key, so a provider that does not route the chain is excluded rather than shown with an asterisk.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities