RPCsUpdated

Interlay RPC endpoints: free public URLs by latency

HTTP round-trip latency for Substrate chain_getHeader queries against every available public Interlay 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 →

Interlay is a Polkadot parachain that brings trustless Bitcoin to DeFi; it issues iBTC, a fully Bitcoin-backed asset, by locking BTC in a decentralized vault system without wrapping or custodians. Interlay uses the Substrate framework and exposes a standard Substrate JSON-RPC interface; block height is queried via chain_getHeader. The Interlay official node (api.interlay.io/parachain) is the only consistently available keyless public endpoint. Every provider was live-verified with consecutive block-height probes at launch.

Methodology

Interlay: 0 free public RPC endpoints answering `chain_getHeader` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Interlay leads at 381 ms; the chain-official endpoint measures 381 ms. We measure the round-trip latency of a Substrate chain_getHeader query against every available public Interlay endpoint that sustains continuous probing: 0 providers live today, every 60 seconds, from us-east, eu-west and Singapore. Each provider is probed via a JSON-RPC POST (chain_getHeader) from which the block number is extracted. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Polkadot-scaled staleness gap (40 blocks, around 8 min at 12 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Interlay-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":"chain_getHeader","params":[]}. The result contains a number field (hex-encoded block number).
  • 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 Interlay-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain=interlay. Provider coverage today: 0 endpoint (Interlay official api.interlay.io/parachain).

Frequently asked

Which Interlay RPC endpoints work without an API key?

The Interlay official node at api.interlay.io/parachain sustains continuous keyless probing. Other providers (OnFinality, Dwellir) were tested but returned connection errors; only the official node was live-verified before inclusion.

What is Interlay and why does its RPC latency matter?

Interlay issues iBTC, a 1:1 Bitcoin-backed asset on Polkadot secured by decentralized vaults. Developers integrating iBTC, building vault monitoring tools, or querying collateral positions need reliable low-latency RPC access. Knowing which public endpoint is fastest from your region matters for application responsiveness.

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