Nibiru RPC endpoints: free public URLs by latency
HTTP round-trip latency for the Tendermint status method against every free, no-key public Nibiru Cosmos SDK endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Nibiru Foundation has the lowest median latency of the 2 free public Nibiru RPC endpoints measured, 89 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/nibiru-rpc. Endpoint URLs for the 2 public providers are listed below.
Public Nibiru 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. Providers that need an API key are never listed with a URL.
- NFNibiru Foundation
https://rpc.nibiru.fi:44389 ms100.0% 
Polkachuhttps://nibiru-rpc.polkachu.com133 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.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Nibiru (cataclysm-1) is a high-throughput Cosmos SDK blockchain supporting both CosmWasm and EVM smart contracts, NIBI staking token, using CometBFT consensus with sub-second block times. This bench covers the Tendermint RPC path. Polkachu, PublicNode, and the Nibiru Foundation provide keyless Tendermint RPC endpoints probed every 60 seconds from three regions.
Methodology
Nibiru: 2 free public RPC endpoints answering `status` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Nibiru Foundation leads at 89 ms; the chain-official endpoint measures 89 ms. We measure the round-trip latency of a single, identical Cosmos SDK call (Tendermint `status`) against every no-key public Nibiru 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 Nibiru-scoped answer with per-region breakdowns as a first-class dimension.
Results: 2 free public Nibiru RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Provider | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Nibiru Foundation | 89 ms | 94 ms | 274 ms | 100.00% |
| 2 | Polkachu | 133 ms | 141 ms | 249 ms | 100.00% |
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities