RPCsLive

Fastest free Starknet RPC, live no-key endpoint 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 , Lava Network leads rpc latency at 297 ms (p50, 24h) on Fastest free Starknet RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/starknet-rpc.

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

Per-chain member of the RPC latency cluster, extended to Starknet. 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: 5 providers at launch, 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.

Frequently asked

What is the fastest free Starknet RPC right now?

Lava Network currently leads at 297 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