Fastest free Core Chain RPC, live no-key EVM endpoint latency
HTTP round-trip latency for the `eth_getBlockByNumber("latest", false)` method against every free, no-key public Core Chain EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Ankr leads rpc latency at 17 ms (p50, 24h) on Fastest free Core Chain RPC, live no-key EVM endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/core-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Core Chain is a Bitcoin-aligned EVM-compatible L1 blockchain (chain 1116) using a hybrid Satoshi Plus consensus that combines Bitcoin PoW mining with delegated PoS, CORE as gas token, ~3 s block cadence, BTC staking via the Self-Custodial Bitcoin Staking protocol. The 2026-08-04 audit confirms 4 clean keyless providers: the Core DAO official endpoint (rpc.coredao.org), dRPC (core.drpc.org), Thirdweb (1116.rpc.thirdweb.com), and Ankr (rpc.ankr.com/core). Excluded: Alchemy (no Core route), QuickNode (key required).
Methodology
Per-chain member of the RPC latency cluster, extended to Core Chain. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber("latest", false)`) against every no-key public Core Chain endpoint that sustains continuous probing, 4 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 Core Chain-scaled staleness gap (20 blocks at Core Chain's ~3 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Core Chain-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Core Chain RPC right now?
Ankr currently leads at 17 ms (`eth_getBlockByNumber("latest", false)` p50 over the last 24h), measured against 4 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples. Use the region tabs to see the leader from the origin closest to your deployment.
Which Core Chain RPCs work without an API key?
4 endpoints sustain continuous keyless probing: Core DAO official (https://rpc.coredao.org), dRPC (https://core.drpc.org), Thirdweb (https://1116.rpc.thirdweb.com), and Ankr (https://rpc.ankr.com/core). Every listed endpoint was live-verified with a `eth_getBlockByNumber` POST returning a parsable response before inclusion.
Does the fastest Core Chain 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; pick the one closest to where your requests originate.
How is Core Chain RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` POST 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities