Fastest free Telos EVM RPC, live no-key endpoint latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Telos EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , dRPC leads rpc latency at 201 ms (p50, 24h) on Fastest free Telos EVM RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/telos-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Telos EVM (chain 40) is a high-performance EVM-compatible blockchain with sub-0.5 second block times, TLOS as the gas token, and a carbon-neutral operational commitment. One of the longest-running EVM-compatible chains, live since 2021. Three keyless endpoints are probed continuously: Telos Foundation official (mainnet.telos.net/evm), dRPC (telos.drpc.org), and Blast API.
Methodology
Per-chain member of the RPC latency cluster, extended to Telos EVM. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Telos EVM endpoint that sustains continuous probing, 3 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Telos-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Telos EVM RPC right now?
dRPC currently leads at 201 ms (`eth_getBlockByNumber` p50 over the last 24h), measured against 3 no-key providers probed every 60 seconds from us-east, eu-west and Singapore.
Which Telos EVM RPCs work without an API key?
3 endpoints sustain continuous keyless probing: Telos Foundation official, dRPC, and Blast API. Every endpoint was live-verified before inclusion.
Does the fastest Telos RPC change by region?
Often. The region tabs at the top of the page re-scope every number to a single origin.
How is Telos EVM RPC latency measured here?
One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against each provider from each of 3 regions.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities