Kaia public RPC endpoints, tested
Every keyless Kaia (chain ID 8217) 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. 5 of 13 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://klaytn.drpc.org | 31 ms | 2 blocks | under 1,000 | none |
| https://kaia.api.pocket.network | 81 ms | 3 blocks | 10,000+ | none |
| https://rpc.ankr.com/kaia | 149 ms | 0 blocks | 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/kaia (SwiftNodes, keyless: 2 req/s) | 408 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://public-en.node.kaia.io | 288 ms | 4 blocks | 10,000+ | archive (1M+) |
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
rpc.swiftnodes.io/ws/kaia(SwiftNodes): first head after 18 ms - does not stream
klaytn.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
Listed but not working
kaia-public.nodies.app: no answer (HTTP 403)go.getblock.io/d7094dbd80ab474ba7042603fe912332: no answer (HTTP 401)public.1rpc.io/klay: chainId: You've reached the usage limit for your current plan. To continue with higher limits and unkaia.therpc.io: chainId: fetch failedlb.routeme.sh/rpc/evm/8217: chainId: rate limitedalpha-hardworking-orb.kaia-mainnet.quiknode.pro: chainId: rate limitedklaytn.api.onfinality.io/public: chainId: rate limitedkaia-mainnet.gateway.tatum.io: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Kaia endpoint, limits and status: Kaia RPC, uptime history.