Chiliz public RPC endpoints, tested
Every keyless Chiliz (chain ID 88888) 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 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.ankr.com/chiliz | 24 ms | 0 blocks | 1,000 | archive (1M+) |
| https://rpc.chiliz.com | 30 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://chiliz-mainnet.gateway.tatum.io | 37 ms | 0 blocks | under 1,000 | none |
| https://chiliz.publicnode.com | 92 ms | 1 blocks | 10,000+ | none |
| https://rpc.swiftnodes.io/rpc/chiliz (SwiftNodes, keyless: 2 req/s) | 356 ms | 2 blocks | 10,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
rpc.swiftnodes.io/ws/chiliz(SwiftNodes): first head after 2512 ms
Listed but not working
lb.routeme.sh/rpc/evm/88888: eth_blockNumber failedapi-chiliz-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Chiliz endpoint, limits and status: Chiliz RPC, uptime history.