Mode public RPC endpoints, tested

Every keyless Mode (chain ID 34443) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: 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. 5 of 8 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc.swiftnodes.io/rpc/mode (SwiftNodes, keyless: 2 req/s)244 ms2 blocks10,000+archive (1M+)
https://rpc.nodeflare.app/mode/public617 ms0 blocks1,000recent only
https://mode.drpc.org20 ms6 blocksunder 1,000archive (1M+)
https://mainnet.mode.network162 ms6 blocks10,000+archive (1M+)
https://mode-mainnet.rpc.sentio.xyz166 ms4 blocks10,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 mode.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
  • does not stream rpc.swiftnodes.io/ws/mode (SwiftNodes): subscribe rejected: method is not available on free plan, please upgrade to paid plan

Listed but not working

  • public.1rpc.io/mode: chainId: You've reached the usage limit for your current plan. To continue with higher limits and un
  • mode.gateway.tenderly.co: chainId: rate limited
  • lb.routeme.sh/rpc/evm/34443: eth_blockNumber failed

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