Kava public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://kava-evm-rpc.publicnode.com20 ms2 blocks10,000+none
https://rpc.swiftnodes.io/rpc/kava (SwiftNodes, keyless: 2 req/s)47 ms1 blocksunder 1,000none
https://kava.api.pocket.network51 ms1 blocks10,000+none
https://rpc.ankr.com/kava_evm93 ms2 blocks10,000+archive (1M+)
https://kava.drpc.org95 ms2 blocksunder 1,000none
https://evm.kava-rpc.com95 ms2 blocks10,000+archive (1M+)
https://evm.kava.io102 ms3 blocks10,000+recent only
https://lb.routeme.sh/rpc/evm/2222115 ms0 blocksunder 1,000none
https://kava-public.nodies.app125 ms1 blocksunder 1,000none
https://kava.api.onfinality.io/public237 ms1543188 blocksunder 1,000recent only

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 wevm.kava.io: first head after 2268 ms
  • streams wevm.kava-rpc.com: first head after 2911 ms
  • streams kava-evm-rpc.publicnode.com: first head after 4315 ms
  • streams kava.drpc.org: first head after 5242 ms
  • does not stream wevm.kava.chainstacklabs.com: connection failed (connect)
  • does not stream rpc.swiftnodes.io/ws/kava (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • kava-evm.rpc.thirdweb.com: chainId: Invalid chain
  • evm.kava.chainstacklabs.com: chainId: fetch failed
  • kava.therpc.io: no answer (HTTP 200)

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