Sui RPC endpoints: free public URLs by latency
HTTP round-trip latency for sui_getLatestCheckpointSequenceNumber against every free, no-key public Sui RPC endpoint, audited every 60 seconds from 3 regions.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Sui is a Move-based L1 blockchain using the Mysticeti DAG-BFT consensus protocol, producing checkpoints every roughly 3 seconds with deterministic sub-second finality. Free public RPC endpoints are available without an API key from PublicNode, BlockVision, Suiet and OnFinality. Mysten Labs' public fullnode retired JSON-RPC and left on 2026-10-19. Every provider was live-verified with consecutive keyless sui_getLatestCheckpointSequenceNumber probes at launch.
Methodology
Sui: 0 free public RPC endpoints answering `sui_getLatestCheckpointSequenceNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 74 ms. We measure the round-trip latency of a single, identical JSON-RPC call (sui_getLatestCheckpointSequenceNumber) against every no-key public Sui endpoint that sustains continuous probing: 0 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 Sui-scaled staleness gap (100 checkpoints, around 5 min). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Sui-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":"sui_getLatestCheckpointSequenceNumber","params":[]}. 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 archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Sui-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=sui. Provider coverage today: 0 no-key endpoints.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities