Avalanche public RPC endpoints, tested

Every keyless Avalanche (chain ID 43114) 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. 12 of 28 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc.swiftnodes.io/rpc/avalanche (SwiftNodes, keyless: 2 req/s)63 ms1 blocks10,000+none
https://spectrum-01.simplystaking.xyz/avalanche-mn-rpc/ext/bc/C/rpc94 ms0 blocks10,000+none
https://avax-mainnet.gateway.tatum.io16 ms8 blocksunder 1,000none
https://avalanche-c-chain-rpc.publicnode.com19 ms25 blocks10,000+none
https://avalanche.drpc.org22 ms14 blocksunder 1,000archive (1M+)
https://api.avax.network/ext/bc/C/rpc28 ms27 blocks10,000+archive (1M+)
https://rpc-avalanche.blockmachine.io47 ms5 blocks1,000archive (1M+)
https://avax.api.pocket.network91 ms9 blocks10,000+archive (1M+)
https://avalanche.api.onfinality.io/public/ext/bc/C/rpc160 ms14 blocks10,000+archive (1M+)
https://avalanche.rpc.sentio.xyz166 ms7 blocks10,000+archive (1M+)
https://api.zan.top/avax-mainnet/ext/bc/C/rpc170 ms14 blocksunder 1,000archive (1M+)
https://xrpc.cl/avalanche1453 ms18 blocks10,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 avalanche.drpc.org: first head after 110 ms
  • streams avalanche-c-chain-rpc.publicnode.com: first head after 238 ms
  • streams rpc.swiftnodes.io/ws/avalanche (SwiftNodes): first head after 578 ms

Listed but not working

  • avalanche.public-rpc.com: chainId: Unauthorized: You must authenticate your request with an API key. Create an account on http
  • ava-mainnet.public.blastapi.io/ext/bc/C/rpc: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
  • public.1rpc.io/avax/c: no answer (HTTP 403)
  • avalanche-public.nodies.app/ext/bc/C/rpc: no answer (HTTP 403)
  • rpc.nodeflare.app/avax/public: chainId: rate limited
  • lb.routeme.sh/rpc/evm/43114: chainId: rate limited
  • avax.meowrpc.com: chainId: fetch failed
  • endpoints.omniatech.io/v1/avax/mainnet/public: no answer (HTTP 521)
  • public.stackup.sh/api/v1/node/avalanche-mainnet: chainId: fetch failed
  • avax-x-mainnet.gateway.tatum.io: chainId: Method not found: eth_chainId
  • rpc.owlracle.info/avax/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)
  • avalancheapi.terminet.io/ext/bc/C/rpc: chainId: timeout
  • avalanche.therpc.io: chainId: fetch failed
  • rpc.poolz.finance/avalanche: chainId: fetch failed
  • avax-rpc.keccak.io: chainId: auth error - api key required. This method needs an account — register free and get an API
  • avalanche-mainnet.gateway.tenderly.co: chainId: rate limited

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