Tezos RPC endpoints: free public URLs by latency
HTTP round-trip latency for GET /chains/main/blocks/head/header against every available public Tezos node, audited every 60 seconds from 3 regions.
TL;DR. As of , TezBeta has the lowest median latency of the 4 free public Tezos RPC endpoints measured, 91 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/tezos-rpc. 4 public endpoints, no key: rpc.tzbeta.net, rpc.tzkt.io, mainnet.smartpy.io, prod.tcinfra.net. 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 →
Tezos is a self-amending proof-of-stake blockchain using Liquid Proof of Stake (LPoS) and an on-chain governance mechanism that allows protocol upgrades without hard forks. It targets roughly one block every 30 seconds on mainnet. Public REST endpoints are available without an API key from SmartPy, TezBeta, TzKT (Baking Bad) and TCInfra. Every provider was live-verified with consecutive block header probes at launch.
Methodology
Tezos: 4 free public RPC endpoints answering `GET /chains/main/blocks/head/header` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. TezBeta leads at 91 ms. We measure the round-trip latency of a single REST call (GET /chains/main/blocks/head/header) against every available public Tezos node that sustains continuous probing: 4 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 Tezos-scaled staleness gap (10 blocks, around 5 min at 30 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Tezos-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: HTTP GET /chains/main/blocks/head/header. Plain REST call. The response carries a JSON object with the level field as a plain integer.
- 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 Tezos-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=tezos. Provider coverage today: 4 endpoints (SmartPy, TezBeta, TzKT, TCInfra).
Results: 4 free public Tezos RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | TezBetaTezBeta public Tezos mainnet RPC, keyless | 91 ms | 101 ms | 378 ms | 99.61% (n=4320) |
| 2 | TzKT (Baking Bad)TzKT public Tezos mainnet RPC by Baking Bad, keyless | 208 ms | 239 ms | 621 ms | 99.91% (n=4315) |
| 3 | SmartPySmartPy public Tezos mainnet RPC, keyless | 242 ms | 1.03 s | 4.78 s | 90.28% (n=4321) |
| 4 | TCInfraTCInfra public Tezos mainnet RPC, keyless | 251 ms | 317 ms | 594 ms | 99.24% (n=4319) |
Public Tezos RPC endpoints measured
The 4 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.
TezBetahttps://rpc.tzbeta.net91 ms99.6%
TzKT (Baking Bad)https://rpc.tzkt.io/mainnet208 ms99.9%- SMSmartPy
https://mainnet.smartpy.io242 ms90.3%
TCInfrahttps://prod.tcinfra.net/rpc/mainnet251 ms99.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 Tezos RPC endpoints work without an API key?
4 endpoints are probed on this chain: SmartPy (mainnet.smartpy.io), TezBeta (rpc.tzbeta.net), TzKT by Baking Bad (rpc.tzkt.io/mainnet) and TCInfra (prod.tcinfra.net/rpc/mainnet). Every listed endpoint was live-verified with a block header call returning a parsable level before inclusion.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities