Merlin Chain public RPC endpoints, tested

Every keyless Merlin Chain (chain ID 4200) 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 8 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://merlin.drpc.org21 ms2 blocksunder 1,000archive (1M+)
https://rpc.merlinchain.io176 ms0 blocks1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/merlin (SwiftNodes, keyless: 2 req/s)203 ms1 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 merlin.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
  • does not stream rpc.swiftnodes.io/ws/merlin (SwiftNodes): gateway: WebSocket not available for chain: merlin

Listed but not working

  • merlin-mainnet-enterprise.unifra.io: chainId: fetch failed
  • rpc-merlin.rockx.com: chainId: fetch failed
  • merlin.blockpi.network/v1/rpc/public: chainId: Due to the high consumption or high frequency of Remote Procedure Call (RPC) requests, you
  • endpoints.omniatech.io/v1/merlin/mainnet/public: no answer (HTTP 521)
  • lb.routeme.sh/rpc/evm/4200: eth_blockNumber failed

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