OKT Chain public RPC endpoints, tested
Every keyless OKT Chain (chain ID 66) 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. 4 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://oktc.drpc.org | 40 ms | 1 blocks | under 1,000 | none |
| https://public.1rpc.io/oktc | 104 ms | 0 blocks | under 1,000 | none |
| https://exchainrpc.okex.org | 212 ms | 1 blocks | 1,000 | none |
| https://rpc.swiftnodes.io/rpc/okt-chain (SwiftNodes, keyless: 2 req/s) | 231 ms | 0 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
oktc.drpc.org: subscribe rejected: method is not available - does not stream
rpc.swiftnodes.io/ws/okt-chain(SwiftNodes): gateway: WebSocket not available for chain: okt-chain
Listed but not working
okc-mainnet.gateway.pokt.network/v1/lb/6275309bea1b320039c893ff: chainId: fetch failedoktc-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API instelb.routeme.sh/rpc/evm/66: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our OKT Chain endpoint, limits and status: OKT Chain RPC, uptime history.