GD Markets Global
Trading Servers

Trading Server

The server is not a background word in the page, but the real path between quotes, routing and order execution. GD connects market liquidity through the New York NY4 and London LD5 infrastructure, with the goal of allowing transaction requests to enter the executable environment as stably and quickly as possible.

Schematic diagram of cross-interconnection of trading servers
Low-latency cross-connection diagram
Infrastructure Brief

The value of low-latency infrastructure lies in reducing the distance between orders and liquidity.

The location, connection method and liquidity aggregation path of the trading server will affect quote refresh, order routing and transaction experience. GD server infrastructure is deployed around data centers commonly used in financial markets, connecting bank and non-bank liquidity sources and reducing reliance on public Internet paths through dedicated interconnection.

35msLow latency execution goal
60+Trading platform ecology
675+Network connection line
NY4 / New York

New York NY4: Execution environment close to quote providers

GD MetaTrader 5 servers are hosted in the NY4 data center in New York. NY4 is one of the financial market interconnection hubs, suitable for trading systems that require fast quotes, deep liquidity and stable connections.

  • Use low-latency connections between servers, aggregation environments, and liquidity sources.
  • Quotes can be aggregated across multiple bank and non-bank liquidity venues.
  • Shorter paths help improve the speed at which orders reach the executable price.
LD5 / London

London LD5: Low-latency node for European connectivity

LD5 is located near the London financial ecosystem and is often used to quickly connect liquidity providers and trading systems. It complements NY4, allowing traders in different regions to obtain more reasonable network paths.

  • Suitable for manual and automated trading workflows in Europe and surrounding regions.
  • Designed for financial connectivity, stability, and low-latency communications.
  • Help the platform maintain more consistent connectivity performance across different market periods.
Execution Route

Path from quote to order execution

  1. Quote inputMultiple liquidity sources provide tradable prices to the aggregation environment.
  2. Server routingTransaction requests enter the execution environment over a low-latency connection.
  3. Order matchingThe system processes orders based on available price, depth, and market conditions.
  4. Result returnedThe transaction, rejection or partial transaction results are returned to the trading platform.
Next Step

Select account, platform and connection method.

If you are focused on automated trading, scalping, or a high-frequency trading environment, server connection quality and platform deployment location should be part of account selection.