NEO N3 RPC endpoints: free public URLs by 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 , NSPCC has the lowest median latency of the 3 free public NEO N3 RPC endpoints measured, 90 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/neo-rpc. 3 public endpoints, no key: rpc10.n3.nspcc.ru:10331, n3seed2.ngd.network:10332, n3seed1.ngd.network:10332. 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 →
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 60 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
NEO N3: 3 free public RPC endpoints answering `getblockcount` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. NSPCC leads at 90 ms. 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 live today, 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.
Results: 3 free public NEO N3 RPC endpoints ranked by p50 latency (24h, 3 regions)
Public NEO N3 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.
NSPCChttps://rpc10.n3.nspcc.ru:1033190 ms100.0%- NGD (2)
https://n3seed2.ngd.network:10332146 ms100.0% - NGD
https://n3seed1.ngd.network:10332146 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 NEO N3 RPC endpoints work without an API key?
3 endpoints are probed on this chain: 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities