RPCsUpdated

CONX (ex-XPLA) RPC endpoints: free public URLs

HTTP round-trip latency for the Tendermint `status` method against every free, no-key public CONX (ex-XPLA) Cosmos SDK endpoint, audited every 60 seconds from 3 regions.

TL;DR. As of , PublicNode posts the lowest RPC latency at 96 ms (p50, 24h) across 3 ranked providers. 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 →

CONX is a Cosmos SDK chain (dimension_37-1), known as XPLA until a governance proposal renamed the token, its symbol and the chain brand in November 2025; the public endpoints still carry the old name. Three public Tendermint RPCs answered on 2026-10-07: the chain-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

CONX (formerly 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 96 ms; the chain-official endpoint measures 125 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.

  • Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
  • Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"status","params":[]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the exclusion rules follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the XPLA-scoped view of the same harness.
  • Roster: every endpoint here answered a real Tendermint status call without a key on the 2026-10-07 sweep before being added to the probe matrix. An endpoint that needs a key, region-blocks us or rate-limits below the 60-second cadence is excluded rather than listed with an asterisk.
  • Chain scope: every query on this page is pinned to `chain="xpla"`. Provider coverage: 3 no-key endpoints.

Results: 3 providers ranked by RPC latency (p50, 24h)

CONX (ex-XPLA) RPC endpoints: free public URLs: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1PublicNodePublicNode free public Tendermint RPC endpoint for XPLA96 ms212 ms294 ms100.00% (n=4323)
2PolkachuPolkachu public Tendermint RPC endpoint for XPLA125 ms134 ms275 ms100.00% (n=4318)
3XPLAXPLA official public Tendermint RPC endpoint125 ms136 ms162 ms100.00% (n=4318)

Public 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.

  • PublicNode logoPublicNodehttps://xpla-rpc.publicnode.com96 ms100.0%
  • Polkachu logoPolkachuhttps://xpla-rpc.polkachu.com125 ms100.0%
  • XPLA logoXPLAhttps://dimension-rpc.xpla.dev125 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