How to Accurately Determine the Latency to Your Broker (Advanced Users)


  • 4 mins read
  • |
  • Last Updated:

Accurately determining the latency to your broker. (Advanced users)

Latency is the time a data packet takes to travel from your ForexVPS to your broker’s server and back, measured in milliseconds. MetaTrader displays an estimated latency figure, but since it’s a trading platform and not a network measurement tool, that number is only an approximation. This guide uses two tools built into your ForexVPS — TCPView and PsPing — to get an accurate reading.

Before you start: For faster trade execution, lower latency is better. This method requires MetaTrader to already be running and connected to your trading account on your ForexVPS.

What you’ll need

  • An active ForexVPS with Remote Desktop access
  • MetaTrader installed, running, and logged in to your trading account
  • TCPView and PsPing — both pre-installed in C:\Windows\Scripts on ForexVPS instances

Why MetaTrader’s latency reading isn’t accurate

MetaTrader shows a live latency figure while connected, but this is only an estimate — the platform is designed for trading, not network diagnostics. To get a precise millisecond reading of the round-trip time between your ForexVPS and your broker’s server, you need dedicated network tools. ForexVPS instances come with TCPView and PsPing built in for exactly this purpose.

Part 1: Find your broker’s server address

Step 1: Confirm MetaTrader is running and connected

Access your ForexVPS and make sure you have MetaTrader running with your trading account logged in and connected. The latency measurement depends on an active connection to your broker’s server.

VPS desktop with File Explorer icon highlighted

Step 2: Navigate to the Scripts folder

Open File Explorer and navigate to Disk C:\Windows\Scripts. This folder contains the pre-installed network diagnostic tools.

Scripts folder in File Explorer with Tcpview.exe visible

Step 3: Launch TCPView

Double-click Tcpview.exe to launch the application. TCPView shows every active network connection on your ForexVPS in real time.

Scripts folder in File Explorer sorted with Tcpview.exe highlighted

Step 4: Disable address resolution in TCPView

Go to Options and untick Resolve addresses. This displays raw IP addresses instead of resolved hostnames, which you need for the next step.

TCPView Options menu with Resolve Addresses highlighted

Step 5: Note the Remote Address and Port of terminal.exe

Find terminal.exe in the TCPView list — this is your MetaTrader process — and note its Remote Address and Port. In this example, it is 192.149.49.199:443. This is your broker’s server address.

TCPView with terminal64.exe Remote Address and Port highlighted

Part 2: Measure latency with PsPing

Step 6: Open Command Prompt

Click the search menu, type CMD, and click Command Prompt.

Windows search menu with Command Prompt result

Step 7: Navigate to the Scripts folder and run PsPing

Run the following commands in order, pressing Enter after each one:

  1. cd..
  2. cd..
  3. cd Windows
  4. cd Scripts
  5. psping.exe -4 -t REMOTEIP:PORT

Replace REMOTEIP:PORT with the Remote Address and Port you noted from TCPView — for example, 192.149.48.199:443. If a pop-up appears, accept the prompt and continue.

Command Prompt navigated to Windows scripts folder

PsPing continuously pings your broker’s server and returns real round-trip latency in milliseconds — a far more accurate measurement than the estimate shown inside MetaTrader. Let it run for at least 30-60 seconds to get a reliable average.

Troubleshooting latency measurement

If TCPView or PsPing aren’t behaving as expected, check these common fixes.

Problem Likely cause Fix
Can’t find terminal.exe in TCPView MetaTrader not running or not connected Open MetaTrader and confirm it’s logged in and connected to your trading account before checking TCPView.
psping.exe command not recognized Not in the correct Scripts directory Confirm you ran all four cd commands in order before running psping.exe.
PsPing shows very high or inconsistent latency Server location mismatch or network congestion Consider a VPS location closer to your broker’s server — contact ForexVPS support for location options.
Security pop-up blocks psping.exe Windows flags the tool on first run Accept the prompt to allow PsPing to run — it is a legitimate Microsoft Sysinternals tool.

Frequently asked questions about measuring latency to your broker

Still have questions about testing your connection speed to your broker’s server? Find quick answers below.

Why is MetaTrader’s latency reading not accurate?

MetaTrader is a trading platform, not a network diagnostic tool. Its latency display is only an estimate. TCPView and PsPing measure the actual round-trip time to your broker’s server in milliseconds.

What is a good latency value for trading?

Lower is always better for trade execution speed. Values under 5ms are excellent, under 20ms are good for most retail trading, and anything above 50ms may noticeably affect execution on fast-moving markets.

Do I need to install TCPView and PsPing myself?

No. Both tools come pre-installed on ForexVPS instances in C:\Windows\Scripts — no download or setup required.

What does the Remote Address and Port in TCPView represent?

This is the IP address and port of your broker’s trading server that MetaTrader is actively connected to. You use this exact address as the target for the PsPing latency test.

Can I run this latency test while actively trading?

Yes. PsPing runs independently of MetaTrader and does not interrupt your trading activity or open positions.

Related articles

Annoyed by slow trade execution, power cuts and downtime?

Forex VPS Plans starting from $32