Kaia public RPC endpoints, tested

Every keyless Kaia (chain ID 8217) 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. 6 of 12 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	Behind best	eth_getLogs	State
https://kaia.api.pocket.network	40 ms	1 blocks	10,000+	none
https://kaia-mainnet.gateway.tatum.io	42 ms	0 blocks	under 1,000	none
https://alpha-hardworking-orb.kaia-mainnet.quiknode.pro	89 ms	2 blocks	10,000+	archive (1M+)
https://klaytn.drpc.org	29 ms	18 blocks	under 1,000	archive (1M+)
https://public-en.node.kaia.io	270 ms	6 blocks	10,000+	archive (1M+)
https://rpc.swiftnodes.io/rpc/kaia (SwiftNodes, keyless: 2 req/s)	285 ms	4 blocks	under 1,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

does not stream klaytn.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
does not stream rpc.swiftnodes.io/ws/kaia (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

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 un
rpc.ankr.com/kaia: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403
lb.routeme.sh/rpc/evm/8217: chainId: rate limited
klaytn.api.onfinality.io/public: eth_blockNumber failed

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