Berachain RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Berachain RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Berachain has the lowest median latency of the 4 free public Berachain RPC endpoints measured, 59 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/berachain-rpc. Chain ID 80094. 4 public endpoints, no key: rpc.berachain.com, berachain-rpc.publicnode.com, berachain.drpc.org, gateway.tenderly.co. 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 →
Berachain's proof-of-liquidity L1 fields 4 no-key providers: the Foundation's `rpc.berachain.com` plus PublicNode, dRPC and Tenderly. A thin cohort is itself a signal, several sibling chains failed the cluster's keyless-provider bar entirely, so each endpoint that qualifies here carries more of the redundancy burden. Identical probes every 60 seconds, three regions, full response classification.
Methodology
Berachain: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Berachain leads at 59 ms; the chain-official endpoint measures 59 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Berachain endpoint that sustains continuous probing, 4 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness also classifies every response (ok / http_err / jsonrpc_err / stale / timeout) and audits archive depth every 5 minutes, so the leaderboard rewards sustained, honest availability rather than a fast error message. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Berachain-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Berachain RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Berachain | 59 ms | 67 ms | 69 ms | 100.00% |
| 2 | PublicNode | 71 ms | 88 ms | 151 ms | 100.00% |
| 3 | dRPC | 140 ms | 182 ms | 245 ms | 99.60% |
| 4 | Tenderly | 152 ms | 157 ms | 165 ms | 100.00% |
Public Berachain RPC endpoints measured
Chain ID 80094, currency BERA. The 4 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.
Berachainhttps://rpc.berachain.com59 ms100.0%
PublicNodehttps://berachain-rpc.publicnode.com71 ms100.0%
dRPChttps://berachain.drpc.org140 ms99.6%
Tenderlyhttps://gateway.tenderly.co/public/berachain152 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 Berachain RPCs work without an API key?
The 4 providers on this page are listed with their URLs in the endpoints table above. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.
Are free Berachain RPCs ready for production traffic?
The 4 qualifying endpoints all sustain our 60-second cadence with high measured success rates, which is the floor for production reads. The real constraint is redundancy: with 4 providers, one incident removes a quarter of your options, so run the current leader (Berachain, 59 ms) as primary with the runner-up wired as fallback and let this page arbitrate after incidents.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities