RPCsUpdated

Linea RPC endpoints: free public URLs by latency

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

TL;DR. As of , PublicNode has the lowest median latency of the 3 free public Linea RPC endpoints measured, 77 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/linea-rpc. Chain ID 59144. 3 public endpoints, no key: linea-rpc.publicnode.com, gateway.tenderly.co, linea.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 →

The no-key field thins out on Linea: 3 providers qualify, all multi-chain gateways. Thinner competition makes the reliability columns matter more than raw speed, a fast endpoint with a high stale or timeout rate is a worse default than a slightly slower consistent one. Probes run every 60 seconds from us-east, eu-west and Singapore with full response classification.

Methodology

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

Linea RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1PublicNodeAllnodes-operated, 70+ chains, archive on most77 ms93 ms185 ms99.95% (n=4318)
2TenderlyMulti-chain public gateway, 9 chains, no key153 ms161 ms217 ms100.00% (n=4321)
3dRPCDecentralized RPC mesh, consensus-checked162 ms295 ms432 ms99.93% (n=4320)

Public Linea RPC endpoints measured

Chain ID 59144, currency ETH. The 3 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://linea-rpc.publicnode.com77 ms100.0%
  • Tenderly logoTenderlyhttps://gateway.tenderly.co/public/linea153 ms100.0%
  • dRPC logodRPChttps://linea.drpc.org162 ms99.9%

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 Linea RPCs work without an API key?

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

Why do so few free RPCs support Linea?

Free-tier coverage follows demand: gateways add no-key chains when traffic justifies the infrastructure. Linea's cohort (3 providers) is typical of newer L2s; the Ethereum and Arbitrum pages list their own live counts. The flip side is that the providers that do qualify are the disciplined multi-chain operators, so the measured success rates (listed in the endpoints table) stay high even where the field is thin.

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