Order-to-Fill Latency
How long does it take to place an order on Hyperliquid and get a fill response?
What We Measured
We placed real market orders from AWS Tokyo and measured the round-trip time of the POST /exchange API call. This is the time from sending the order to receiving the fill confirmation back. Results are based on multiple test sessions and will be updated over time.
Of the 884ms median, we estimate ~5ms is network transit within Tokyo. The remaining ~879ms is approximately server-side processing. From other locations, you add your network round-trip on top of that.
Estimated Latency From Our Probes
Using our live API latency data as the network component, plus the measured ~879ms processing time.
Context
Hyperliquid's official documentation states a median end-to-end latency of 0.2 seconds from a geographically co-located client. Our measurements from AWS Tokyo in March 2026 show a median of 884ms across 120 samples. Hyperliquid has grown significantly since those docs were written — the network now has 24 active validators (determined by top stake) processing 200,000+ orders per second, which likely contributes to higher response times than the original benchmarks.
All orders on Hyperliquid are submitted through the public API at api.hyperliquid.xyz. Running a dedicated non-validator node can give you faster market data reads, but order submission still goes through the same API endpoint.