Unichain RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Unichain RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 5 free public Unichain RPC endpoints measured, 83 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/unichain-rpc. Chain ID 130. 5 public endpoints, no key: unichain-rpc.publicnode.com, gateway.tenderly.co, mainnet.unichain.org, unichain.drpc.org, api.blockvectra.com. 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 →
Unichain, Uniswap Labs' OP Stack rollup, fields 5 no-key providers including the house `mainnet.unichain.org`. For a chain this young the gateway coverage is unusually complete, PublicNode, dRPC and Tenderly all sustain no-key probing at our 60-second cadence, so the official endpoint faces a full gateway tier from day one. Three regions, identical probes, stale-head detection.
Methodology
Unichain: 5 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 83 ms; the chain-official endpoint measures 117 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Unichain endpoint that sustains continuous probing, 5 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 Unichain-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 Unichain-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain="unichain". Provider coverage: 5 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: 5 free public Unichain RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNodeAllnodes-operated, 70+ chains, archive on most | 83 ms | 97 ms | 239 ms | 99.88% (n=4320) |
| 2 | TenderlyMulti-chain public gateway, no key | 105 ms | 112 ms | 120 ms | 100.00% (n=4319) |
| 3 | Unichain (Uniswap Labs)Uniswap Labs public RPC, Unichain mainnet only | 117 ms | 125 ms | 370 ms | 100.00% (n=4320) |
| 4 | dRPCDecentralized RPC mesh, consensus-checked | 148 ms | 183 ms | 243 ms | 99.81% (n=4320) |
| 5 | BlockVectraBlockVectra keyless public Unichain endpoint (3 req/s per IP, 1,000-block history window) | 159 ms | 256 ms | 884 ms | 98.40% (n=4317) |
Public Unichain RPC endpoints measured
Chain ID 130, currency ETH. The 5 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://unichain-rpc.publicnode.com83 ms99.9%Tenderly
https://gateway.tenderly.co/public/unichain105 ms100.0%
Unichain (Uniswap Labs)https://mainnet.unichain.org117 ms100.0%
dRPChttps://unichain.drpc.org148 ms99.8%BlockVectra
https://api.blockvectra.com/v1/unichain_mainnet/public159 ms98.4%
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 Unichain RPCs work without an API key?
The 5 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.
Should I use mainnet.unichain.org or a gateway for Unichain?
Check the region tab nearest your deployment. Chain-official endpoints are typically a single origin, so they can only be close to one of our three probes, while anycast gateways answer everywhere. On the 3-region average the current leader is PublicNode at 83 ms; a primary-plus-fallback pair from the top of this page is the resilient default for a chain this young.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities