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 300 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.
Results: 5 free public ZIGChain RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | NodeStake | 86 ms | 90 ms | 362 ms | 99.83% |
| 2 | Stake and Relax | 91 ms | 96 ms | 302 ms | 100.00% |
| 3 | Polkachu | 128 ms | 140 ms | 209 ms | 100.00% |
| 4 | Numia | 135 ms | 159 ms | 241 ms | 100.00% |
| 5 | ZIGChain | 300 ms | 312 ms | 382 ms | 100.00% |
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.
NodeStakehttps://rpc.zigchain.nodestake.org86 ms99.8%
Stake and Relaxhttps://zigchain-rpc.stakeandrelax.net91 ms100.0%
Polkachuhttps://zigchain-rpc.polkachu.com128 ms100.0%
Numiahttps://public-zigchain-rpc.numia.xyz135 ms100.0%
ZIGChainhttps://rpc.zigchain.com300 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