RPCsUpdated

Stride RPC endpoints: free public URLs by latency

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

Companion page

Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →

Stride (stride-1) is a Cosmos SDK liquid staking protocol providing stATOM, stTIA, stOSMO, and other IBC-connected staked assets, STRD governance token, using CometBFT consensus. It integrates with the broader Cosmos IBC ecosystem for cross-chain liquid staking. Polkachu and LavenderFive provide keyless Tendermint RPC endpoints probed every 60 seconds from three regions.

Methodology

Stride: 0 free public RPC endpoints answering `status` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Polkachu leads at 127 ms. We measure the round-trip latency of a single, identical Cosmos SDK call (Tendermint `status`) against every no-key public Stride endpoint that sustains continuous probing, 0 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 Stride-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 Stride-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to `chain="stride"`. Provider coverage today: 0 no-key endpoints.

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