Where are Hyperliquid's servers? Tokyo, for the lowest latency
Hyperliquid does not publish where its servers are, but its node instructions say: for lowest latency, run in Tokyo, Japan. From a server in Tokyo an order reaches Hyperliquid's API in about 4.5 ms in our measurements. From other continents it takes several hundred milliseconds.
Free key14 days of history at 60 requests a minute. Without a key, the API reaches 24 hours back.
By requesting a key you agree to the Terms and API terms; see the Privacy Policy. We may email you when your key keeps hitting its limits; you can opt out at any time.
The answer#
- Region: Tokyo, as Hyperliquid's own node README recommends.
- From Tokyo: about 4.5 ms to the order API, about 2 ms to the nearest gossip peer.
- A ping lies:
api.hyperliquid.xyzsits behind CloudFront, so the first hop is a nearby edge.
Measure it yourself#
Time a full read, not a ping. Run it a few times and take the lowest:
curl -s -o /dev/null \
-w 'connect %{time_connect}s total %{time_total}s\n' \
-X POST https://api.hyperliquid.xyz/info \
-H 'Content-Type: application/json' -d '{"type":"meta"}'connect is the trip to the CloudFront edge. total includes the request going on to Hyperliquid and back, which is what an order pays too.
When location matters#
- It matters for quoting, for trading liquidations as they print, and for a node that must keep up with its peers.
- It does not for bots that act on hourly candles, funding or open interest: a few hundred milliseconds is nothing next to an hour.
Running a node away from Tokyo works, it just falls behind more often: Hyperliquid node falling behind.
Run from Tokyo without a server#
Ironflow's sandboxes run in Tokyo. Type a trading idea or boot an empty sandbox and run the timing above from its shell. An agent can make a paper account in one call, no key needed:
curl -X POST https://api.ironflow.sh/v1/ironboxFor your own machine there, we run dedicated nodes in Tokyo.
Questions#
Where are Hyperliquid's servers located?#
Hyperliquid does not publish a server list. Its node instructions say to run in Tokyo, Japan for the lowest latency, and from a Tokyo server an order reaches its API in about 4.5 ms in our measurements.
Why does api.hyperliquid.xyz answer fast from everywhere?#
It is served through Amazon CloudFront, so the connection ends at the nearest edge. Time a full POST /info request instead of a ping or the TLS handshake.
Does my trading bot need to run in Tokyo?#
Only if it reacts within seconds, such as market making or trading liquidations as they happen. A bot that acts on hourly candles or funding works from anywhere.
Does a Hyperliquid node have to be in Tokyo?#
No, but it falls behind more often elsewhere. Hyperliquid asks for 200 ms two-way latency to at least a third of validators by stake, and recommends Tokyo for the lowest latency.
Related guides#
- How to run a Hyperliquid non-validator node
- Hyperliquid node falling behind: fix a slow or far gossip peer
- Hyperliquid API endpoints: which one to use
- A sandbox for Hyperliquid trading agents
References#
- Hyperliquid node repository. "For lowest latency, run the node in Tokyo, Japan." and the 200 ms validator target.
Free key14 days of history at 60 requests a minute. Without a key, the API reaches 24 hours back.
By requesting a key you agree to the Terms and API terms; see the Privacy Policy. We may email you when your key keeps hitting its limits; you can opt out at any time.