Latency Route Map

Latency Route Map

Where CoinAPI sits relative to exchange matching engines, and how fast your data can get there.

Market data latency is mostly geography. CoinAPI runs points of presence next to the cloud regions and colocation campuses where exchanges host their matching engines, so the fastest path is usually a short one.

The map shows the network round-trip time from every CoinAPI point of presence to every exchange hosting location over standard IP transit, and the Enterprise private route where CoinAPI can provision a dedicated low-latency path.

Transport-layer round-trip times, last reviewed 2026-10-20. Exchange processing and application time are not included.

Talk to EnterpriseLatency Optimization
5Regional points of presence
8Enterprise PoPs deployed on request
8Exchange hosting locations
21Exchanges mapped
12Enterprise private route corridors
−131.1 msLargest round-trip saving
Interactive map

Standard routes and Enterprise private routes, side by side

Pick a CoinAPI point of presence to see the round-trip time to every exchange hosting location, or pick an exchange location to find the closest point of presence. Switch the overlay off to see standard routes alone.

Europe
Americas
Asia-Pacific
London12 ms1 ms90 ms67.4 ms160 ms137.7 ms200 ms175 ms
  • CoinAPI point of presence
  • Exchange hosting location
  • Standard route
  • Enterprise private route
Round-trip latency from the London point of presence · 3 of 8 routes have an Enterprise private route
Exchange location0 msRound-trip time250 msStandardEnterpriseSaving
1 mson request—
12 mson request—
77.4 ms67.4 ms−10 ms (13%)
90 mson request—
215 ms137.7 ms−77.3 ms (36%)
246.6 ms160 ms−86.6 ms (35%)
175 mson request—
200 mson request—

Round-trip time between the CoinAPI point of presence and the exchange hosting location at the transport layer. Standard-route figures are indicative public-internet and cloud-backbone measurements; Enterprise private routes are measured equipment to equipment and provisioned per customer.

Enterprise private routes

Dedicated low-latency corridors available to Enterprise customers

On these corridors CoinAPI can deliver market data over a private, SLA-backed path instead of public transit. Each route is provisioned for a single customer, with cloud on-ramps at both ends where the exchange and the customer run in public cloud.

From CoinAPI PoPTo exchange locationExchangesStandard routeEnterprise private routeSaving
Stockholm (AWS eu-north-1)Tokyo (AWS ap-northeast-1)Binance, Bitget, Gate.io, HTX and 6 more250 ms118.9 ms−131.1 ms (52%)
Frankfurt (AWS eu-central-1 · Equinix FR5)Tokyo (AWS ap-northeast-1)Binance, Bitget, Gate.io, HTX and 6 more228 ms133.9 ms−94.1 ms (41%)
Amsterdam (Azure West Europe · Equinix AM)Tokyo (AWS ap-northeast-1)Binance, Bitget, Gate.io, HTX and 6 more220 ms133.2 ms−86.8 ms (39%)
London (Equinix LD4)Seoul (Seoul data centers)Upbit, Bithumb246.6 ms160 ms−86.6 ms (35%)
Tokyo (Equinix TY8 · AWS ap-northeast-1)London (Equinix LD4)Deribit, LMAX Digital215 ms137.7 ms−77.3 ms (36%)
Tokyo (Equinix TY8 · AWS ap-northeast-1)Dublin (AWS eu-west-1)BitMEX212 ms145 ms−67 ms (32%)
New York (Equinix NY4)Tokyo (AWS ap-northeast-1)Binance, Bitget, Gate.io, HTX and 6 more165 ms135.2 ms−29.8 ms (18%)
Ohio (AWS us-east-2)Tokyo (AWS ap-northeast-1)Binance, Bitget, Gate.io, HTX and 6 more145 ms129 ms−16 ms (11%)
Tokyo (Equinix TY8 · AWS ap-northeast-1)N. Virginia (AWS us-east-1)Coinbase, Gemini150.2 ms135.4 ms−14.8 ms (10%)
Tokyo (Equinix TY8 · AWS ap-northeast-1)Hong Kong (Hong Kong cloud regions)OKX, HashKey54.5 ms40.7 ms−13.8 ms (25%)
Tokyo (Equinix TY8 · AWS ap-northeast-1)Chicago (CME Globex, Aurora)CME Group132 ms119.6 ms−12.4 ms (9%)
London (Equinix LD4)N. Virginia (AWS us-east-1)Coinbase, Gemini77.4 ms67.4 ms−10 ms (13%)
Selected corridors also have an ultra-low-latency hybrid fiber and microwave option on request. Additional corridors, including Seoul and Singapore, are quoted individually.

What the figures mean

Every figure is a network round-trip time (RTT) in milliseconds between a CoinAPI point of presence and the data center where an exchange hosts its matching engine. One-way latency is roughly half.

  • Standard route: the path your traffic takes today over public IP transit and cloud backbones, as served by the regional and GeoDNS endpoints.
  • Enterprise private route: a dedicated fiber path CoinAPI provisions for an Enterprise customer, measured equipment to equipment.
  • Points of presence marked as deployed on request are stood up together with the private route for Enterprise deployments.
Exchange matching time, API processing and your application are on top of these figures. The map tells you how much of your latency budget physics takes.

What is not in the map

The map is deliberately conservative. It shows transport-layer numbers CoinAPI can stand behind, not best-case marketing figures.

  • Exchange-event to client-receive latency, which depends on the exchange feed and your consumption pattern.
  • Jitter and loss, which are covered by the service-level terms of an Enterprise agreement.
  • Customer-side cloud hops. Direct Connect and VPC peering add roughly one to two milliseconds at each end.

Standard-route figures are reviewed periodically and updated as CoinAPI collects new measurements. Enterprise figures come from route-specific benchmarks.

Open data

The same data, as JSON

The map is rendered from a public JSON document, so you can pull the figures into your own tooling, compare regions programmatically, or track changes over time.

Each route lists the standard round-trip time and, when a corridor has one, the Enterprise private route. Identifiers are stable.

GET/api/latency-route-map
latency-route-map.sh
curl https://www.coinapi.io/api/latency-route-map

{
  "asOf": "2026-10-20",
  "metric": "rtt",
  "unit": "ms",
  "pops": [{ "id": "london", "name": "London", "facility": "Equinix LD4", "region": "EMEA", ... }],
  "locations": [{ "id": "tokyo-aws", "name": "Tokyo", "hosting": "AWS ap-northeast-1", "exchanges": ["Binance", ...] }],
  "routes": [
    { "from": "london", "to": "tokyo-aws", "standardRttMs": 215, "enterpriseRttMs": 137.7 },
    ...
  ]
}

Need a route that is not on the map?

Enterprise plans include latency consulting, dedicated connectivity and private routes provisioned for your trading or analytics infrastructure. Tell us which exchanges and regions matter and we will benchmark the path.

Private routes, dedicated points of presence and ultra-low-latency options are available exclusively on CoinAPI Enterprise plans.
Talk to EnterpriseCheck Enterprise