Dymension public RPC endpoints, tested

Every keyless Dymension (chain ID 1100) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-22: 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 10 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://jsonrpc.dymension.nodestake.org26 ms1 blocks1,000none
https://dymension.drpc.org48 ms0 blocksunder 1,000none
https://rollapp.jrpc.cumulo.com.es120 ms1 blocks10,000+none
https://dymension.api.onfinality.io/public120 ms0 blocks10,000+recent only
https://rpc.swiftnodes.io/rpc/dymension (SwiftNodes, keyless: 2 req/s)179 ms2 blocksunder 1,000none

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 dymension-evm-rpc.publicnode.com: connection failed (connect)
  • does not stream dymension.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
  • does not stream rpc.swiftnodes.io/ws/dymension (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • dymension-evm.blockpi.network/v1/rpc/public: chainId: fetch failed
  • dymension-evm-rpc.publicnode.com: no answer (HTTP 404)
  • dymension-evm.kynraze.com: chainId: fetch failed
  • lb.routeme.sh/rpc/evm/1100: chainId: rate limited
  • dymension.liquify.com/json-rpc: chainId: timeout

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