RPCsUpdated

Optimism RPC endpoints: free public URLs by latency

HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Optimism RPC endpoint, audited every 60 seconds from 3 regions.

TL;DR. As of , PublicNode has the lowest median latency of the 7 free public Optimism RPC endpoints measured, 73 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/optimism-rpc. Chain ID 10. 7 public endpoints, no key: optimism-rpc.publicnode.com, optimism.drpc.org, gateway.tenderly.co, optimism-mainnet.rpc.thyme.sh, api.blockvectra.com, op-pokt.nodies.app, mainnet.optimism.io. 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 →

Optimism pits the Foundation's `mainnet.optimism.io` against 7 multi-chain no-key gateways. As on Arbitrum, the official endpoint is documented best-effort, and the measured tail confirms it, while the gateway tier competes on tighter distributions. Probes run every 60 seconds from three regions with full response classification, so an endpoint stuck on an old head is flagged `stale` rather than ranked fast.

Methodology

Optimism: 7 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 73 ms; the chain-official endpoint measures 155 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Optimism endpoint that sustains continuous probing, 7 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 Optimism-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 Optimism-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain="optimism". Provider coverage: 7 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: 7 free public Optimism RPC endpoints ranked by p50 latency (24h, 3 regions)

Optimism RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1PublicNodeAllnodes-operated, 70+ chains, archive on most73 ms84 ms176 ms100.00% (n=4320)
2dRPCDecentralized RPC mesh, consensus-checked88 ms113 ms166 ms96.94% (n=4321)
3TenderlyMulti-chain public gateway, 9 chains, no key93 ms106 ms117 ms100.00% (n=4320)
4Thyme GateThyme Labs-operated, keyless, 22 units/s per IP, no paid fallback110 ms111 ms138 ms100.00% (n=4320)
5BlockVectraKeyless public RPC, 1,000-block history window112 ms179 ms407 ms99.93% (n=4319)
6NodiesPOKT Network's decentralized public RPC successor, 7+ chains141 ms152 ms178 ms99.98% (n=4321)
7OptimismOptimism Foundation public RPC, Optimism mainnet only155 ms159 ms192 ms100.00% (n=4321)

Public Optimism RPC endpoints measured

Chain ID 10, currency ETH. The 7 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.

  • PublicNode logoPublicNodehttps://optimism-rpc.publicnode.com73 ms100.0%
  • dRPC logodRPChttps://optimism.drpc.org88 ms96.9%
  • Tenderly logoTenderlyhttps://gateway.tenderly.co/public/optimism93 ms100.0%
  • Thyme Gate logoThyme Gatehttps://optimism-mainnet.rpc.thyme.sh/public110 ms100.0%
  • BlockVectra logoBlockVectrahttps://api.blockvectra.com/v1/op_mainnet/public112 ms99.9%
  • Nodies logoNodieshttps://op-pokt.nodies.app141 ms100.0%
  • Optimism logoOptimismhttps://mainnet.optimism.io155 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.

Not listed on Optimism

  • Ankr: public endpoint requires an API key
  • NodeReal: requires an API key
  • GetBlock: requires an API key; compared on the keyed pages
  • Chainstack: requires an API key; compared on the keyed pages
  • 1RPC: delisted for reliability: under 13 % success at one probe per minute (since 2026-07-09)
  • gateway.fm: 29 requests per IP budget, too small for continuous probing
  • LlamaRPC: Cloudflare 521 from the probe regions
  • BlockPI: Cloudflare 521 from the probe regions
  • OmniaTech: Cloudflare 521 from the probe regions
  • Alchemy demo: rate-limited public demo endpoint; the keyed tier is compared on the keyed pages

Frequently asked

Which Optimism RPCs work without an API key?

The 7 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.

Do Base and Optimism RPCs perform the same since both are OP Stack?

No. The stack is shared but the infrastructure is not: different operators, different peering, different gateway coverage. Our measurements regularly show different leaders and different tail behavior on the two chains. If you deploy on both, pick the RPC per chain from each page rather than assuming OP Stack parity.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities