BOB public RPC endpoints, tested

Every keyless BOB (chain ID 60808) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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. 6 of 8 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc.swiftnodes.io/rpc/bob (SwiftNodes, keyless: 2 req/s)51 ms3 blocks10,000+archive (1M+)
https://bob.rpc.sentio.xyz162 ms3 blocks10,000+archive (1M+)
https://rpc.nodeflare.app/bob/public335 ms0 blocks1,000recent only
https://bob.drpc.org22 ms5 blocksunder 1,000archive (1M+)
https://rpc.gobob.xyz159 ms6 blocks10,000+archive (1M+)
https://lb.routeme.sh/rpc/evm/60808281 ms4 blocksunder 1,000none

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

  • does not stream rpc.gobob.xyz: connection failed (connect)
  • does not stream bob-mainnet.public.blastapi.io: connection failed (connect)
  • does not stream bob.drpc.org: subscribe rejected: Unsupported subscription: newHeads
  • does not stream rpc.swiftnodes.io/ws/bob (SwiftNodes): gateway: WebSocket not available for chain: bob

Listed but not working

  • bob-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
  • bob.gateway.tenderly.co: chainId: rate limited

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