Opening checkout

60% off your first month

Ends in

Trading VPS latency by city and venue

Every latency figure we publish, by datacenter and by venue, with what it measures and how to check it from your own VPS.

How we measure
  • 8 datacenters, one table
  • Round trip, explained
  • Test it yourself
Same order. Shorter trip.Replayed 1000× slower: the round trip from QuantVPS Chicago to CME Globex (0.52ms) against typical, illustrative home connections from Atlanta (~18ms), Miami (~32ms), Los Angeles (~45ms), and Paris (~92ms).

What a latency figure measures. And what it leaves out.

Every latency figure on our pages is a network round trip from one of our datacenters to a venue or broker server. It is one leg of an order’s path.

The path of an order

  1. Your device to your VPSNot in the figure

    Remote Desktop over your home internet. It sets how the screen feels. Your orders don’t travel it.

  2. Your platform on the VPSNot in the figure

    Charts, strategies and order entry run here, on your reserved cores.

  3. Your VPS to the venue and backIn the figure

    The network round trip, the one leg a figure measures. From our Chicago datacenter to CME Globex it is as low as 0.52ms.

  4. Your broker and the exchangeNot in the figure

    Risk checks, order routing and the matching engine’s queue.

Every published figure

What
A network round trip: a packet goes out and comes back. About half of it is each way.
From
The QuantVPS datacenter named beside the figure.
To
The venue or broker servers named beside it. Your broker or data feed picks the gateway you connect to, and its route can read higher.
Leaves out
Your home internet, your platform’s processing, broker risk checks, order routing and the exchange’s queue.
Is not
An execution time, a promise of a fill or a live reading of your own server.

Every datacenter’s figures. All 8, as their pages state them.

The figures each city page publishes, in one place. In New York the plan decides the route: Standard VPS plans run at the New York site, Dedicated and Dedicated+ servers on the NY4 campus.
  • Chicago

    CME Futures Trading

    Published latency from Chicago
    ToRound trip
    CME Globex in Aurora0.52ms
    Tradovate0.52ms
    Rithmic and CQG<1ms
  • New York

    Equities, Options, FX & Polymarket US

    Published latency from New York
    ToRound trip
    NYSE and NASDAQ (Standard)0–2ms
    NYSE and NASDAQ (Dedicated)<1ms
    NY4 forex brokers (Standard)0–10ms
    NY4 forex brokers (Dedicated)<1ms
  • London

    FX EA Trading

    Published latency from London
    ToRound trip
    LD4 and LD5 forex broker servers0–10ms
    London Stock Exchange<2ms
    Kraken0–10ms
  • Dublin

    EU Cloud and API Trading

    Published latency from Dublin
    ToRound trip
    Polymarket<1msMeasured 0.7 to 0.9ms (October 2026)
  • Amsterdam

    European FX Trading

    No single published figure: latency depends on your broker's trade server. Measure it from here before you move a live account.

  • Frankfurt

    Central European Trading

    No single published figure: latency depends on your broker's trade server. Measure it from here before you move a live account.

  • Tokyo

    APAC Crypto Trading

    Published latency from Tokyo
    ToRound trip
    Binance and Bybit0–1ms
  • Singapore

    APAC Forex and API Trading

    No single published figure: latency depends on your broker or API endpoint. Compare the same endpoint from Singapore and Tokyo.

By venue and platform. As each platform page shows it.

Find your platform: the venue its orders or data go to, the datacenter its plans start in, and the figure its page publishes from there.
Published latency by venue, with the platform pages that route there
VenueFromRound tripPlatform pages
CME GlobexChicago0.52msNinjaTrader, Quantower, Tradovate, TradingView, Rithmic
+16 moreATAS, TradeStation, MultiCharts, Sierra Chart, AMP Futures, Bookmap, CME Futures, CQG, DeepCharts, Discount Trading, IronBeam, Jigsaw Trading, MotiveWave, Optimus, TickBlaze, Trading Technologies
DatabentoChicago0–5msDataBento
KalshiChicago0–1msKalshi
NY4 forex broker serversNew York0–10ms<1ms on NY4 (Dedicated)Axi (AxiTrader), cTrader, Fusion Markets, IC Markets, OANDA
+1 moreVantage Markets
NYSE and NasdaqNew York0–2ms<1ms on NY4 (Dedicated)Thinkorswim, Polygon.io
AlpacaNew York0–10msAlpaca
CoinbaseNew York0–1msCoinbase
DAS Trader Pro serversNew York0–10ms<1ms on NY4 (Dedicated)DAS Trader Pro
IBKRNew York0–2ms<1ms on NY4 (Dedicated)Interactive Brokers
SolanaNew York0–1msSolana
LD4 forex broker serversLondon0–10msMetaTrader 4/5, Blueberry Markets, Exness, FTMO, FundedNext
+3 moreFunding Pips, Pepperstone, ThinkMarkets
KrakenLondon0–10msKraken
PolymarketDublin<1msPolymarket
BinanceTokyo0–1msBinance
BybitTokyo0–1msBybit

Your home internet, for contrast. Round trips to CME Globex.

From a home PC, every order crosses the distance to the venue. With a VPS, your orders leave from the datacenter, and only your screen crosses that distance.
Round trip to CME Globex: QuantVPS Chicago and typical home internet
FromRound trip
QuantVPS ChicagoOur datacenter, published figure0.52ms
TorontoHome internet, typical~16ms
AtlantaHome internet, typical~18ms
MiamiHome internet, typical~32ms
Los AngelesHome internet, typical~45ms
ParisHome internet, typical~92ms
São PauloHome internet, typical~145ms
DubaiHome internet, typical~180ms
Hong KongHome internet, typical~195ms
SydneyHome internet, typical~220ms

Home figures are typical, illustrative home-internet round trips, not measurements of your connection. Distance adds most of it, then Wi-Fi, your provider’s routing and every network hop.

Where latency comes from

Test it from your own VPS. The same leg our figures measure.

Ping the gateway your account actually uses, from inside the VPS, not from your home PC. Run it before you move a live account.

Three steps

  1. 1

    Open a command line on your VPS.

    On Windows: Start, type cmd, open Command Prompt. On Ubuntu: open a terminal or SSH session.

  2. 2

    Ping the server your platform uses.

    Windows: ping -t live.tradovateapi.com for 10 to 15 seconds. Ubuntu: ping -c 20 live.tradovateapi.com, which stops by itself.

  3. 3

    Read the summary.

    On Windows, press Ctrl+C. Average is your round trip; compare it with the figure for that datacenter above. Packet loss should be 0%.

Step by step in the help center

Hosts to ping

Hosts to ping from your VPS, with the datacenter to test each from
ProviderTest fromHost
TradovateChicagolive.tradovateapi.com
RithmicChicagoping.rithmic.com
IBKRChicagocdc1.ibllc.com
KalshiChicagoapi.elections.kalshi.com
DAS TraderNew Yorkping.dastrader.org
Polymarket (CLOB)Dublinclob.polymarket.com

Trading VPS latency FAQ.

Sound familiar?5 common ones

Ever missed a setup because you were away from your desk?

Market data keeps flowing and your strategies keep running.

If any of these sound familiar, a trading VPS is the fix.

In one datacenter, yes: plans differ in CPU and memory, not in the route. New York is the exception: Dedicated and Dedicated+ servers run on the NY4 campus and reach NYSE, Nasdaq and NY4 forex brokers in under 1ms, while Standard VPS plans at the New York site read 0–2ms to NYSE and Nasdaq and 0–10ms to forex brokers.

Usually it measures something else. Ping from inside the VPS, not from your home PC. Your broker or data feed assigns the server you connect to, and its route can be longer than the published one. Windows rounds to whole milliseconds, so a reply under 1ms reads time<1ms. If the average stays well above the figure for your datacenter, open a support ticket with your results. How to test latency.

They serve brokers whose trade servers sit in many places, so no single figure fits. Amsterdam peers on AMS-IX and Frankfurt on DE-CIX. Measure the route to your own broker from there before you move a live account.

No. A shorter route gets your order to the venue sooner. Your fill still depends on the order type, your place in the queue and how fast the price moves. Latency and order execution.

No. Remote Desktop streams your screen from the VPS to your device over your home internet. Your platform runs on the VPS, so your orders leave from the datacenter. The lag you see does not slow them down.

No. They are the figures we publish for each route, the same ones the city and platform pages show. To watch your own server’s latency, use QuantVPS Detect+ (beta): it pings trading servers from inside your VPS and shows their latency and packet loss. How Detect+ works.