Black Friday ~40% off Growth and Pro annual plans See offers
  • Agents
  • Pricing

How Global Node GEN 2.0 upgrade made Hyperliquid RPC up to 48x faster

Created Nov 18, 2026 Updated Nov 20, 2026
Hyperliquid Gen 2 Banner logo

Summary: GEN 2.0 is a major update to Chainstack Global Nodes, as significant for Hyperliquid developers as a protocol upgrade is for the network. On Hyperliquid mainnet it brings the median time to first byte (TTFB) down from 175 ms to 81 ms: 53.7% lower, or 2.2x faster. The same probe measured both routes in all 16 cities, and 15 of them improved, from 1.9x in New York to 48.0x in Los Angeles. Dubai is the exception, going from 199 ms to 265 ms.

On Hyperliquid, trading bots and market-data tools poll the node constantly, and a slow first byte costs them reaction time. The GEN 2.0 routing change targets exactly that wait. This post measures it from 16 cities, including the one where it went the wrong way.

What changed for Hyperliquid requests

Hyperliquid Global Nodes no longer send calls through a Cloudflare Workers edge layer. DNS load balancing picks the nearest healthy region, and the request lands on that region’s gateway and then on the node, the same path every Global Nodes chain now uses.

Hyperliquid request path before and after GEN 2.0: client, edge worker, ingress and node on top; client, regional gateway and node below

The wider rollout. Hyperliquid is one of the chains moved to GEN 2.0. For the architecture and the rest of the list, see Chainstack GEN 2.0 is live: faster Global Nodes.

How we measured Hyperliquid

We sent an RPC request to a Chainstack Hyperliquid endpoint from Globalping probes in 16 cities and recorded the TTFB on two routes in the same minute on Oct 29, 2026: the pre-GEN 2.0 route through Cloudflare and the GEN 2.0 direct route.

Unlike on some other chains, every one of the 16 cities used the same probe on both routes, so the headline covers all 16 and the full table has no asterisks.

Hyperliquid mainnet results: median TTFB fell from 175 ms to 81 ms

Metric (16 cities)Before GEN 2.0GEN 2.0
Median TTFB175 ms81 ms
Mean TTFB286 ms93 ms
Reduction at the median–53.7%
Faster at the median–2.2x
Cities that improved–15 of 16
Range of improvement–0.8x to 48.0x
Hyperliquid Mainnet time to first byte before and after GEN 2.0 in 16 cities: median 175 ms before, 81 ms with GEN 2.0

Full per-city results (Hyperliquid mainnet)

CityCountryBefore GEN 2.0 (ms)GEN 2.0 (ms)Saved (ms)Faster (x)
New DelhiIndia7191565634.6
San JoséCosta Rica5571064515.3
São PauloBrazil5361963402.7
Cape TownSouth Africa5121513613.4
Buenos AiresArgentina4831902932.5
MelbourneAustralia3611132483.2
SingaporeSingapore260831773.1
DubaiUnited Arab Emirates199265-660.8
LisbonPortugal151381134.0
New YorkUnited States14779681.9
IstanbulTurkey145431023.4
DallasUnited States143361074.0
TokyoJapan113311037.7
Los AngelesUnited States9629448.0
LondonUnited Kingdom8420644.2
AmsterdamNetherlands729638.0

All 16 rows used the same probe on both routes. A value of 0.8x means the GEN 2.0 route was slower in that city.

Where Hyperliquid gains the most

  • In milliseconds: New Delhi saves 563 ms (719 ms to 156 ms), San José 451 ms (557 ms to 106 ms) and Cape Town 361 ms (512 ms to 151 ms).
  • As a ratio: Los Angeles drops from 96 ms to 2 ms (48.0x), Tokyo from 113 ms to 3 ms (37.7x) and Amsterdam from 72 ms to 9 ms (8.0x).
  • The smallest gain: New York improves 1.9x, from 147 ms to 79 ms.
  • The exception: Dubai is the only city that got slower, from 199 ms to 265 ms (0.8x).

How does Hyperliquid compare today?

Compare ranks providers on p95 latency and success rate, measured for Hyperliquid from Germany, Japan and the US, over methods that include the Hyperliquid-specific clearinghouseState and openOrders. As of Nov 18, 2026 (last 7 days), Chainstack ranks #1:

  • Score 0.030 (lower is better), availability 99.93%.
  • p50 / p95 / p99: 17 ms / 29 ms / 863 ms.
  • p95 by probe region: Germany 19 ms, US 46 ms, Japan 21 ms.
Chainstack Compare for Hyperliquid, last 7 days: Chainstack ranks first with a score of 0.030
Chainstack Compare, Hyperliquid, last 7 days, captured Nov 18, 2026.

The next provider is at 0.050. The weak spot is the tail: p99 is 863 ms against 87 to 278 ms for the other three, and one provider shows 100.00% availability against 99.93% here. The live view is Hyperliquid on Compare. For a fixed window (Nov 5 to Nov 12, 2026, score 0.028), see the Hyperliquid RPC provider benchmark: latency and uptime (November 2026).

How to read these numbers (and what they don’t prove)

  • One run, 16 cities. Every row is a single measurement from Oct 29, 2026. With 16 cities the median is steady, but single rows such as Dubai can be noise.
  • TTFB, not total call time. The clock stops at the first byte, so it leaves out the download of large responses (a wide eth_getLogs range, for example) and the time the node spends computing them.
  • One request type. The A/B timed one RPC request per probe, so it does not show how Hyperliquid-specific calls such as clearinghouseState behave.
  • Chainstack against Chainstack. The A/B compares two Chainstack routes. For other providers, see Compare and the Chainstack vs Alchemy RPC benchmark, where Chainstack won 52.4% of HyperEVM JSON-RPC regional p95 comparisons and Alchemy led Asia (61.8%).

What this means for Hyperliquid builders

Hyperliquid bots and dashboards poll all day: a bot reading market state before it acts, a portfolio tool refreshing positions, a wallet loading balances. From far regions the saving is hundreds of milliseconds per call (New Delhi 563 ms, San José 451 ms), and it repeats on every loop iteration.

In short: GEN 2.0 is a major update, as significant for Hyperliquid RPC users as a protocol upgrade is for the network. Same endpoint, same API, and a median first byte of 81 ms instead of 175 ms.

To try Hyperliquid on GEN 2.0, deploy a Global Node on the free Developer plan in a few seconds. More about Hyperliquid on Chainstack.

FAQ

Is my Hyperliquid endpoint URL the same?

Yes, nothing to reconfigure. The hostname and the API are unchanged, and GEN 2.0 applies to Hyperliquid mainnet.

How much faster is Hyperliquid on GEN 2.0?

On Hyperliquid mainnet the median time to first byte fell from 175 ms to 81 ms, about 2.2x, in a same-minute test from 16 cities on Oct 29, 2026. The gain ranged from 1.9x to 48.0x in the 15 cities that improved.

Did every city get faster?

No. 15 of 16 did. Dubai went from 199 ms to 265 ms, and the other 15 gained between 1.9x and 48.0x.

Is Chainstack the fastest Hyperliquid provider?

On Compare, Chainstack ranks #1 on score for the last 7 days (0.030 as of Nov 18, 2026), with the lowest p95 in the US and Japan and a tie in Germany. The tail is the weak spot: p99 is 863 ms, higher than the other providers, and availability is 99.93%.

Which methods does the Hyperliquid Compare ranking use?

Seven: eth_call, eth_getBalance, eth_getLogs, eth_getTransactionReceipt, eth_blockNumber and the Hyperliquid-specific clearinghouseState and openOrders, measured from Germany, Japan and the US. The score combines p95 latency per method with the success rate, and lower is better.

Is the 2.2x figure a guarantee?

No. It is the median of one A/B test in 16 cities on Oct 29, 2026, and your result depends on where your servers and users are.

SHARE THIS ARTICLE
Best Avalanche 530x281 logo

Best Avalanche RPC providers in 2026

Compare the best Avalanche RPC providers in 2026. See performance, uptime, pricing, and enterprise-ready RPC options for production workloads.

T9c0d9l8p U0a2lha30nl 07cf70c046c6 512 150x150 logo
Alex Usachev
Jan 22
Customer Stories

Brave Wallet

Brave Wallet optimizes cross-chain operations with reliable Chainstack RPC infrastructure, enhancing user experience and security.

BonusTrade.AI

BonusTrade.AI unlocks real-time crypto market insights with low latency and high-performance Chainstack infrastructure.

tendex

Multi-contract stress-testing to ensure smooth trading infrastructure mainnet operations.