Berachain public RPC endpoints, tested

Every keyless Berachain (chain ID 80094) 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. 8 of 11 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	Behind best	eth_getLogs	State
https://api-berachain-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c	42 ms	0 blocks	under 1,000	archive (1M+)
https://rpc.swiftnodes.io/rpc/berachain (SwiftNodes, keyless: 2 req/s)	143 ms	3 blocks	10,000+	archive (1M+)
https://rpc.berachain.com	12 ms	9 blocks	10,000+	archive (1M+)
https://berachain-rpc.publicnode.com	18 ms	9 blocks	10,000+	recent only
https://berachain.drpc.org	28 ms	7 blocks	under 1,000	archive (1M+)
https://rpc.berachain-apis.com	39 ms	9 blocks	10,000+	recent only
https://bera.api.pocket.network	51 ms	7 blocks	10,000+	archive (1M+)
https://berachain.rpc.sentio.xyz	169 ms	5 blocks	10,000+	archive (1M+)

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 bera.api.pocket.network: first head after 709 ms
streams berachain.drpc.org: first head after 1088 ms
streams rpc.swiftnodes.io/ws/berachain (SwiftNodes): first head after 1425 ms
does not stream rpc.berachain-apis.com: connection failed (connect)
does not stream berachain-rpc.publicnode.com: timeout (subscribe)

Listed but not working

berachain.therpc.io: chainId: fetch failed
lb.routeme.sh/rpc/evm/80094: chainId: rate limited
berachain-mainnet.gateway.tatum.io: chainId: rate limited

Test any endpoint yourself with the RPC tester. Our Berachain endpoint, limits and status: Berachain RPC, uptime history.