opBNB public RPC endpoints, tested
Every keyless opBNB (chain ID 204) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: does it answer on the right chain, how fast, how far behind the best head, how large an eth_getLogs range it accepts, whether it keeps archive state, and whether its WebSocket actually streams. 7 of 12 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://opbnb.api.pocket.network | 102 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://opbnb-rpc.publicnode.com | 17 ms | 11 blocks | 10,000+ | recent only |
| https://opbnb.drpc.org | 32 ms | 9 blocks | under 1,000 | none |
| https://opbnb-mainnet-rpc.bnbchain.org | 100 ms | 23 blocks | 10,000+ | none |
| https://opbnb-mainnet.nodereal.io/v1/64a9df0874fb4a93b9d0a3849de012d3 | 102 ms | 21 blocks | 10,000+ | archive (1M+) |
| https://opbnb-mainnet.nodereal.io/v1/e9a36765eb8a40b9bd12e680a1fd2bc5 | 102 ms | 15 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/opbnb (SwiftNodes, keyless: 2 req/s) | 308 ms | 14 blocks | 10,000+ | none |
Order: endpoints within 3 blocks of the best head first, then by median latency. Latency is measured from one server, so yours will differ by region; lag and limits do not.
WebSocket endpoints
- streams
rpc.swiftnodes.io/ws/opbnb(SwiftNodes): first head after 2 ms - streams
opbnb.drpc.org: first head after 10 ms - streams
opbnb-mainnet.nodereal.io/ws/v1/64a9df0874fb4a93b9d0a3849de012d3: first head after 149 ms - streams
opbnb-mainnet.nodereal.io/ws/v1/e9a36765eb8a40b9bd12e680a1fd2bc5: first head after 160 ms - streams
opbnb-rpc.publicnode.com: first head after 255 ms - streams
opbnb.api.pocket.network: first head after 307 ms - does not stream
opbnb-mainnet.4everland.org/ws/v1/37fa9972c1b1cd5fab542c7bdd4cde2f: connection failed (connect)
Listed but not working
public.1rpc.io/opbnb: chainId: You've reached the usage limit for your current plan. To continue with higher limits and unopbnb-mainnet.4everland.org/v1/37fa9972c1b1cd5fab542c7bdd4cde2f: chainId: Invalid API Key.opbnb.therpc.io: chainId: fetch failedlb.routeme.sh/rpc/evm/204: chainId: rate limitedapi-opbnb-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our opBNB endpoint, limits and status: opBNB RPC, uptime history.