Fastest free MultiversX RPC, live no-key endpoint latency
HTTP round-trip latency for GET /network/status/4294967295 (metachain nonce) against every available public MultiversX node, audited every 60 seconds from 3 regions.
TL;DR. As of , Elrond API leads rpc latency at 170 ms (p50, 24h) on Fastest free MultiversX RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/multiversx-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
MultiversX (formerly Elrond) is a proof-of-stake L1 blockchain using Secure Proof of Stake (SPoS) with adaptive state sharding, supporting up to 15,000 TPS per shard. The metachain coordinates shard consensus and commits a nonce (block height) approximately every 6 seconds with immediate finality. Public gateway endpoints are available without an API key from the MultiversX Foundation (gateway.multiversx.com and api.multiversx.com) and via the legacy Elrond API domain (api.elrond.com, maintained as an alias). Every provider was live-verified with consecutive metachain status probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to MultiversX. We measure the round-trip latency of a single REST GET to /network/status/4294967295 (metachain) against every available public MultiversX 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 / stale / timeout) with a MultiversX-scaled staleness gap (50 nonces, around 5 min at 6 s/nonce). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the MultiversX-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free MultiversX RPC right now?
Elrond API currently leads at 170 ms (MultiversX metachain nonce 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 MultiversX RPC endpoints work without an API key?
3 endpoints sustain continuous keyless probing at launch: the MultiversX Gateway (gateway.multiversx.com), the MultiversX API (api.multiversx.com), and the Elrond legacy API (api.elrond.com, maintained as a public alias by the MultiversX team). Every listed endpoint was live-verified with a GET /network/status/4294967295 returning a parsable erd_nonce before inclusion.
Does the fastest MultiversX 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 MultiversX RPC latency measured here, technically?
One GET /network/status/4294967295 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