MultiversX RPC endpoints: free public URLs by 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 , MultiversX Gateway has the lowest median latency of the 3 free public MultiversX RPC endpoints measured, 87 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/multiversx-rpc. 3 public endpoints, no key: gateway.multiversx.com, api.elrond.com, api.multiversx.com. 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 →
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
MultiversX: 3 free public RPC endpoints answering HTTP GET /network/status/4294967295 every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. MultiversX Gateway leads at 87 ms. 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 live today, 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.
Results: 3 free public MultiversX RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | MultiversX Gateway | 87 ms | 101 ms | 193 ms | 100.00% |
| 2 | Elrond API | 129 ms | 144 ms | 354 ms | 99.84% |
| 3 | MultiversX API | 130 ms | 145 ms | 211 ms | 100.00% |
Public MultiversX RPC endpoints measured
The 3 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.
MultiversX Gatewayhttps://gateway.multiversx.com87 ms100.0%- EAElrond API
https://api.elrond.com129 ms99.8% - MultiversX API
https://api.multiversx.com130 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.
Frequently asked
Which MultiversX RPC endpoints work without an API key?
3 endpoints are probed on this chain: 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities