Fastest free HAQQ Network RPC, live no-key endpoint latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public HAQQ Network EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode leads rpc latency at 109 ms (p50, 24h) on Fastest free HAQQ Network RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/haqq-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
HAQQ Network (chain 11235) is a Cosmos SDK EVM-compatible blockchain focused on Islamic finance and halal DeFi, with ISLM as the native gas token. Four keyless endpoints are probed continuously: PublicNode (haqq-evm-rpc.publicnode.com), dRPC (haqq.drpc.org), HAQQ Foundation official (rpc.eth.haqq.network), and Blast API.
Methodology
Per-chain member of the RPC latency cluster, extended to HAQQ Network. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public HAQQ Network endpoint that sustains continuous probing, 4 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the HAQQ-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free HAQQ Network RPC right now?
PublicNode currently leads at 109 ms (`eth_getBlockByNumber` p50 over the last 24h), measured against 4 no-key providers probed every 60 seconds from us-east, eu-west and Singapore.
Which HAQQ Network RPCs work without an API key?
4 endpoints sustain continuous keyless probing: PublicNode, dRPC, HAQQ Foundation official, and Blast API. Every endpoint was live-verified before inclusion.
Does the fastest HAQQ RPC change by region?
Often. The region tabs at the top of the page re-scope every number to a single origin.
How is HAQQ Network RPC latency measured here?
One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against each provider from each of 3 regions.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities