ICON RPC endpoints: free public URLs by latency
HTTP round-trip latency for icx_getLastBlock queries against every available public ICON blockchain endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , ICON Foundation has the lowest median latency of the 3 free public ICON RPC endpoints measured, 64 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/icon-rpc. 3 public endpoints, no key: ctz.solidwallet.io, api.iconblockchain.xyz, api.icon.community. 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 →
ICON is a South Korean L1 blockchain focused on interoperability and enterprise adoption, using a Delegated Proof of Contribution (DPoC) consensus with roughly 2-second block finality. ICON nodes expose a JSON-RPC 2.0 API: POST /api/v3 with method icx_getLastBlock returns the latest block height as a decimal integer. Free public endpoints are available keyless from the ICON Foundation (ctz.solidwallet.io), ICON Community (api.icon.community), and iconblockchain.xyz. Every provider was live-verified with consecutive block-height probes at launch.
Methodology
ICON: 3 free public RPC endpoints answering `POST /api/v3` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. ICON Foundation leads at 64 ms. We measure the round-trip latency of a JSON-RPC icx_getLastBlock call against every available public ICON endpoint that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. Each provider is probed via a POST /api/v3 request from which the block height is extracted from result.height. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with an ICON-scaled staleness gap (150 blocks, around 5 min at 2 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the ICON-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public ICON RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | ICON Foundation | 64 ms | 112 ms | 194 ms | 99.98% |
| 2 | iconblockchain.xyz | 210 ms | 403 ms | 1.71 s | 85.64% |
| 3 | ICON Community | 231 ms | 595 ms | 837 ms | 99.86% |
Public ICON 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.
ICON Foundationhttps://ctz.solidwallet.io64 ms100.0%
iconblockchain.xyzhttps://api.iconblockchain.xyz210 ms85.6%- ICON Community
https://api.icon.community231 ms99.9%
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 ICON RPC endpoints work without an API key?
3 endpoints are probed on this chain: ICON Foundation (ctz.solidwallet.io), ICON Community (api.icon.community), and iconblockchain.xyz. Every listed endpoint was live-verified before inclusion.
What is ICON and why does its RPC latency matter?
ICON is a South Korean blockchain focused on enterprise interoperability, originally built for connecting financial institutions and public organizations. ICX wallets, DApp integrations, and BTP cross-chain bridging all depend on reliable RPC access. Low latency matters for real-time ICX transfers and DeFi protocols built on the ICON ecosystem.
What is the ICX token?
ICX is the native staking and governance token of the ICON network. It is used to pay transaction fees, stake with validators (P-Reps), and participate in on-chain governance. ICON uses a Delegated Proof of Contribution model where P-Reps are elected by ICX holders.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities