Juno RPC endpoints: free public URLs by latency
HTTP round-trip latency for the Tendermint status method against every free, no-key public Juno Cosmos SDK endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 2 free public Juno RPC endpoints measured, 83 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/juno-rpc. 2 public endpoints, no key: juno-rpc.publicnode.com, juno-rpc.polkachu.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 →
Juno (juno-1) is a Cosmos SDK blockchain and the original CosmWasm smart contract hub in the Cosmos ecosystem, JUNO staking token, using CometBFT consensus. It hosts an active ecosystem of DEXes, lending protocols, and NFT platforms built with CosmWasm. Polkachu and PublicNode provide keyless Tendermint RPC endpoints probed every 60 seconds from three regions.
Methodology
Juno: 2 free public RPC endpoints answering `status` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 83 ms. We measure the round-trip latency of a single, identical Cosmos SDK call (Tendermint `status`) against every no-key public Juno 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 Juno-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 Juno-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="juno"`. Provider coverage today: 2 no-key endpoints.
Results: 2 free public Juno RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNodeAllnodes-operated, 70+ chains | 83 ms | 121 ms | 258 ms | 100.00% (n=4321) |
| 2 | PolkachuCommunity Cosmos validator and public RPC | 127 ms | 139 ms | 255 ms | 100.00% (n=4314) |
Public Juno 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.
PublicNodehttps://juno-rpc.publicnode.com83 ms100.0%Polkachu
https://juno-rpc.polkachu.com127 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities