HTX

Where Are HTX's Servers Located?

HTX responds fastest from the AWS Tokyo region (ap-northeast-1) — about 70 ms round-trip for a REST call, which places its API infrastructure in or near Tokyo. From London, the slowest measured region, the same call takes around 392 ms — 6× slower. Picking the right server location is the single biggest latency win available when trading on HTX.

Measured latency to HTX around the world

REST ticker round-trip from eight AWS regions

London · 392 ms Frankfurt · 376 ms N. Virginia · 283 ms Singapore · 208 ms N. California · 177 ms Hong Kong · 111 ms Seoul · 80 ms Tokyo · 70 ms

HTX latency from eight AWS regions

AWS region Round-trip
Tokyo ap-northeast-1 ~70 ms
Seoul ap-northeast-2 ~80 ms
Hong Kong ap-east-1 ~111 ms
N. California us-west-1 ~177 ms
Singapore ap-southeast-1 ~208 ms
N. Virginia us-east-1 ~283 ms
Frankfurt eu-central-1 ~376 ms
London eu-west-1 ~392 ms

Indicative REST round-trips from our multi-region measurements — for comparing regions, not an SLA. WebSocket feeds are faster in absolute terms, but the regional proportions hold.

Best server location for trading on HTX

Host your trading server or bot in AWS Tokyo (ap-northeast-1): it reaches HTX in about 70 ms, fast enough that order placement and market data stay effectively real-time.

Avoid running latency-sensitive strategies against HTX from London or other distant regions. At ~392 ms (6× the co-located figure) every price you see is stale before you can act on it, and that staleness turns into slippage on every market order.

Trade on HTX with a co-located server

Arbitron runs every account on its own dedicated trading server with its own IP, and you are able to choose the server region — so your orders reach HTX from Tokyo in milliseconds, with no shared infrastructure and no extra hops.

Compare with other exchanges

All exchange server locations and latencies →

Frequently asked questions

Where are HTX's servers located?

HTX responds fastest from AWS Tokyo (ap-northeast-1) — about 70 ms round-trip — which places its API infrastructure in or near Tokyo.

What is the best server location for HTX?

AWS Tokyo (ap-northeast-1). A server there reaches HTX in ~70 ms, versus ~392 ms from London — a 6× difference on every API call.

How much does server location change latency to HTX?

In our measurements: ~70 ms from Tokyo versus ~392 ms from London — a 6× spread. Every order and every orderbook update pays this tax in both directions.

Can I trade on HTX with a co-located server?

Yes. HTX is supported by Arbitron: each account gets a dedicated trading server with a selectable region, placed next to the exchanges you trade.

An unhandled error has occurred. Reload X

Reconnecting…

Retrying in s…

Reconnecting…

Session paused

Reloading…