Broker server location finder

Four of the guides say each figure was “read inside MT4 and MT5 against a live account, taken as the median of a week” and “not an ICMP ping”; the IC Markets guide says only “read inside the terminal against a live account”, and the Exness guide adds that the figures are re-taken monthly. The city is the FXSVPS location with the lowest round trip, which is not the same as the broker's address: Exness-Real23's row reads “Central Europe”. FXSVPS rents the VPS in those cities, and ProEA is an FXSVPS affiliate (see the note under the finder). Sources: Exness, IC Markets, XM, HFM and FBS.

The group number carries no geography: FXSVPS measured MT5Real34 from Amsterdam, MT5Real35 from Frankfurt and MT5Real36 from London. MT5Real19, 20 and 21 answered from Singapore and MT5Real25 from Beauharnois, in Canada. The trial groups don't follow the live ones: Exness-Trial10 answered from New York, and Exness-MT5Trial9 from London. Your group is in MT5's login window and next to the account in the Exness area; type it into the finder above.

“The IC Markets MetaTrader 4 and 5 servers are currently located in the NY4 data centre in New York”; its cTrader servers, the page says, are in the LD5 data centre in London. (IC Markets, Trading Servers). FXSVPS measured every live group on its guide fastest from New York, at 1.63 to 3.08 ms, and adds a rule for the labels beside a server: DC_NY is New York, DC_LD London, DC_Syd Sydney (where it has “not seen a live group”), DC_FRANK Frankfurt (mostly demo), DC_Vir Virginia (“Ashburn or New York”). Groups named Access or Demo are shared entry points that move. An Australian broker with its MetaTrader servers in New York is why a Sydney VPS is the wrong guess for most IC Markets accounts.

XM: XMGlobal-Real 39 answered from London and XMGlobal-Real 33 from Singapore; XMGlobal-MT5 13 from Beauharnois. HFM: the prefix matters more than the number, with HFMarketsSA-Live2 from London and the HFMarketsGlobal groups from Mumbai, New York and Frankfurt. FBS: FBS-Real-5 and FBS-Real from London, FBS-Real-10 from New York.

FXSVPS's own warning sits above its table: a broker runs many servers, and “they decide which one your account sits on — and it may not be the one anybody measured.” The table's date reads “Measured DATE NEEDED”, its header counts 103 brokers while 71 rows are listed, and it doesn't say which server of each broker it measured. Use it to pick a city to test, not to predict a number (FXSVPS, Latency Table).

The first two are FXSVPS's published steps (How To Find Forex Broker Server Location, 31 May 2026), the third its latency table's (Latency Table); we haven't run them against every broker. Many brokers block ping, so Resource Monitor's Network tab, which lists terminal64.exe's open connections with their Remote Address, is the reliable way to the IP. An IP lookup gives an approximate city and the data centre's network; FXSVPS names Equinix LD4 (London), NY4 and NY5 (New York) and TY3 (Tokyo) as where many brokers sit. If the terminal can't connect at all, read the Journal first: MT5 “No connection” decodes its messages.

FXSVPS writes that scalping and news trading feel milliseconds and a swing strategy doesn't, and that paying for high-frequency hardware to run one “is money that buys nothing”. What matters to every EA is that the terminal stays on and connected. On MetaQuotes' own hosting, “the system will automatically select the server that is closest to your broker” ( MetaQuotes, Register a Server), one account per rented terminal; the MT5 VPS size calculator says whether it takes your setup, and MT5 VPS walks renting it.