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.
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 dRPC, Lava, Nethermind, OnFinality and 1RPC. Every provider was live-verified with consecutive keyless starknet_blockNumber probes at launch.
Methodology
Starknet: 2 free public RPC endpoints answering `starknet_blockNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Lava Network leads at 521 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: 2 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.
Results: measurement paused since 2026-09-08, last ranking of 2 free public Starknet RPC endpoints
| № | Providers | p50 | p90 | p99 | Success | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Measured, not ranked: sample below the ranking floor | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| not ranked | Lava Network | 521 ms | 846 ms | 1.25 s | 23.44% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| not ranked | OnFinality | 800 ms | 1.02 s | 2.69 s | 10.14% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Public Starknet RPC endpoints measured
The 2 no-key endpoints answering our probes today, with their current 24h median; 2 of them sit below the 50 % success floor and are 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.
Lava Networkhttps://rpc.starknet.lava.build521 ms23.4% ▾
OnFinalityhttps://starknet.api.onfinality.io/public800 ms10.1% ▾
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.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- 1RPC
https://public.1rpc.io/starknet0.0 % success over 24 h
Frequently asked
What is the fastest free Starknet RPC right now?
Lava Network currently leads at 521 ms (starknet_blockNumber p50 over the last 24h), measured against 5 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Starknet RPCs work without an API key?
5 endpoints sustain continuous keyless probing at launch: dRPC, Lava Network, Nethermind, OnFinality and 1RPC. Every listed endpoint was live-verified with a starknet_blockNumber POST returning a parsable block number before inclusion.
Does the fastest Starknet RPC change by region?
Often. Public infra concentrates in specific regions; a gateway that wins from Amsterdam can lose from Singapore by multiples. The region tabs at the top of the page re-scope every number to a single origin.
How is Starknet RPC latency measured here, technically?
One identical starknet_blockNumber POST every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus quantile_over_time over 24 hours.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities