ZetaChain public RPC endpoints, tested
Every keyless ZetaChain (chain ID 7000) 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 8 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://api-zetachain-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c | 45 ms | 0 blocks | under 1,000 | none |
| https://rpc.swiftnodes.io/rpc/zetachain (SwiftNodes, keyless: 2 req/s) | 193 ms | 1 blocks | 1,000 | archive (1M+) |
| https://zeta-chain.drpc.org | 37 ms | 4 blocks | under 1,000 | recent only |
| https://zetachain-evm.blockpi.network/v1/rpc/public | 60 ms | 4 blocks | 1,000 | archive (1M+) |
| https://zetachain-mainnet.g.allthatnode.com/archive/evm | 370 ms | 4 blocks | 10,000+ | archive (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
- streams
zeta-chain.drpc.org: first head after 2418 ms - streams
rpc.swiftnodes.io/ws/zetachain(SwiftNodes): first head after 3295 ms
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 inste7000.rpc.thirdweb.com: chainId: rate limitedlb.routeme.sh/rpc/evm/7000: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our ZetaChain endpoint, limits and status: ZetaChain RPC, uptime history.