RPCsLive

Litecoin RPC endpoints: free public URLs by latency

HTTP round-trip latency for block-height queries against every available public Litecoin endpoint, audited every 60 seconds from 3 regions.

TL;DR. As of , Tatum has the lowest median latency of the 2 free public Litecoin RPC endpoints measured above the 50 % success floor (3 listed), 97 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/litecoin-rpc. 3 public endpoints, no key: litecoin-mainnet.gateway.tatum.io, litecoinspace.org, api.blockcypher.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 →

Litecoin is a proof-of-work UTXO blockchain forked from Bitcoin in October 2011; it targets one block every 150 seconds using the Scrypt hashing algorithm. Litecoin exposes a Bitcoin-compatible JSON-RPC interface; the canonical height method is getblockcount. Public endpoints are available without an API key from Tatum (JSON-RPC gateway), BlockCypher (REST GET of its blockchain info endpoint) and LitecoinSpace (Esplora REST GET returning a plain block-height integer). Every provider was live-verified with consecutive block-height probes at launch.

Methodology

Litecoin: 3 free public RPC endpoints answering `getblockcount` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Tatum leads at 97 ms. We measure the round-trip latency of a block-height query against every available public Litecoin endpoint that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. Tatum is probed via JSON-RPC POST (getblockcount). BlockCypher is probed via REST GET of its blockchain info endpoint (height field). LitecoinSpace is probed via Esplora REST GET returning a plain block-height integer. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Litecoin-scaled staleness gap (4 blocks, around 10 min at 150 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Litecoin-scoped answer with per-region breakdowns as a first-class dimension.

Results: 3 free public Litecoin RPC endpoints measured, 2 ranked by p50 latency (24h, 3 regions)

Litecoin RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1Tatum97 ms168 ms221 ms76.19%
2LitecoinSpace128 ms484 ms1.36 s66.13%
Measured, not ranked: sample below the ranking floor
not rankedBlockCypher125 ms136 ms176 ms26.15%

Public Litecoin RPC endpoints measured

The 3 no-key endpoints answering our probes today, with their current 24h median; 1 of them sits below the 50 % success floor and is listed last. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.

  • Tatum logoTatumhttps://litecoin-mainnet.gateway.tatum.io97 ms76.2%
  • LitecoinSpace logoLitecoinSpacehttps://litecoinspace.org/api/blocks/tip/height128 ms66.1%
  • BlockCypher logoBlockCypherhttps://api.blockcypher.com/v1/ltc/main125 ms26.2% ▾

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 Litecoin RPC endpoints work without an API key?

3 endpoints are probed on this chain: Tatum (litecoin-mainnet.gateway.tatum.io, JSON-RPC), BlockCypher (api.blockcypher.com/v1/ltc/main, REST GET) and LitecoinSpace (litecoinspace.org/api/blocks/tip/height, Esplora REST). Every listed endpoint was live-verified with a block-height probe returning a parsable result before inclusion.

Why does LitecoinSpace return a plain integer instead of JSON?

LitecoinSpace is built on the Esplora block explorer API, which exposes the current tip height at /api/blocks/tip/height as a raw ASCII integer with no JSON envelope. This is the same format used by mempool.space for Bitcoin. The harness reads the body directly and parses it as a uint64.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities