Canto public RPC endpoints, tested

Every keyless Canto (chain ID 7700) 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.

Working HTTP endpoints

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 canto.dexvaults.com/ws: connection failed (connect)
• does not stream canto.gravitychain.io:8546: connection failed (connect)
• does not stream rpc.swiftnodes.io/ws/canto (SwiftNodes): gateway: Upstream WebSocket unavailable for chain: canto

Listed but not working

• canto-rpc.ansybl.io: chainId: fetch failed
• mainnode.plexnode.org:8545: chainId: fetch failed
• canto.evm.chandrastation.com: chainId: fetch failed
• canto.gravitychain.io: chainId: fetch failed
• jsonrpc.canto.nodestake.top: chainId: fetch failed
• canto.dexvaults.com: chainId: fetch failed
• canto.dexrouting.com: chainId: fetch failed
• canto.slingshot.finance: chainId: timeout
• lb.routeme.sh/rpc/evm/7700: chainId: rate limited
• rpc.swiftnodes.io/rpc/canto: chainId: Backend node error

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