Avalanche RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Avalanche RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 4 free public Avalanche RPC endpoints measured, 69 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/avalanche-rpc. Chain ID 43114. 4 public endpoints, no key: avalanche-c-chain-rpc.publicnode.com, api.avax.network, gateway.tenderly.co, avalanche.drpc.org. Full URLs with their 24h median are listed below.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Avalanche's C-Chain field combines Ava Labs' official `api.avax.network` with 4 no-key multi-chain gateways. The official endpoint shows one of the tightest distributions among foundation RPCs, a contrast with the best-effort profiles on Arbitrum and Optimism. Every provider answers the identical probe every 60 seconds from us-east, eu-west and Singapore, with stale-head detection flagging anything more than 20 blocks behind the cross-provider tip.
Methodology
Avalanche: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 69 ms; the chain-official endpoint measures 86 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Avalanche endpoint that sustains continuous probing, 4 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness also classifies every response (ok / http_err / jsonrpc_err / stale / timeout) and audits archive depth every 5 minutes, so the leaderboard rewards sustained, honest availability rather than a fast error message. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Avalanche-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Avalanche RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 69 ms | 81 ms | 624 ms | 99.79% |
| 2 | Avalanche | 86 ms | 105 ms | 124 ms | 100.00% |
| 3 | Tenderly | 104 ms | 111 ms | 121 ms | 100.00% |
| 4 | dRPC | 169 ms | 354 ms | 583 ms | 98.00% |
Public Avalanche RPC endpoints measured
Chain ID 43114, currency AVAX. The 4 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
PublicNodehttps://avalanche-c-chain-rpc.publicnode.com69 ms99.8%
Avalanchehttps://api.avax.network/ext/bc/C/rpc86 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/avalanche104 ms100.0%
dRPChttps://avalanche.drpc.org169 ms98.0%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Not listed on Avalanche
- Ankr: public endpoint requires an API key
- NodeReal: requires an API key
- GetBlock: requires an API key; compared on the keyed pages
- Chainstack: requires an API key; compared on the keyed pages
- 1RPC: delisted for reliability: under 13 % success at one probe per minute (since 2026-07-09)
- gateway.fm: 29 requests per IP budget, too small for continuous probing
- LlamaRPC: Cloudflare 521 from the probe regions
- BlockPI: Cloudflare 521 from the probe regions
- OmniaTech: Cloudflare 521 from the probe regions
- Alchemy demo: rate-limited public demo endpoint; the keyed tier is compared on the keyed pages
Frequently asked
Which Avalanche RPCs work without an API key?
The 4 providers on this page are listed with their URLs in the endpoints table above. Nodies was delisted in July 2026 when its Avalanche endpoint moved behind a paid plan. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.
Is the official Avalanche RPC good enough for production reads?
Among chain-official endpoints it is one of the strongest we measure: tight latency distribution and a high success rate rather than the best-effort tail seen on some other foundation RPCs. The usual free-tier caveats still apply (shared rate limits, no SLA), but as a read path it holds up unusually well against the commercial gateways.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities