Celestia RPC endpoints: free public URLs by latency
HTTP round-trip latency for the Tendermint status method against every free, no-key public Celestia Cosmos SDK endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 3 free public Celestia RPC endpoints measured, 65 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/celestia-rpc. 3 public endpoints, no key: celestia-rpc.publicnode.com, celestia-rpc.polkachu.com, 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 →
Celestia (celestia mainnet) is a modular data availability network decoupling DA from execution, with TIA as the gas token and ~12 s block time. It is used as the DA layer by Arbitrum Nitro, OP Stack, and other rollup frameworks. PublicNode, Polkachu, and LavenderFive all run keyless Tendermint RPC endpoints probed every 60 seconds from three regions.
Methodology
Celestia: 3 free public RPC endpoints answering `status` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 65 ms. We measure the round-trip latency of a single, identical Cosmos SDK call (Tendermint `status`) against every no-key public Celestia endpoint that sustains continuous probing, 3 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) with a Celestia-scaled staleness gap (10 blocks at ~12 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Celestia-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 Celestia-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="celestia"`. Provider coverage today: 3 no-key endpoints.
Results: 3 free public Celestia RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 65 ms | 92 ms | 332 ms | 100.00% (n=4321) |
| 2 | Polkachu | 151 ms | 171 ms | 277 ms | 99.93% (n=4317) |
| 3 | LavenderFive | 183 ms | 212 ms | 243 ms | 100.00% (n=4319) |
Public Celestia 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://celestia-rpc.publicnode.com65 ms100.0%Polkachu
https://celestia-rpc.polkachu.com151 ms99.9%LavenderFive
https://rpc.lavenderfive.com:443/celestia183 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