Fastest free LUKSO RPC, live no-key endpoint latency
HTTP round-trip latency for eth_getBlockByNumber against every available public LUKSO endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , LUKSO Foundation posts the lowest rpc latency at 345 ms (p50, 24h) on Fastest free LUKSO RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/lukso-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
LUKSO is an EVM layer-1 (chain ID 42) built around Universal Profiles and the LSP standards. It speaks standard Ethereum JSON-RPC, so the canonical height probe is eth_getBlockByNumber('latest'). Three providers serve LUKSO mainnet with no API key: the LUKSO Foundation's official RPC, NOWNodes (public no-key endpoint, 5 requests per second) and thirdweb's public edge. All three were live-verified at launch, returning the same chain tip.
Methodology
Per-chain member of the RPC latency cluster, extended to LUKSO. We probe every public no-key endpoint with a single eth_getBlockByNumber call every 60 seconds from three regions (us-east, eu-west, Singapore) and record wall-clock round-trip latency. Only ok responses (HTTP 200 with a usable block height, not stale) contribute to the distribution; p50/p90/p99 are computed via Prometheus quantile_over_time over a rolling 24-hour window.
Frequently asked
Which free LUKSO RPC is fastest?
Per the live data above: LUKSO Foundation at 345 ms (eth_getBlockByNumber p50, 24h) across the no-key providers measured here.
How is LUKSO RPC latency measured?
A single eth_getBlockByNumber call every 60 seconds from three regions (us-east, eu-west, Singapore), recording the wall-clock round trip. Only successful, non-stale responses count.
Do these endpoints need an API key?
No. LUKSO Foundation, NOWNodes and thirdweb all serve LUKSO mainnet JSON-RPC with no key. NOWNodes' public endpoint is rate-limited to 5 requests per second.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities