Hyperliquid RPC endpoints: free public URLs and private API-key providers by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Hyperliquid RPC endpoint (probed every 60 seconds) and, under the Access selector (Private), against the API-key endpoints of Alchemy, Chainstack, GetBlock, QuickNode and Dwellir (every 120 seconds), from 3 regions. The two cohorts are ranked separately, never against each other.
TL;DR. As of , Purroof Group has the lowest median latency of the 5 free public Hyperliquid RPC endpoints measured, 126 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/hyperliquid-rpc. Chain ID 999. 5 public endpoints, no key: rpc.purroofgroup.com, rpc.hyperliquid.xyz, rpc.hypurrscan.io, hyperliquid.drpc.org, hyperliquid-json-rpc.stakely.io. Full URLs with their 24h median are listed below; Alchemy, Chainstack, GetBlock, QuickNode, Dwellir (private, API key) are ranked apart under the Private tab.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Hyperliquid's HyperEVM (chain id 999) is the EVM execution layer bolted onto the HyperCore perps engine. Standard Ethereum JSON-RPC wire, so the probe is `eth_getBlockByNumber("latest", false)` , the same call the Ethereum, Base, Arbitrum and 20+ other chain benches use. Provider cohort at launch: Hyperliquid Labs's official `rpc.hyperliquid.xyz/evm`, dRPC, Stakely, Purroof Group and Hypurrscan. Alchemy demo path (rate-limited dead), Grove/Pocket public LB (needs an app id at the public LB path), thirdweb (returns "Invalid chain" on HyperEVM) and the AllThatNode / Blast API guesses (DNS not resolving to a public HyperEVM endpoint) were audited alongside and excluded. Each will be revisited when a stable no-key path reappears.
Methodology
Hyperliquid: 5 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Purroof Group leads at 126 ms; the chain-official endpoint measures 151 ms. The same page carries the private cohort (API key), Alchemy, Chainstack, GetBlock, QuickNode and Dwellir on their keyed Hyperliquid endpoints every 120 seconds: switch the Access selector; QuickNode leads it at 6 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber("latest", false)`) against every no-key public HyperEVM endpoint that sustains continuous probing, 5 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with the standard EVM staleness gap (block gap = 25 blocks ≈ 50 seconds at HyperEVM's ~2 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Hyperliquid-scoped answer with per-region breakdowns as a first-class dimension.
Results: 5 free public Hyperliquid RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Purroof Group | 126 ms | 133 ms | 155 ms | 97.66% (n=4323) |
| 2 | Hyperliquid Labs | 151 ms | 167 ms | 217 ms | 97.78% (n=4329) |
| 3 | Hypurrscan | 160 ms | 177 ms | 565 ms | 100.00% (n=4330) |
| 4 | dRPC | 160 ms | 216 ms | 607 ms | 99.70% (n=4329) |
| 5 | Stakely | 381 ms | 657 ms | 1.13 s | 99.26% (n=4328) |
Public Hyperliquid RPC endpoints measured
Chain ID 999, currency HYPE. The 5 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. Alchemy, Chainstack, GetBlock, QuickNode and Dwellir, private endpoints that need an API key, are ranked separately under the Private tab; keyed URLs are never listed.
Purroof Grouphttps://rpc.purroofgroup.com126 ms97.7%
Hyperliquid Labshttps://rpc.hyperliquid.xyz/evm151 ms97.8%
Hypurrscanhttps://rpc.hypurrscan.io160 ms100.0%
dRPChttps://hyperliquid.drpc.org160 ms99.7%
Stakelyhttps://hyperliquid-json-rpc.stakely.io381 ms99.3%
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 Hyperliquid RPCs work without an API key?
5 endpoints are probed on this chain; each is listed with its URL, 24h median and success rate in the endpoints table on this page. Every listed endpoint was live-verified with an `eth_getBlockByNumber` POST returning a parsable hex head before inclusion. Excluded by the audit: Alchemy's demo key path is rate-limited dead, thirdweb returns `Invalid chain` on HyperEVM, Grove/Pocket public LB requires an app id at the LB path, and AllThatNode / Blast API / Chainstack / Gelato / Imperator HyperEVM paths either DNS-fail or 401 without a key. HyperEVM is a young chain so this list will shift as providers stand up dedicated endpoints.
How is Hyperliquid RPC latency measured here, technically?
One identical JSON-RPC POST (`eth_getBlockByNumber("latest", false)`) every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the EVM cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Why is the probe `eth_getBlockByNumber` and not `eth_blockNumber`?
Two reasons. First, `eth_getBlockByNumber("latest", false)` forces the node to actually assemble the block header (timestamp, hash, gas metrics) which a polite CDN cannot synthesise from a stale integer , `eth_blockNumber` on its own can be answered from an edge cache without touching a node, defeating the point of a latency probe. Second, the returned header lets the harness populate the `latest_block_hash` and `timestamp` fields the cross-provider tip machinery uses to detect stale endpoints. Both together mean the number on this page is what your app actually pays when it fetches a fresh head.
Which Hyperliquid RPC provider is fastest with an API key?
Per the live data: QuickNode at 6 ms (eth_getBlockByNumber p50 over 24h, averaged across us-east, eu-west and Singapore); Alchemy measures 8 ms, Chainstack 48 ms and QuickNode 6 ms; GetBlock measures 83 ms. On the free cohort Purroof Group leads at 126 ms, measured on the same call from the same three regions; the two cohorts are never ranked in one table (shared gateways at 60 s against metered endpoints at 120 s). Switch the Access selector to Private for the region tabs and the p99 column; plan tiers are disclosed in the methodology.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities