Beam public RPC endpoints, tested
Every keyless Beam (chain ID 4337) 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. 3 of 4 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://build.onbeam.com/rpc | 15 ms | 0 blocks | 1,000 | archive (1M+) |
| https://subnets.avax.network/beam/mainnet/rpc | 113 ms | 0 blocks | 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/beam (SwiftNodes, keyless: 2 req/s) | 198 ms | 0 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
subnets.avax.network/beam/mainnet/ws: chainId: the method eth_chainId does not exist/is not available - subscribed
build.onbeam.com/ws: accepted; this chain produced no block during the 15 s window - does not stream
rpc.swiftnodes.io/ws/beam(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
lb.routeme.sh/rpc/evm/4337: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Beam endpoint, limits and status: Beam RPC, uptime history.