Metal L2 public RPC endpoints, tested
Every keyless Metal L2 (chain ID 1750) 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://metall2.drpc.org | 23 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://rpc.metall2.com | 167 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/metal-l2 (SwiftNodes, keyless: 2 req/s) | 243 ms | 3 blocks | 10,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
- streams
metall2.drpc.org: first head after 99 ms - does not stream
rpc.swiftnodes.io/ws/metal-l2(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/1750: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Metal L2 endpoint, limits and status: Metal L2 RPC, uptime history.