Gateway.fm vs SorobanRPC.com

Gateway.fm leads on the only live benchmark. Gateway.fm wins on Fastest free Stellar Soroban RPC, live no-key endpoint latency (271 ms vs 352 ms).

Read methodology Last measured Window: rolling 24h1 shared benchmark
Gateway.fm logo
Gateway.fm

Gateway.fm operates decentralized RPC infrastructure across multiple chains including Stellar Soroban. Public no-key endpoint with generous free tier, routing through a distributed node network.

SorobanRPC.com logo
SorobanRPC.com

Community-operated free public Soroban RPC endpoint dedicated to the Stellar smart contract platform. No API key required; maintained for open developer access to Soroban RPC.

Side by side measurements

Frequently asked questions

Gateway.fm vs SorobanRPC.com: which one is better?

Gateway.fm and SorobanRPC.com are compared on 1 shared OpenChainBench benchmarks. Gateway.fm leads on Fastest free Stellar Soroban RPC, live no-key endpoint latency. See the live table on this page for every metric.

Which is faster, Gateway.fm or SorobanRPC.com?

On the Fastest free Stellar Soroban RPC, live no-key endpoint latency benchmark, Gateway.fm leads at 271 ms versus SorobanRPC.com at 352 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the Gateway.fm vs SorobanRPC.com comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

How this pair was selected

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.