Stellar Soroban RPC endpoints: free public URLs by latency
HTTP round-trip latency for getLatestLedger against every free, no-key public Stellar Soroban RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , OnFinality has the lowest median latency of the 5 free public Stellar Soroban RPC endpoints measured, 112 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/stellar-rpc. 5 public endpoints, no key: stellar.api.onfinality.io, rpc.lightsail.network, mainnet.sorobanrpc.com, soroban-rpc.mainnet.stellar.gateway.fm, rpc.ankr.com. 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 →
Stellar uses the Stellar Consensus Protocol (SCP) with roughly 5-second ledger closes and deterministic finality on every close. Soroban is Stellar's smart contract platform with a dedicated JSON-RPC interface. Free public Soroban RPC endpoints are available without an API key from Gateway.fm, Ankr, OnFinality, SorobanRPC.com and Lightsail Network. Every provider was live-verified with consecutive keyless getLatestLedger probes at launch.
Methodology
Stellar Soroban: 5 free public RPC endpoints answering `getLatestLedger` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. OnFinality leads at 112 ms. We measure the round-trip latency of a single, identical JSON-RPC call (getLatestLedger) against every no-key public Stellar Soroban endpoint that sustains continuous probing: 5 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 Stellar-scaled staleness gap (roughly 5 s per ledger). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Stellar-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":"getLatestLedger","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 Stellar Soroban-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=stellar. Provider coverage today: 5 no-key Soroban endpoints.
Results: 5 free public Stellar Soroban RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | OnFinalityGlobal multi-chain gateway, 70+ networks, rate-limited public tier, 5 req/sec | 112 ms | 128 ms | 730 ms | 88.65% (n=4318) |
| 2 | Lightsail NetworkLightsail Quasar node, public Stellar Soroban RPC for mainnet, no key required | 148 ms | 266 ms | 699 ms | 98.70% (n=4318) |
| 3 | SorobanRPC.comCommunity-run public Soroban RPC endpoint dedicated to Stellar mainnet, no key required | 159 ms | 311 ms | 873 ms | 95.60% (n=4319) |
| 4 | Gateway.fmDecentralized infrastructure provider with a public Stellar Soroban RPC endpoint, no key required | 189 ms | 261 ms | 430 ms | 99.77% (n=4320) |
| 5 | AnkrMulti-chain RPC platform with a public Stellar Soroban endpoint, no key required | 610 ms | 1.24 s | 1.81 s | 99.77% (n=4318) |
Public Stellar Soroban RPC endpoints measured
The 5 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.
OnFinalityhttps://stellar.api.onfinality.io/public112 ms88.6%Lightsail Network
https://rpc.lightsail.network/148 ms98.7%SorobanRPC.com
https://mainnet.sorobanrpc.com159 ms95.6%Gateway.fm
https://soroban-rpc.mainnet.stellar.gateway.fm189 ms99.8%
Ankrhttps://rpc.ankr.com/stellar_soroban610 ms99.8%
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 Stellar Soroban RPCs work without an API key?
5 endpoints are probed on this chain; each is listed with its URL, 24h median and success rate in the endpoints table on this page, and the list changes as providers come and go. Every listed endpoint was live-verified with a `getLatestLedger` request before inclusion.
What is the difference between Stellar Horizon and Soroban RPC?
Horizon is Stellar's REST API for classic payments and account operations. Soroban RPC is the JSON-RPC interface for Stellar's smart contract platform. This benchmark measures Soroban RPC endpoints since they are the primary interface for dApp developers building on Stellar.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities