Fastest free Dogecoin RPC, live no-key endpoint latency
HTTP round-trip latency for getblockcount against every available public Dogecoin node, audited every 60 seconds from 3 regions.
TL;DR. As of , Tatum posts the lowest rpc latency at 190 ms (p50, 24h) on Fastest free Dogecoin RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/dogecoin-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Dogecoin is a proof-of-work UTXO blockchain forked from Litecoin (itself a Bitcoin fork) and launched in December 2013. It targets one block every 60 seconds using the Scrypt hashing algorithm and has no hard supply cap. Dogecoin exposes a Bitcoin-compatible JSON-RPC interface; most node implementations accept `getblockcount` as a standard method. Public endpoints are available without an API key from Tatum, dRPC and BlockCypher. BlockCypher exposes a REST API instead of JSON-RPC, returning the current chain height via a GET request to its blockchain info endpoint. Every provider was live-verified with consecutive block-height probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to Dogecoin. We measure the round-trip latency of a block-height query against every available public Dogecoin node that sustains continuous probing: 3 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. Tatum and dRPC are probed via JSON-RPC POST (getblockcount); BlockCypher via REST GET of its blockchain info endpoint. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Dogecoin-scaled staleness gap (5 blocks, around 5 min at 60 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Dogecoin-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Dogecoin RPC right now?
Tatum currently leads at 190 ms (Dogecoin block count 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 Dogecoin RPC endpoints work without an API key?
3 endpoints sustain continuous keyless probing at launch: Tatum (dogecoin-mainnet.gateway.tatum.io, JSON-RPC), dRPC (dogecoin.drpc.org, JSON-RPC) and BlockCypher (api.blockcypher.com/v1/doge/main, REST GET). Every listed endpoint was live-verified with a block-height probe returning a parsable result before inclusion.
Does the fastest Dogecoin RPC change by region?
Often. dRPC routes through a decentralized mesh so latency varies by origin region; Tatum and BlockCypher have fixed infrastructure, so latency rankings can shift significantly depending on your geographic origin. The region tabs at the top of the page re-scope every number to a single origin.
How is Dogecoin RPC latency measured here, technically?
One block-height probe 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. Tatum and dRPC use JSON-RPC POST (getblockcount); BlockCypher uses REST GET of its blockchain info endpoint. 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.
Why does BlockCypher use a different API method than the other Dogecoin providers?
BlockCypher exposes a proprietary REST API rather than a Bitcoin-compatible JSON-RPC interface. Instead of getblockcount, we send a GET request to its blockchain info endpoint, which returns a JSON object with a height field. The measurement logic is identical: client-side round-trip in milliseconds, classified as ok when a parsable block height is returned.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities