Dogecoin RPC endpoints: free public URLs by 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 has the lowest median latency of the 2 free public Dogecoin RPC endpoints measured above the 50 % success floor (3 listed), 102 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/dogecoin-rpc. 3 public endpoints, no key: dogecoin-mainnet.gateway.tatum.io, dogecoin.drpc.org, api.blockcypher.com. 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 →
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
Dogecoin: 3 free public RPC endpoints answering `height` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Tatum leads at 102 ms. We measure the round-trip latency of a block-height query against every available public Dogecoin node that sustains continuous probing: 3 providers live today, 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.
Results: 3 free public Dogecoin RPC endpoints measured, 2 ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Tatum | 102 ms | 143 ms | 221 ms | 74.38% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | dRPC | 179 ms | 256 ms | 810 ms | 99.75% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Measured, not ranked: sample below the ranking floor | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| not ranked | BlockCypher | 128 ms | 146 ms | 372 ms | 26.12% | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Public Dogecoin RPC endpoints measured
The 3 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.
Tatumhttps://dogecoin-mainnet.gateway.tatum.io102 ms74.4%
dRPChttps://dogecoin.drpc.org179 ms99.7%
BlockCypherhttps://api.blockcypher.com/v1/doge/main128 ms26.1% ▾
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.
Frequently asked
Which Dogecoin RPC endpoints work without an API key?
3 endpoints are probed on this chain: 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.
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