Boba Network public RPC endpoints, tested
Every keyless Boba Network (chain ID 288) 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. 3 of 6 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://boba-eth.drpc.org | 75 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://mainnet.boba.network | 116 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/boba (SwiftNodes, keyless: 2 req/s) | 551 ms | 3 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
rpc.swiftnodes.io/ws/boba(SwiftNodes): first head after 42 ms - streams
boba-eth.drpc.org: first head after 161 ms - does not stream
boba-ethereum.gateway.tenderly.co: connection failed (connect) - does not stream
gateway.tenderly.co/public/boba-ethereum: connection failed (connect)
Listed but not working
replica.boba.network: chainId: fetch failedboba-ethereum.gateway.tenderly.co: chainId: rate limitedgateway.tenderly.co/public/boba-ethereum: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Boba Network endpoint, limits and status: Boba Network RPC, uptime history.