Kava public RPC endpoints, tested
Every keyless Kava (chain ID 2222) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: 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 14 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/2222 | 54 ms | 0 blocks | 1,000 | none |
| https://kava.api.pocket.network | 61 ms | 3 blocks | under 1,000 | none |
| https://rpc.swiftnodes.io/rpc/kava (SwiftNodes, keyless: 2 req/s) | 111 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://kava-evm-rpc.publicnode.com | 21 ms | 5 blocks | 10,000+ | none |
| https://kava.drpc.org | 27 ms | 4 blocks | under 1,000 | recent only |
| https://evm.kava-rpc.com | 90 ms | 5 blocks | 10,000+ | archive (1M+) |
| https://rpc.ankr.com/kava_evm | 90 ms | 5 blocks | 10,000+ | archive (1M+) |
| https://evm.kava.io | 107 ms | 6 blocks | 10,000+ | recent only |
| https://kava.api.onfinality.io/public | 109 ms | 1118627 blocks | under 1,000 | recent only |
| https://kava-public.nodies.app | 113 ms | 4 blocks | under 1,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-evm-rpc.publicnode.com: first head after 2499 ms - streams
wevm.kava.io: first head after 3705 ms - streams
wevm.kava-rpc.com: first head after 4268 ms - streams
kava.drpc.org: first head after 4368 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: rate limitedevm.kava.chainstacklabs.com: chainId: fetch failednode.histori.xyz/kava-mainnet/8ry9f6t9dct1se2hlagxnd9n2a: chainId: fetch failedkava.therpc.io: chainId: fetch failed
Test any endpoint yourself with the RPC tester. Our Kava endpoint, limits and status: Kava RPC, uptime history.