Harmony ONE RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Harmony ONE RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Harmony S0 has the lowest median latency of the 2 free public Harmony ONE RPC endpoints measured, 129 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/harmony-rpc. Chain ID 1666600000. 2 public endpoints, no key: a.api.s0.t.hmny.io, harmony-0.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 →
Harmony (chain 1666600000) is a proof-of-stake sharded EVM blockchain, ONE gas token, running four shards with Effective Proof of Stake across roughly 1000 validators, achieving fast-finality at around 2 seconds on Shard 0. Harmony S0 provides keyless shard-0 access probed every 60 seconds from three regions.
Methodology
Harmony ONE: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Harmony S0 leads at 129 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Harmony ONE endpoint that sustains continuous probing, 2 provider at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) so the leaderboard rewards sustained availability rather than fast error messages. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Harmony ONE-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.
- 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 Harmony ONE-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="harmony"`. Provider coverage today: 2 no-key endpoints (Harmony S0).
Results: 2 free public Harmony ONE RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Harmony S0Harmony Foundation Shard-0 alternate gateway | 129 ms | 139 ms | 393 ms | 100.00% (n=4321) |
| 2 | dRPCDecentralized RPC mesh, keyless public endpoint for shard 0 | 177 ms | 357 ms | 443 ms | 100.00% (n=4321) |
Public Harmony ONE RPC endpoints measured
Chain ID 1666600000, currency ONE. 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.
Harmony S0https://a.api.s0.t.hmny.io129 ms100.0%
dRPChttps://harmony-0.drpc.org177 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 Harmony ONE RPCs work without an API key?
2 endpoint sustains continuous keyless probing at launch: Harmony S0. Every listed endpoint was live-verified before inclusion.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities