RPCsUpdated

Neo X RPC endpoints: free public URLs by latency

HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public Neo X EVM endpoint, audited every 60 seconds from 3 regions.

TL;DR. As of , Bane Labs has the lowest median latency of the 2 free public Neo X RPC endpoints measured, 117 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/neox-rpc. 2 public endpoints, no key: mainnet-1.rpc.banelabs.org, mainnet-2.rpc.banelabs.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 →

Neo X is Neo's EVM-compatible sidechain (chain 47763). Its keyless roster is unusual: a pair of Bane Labs endpoints (mainnet-1 and mainnet-2.rpc.banelabs.org) plus Thirdweb (47763.rpc.thirdweb.com), all returning chain id 0xba93 on the 2026-10-07 sweep. Neither dRPC nor PublicNode routes Neo X, so two thirds of this board is one operator behind two hostnames, and the page is honest about that rather than presenting three independent choices.

Methodology

Neo X: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Bane Labs leads at 117 ms; the chain-official endpoint measures 117 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public Neo X endpoint that sustains continuous probing, 2 providers measured, 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 X-scaled staleness gap (20 blocks at Neo X's ~1 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Neo X-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":"eth_getBlockByNumber","params":["latest", false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the exclusion rules follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Neo X-scoped view of the same harness.
  • Roster: every endpoint here answered a real `eth_getBlockByNumber` call without a key on the 2026-10-07 sweep before being added to the probe matrix. An endpoint that needs a key, region-blocks us or rate-limits below the 60-second cadence is excluded rather than listed with an asterisk.
  • Chain scope: every query on this page is pinned to `chain="neox"`. Provider coverage: 2 no-key endpoints.

Results: 2 free public Neo X RPC endpoints ranked by p50 latency (24h, 3 regions)

Neo X RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1Bane LabsBane Labs official public RPC endpoint for Neo X mainnet117 ms122 ms455 ms100.00% (n=4321)
2Bane Labs (secondary)Bane Labs secondary public RPC endpoint for Neo X mainnet118 ms121 ms460 ms100.00% (n=4320)

Public Neo X RPC endpoints measured

The 2 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.

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.

Declared, but not answering our probes

This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.

  • Thirdwebhttps://47763.rpc.thirdweb.com1.9 % success over 24 h

Frequently asked

Which Neo X RPCs work without an API key?

3 endpoints are probed on this chain: Bane Labs (mainnet-1.rpc.banelabs.org), Bane Labs (secondary) (mainnet-2.rpc.banelabs.org), Thirdweb (47763.rpc.thirdweb.com). Every listed endpoint was live-verified with a `eth_getBlockByNumber` call returning a parsable response before inclusion.

How is Neo X RPC latency measured here, technically?

One identical `eth_getBlockByNumber` call every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.

Are Neo X's two official endpoints independent?

They are two hostnames operated by Bane Labs, so treat them as one operator with two entry points rather than as redundancy across organisations. That matters for failover planning: if the operator has an incident, both rows on this board can move together, and Thirdweb is the only independent fallback measured here. We list them separately because they measure differently, not because they fail independently.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities