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-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. 4 of 8 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://b2-mainnet.alt.technology | 160 ms | 0 blocks | 1,000 | archive (1M+) |
| https://b2-mainnet.rpc.sentio.xyz | 165 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.bsquared.network | 167 ms | 1 blocks | 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/bsquared (SwiftNodes, keyless: 2 req/s) | 218 ms | 3 blocks | 1,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
- does not stream
rpc.swiftnodes.io/ws/bsquared(SwiftNodes): gateway: WebSocket not available for chain: bsquared
Listed but not working
mainnet.b2-rpc.com: chainId: message: API key disabled, reason: tenant disabled, json-rpc code: -32051, rest code: 403b2-mainnet-public.s.chainbase.com: chainId: fetch failedrpc.ankr.com/b2: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403lb.routeme.sh/rpc/evm/223: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our B2 Network endpoint, limits and status: B2 Network RPC, uptime history.