NEAR RPC endpoints: free public URLs by latency
HTTP round-trip latency for block (finality=final) against every available public NEAR Protocol node, audited every 60 seconds from 3 regions.
TL;DR. As of , FastNEAR has the lowest median latency of the 3 free public NEAR RPC endpoints measured, 31 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/near-rpc. 3 public endpoints, no key: free.rpc.fastnear.com, near.drpc.org, rpc.mainnet.near.org. 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 →
NEAR Protocol is a sharded Proof-of-Stake L1 blockchain using Nightshade sharding and Doomslug consensus, targeting roughly one block per second with near-instant practical finality. Public JSON-RPC endpoints are available without an API key from the NEAR Foundation, FastNEAR and dRPC. Every provider was live-verified with consecutive block/finality:final probes at launch.
Methodology
NEAR: 3 free public RPC endpoints answering `block` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. FastNEAR leads at 31 ms. We measure the round-trip latency of a single JSON-RPC call (block with finality=final) against every available public NEAR 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 NEAR-scaled staleness gap (300 blocks, around 5 min). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the NEAR-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: {"jsonrpc":"2.0","id":<rotating>,"method":"block","params":{"finality":"final"}}. Plain HTTP POST. The response carries result.header.height as a decimal uint64.
- 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 NEAR-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=near. Provider coverage today: 3 endpoints.
Results: 3 free public NEAR RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | FastNEARFastNEAR community RPC, free tier, no key required | 31 ms | 60 ms | 164 ms | 100.00% (n=4320) |
| 2 | dRPCdRPC decentralised multi-chain RPC, public NEAR endpoint, no key required | 113 ms | 147 ms | 280 ms | 99.79% (n=4320) |
| 3 | NEAR FoundationOfficial NEAR Foundation public mainnet RPC, keyless | 3.03 s | 3.07 s | 3.21 s | 99.98% (n=4320) |
Public NEAR 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.
FastNEARhttps://free.rpc.fastnear.com31 ms100.0%
dRPChttps://near.drpc.org113 ms99.8%
NEAR Foundationhttps://rpc.mainnet.near.org3.03 s100.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 NEAR RPC endpoints work without an API key?
3 endpoints are probed on this chain: NEAR Foundation (rpc.mainnet.near.org), FastNEAR (free.rpc.fastnear.com) and dRPC (near.drpc.org). Every listed endpoint was live-verified with a block/finality:final call returning a parsable height before inclusion.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities