Skip to main content
A common point of confusion for traders is the difference between the VPS latency displayed in MetaTrader and the order execution time shown in the Journal logs. These are two separate measurements that mean very different things. Order Execution Time vs VPS Latency

​
VPS Latency (Network Ping)

The latency shown in the bottom-right corner of your MetaTrader terminal is your network ping — the round-trip time for data to travel between your VPS and your broker’s trading server. This is the number that NYCServers optimizes by placing your VPS as close to your broker’s server as possible. A low VPS latency (e.g., 1ms) means your orders are reaching the broker almost instantly.

​
Order Execution Time

The time shown in your MetaTrader Journal logs (e.g., “order done in 500ms”) is the total time your broker took to execute your order. This includes:
  • Receiving the order from your VPS
  • Internal broker processing
  • Liquidity checks and price validation
  • Order matching and fill confirmation
  • Sending the confirmation back to your VPS
This is entirely handled by your broker’s infrastructure and is not something NYCServers controls.

​
Example

In this example, the VPS is doing its job — delivering the order to the broker almost instantly. The 500ms execution time is the time the broker spent processing the order on their end.

​
What Should You Do?

VPS Latency Is Low, Execution Is Slow

Your VPS is performing correctly. The delay is on your broker’s side. Contact your broker to inquire about their execution times and whether a different account type or liquidity provider may offer faster fills.

VPS Latency Is High

Your VPS may be located far from your broker’s server. Consider changing your VPS location to one closer to your broker, or contact support for help identifying the best location.

​
Contact Support

If you are unsure whether the issue is related to your VPS or your broker, please contact support and include a screenshot of both your VPS latency and your MetaTrader Journal logs. We’ll help you determine the source of the delay.
Last modified on April 21, 2026