ApeChain RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public ApeChain EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , ApeChain is the only one of the 2 free public ApeChain RPC endpoints measured above the 50 % success floor, at 178 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/apechain-rpc. Chain ID 33139. 2 public endpoints, no key: rpc.apechain.com, apechain.drpc.org. 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 →
ApeChain is an Arbitrum Orbit L3 (chain 33139) operated by Yuga Labs / ApeDAO, dedicated to the APE ecosystem, APE gas token, ~250 ms block cadence, settlement onto Arbitrum One. 2026-08-03 re-audit brings the total to 2 clean keyless providers: the ApeChain official endpoint (rpc.apechain.com/http), dRPC (apechain.drpc.org), Thirdweb (apechain.rpc.thirdweb.com), and Tenderly Gateway (gateway.tenderly.co/public/apechain). Excluded: Alchemy (key required), QuickNode (key required), Infura (no apechain route).
Methodology
ApeChain: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. ApeChain leads at 178 ms; the chain-official endpoint measures 178 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public ApeChain endpoint that sustains continuous probing, 2 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 an ApeChain-scaled staleness gap (20 blocks at ApeChain's ~250 ms block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the ApeChain-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 archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the ApeChain-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="apechain"`. Provider coverage: 2 no-key endpoints.
Results: 2 free public ApeChain RPC endpoints measured, 1 ranked by p50 latency (24h, 3 regions)
Public ApeChain RPC endpoints measured
Chain ID 33139, currency APE. The 2 no-key endpoints answering our probes today, with their current 24h median; 1 of them sits below the 50 % success floor and is listed last. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
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.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://apechain.rpc.thirdweb.com2.4 % success over 24 h
Frequently asked
Which ApeChain RPCs work without an API key?
4 endpoints are probed on this chain: the ApeChain official endpoint (rpc.apechain.com/http), dRPC (apechain.drpc.org), Thirdweb (apechain.rpc.thirdweb.com), and Tenderly Gateway (gateway.tenderly.co/public/apechain). Every listed endpoint was live-verified with a `eth_getBlockByNumber` POST returning a parsable response before inclusion.
How is ApeChain 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