Tempo RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public Tempo EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , dRPC has the lowest median latency of the 3 free public Tempo RPC endpoints measured, 55 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/tempo-rpc. 3 public endpoints, no key: tempo.drpc.org, tempo-rpc.publicnode.com, rpc.mainnet.tempo.xyz. 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 →
Tempo is an EVM chain (4217) reachable through 3 keyless endpoints: the official RPC (rpc.mainnet.tempo.xyz), dRPC (tempo.drpc.org) and PublicNode (tempo-rpc.publicnode.com), all returning chain id 0x1079 on the 2026-10-07 sweep. Thirdweb returns no route for 4217, so unlike most chains in this cluster the roster here is the official endpoint plus independent public gateways, with no aggregator-of-last-resort behind them.
Methodology
Tempo: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. dRPC leads at 55 ms; the chain-official endpoint measures 137 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public Tempo endpoint that sustains continuous probing, 3 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Tempo-scaled staleness gap (20 blocks at Tempo's ~1 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Tempo-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":"eth_getBlockByNumber","params":["latest", false]}`. 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 exclusion rules follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Tempo-scoped view of the same harness.
- Roster: every endpoint here answered a real `eth_getBlockByNumber` call without a key on the 2026-10-07 sweep before being added to the probe matrix. An endpoint that needs a key, region-blocks us or rate-limits below the 60-second cadence is excluded rather than listed with an asterisk.
- Chain scope: every query on this page is pinned to `chain="tempo"`. Provider coverage: 3 no-key endpoints.
Results: 3 free public Tempo RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | dRPCdRPC public gateway routing to a Tempo node pool | 55 ms | 94 ms | 166 ms | 100.00% (n=4321) |
| 2 | PublicNodePublicNode free public RPC endpoint for Tempo | 82 ms | 120 ms | 325 ms | 100.00% (n=4322) |
| 3 | TempoTempo official public RPC endpoint for Tempo mainnet | 137 ms | 165 ms | 277 ms | 100.00% (n=4316) |
Public Tempo RPC endpoints measured
The 3 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.
dRPChttps://tempo.drpc.org55 ms100.0%
PublicNodehttps://tempo-rpc.publicnode.com82 ms100.0%Tempo
https://rpc.mainnet.tempo.xyz137 ms100.0%
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 Tempo RPCs work without an API key?
3 endpoints are probed on this chain: Tempo (rpc.mainnet.tempo.xyz), dRPC (tempo.drpc.org), PublicNode (tempo-rpc.publicnode.com). Every listed endpoint was live-verified with a `eth_getBlockByNumber` call returning a parsable response before inclusion.
How is Tempo RPC latency measured here, technically?
One identical `eth_getBlockByNumber` call every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Which Tempo RPC should I use if I only pick one?
Read the region tabs rather than the headline. With no Thirdweb fallback on this chain, the practical question is which public gateway is closer to your deployment, because the official endpoint and a gateway usually trade places by origin. The headline p50 averages three probe regions and will mislead you if your traffic comes from one.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities