opBNB RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public opBNB EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , BNB Chain Team has the lowest median latency of the 3 free public opBNB RPC endpoints measured, 56 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/opbnb-rpc. Chain ID 204. 3 public endpoints, no key: opbnb-mainnet-rpc.bnbchain.org, opbnb-rpc.publicnode.com, opbnb.drpc.org. 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 →
opBNB is the OP Stack rollup (chain 204) operated by the BNB Chain team, with BNB gas and settlement onto BNB Chain (not Ethereum). Standard EVM JSON-RPC. Excluded by the launch audit: NodeReal (`opbnb-mainnet.nodereal.io` requires API key), BlockPI (`unknown host`), Grove/Pocket public LB (needs app id), Tatum (404). Every provider live-verified with 4 consecutive keyless probes at launch.
Methodology
opBNB: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. BNB Chain Team leads at 56 ms; the chain-official endpoint measures 56 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public opBNB 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 opBNB-scaled staleness gap (25 blocks at opBNB's ~1 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the opBNB-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public opBNB RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | BNB Chain Team | 56 ms | 61 ms | 143 ms | 100.00% (n=4341) |
| 2 | PublicNode | 83 ms | 105 ms | 343 ms | 98.78% (n=4329) |
| 3 | dRPC | 426 ms | 786 ms | 1.34 s | 98.61% (n=4330) |
Public opBNB RPC endpoints measured
Chain ID 204, currency BNB. 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.
BNB Chain Teamhttps://opbnb-mainnet-rpc.bnbchain.org56 ms100.0%
PublicNodehttps://opbnb-rpc.publicnode.com83 ms98.8%
dRPChttps://opbnb.drpc.org426 ms98.6%
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 opBNB RPCs work without an API key?
3 endpoints are probed on this chain; each is listed with its URL, 24h median and success rate in the endpoints table on this page, and the list changes as providers come and go.
How is opBNB RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` POST every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities