Kite public RPC endpoints, tested
Every keyless Kite (chain ID 2366) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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. 3 of 3 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://kite.drpc.org | 23 ms | 0 blocks | under 1,000 | recent only |
| https://rpc.gokite.ai | 26 ms | 0 blocks | under 1,000 | none |
| https://rpc.swiftnodes.io/rpc/kite (SwiftNodes, keyless: 2 req/s) | 71 ms | 3 blocks | 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
- does not stream
rpc.swiftnodes.io/ws/kite(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Test any endpoint yourself with the RPC tester. Our Kite endpoint, limits and status: Kite RPC, uptime history.