RPCsLive

Hedera RPC endpoints: free public URLs by latency

HTTP round-trip latency for eth_getBlockByNumber against every available public Hedera EVM-compatible node, audited every 60 seconds from 3 regions.

TL;DR. As of , Hashio is the only one of the 2 free public Hedera RPC endpoints answering our probes, at 155 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/hedera-rpc.

Companion page

Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →

Hedera is a proof-of-stake public distributed ledger using the Hashgraph consensus algorithm (asynchronous Byzantine Fault Tolerant), targeting high throughput and deterministic finality in under 3 seconds. Hedera exposes an EVM-compatible JSON-RPC layer via Hashio, allowing standard eth_getBlockByNumber calls. Public EVM-compatible endpoints are available without an API key from Hashio (operated by the Hedera Foundation) and thirdweb. Every provider was live-verified with consecutive eth_getBlockByNumber probes at launch.

Methodology

Hedera: 1 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Hashio leads at 155 ms. We measure the round-trip latency of a single eth_getBlockByNumber ("latest", false) call against every available public Hedera EVM node that sustains continuous probing: 1 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 Hedera-scaled staleness gap (100 blocks, around 5 min at 3 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Hedera-scoped answer with per-region breakdowns as a first-class dimension.

Results: 1 free public Hedera RPC endpoint ranked by p50 latency (24h, 3 regions)

Hedera RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1Hashio155 ms180 ms354 ms100.00%

Public Hedera RPC endpoints measured

The 1 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.

  • Hashio logoHashiohttps://mainnet.hashio.io/api155 ms100.0%

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.

  • thirdwebhttps://295.rpc.thirdweb.com0.3 % success over 24 h

Frequently asked

Which Hedera RPC endpoints work without an API key?

2 endpoints are probed on this chain: Hashio (mainnet.hashio.io/api, operated by the Hedera Foundation) and thirdweb (295.rpc.thirdweb.com). Every listed endpoint was live-verified with an eth_getBlockByNumber call returning a parsable block number before inclusion.

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