Sentinel DVPN RPC endpoints: free public URLs by latency
HTTP round-trip latency for Tendermint /status queries against every available public Sentinel DVPN endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 3 free public Sentinel DVPN RPC endpoints measured, 83 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/sentinel-rpc. 3 public endpoints, no key: sentinel-rpc.publicnode.com, sentinel-rpc.polkachu.com, rpc.cosmos.directory. 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 →
Sentinel is a decentralized VPN (dVPN) protocol built on the Cosmos SDK, operating on the sentinelhub-2 mainnet. It enables users to share bandwidth and access privacy-preserving connectivity through DVPN token incentives. Sentinel uses the standard Cosmos Tendermint RPC interface; block height is fetched via the /status endpoint. Public keyless RPC nodes are available from Polkachu, PublicNode, and Cosmos Directory. Every provider was live-verified with consecutive block-height probes at launch.
Methodology
Sentinel DVPN: 3 free public RPC endpoints answering `GET /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 Tendermint /status query against every available public Sentinel endpoint that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. Each provider is probed via a GET /status request from which the block number is extracted. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Cosmos-scaled staleness gap (20 blocks, around 120 s at 6 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Sentinel-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public Sentinel DVPN RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 83 ms | 164 ms | 364 ms | 100.00% |
| 2 | Polkachu | 124 ms | 141 ms | 234 ms | 98.28% |
| 3 | Cosmos Directory | 190 ms | 313 ms | 656 ms | 100.00% |
Public Sentinel DVPN RPC endpoints measured
The 3 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://sentinel-rpc.publicnode.com83 ms100.0%Polkachu
https://sentinel-rpc.polkachu.com124 ms98.3%Cosmos Directory
https://rpc.cosmos.directory/sentinel190 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 Sentinel DVPN RPC endpoints work without an API key?
3 endpoints are probed on this chain: Polkachu (sentinel-rpc.polkachu.com), PublicNode (sentinel-rpc.publicnode.com), and Cosmos Directory (rpc.cosmos.directory/sentinel). Every listed endpoint was live-verified before inclusion.
What is Sentinel and why does its RPC latency matter?
Sentinel is a decentralized VPN network where node operators earn DVPN tokens for sharing bandwidth. Developers building dVPN clients, node management tools, or on-chain governance integrations require reliable low-latency RPC access to query bandwidth sessions, staking state, and transaction history.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities