RPCsUpdated

Archway RPC endpoints: free public URLs by latency

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

TL;DR. As of , Archway Foundation has the lowest median latency of the 2 free public Archway RPC endpoints measured, 92 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/archway-rpc. 2 public endpoints, no key: rpc.mainnet.archway.io, rpc.lavenderfive.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 →

Archway (archway-1) is a Cosmos SDK CosmWasm blockchain with a built-in developer rewards model where dApps earn a portion of gas fees generated by their users, ARCH staking token, CometBFT consensus. LavenderFive and the Archway Foundation's own endpoint provide keyless Tendermint RPC access probed every 60 seconds from three regions.

Methodology

Archway: 2 free public RPC endpoints answering `status` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Archway Foundation leads at 92 ms; the chain-official endpoint measures 92 ms. We measure the round-trip latency of a single, identical Cosmos SDK call (Tendermint `status`) against every no-key public Archway endpoint that sustains continuous probing, 2 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) so the leaderboard rewards sustained availability rather than fast error messages. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Archway-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.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Archway-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to `chain="archway"`. Provider coverage today: 2 no-key endpoints.

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

Archway RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1Archway FoundationArchway Foundation's official public RPC92 ms103 ms105 ms100.00% (n=4323)
2LavenderFiveCosmos validator and no-key RPC142 ms182 ms234 ms100.00% (n=4322)

Public Archway RPC endpoints measured

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

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.

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