Algorand RPC endpoints: free public URLs by latency
HTTP round-trip latency for the Algorand algod status endpoint (last-round) against every free, no-key public Algorand node, audited every 60 seconds from 3 regions.
TL;DR. As of , Tatum has the lowest median latency of the 3 free public Algorand RPC endpoints measured, 26 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/algorand-rpc. 3 public endpoints, no key: algorand-mainnet-algod.gateway.tatum.io, mainnet-api.algonode.cloud, mainnet-api.4160.nodely.dev. 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 →
Algorand is an L1 blockchain using a Pure Proof-of-Stake consensus (BA* Byzantine Agreement) that commits one round every roughly 3.5 seconds with immediate finality and no forks. Algorand nodes expose a REST algod API rather than JSON-RPC: GET /v2/status returns the current last-round (equivalent to block height). Free public API endpoints are available without a key from AlgoNode, Nodely and Tatum. Every provider was live-verified with consecutive keyless GET /v2/status probes at launch.
Methodology
Algorand: 3 free public RPC endpoints answering HTTP GET /v2/status every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Tatum leads at 26 ms. We measure the round-trip latency of a single REST GET to /v2/status against every no-key public Algorand algod node that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / stale / timeout) with an Algorand-scaled staleness gap (90 rounds, around 5 min). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Algorand-scoped answer with per-region breakdowns as a first-class dimension.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus avg(quantile_over_time(...)); per-region breakdowns are first-class on this page via the region tabs.
- Payload: HTTP GET to <base>/v2/status with Accept: application/json. Pure REST endpoint, no API key in any request. The response JSON includes last-round (integer round number).
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Algorand-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=algorand. Provider coverage today: 3 no-key endpoints.
Results: 3 free public Algorand RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | TatumMulti-chain RPC gateway with Algorand algod support, public endpoint, no key required | 26 ms | 43 ms | 112 ms | 88.73% (n=4321) |
| 2 | AlgoNodeCommunity-operated free Algorand mainnet API node, no key required | 77 ms | 119 ms | 286 ms | 99.10% (n=4319) |
| 3 | NodelyNodely free Algorand algod node (mainnet-api.4160.nodely.dev), no key required | 80 ms | 122 ms | 238 ms | 98.98% (n=4321) |
Public Algorand 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.
Tatum
https://algorand-mainnet-algod.gateway.tatum.io26 ms88.7%AlgoNode
https://mainnet-api.algonode.cloud77 ms99.1%
Nodelyhttps://mainnet-api.4160.nodely.dev80 ms99.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 Algorand nodes work without an API key?
3 endpoints are probed on this chain: AlgoNode community node, Nodely (mainnet-api.4160.nodely.dev) and Tatum gateway. Every listed endpoint was live-verified with a GET /v2/status returning a parsable last-round before inclusion.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities