Fastest free Aptos RPC, live no-key endpoint latency
HTTP round-trip latency for the Aptos REST ledger endpoint (block_height) against every free, no-key public Aptos node, audited every 60 seconds from 3 regions.
TL;DR. As of , Aptos Labs leads rpc latency at 81 ms (p50, 24h) on Fastest free Aptos RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/aptos-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Aptos is a Move-based L1 blockchain targeting over 100,000 TPS via Block-STM parallel execution, producing roughly one block per second with sub-second finality. Unlike EVM chains, Aptos exposes a REST API rather than JSON-RPC: GET /v1/ returns the current ledger block_height as a decimal string. Free public API endpoints are available without a key from Aptos Labs (two endpoints). Every provider was live-verified with consecutive keyless GET /v1/ probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to Aptos. We measure the round-trip latency of a single REST GET to /v1/ against every no-key public Aptos node that sustains continuous probing: 2 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / stale / timeout) with an Aptos-scaled staleness gap (300 blocks, around 5 min). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Aptos-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Aptos RPC right now?
Aptos Labs currently leads at 81 ms (Aptos REST /v1/ block_height p50 over the last 24h), measured against 2 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Aptos nodes work without an API key?
2 endpoints sustain continuous keyless probing at launch: the Aptos Labs official API node and the Aptos Labs fullnode endpoint. Every listed endpoint was live-verified with a GET /v1/ returning a parsable block_height before inclusion.
Does the fastest Aptos RPC change by region?
Often. Public infra concentrates in specific regions; a gateway that wins from Amsterdam can lose from Singapore by multiples. The region tabs at the top of the page re-scope every number to a single origin.
How is Aptos RPC latency measured here, technically?
One identical REST GET to /v1/ every 60 seconds against each provider from each of 3 regions. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus quantile_over_time over 24 hours. Best-effort measurements; p50 is the median, p90 the 90th percentile and p99 the 99th percentile of latency samples collected over the last 24 hours.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities