Fastest free Ink RPC, live no-key EVM endpoint latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public Ink EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Ink (QuickNode) leads rpc latency at 174 ms (p50, 24h) on Fastest free Ink RPC, live no-key EVM endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/ink-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Ink is an OP Stack rollup (chain 57073) launched by Kraken in late 2024, DeFi-first positioning with ETH gas and a native ecosystem incentive program. Standard EVM JSON-RPC. Kraken operates two active-active official endpoints (Gelato-backed `rpc-gel` and QuickNode-backed `rpc-qnd`) so both appear on this leaderboard. Excluded by the launch audit: Alchemy public (chain not enabled on public tier), Blast API (API no longer available). Every provider live-verified with 4 consecutive keyless probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to Ink. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public Ink endpoint that sustains continuous probing, 4 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 Ink-scaled staleness gap (25 blocks at Ink's ~1 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Ink-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Ink RPC right now?
Ink (QuickNode) currently leads at 174 ms (`eth_getBlockByNumber("latest", false)` p50 over the last 24h), measured against 4 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples, so the answer on this page is the answer right now, not a quarterly snapshot. Use the region tabs to see the leader from the origin closest to your deployment.
Which Ink RPCs work without an API key?
5 endpoints sustain continuous keyless probing at launch: Gelato, QuickNode, dRPC, Tenderly Gateway. Every listed endpoint was live-verified with a `eth_getBlockByNumber("latest", false)` POST returning a parsable response before inclusion. See the methodology section for the specific endpoints that were audited and excluded.
Does the fastest Ink 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; pick the one closest to where your requests originate.
How is Ink RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` 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. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities