Acala RPC endpoints: free public URLs by latency
HTTP round-trip latency for Substrate chain_getHeader queries against every available public Acala endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Acala (RPC-2) has the lowest median latency of the 3 free public Acala RPC endpoints measured, 53 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/acala-rpc. 3 public endpoints, no key: acala-rpc-2.aca-api.network, acala-rpc-0.aca-api.network, acala-rpc.n.dwellir.com. 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 →
Acala is the DeFi hub of the Polkadot ecosystem, a Polkadot parachain providing decentralized stablecoin (aUSD), liquid staking (LDOT), and an EVM-compatible execution environment. Acala uses the Substrate framework and exposes a standard Substrate JSON-RPC interface; block height is queried via chain_getHeader. Public endpoints are available without an API key from Dwellir and the Acala official RPC cluster (aca-api.network). Every provider was live-verified with consecutive block-height probes at launch.
Methodology
Acala: 3 free public RPC endpoints answering `chain_getHeader` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Acala (RPC-2) (tied) leads at 53 ms. We measure the round-trip latency of a Substrate chain_getHeader query against every available public Acala endpoint that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. Each provider is probed via a JSON-RPC POST (chain_getHeader) from which the block number is extracted. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Polkadot-scaled staleness gap (40 blocks, around 8 min at 12 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Acala-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public Acala RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Acala (RPC-2) | 53 ms | 89 ms | 170 ms | 100.00% |
| 2 | Acala (RPC-0) | 53 ms | 87 ms | 220 ms | 100.00% |
| 3 | Dwellir | 438 ms | 450 ms | 494 ms | 100.00% |
Public Acala RPC endpoints measured
The 3 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.
Acala (RPC-2)https://acala-rpc-2.aca-api.network53 ms100.0%- Acala (RPC-0)
https://acala-rpc-0.aca-api.network53 ms100.0% 
Dwellirhttps://acala-rpc.n.dwellir.com438 ms100.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.
Frequently asked
Which Acala RPC endpoints work without an API key?
3 endpoints are probed on this chain: Dwellir (acala-rpc.n.dwellir.com), Acala RPC-0 (acala-rpc-0.aca-api.network) and Acala RPC-2 (acala-rpc-2.aca-api.network). Every listed endpoint was live-verified before inclusion.
How does Acala RPC latency compare to other Polkadot parachains?
All Polkadot parachains use the same Substrate JSON-RPC probe (chain_getHeader), making latency directly comparable across the per-chain RPC cluster. The parent rpc-capabilities benchmark shows the cross-chain view.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities