Chiliz public RPC endpoints, tested

Every keyless Chiliz (chain ID 88888) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: 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. 7 of 7 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://lb.routeme.sh/rpc/evm/8888873 ms0 blocksunder 1,000none
https://rpc.swiftnodes.io/rpc/chiliz (SwiftNodes, keyless: 2 req/s)132 ms2 blocks10,000+archive (1M+)
https://chiliz.publicnode.com22 ms5 blocks10,000+recent only
https://chiliz-mainnet.gateway.tatum.io24 ms5 blocksunder 1,000none
https://api-chiliz-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c35 ms4 blocksunder 1,000archive (1M+)
https://rpc.chiliz.com56 ms5 blocks10,000+archive (1M+)
https://rpc.ankr.com/chiliz89 ms5 blocks1,000archive (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 rpc.swiftnodes.io/ws/chiliz (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 Chiliz endpoint, limits and status: Chiliz RPC, uptime history.