Kava public RPC endpoints, tested

Every keyless Kava (chain ID 2222) 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. 8 of 15 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://kava.drpc.org30 ms1 blocksunder 1,000archive (1M+)
https://kava-evm-rpc.publicnode.com32 ms2 blocks10,000+none
https://kava.api.pocket.network71 ms0 blocks1,000none
https://rpc.ankr.com/kava_evm89 ms1 blocks10,000+archive (1M+)
https://evm.kava-rpc.com91 ms1 blocks10,000+archive (1M+)
https://evm.kava.io102 ms2 blocks10,000+recent only
https://kava-public.nodies.app108 ms0 blocksunder 1,000none
https://rpc.swiftnodes.io/rpc/kava (SwiftNodes, keyless: 2 req/s)201 ms2 blocks10,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

  • streams kava.drpc.org: first head after 160 ms
  • streams rpc.swiftnodes.io/ws/kava (SwiftNodes): first head after 1639 ms
  • streams wevm.kava-rpc.com: first head after 4102 ms
  • does not stream wevm.kava.chainstacklabs.com: connection failed (connect)
  • does not stream wevm.kava.io: subscribed, no head in 15 s
  • does not stream kava-evm-rpc.publicnode.com: subscribed, no head in 15 s

Listed but not working

  • kava-rpc.gateway.pokt.network: chainId: fetch failed
  • kava-evm.rpc.thirdweb.com: chainId: rate limited
  • evm.kava.chainstacklabs.com: chainId: fetch failed
  • node.histori.xyz/kava-mainnet/8ry9f6t9dct1se2hlagxnd9n2a: chainId: fetch failed
  • kava.therpc.io: chainId: fetch failed
  • lb.routeme.sh/rpc/evm/2222: chainId: rate limited
  • kava.api.onfinality.io/public: chainId: rate limited

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