Bitlayer public RPC endpoints, tested
Every keyless Bitlayer (chain ID 200901) 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. 2 of 6 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.swiftnodes.io/rpc/bitlayer (SwiftNodes, keyless: 2 req/s) | 81 ms | 2 blocks | 10,000+ | none |
| https://rpc.bitlayer.org | 174 ms | 0 blocks | 10,000+ | recent only |
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
ws.bitlayer.org: first head after 3015 ms - does not stream
ws.bitlayer-rpc.com: connection failed (connect) - does not stream
rpc.swiftnodes.io/ws/bitlayer(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc.bitlayer-rpc.com: chainId: message: API key disabled, reason: tenant disabled, json-rpc code: -32051, rest code: 403rpc.ankr.com/bitlayer: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403rpc-bitlayer.rockx.com: chainId: fetch failedlb.routeme.sh/rpc/evm/200901: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Bitlayer endpoint, limits and status: Bitlayer RPC, uptime history.