ZetaChain public RPC endpoints, tested

Every keyless ZetaChain (chain ID 7000) 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. 4 of 8 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://zetachain-mainnet.g.allthatnode.com/archive/evm21 ms1 blocks10,000+archive (1M+)
https://zeta-chain.drpc.org22 ms0 blocksunder 1,000recent only
https://zetachain-evm.blockpi.network/v1/rpc/public36 ms1 blocks1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/zetachain (SwiftNodes, keyless: 2 req/s)64 ms1 blocks10,000+recent only

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 zeta-chain.drpc.org: first head after 1867 ms
  • does not stream rpc.swiftnodes.io/ws/zetachain (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • zetachain-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
  • 7000.rpc.thirdweb.com: chainId: rate limited
  • api-zetachain-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limited
  • lb.routeme.sh/rpc/evm/7000: eth_blockNumber failed

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