B2 Network public RPC endpoints, tested

Every keyless B2 Network (chain ID 223) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-22: 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. 5 of 7 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://b2-mainnet.rpc.sentio.xyz173 ms3 blocksunder 1,000archive (1M+)
https://lb.routeme.sh/rpc/evm/223185 ms0 blocks1,000none
https://rpc.bsquared.network164 ms6 blocks1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/bsquared (SwiftNodes, keyless: 2 req/s)214 ms4 blocksunder 1,000archive (1M+)
https://b2-mainnet.alt.technology251 ms5 blocks1,000archive (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

  • does not stream rpc.swiftnodes.io/ws/bsquared (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • mainnet.b2-rpc.com: chainId: message: API key disabled, reason: tenant disabled, json-rpc code: -32051, rest code: 403
  • rpc.ankr.com/b2: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403

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