FXPro-Live3 has no reachable access point
2 address(es) filed and none of them has answered. A server with no route is a server no account can log in to, whatever else is configured on it. Nothing is on it yet, which is the good time to find this out.
104.238.188.22:443 on ICMarketsSC-MT4-12 is not answering
It is a failover address, and 1 of 2 access points on that server still answer, so nothing is down right now. It matters when the primary goes: a rotation list with one working entry is not a rotation list.
Brokers47 servers between them
MT5 / MT45 / 2separate estates, separate symbol maps
Access points151 not answering
Servers with no route1nothing can log in
How a broker is filed
Four levels, and none of them collapses
1 · Broker
The company. Carries the contact address you chase when a server goes and nobody told us.
2 · Platform
MT4 and MT5 are separate estates. Different servers, different addresses, and different symbol names for the same instrument.
3 · Server
The string MetaTrader shows in its dropdown, exactly. The symbol profile is keyed on this — not on the broker.
4 · Access points
IP and port, several per server. MetaTrader rotates through them; a node holding one address loses the account when that address does.
Servers
One row per server, not per broker. Two rows for one broker running both platforms is correct — they are separate estates with separate symbol maps.
| Server | Platform | Kind | Primary address | Best latency | Symbols | Accounts | State | |
|---|---|---|---|---|---|---|---|---|
Exness-Real12 Exness | MT5 | Live | 78.140.180.22:443 3 filed · 3 answering | 31 ms | 7 / 8 1 unmapped | 7 | Active | |
Exness-MT4Real8 Exness | MT4 | Live | 78.140.179.14:443 2 filed · 2 answering | 36 ms | 6 / 7 1 unmapped | 1 | Active | |
ICMarketsSC-Live08 IC Markets | MT5 | Live | 104.238.190.4:443 3 filed · 3 answering | 58 ms | 8 / 8 1 not carried | 3 | Active | |
ICMarketsSC-MT4-12 IC Markets | MT4 | Live | 104.238.188.21:443 2 filed · 1 answering | 57 ms | 8 / 8 1 not carried | 1 | Active | |
Pepperstone-Live04 Pepperstone | MT5 | Live | 45.76.108.30:443 2 filed · 2 answering | 44 ms | 8 / 9 1 unmapped | 4 | Active | |
Pepperstone-Demo01 Pepperstone | MT5 | Demo | 45.76.108.90:443 1 filed · 1 answering | 45 ms | 2 / 9 7 unmapped | 0 | Active | |
FXPro-Live3 FXPro | MT5 | Live | 185.66.40.12:443 2 filed · 0 answering | no reply | 0 / 9 9 unmapped | 0 | Draft |
Brokers
The company level. Everything else hangs off one of these.
| Broker | Country | Platforms | Servers | Access points | Accounts | |
|---|---|---|---|---|---|---|
Exness EXN | Cyprus | MT5 MT4 | 2 | 5 | 8 | |
IC Markets ICM | Australia | MT5 MT4 | 2 | 5 | 4 | |
Pepperstone PEP | Australia | MT5 | 2 | 3 | 4 | |
FXPro FXP | UK | MT5 | 1 | 2 | 0 |
Five rules for filing one
Each one is a way this has gone wrong
- Never file MT4 and MT5 as one server. They are separate estates with separate addresses and separate symbol names — IC Markets quotes gold as XAUUSD.a on MT5 and XAUUSD on MT4. One shared map would be wrong for half that broker’s accounts, and wrong silently.
- The server name has to match MetaTrader exactly. It is the key the symbol profile and the account login are both stored against, so a transcription error means no account on it resolves anything and no terminal on it logs in.
- File every access point the broker publishes, not just one. MetaTrader rotates through them and so does the node. A single address is a single point of failure that looks like a broker outage when it is one unreachable IP.
- Latency is per host, not per address. It is measured from the machine the account runs on, so the same endpoint is fast from one region and slow from another. The figure here is the best reply from anywhere.
- A server with no reachable address takes no accounts. It stays in Draft and is not offered when creating one, because placing an account on a server nothing can reach produces a login failure nobody can explain.
Access points
Every address a terminal might dial. Latency is measured from the host the account runs on, so the same address can be fast in Frankfurt and slow in Mumbai.
| Address | Server | Platform | Role | Latency | Health | |
|---|---|---|---|---|---|---|
| 78.140.180.22:443 | Exness-Real12 Exness | MT5 | Primary | 31 ms | Reachable | |
| 78.140.180.23:443 | Exness-Real12 Exness | MT5 | Failover | 34 ms | Reachable | |
| 78.140.181.9:443 | Exness-Real12 Exness | MT5 | Failover | 240 ms | Slow | |
| 78.140.179.14:443 | Exness-MT4Real8 Exness | MT4 | Primary | 36 ms | Reachable | |
| 78.140.179.15:443 | Exness-MT4Real8 Exness | MT4 | Failover | 39 ms | Reachable | |
| 104.238.190.4:443 | ICMarketsSC-Live08 IC Markets | MT5 | Primary | 58 ms | Reachable | |
| 104.238.190.5:443 | ICMarketsSC-Live08 IC Markets | MT5 | Failover | 61 ms | Reachable | |
| 104.238.191.8:1950 | ICMarketsSC-Live08 IC Markets | MT5 | Failover | 64 ms | Reachable | |
| 104.238.188.21:443 | ICMarketsSC-MT4-12 IC Markets | MT4 | Primary | 57 ms | Reachable | |
| 104.238.188.22:443 | ICMarketsSC-MT4-12 IC Markets | MT4 | Failover | — | Unreachable | |
| 45.76.108.30:443 | Pepperstone-Live04 Pepperstone | MT5 | Primary | 44 ms | Reachable | |
| 45.76.108.31:443 | Pepperstone-Live04 Pepperstone | MT5 | Failover | 47 ms | Reachable | |
| 45.76.108.90:443 | Pepperstone-Demo01 Pepperstone | MT5 | Primary | 45 ms | Reachable | |
| 185.66.40.12:443 | FXPro-Live3 FXPro | MT5 | Primary | — | Not checked | |
| 185.66.40.13:443 | FXPro-Live3 FXPro | MT5 | Failover | — | Not checked |