Fastest free ThunderCore RPC, live no-key endpoint latency
HTTP round-trip latency for eth_getBlockByNumber against every available public ThunderCore node, audited every 60 seconds from 3 regions.
TL;DR. As of , ThunderToken leads rpc latency at 37 ms (p50, 24h) on Fastest free ThunderCore RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/thundercore-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
ThunderCore is an EVM-compatible Layer 1 blockchain (chain ID 108) designed for high throughput, producing approximately one block per second with fast finality. It runs a modified version of Ethereum with the Thunder consensus protocol and exposes a standard JSON-RPC interface. Public EVM endpoints are available without an API key from ThunderCore Official, ThunderToken and dRPC. Every provider was live-verified with consecutive eth_getBlockByNumber probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to ThunderCore. We measure the round-trip latency of a single eth_getBlockByNumber ("latest", false) call against every available public ThunderCore node that sustains continuous probing: 3 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a standard EVM staleness gap. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the ThunderCore-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free ThunderCore RPC right now?
ThunderToken currently leads at 37 ms (ThunderCore block number p50 over the last 24h), measured against 3 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which ThunderCore RPC endpoints work without an API key?
3 endpoints sustain continuous keyless probing at launch: ThunderCore Official (mainnet-rpc.thundercore.com), ThunderToken (mainnet-rpc.thundertoken.net) and dRPC (thundercore.drpc.org). Every listed endpoint was live-verified with an eth_getBlockByNumber call returning a parsable block number before inclusion.
Does the fastest ThunderCore RPC change by region?
Often. Public infra concentrates in specific regions; a gateway that wins from Amsterdam can lose from Singapore by multiples. The region tabs at the top of the page re-scope every number to a single origin.
How is ThunderCore RPC latency measured here, technically?
One eth_getBlockByNumber JSON-RPC call every 60 seconds against each provider from each of 3 regions. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus quantile_over_time over 24 hours. Best-effort measurements; p50 is the median, p90 the 90th percentile and p99 the 99th percentile of latency samples collected over the last 24 hours.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities