Ink RPC endpoints: free public URLs by 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 , QuickNode has the lowest median latency of the 4 free public Ink RPC endpoints measured, 75 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/ink-rpc. Chain ID 57073. 4 public endpoints, no key: rpc-qnd.inkonchain.com, rpc-gel.inkonchain.com, ink.gateway.tenderly.co, ink.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 →
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 a pair of 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
Ink: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. QuickNode leads at 75 ms; the chain-official endpoint measures 93 ms. 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 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 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.
Results: 4 free public Ink RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | QuickNode | 75 ms | 85 ms | 117 ms | 100.00% (n=4341) |
| 2 | Gelato | 93 ms | 116 ms | 366 ms | 100.00% (n=4326) |
| 3 | Tenderly Gateway | 94 ms | 101 ms | 135 ms | 100.00% (n=4343) |
| 4 | dRPC | 129 ms | 185 ms | 562 ms | 99.84% (n=4324) |
Public Ink RPC endpoints measured
Chain ID 57073, currency ETH. The 4 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.
QuickNodehttps://rpc-qnd.inkonchain.com75 ms100.0%
Gelatohttps://rpc-gel.inkonchain.com93 ms100.0%
Tenderly Gatewayhttps://ink.gateway.tenderly.co94 ms100.0%
dRPChttps://ink.drpc.org129 ms99.8%
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 Ink RPCs work without an API key?
4 endpoints are probed on this chain; each is listed with its URL, 24h median and success rate in the endpoints table on this page, and the list changes as providers come and go.
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