Fastest free EOS RPC, live no-key endpoint latency
HTTP round-trip latency for GET /v1/chain/get_info against every available public EOS (Antelope) node, audited every 60 seconds from 3 regions.
TL;DR. As of , EOS Nation leads rpc latency at 220 ms (p50, 24h) on Fastest free EOS RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/eos-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
EOS is a delegated proof-of-stake (DPoS) blockchain built on the Antelope protocol, producing one block every 0.5 seconds across 21 elected block producers. The chain provides a REST chain API under /v1/chain/ allowing standard queries without an API key. Public endpoints are available from Greymass, EOS Nation and Aloha EOS. Every provider was live-verified with consecutive get_info probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to EOS. We measure the round-trip latency of a single REST call (GET /v1/chain/get_info) against every available public EOS node that sustains continuous probing: 3 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 an EOS-scaled staleness gap (600 blocks, around 5 min at 0.5 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the EOS-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free EOS RPC right now?
EOS Nation currently leads at 220 ms (EOS head block number p50 over the last 24h), measured against 3 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which EOS RPC endpoints work without an API key?
3 endpoints sustain continuous keyless probing at launch: Greymass (eos.greymass.com), EOS Nation (eos.api.eosnation.io) and Aloha EOS (api.main.alohaeos.com). Every listed endpoint was live-verified with a get_info call returning a parsable head_block_num before inclusion.
Does the fastest EOS 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 EOS RPC latency measured here, technically?
One GET /v1/chain/get_info REST call every 60 seconds against each provider from each of 3 regions. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus quantile_over_time over 24 hours. Best-effort measurements; p50 is the median, p90 the 90th percentile and p99 the 99th percentile of latency samples collected over the last 24 hours.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities