Dymension public RPC endpoints, tested

Every keyless Dymension (chain ID 1100) 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. 5 of 12 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	Behind best	eth_getLogs	State
https://lb.routeme.sh/rpc/evm/1100	68 ms	0 blocks	under 1,000	none
https://dymension.api.onfinality.io/public	104 ms	3 blocks	10,000+	recent only
https://rpc.swiftnodes.io/rpc/dymension (SwiftNodes, keyless: 2 req/s)	116 ms	2 blocks	10,000+	recent only
https://jsonrpc.dymension.nodestake.org	14 ms	6 blocks	10,000+	none
https://rollapp.jrpc.cumulo.com.es	113 ms	6 blocks	10,000+	none

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 evm.webSocket.mainnet.dymension.aviaone.com: connection failed (connect)
does not stream rpc.swiftnodes.io/ws/dymension (SwiftNodes): gateway: WebSocket not available for chain: dymension

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
dymension.drpc.org: eth_blockNumber failed
rpc.mainnet.dymension.aviaone.com: chainId: fetch failed
evm.rpc.mainnet.dymension.aviaone.com: chainId: fetch failed
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.