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 4 free public Unichain RPC endpoints measured, 70 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/unichain-rpc. Chain ID 130. 4 public endpoints, no key: unichain-rpc.publicnode.com, gateway.tenderly.co, unichain.drpc.org, mainnet.unichain.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 →
Unichain, Uniswap Labs' OP Stack rollup, fields 4 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: 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 70 ms; the chain-official endpoint measures 129 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, 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 Unichain-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Unichain RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 70 ms | 87 ms | 147 ms | 100.00% |
| 2 | Tenderly | 106 ms | 112 ms | 118 ms | 100.00% |
| 3 | dRPC | 113 ms | 140 ms | 195 ms | 99.40% |
| 4 | Unichain (Uniswap Labs) | 129 ms | 144 ms | 155 ms | 100.00% |
Public Unichain RPC endpoints measured
Chain ID 130, 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.
PublicNodehttps://unichain-rpc.publicnode.com70 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/unichain106 ms100.0%
dRPChttps://unichain.drpc.org113 ms99.4%
Unichain (Uniswap Labs)https://mainnet.unichain.org129 ms100.0%
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 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.
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 70 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