XPLA RPC endpoints: free public URLs by latency
HTTP round-trip latency for the Tendermint `status` method against every free, no-key public XPLA Cosmos SDK endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 3 free public XPLA RPC endpoints measured, 87 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/xpla-rpc. 3 public endpoints, no key: xpla-rpc.publicnode.com, xpla-rpc.polkachu.com, dimension-rpc.xpla.dev. 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 →
XPLA is a Cosmos SDK chain (dimension_37-1). Three public Tendermint RPCs answered on 2026-10-07: the XPLA official endpoint (dimension-rpc.xpla.dev), PublicNode and Polkachu. One detail worth recording because it changes the count: the registry's Allnodes entry resolves to PublicNode's host, so it is the same endpoint under two names and appears once here rather than twice.
Methodology
XPLA: 3 free public RPC endpoints answering Tendermint status every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 87 ms; the chain-official endpoint measures 132 ms. We measure the round-trip latency of a single Tendermint `status` call against every no-key public XPLA endpoint that sustains continuous probing, 3 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a XPLA-scaled staleness gap (20 blocks at XPLA's ~5 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the XPLA-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public XPLA RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 87 ms | 218 ms | 308 ms | 100.00% |
| 2 | Polkachu | 125 ms | 138 ms | 310 ms | 100.00% |
| 3 | XPLA | 132 ms | 140 ms | 147 ms | 100.00% |
Public XPLA 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.
PublicNodehttps://xpla-rpc.publicnode.com87 ms100.0%
Polkachuhttps://xpla-rpc.polkachu.com125 ms100.0%
XPLAhttps://dimension-rpc.xpla.dev132 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 XPLA RPCs work without an API key?
3 endpoints are probed on this chain: XPLA (dimension-rpc.xpla.dev), PublicNode (xpla-rpc.publicnode.com), Polkachu (xpla-rpc.polkachu.com). Every listed endpoint was live-verified with a Tendermint status call returning a parsable response before inclusion.
How is XPLA RPC latency measured here, technically?
One identical Tendermint status call every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Why does XPLA show PublicNode but not Allnodes?
They are the same endpoint. The Cosmos registry lists an Allnodes entry for XPLA whose address resolves to PublicNode's host, so counting both would inflate the roster with a duplicate and make the board look wider than it is. We keep the operator that actually serves the request. The same rule applies across this cluster: one host, one row.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities