Fastest free NEO N3 RPC, live no-key endpoint latency
HTTP round-trip latency for getblockcount against every available public NEO N3 node, audited every 60 seconds from 3 regions.
TL;DR. As of , NGD (2) leads rpc latency at 3 ms (p50, 24h) on Fastest free NEO N3 RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/neo-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
NEO N3 is the third generation of the NEO blockchain, a delegated Byzantine Fault Tolerant (dBFT) proof-of-stake L1 blockchain targeting one block every 15 seconds with one-block deterministic finality. NEO N3 uses a dual-token model (NEO for governance/GAS generation, GAS for transaction fees) and supports smart contracts in multiple languages via the NeoVM. Public JSON-RPC endpoints are available without an API key from NSPCC and Neo Global Development. Every provider was live-verified with consecutive getblockcount probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to NEO N3. We measure the round-trip latency of a single JSON-RPC call (getblockcount) against every available public NEO N3 node that sustains continuous probing: 3 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a NEO-scaled staleness gap (20 blocks, around 5 min at 15 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the NEO N3-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free NEO N3 RPC right now?
NGD (2) currently leads at 3 ms (NEO N3 block count p50 over the last 24h), measured against 3 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which NEO N3 RPC endpoints work without an API key?
3 endpoints sustain continuous keyless probing at launch: NSPCC (rpc10.n3.nspcc.ru:10331), NGD seed node 1 (n3seed1.ngd.network:10332) and NGD seed node 2 (n3seed2.ngd.network:10332). Every listed endpoint was live-verified with a getblockcount call returning a parsable block count before inclusion.
Does the fastest NEO N3 RPC change by region?
Often. Public infra concentrates in specific regions; NSPCC is Russia-hosted and NGD nodes are in Asia, so latency rankings shift significantly by origin. The region tabs at the top of the page re-scope every number to a single origin.
How is NEO N3 RPC latency measured here, technically?
One getblockcount JSON-RPC call 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