RPCsUpdated

ZIGChain RPC endpoints: free public URLs by latency

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

TL;DR. As of , NodeStake has the lowest median latency of the 5 free public ZIGChain RPC endpoints measured, 86 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/zigchain-rpc. 5 public endpoints, no key: rpc.zigchain.nodestake.org, zigchain-rpc.stakeandrelax.net, zigchain-rpc.polkachu.com, public-zigchain-rpc.numia.xyz, rpc.zigchain.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 →

ZIGChain is a Cosmos SDK chain (zigchain-1) and carries the widest keyless roster of every chain added on 2026-10-07: all five public RPCs the Cosmos chain registry lists answered the Tendermint `status` probe. That is rare. Across the same sweep Agoric listed eleven and three answered, and most chains at this size have two. The five are the ZIGChain official endpoint (rpc.zigchain.com), Numia, Polkachu, NodeStake and Stake and Relax.

Methodology

ZIGChain: 5 free public RPC endpoints answering Tendermint status every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. NodeStake leads at 86 ms; the chain-official endpoint measures 311 ms. We measure the round-trip latency of a single Tendermint `status` call against every no-key public ZIGChain endpoint that sustains continuous probing, 5 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 ZIGChain-scaled staleness gap (20 blocks at ZIGChain's ~5 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the ZIGChain-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 ZIGChain-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="zigchain"`. Provider coverage: 5 no-key endpoints.

Results: 5 free public ZIGChain RPC endpoints ranked by p50 latency (24h, 3 regions)

ZIGChain RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1NodeStakeNodeStake public Tendermint RPC endpoint for ZIGChain86 ms90 ms97 ms99.58% (n=4321)
2Stake and RelaxStake and Relax public Tendermint RPC endpoint for ZIGChain98 ms121 ms340 ms99.91% (n=4314)
3PolkachuPolkachu public Tendermint RPC endpoint for ZIGChain128 ms139 ms251 ms100.00% (n=4309)
4NumiaNumia public Tendermint RPC endpoint for ZIGChain131 ms149 ms228 ms99.95% (n=4318)
5ZIGChainZIGChain official public Tendermint RPC endpoint311 ms351 ms417 ms100.00% (n=4320)

Public ZIGChain RPC endpoints measured

The 5 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.

  • NodeStake logoNodeStakehttps://rpc.zigchain.nodestake.org86 ms99.6%
  • Stake and Relax logoStake and Relaxhttps://zigchain-rpc.stakeandrelax.net98 ms99.9%
  • Polkachu logoPolkachuhttps://zigchain-rpc.polkachu.com128 ms100.0%
  • Numia logoNumiahttps://public-zigchain-rpc.numia.xyz131 ms100.0%
  • ZIGChain logoZIGChainhttps://rpc.zigchain.com311 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 ZIGChain RPCs work without an API key?

5 endpoints are probed on this chain: ZIGChain (rpc.zigchain.com), Numia (public-zigchain-rpc.numia.xyz), Polkachu (zigchain-rpc.polkachu.com), NodeStake (rpc.zigchain.nodestake.org), Stake and Relax (zigchain-rpc.stakeandrelax.net). Every listed endpoint was live-verified with a Tendermint status call returning a parsable response before inclusion.

How is ZIGChain 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.

Five working endpoints is unusual for a chain this size. Why?

Because the validator operators behind them keep their public RPCs running, which is not the norm. The Cosmos chain registry lists endpoints that were contributed once and are never pruned when they die, so a long list usually collapses under probing: on this sweep Agoric's eleven listed endpoints produced three live ones. ZIGChain's five listed produced five live. The count on this page is what answered, not what is listed.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities