What Is Terminal Ping? Latency to Your Trade Server

Terminal ping is the round-trip time between a MetaTrader terminal and the broker's trade server: how long a packet takes to travel out and come back, measured in milliseconds. It is a property of the network path, not of the strategy running on top of it: the dead time inside which a requested price is only a hope. MetaTrader reports it in microseconds; ShowMyTrades converts and displays it as milliseconds to one decimal, so 12,245 µs reads 12.2 ms.

How it works

The terminal records the last known round trip to the trade server. Everything an order does is layered on top of it.

Ping (ms) = last measured round trip terminal ↔ trade server

Order latency ≈ ping/2   (request travelling out)
              + broker matching and validation
              + ping/2   (confirmation travelling back)

Only the middle term belongs to the broker. The first and third are geography and routing, which is why the same broker gives a 3 ms reading to a terminal in the same data centre and 280 ms to a home connection across the world.

Useful bands:

• Under 50 ms — excellent, which is the word the tile's own tooltip uses. Typical of a VPS near the broker's data centre.
• 50 to 150 ms — ordinary for a home or office connection to a regional server.
• Above 200 ms — the tooltip's warning threshold: measurably slower order execution and wider realised slippage.

One distinction decides how much any of this matters. Stop loss and take profit orders live on the trade server, not in the terminal, so they trigger however bad the connection is. Ping delays only what the terminal initiates: entries, manual closes, modifications, and any trailing logic implemented inside an Expert Advisor rather than as a server-side order.

Why it matters

Latency converts directly into cost on market execution, because the fill happens at whatever price exists when the request arrives, not the one that was on screen when it left. A 200 ms round trip is a fifth of a second in which the market is free to move, and it moves furthest precisely when orders matter most.

Whether that fifth of a second is expensive depends entirely on the target. A position held for hours, aiming at a fifty-pip move, absorbs it without noticing. A system targeting three to five pips can lose a meaningful share of its edge in the same interval, on every trade. Backtests are silent on this: they fill at the requested price, instantly, always.

Ping is the first thing to check before blaming a broker. Poor fills with a 300 ms reading is a network problem wearing a broker's name.

What the data shows

The figures below describe accounts published on ShowMyTrades, not traders in general. A terminal reading only exists where there is a terminal, and the overwhelming majority of the 10,000+ connected accounts run MetaTrader. cTrader and TradeLocker accounts connect through broker APIs with no local terminal, so they have no ping to report.

Sensitivity across that population is high. The median autotrading share is 99% and 53.9% of accounts are more than 90% automated, so almost every order is machine-sent, travelling the round trip without a human pausing to check the price. Those accounts reach 703 distinct broker servers, so there is no single latency environment here.

The median trade length is 2.4 hours, which puts the median account outside the range where milliseconds decide anything. The tail that trades in seconds is where this number earns its place on the page.

Where you see it on ShowMyTrades

Ping is the first of six tiles in the Terminal panel, on the owner's own dashboard page for the account. The header reads Terminal & Open Charts on MT5, where the terminal also reports the charts it has open, and plain Terminal on MT4, whose Expert Advisor does not collect that list. The other tiles are Retransmission, Terminal build, Memory, Auto trading and DLL imports.

Beside the header sits a status badge — Connected, No trade server or Offline — and the age of the reading. Freshness overrules the flag: after 11 minutes without an update the account is shown as offline, whatever the terminal last said.

Two limits matter. The panel is owner-only, served by an endpoint that refuses anyone else's account, so terminal readings — including the names of Expert Advisors on open charts — never appear on public pages or in widgets. And it exists only for MetaTrader: cTrader and TradeLocker accounts have no terminal, and the panel does not render at all until one has reported.

Common misunderstandings

• "Low ping means a good broker." It measures the path, not the counterparty. A 2 ms reading to a server with poor fills is a fast route to a bad price.
• "One reading is the truth." It is the last value at the last sync. Stability matters more than the number, which is what retransmission adds.
• "A VPS fixes execution." It fixes the network path. Matching speed, price feed and spread policy stay exactly where they were.

The same round trip described from the network's side, rather than from this tile, is server latency. For a method that separates latency from cost when the same strategy runs at two brokers, see same strategy, different brokers.

Related terms