RPCsUpdated

Starknet RPC endpoints: free public URLs by latency

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

TL;DR. As of , PublicNode has the lowest median latency of the 2 free public Starknet RPC endpoints measured above the 50 % success floor (3 listed), 85 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/starknet-rpc. 3 public endpoints, no key: starknet-rpc.publicnode.com, api.zan.top, starknet.api.onfinality.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 →

Starknet is a ZK-Rollup on Ethereum using STARK proofs for validity. Blocks finalize on Ethereum L1. Free public RPC endpoints are available without an API key from OnFinality, PublicNode and ZAN. Lava, 1RPC, Nethermind's free endpoint and dRPC's keyless Starknet route stopped answering in 2026 and were removed on 2026-10-19.

Methodology

Starknet: 3 free public RPC endpoints answering `starknet_blockNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 85 ms. We measure the round-trip latency of a single, identical JSON-RPC call (starknet_blockNumber) against every no-key public Starknet endpoint that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Starknet-scaled staleness gap. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Starknet-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":"starknet_blockNumber","params":[]}. 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 Starknet-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain=starknet. Provider coverage today: 3 no-key endpoints (OnFinality, PublicNode, ZAN).

Results: 3 free public Starknet RPC endpoints measured, 2 ranked by p50 latency (24h, 3 regions)

Starknet RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1PublicNodeAllnodes' free public RPC, no key, no sign-up85 ms99 ms246 ms99.91% (n=4318)
2ZANAnt Digital Technologies' node service, public Starknet endpoint without a key424 ms672 ms1.00 s99.93% (n=4316)
Measured, not ranked: sample below the ranking floor
not rankedOnFinalityGlobal multi-chain gateway, 70+ networks, rate-limited public tier, 5 req/sec173 ms533 ms1.74 s22.99% (n=4321)

Public Starknet RPC endpoints measured

The 3 no-key endpoints answering our probes today, with their current 24h median; 1 of them sits below the 50 % success floor and is listed last. 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://starknet-rpc.publicnode.com85 ms99.9%
  • ZAN logoZANhttps://api.zan.top/public/starknet-mainnet424 ms99.9%
  • OnFinality logoOnFinalityhttps://starknet.api.onfinality.io/public173 ms23.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.

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