Peaq Network RPC endpoints: free public URLs by latency
HTTP round-trip latency for chain_getHeader against every free, no-key public Peaq Network Polkadot parachain endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , OnFinality has the lowest median latency of the 2 free public Peaq Network RPC endpoints measured, 49 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/peaq-rpc. 2 public endpoints, no key: peaq.api.onfinality.io, peaq-rpc.publicnode.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 →
Peaq Network is a DePIN (Decentralized Physical Infrastructure) parachain on Polkadot focused on the machine economy and IoT connectivity. PEAQ is the native token. Partnerships with Bosch and Fetch.ai underpin its real-world machine data use cases. 2 keyless endpoints are probed continuously, each listed with its URL in the endpoints table above.
Methodology
Peaq Network: 2 free public RPC endpoints answering `chain_getHeader` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. OnFinality leads at 49 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`chain_getHeader`) against every no-key public Peaq parachain endpoint that sustains continuous probing, 2 providers live today, 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 Peaq-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":"chain_getHeader","params":[]}`. Plain HTTP POST, identical for every endpoint, no API key in any request.
- 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 Peaq Network-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="peaq"`. Provider coverage today: 2 no-key endpoints.
Results: 2 free public Peaq Network RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | OnFinalityOnFinality Substrate public gateway for Peaq | 49 ms | 95 ms | 1.38 s | 100.00% (n=4321) |
| 2 | PublicNodePublicNode multi-chain gateway including Substrate/Peaq | 81 ms | 103 ms | 255 ms | 100.00% (n=4319) |
Public Peaq Network RPC endpoints measured
The 2 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
OnFinalityhttps://peaq.api.onfinality.io/public49 ms100.0%
PublicNodehttps://peaq-rpc.publicnode.com81 ms100.0%
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 Peaq Network RPCs work without an API key?
2 endpoints are probed on this chain, each listed with its URL in the endpoints table above.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities