Trading MyForexFunds with a clean network
MFF's IP consistency requirements at payout follow the same pattern as most London-based prop firms — and the shared-IP risk applies here too.
MFF's broker infrastructure is in London (Equinix LD4 region). Their IP policy typically involves payout-stage compliance checks for IP collision and geographic consistency. TradersProxy uses a shared exit IP — better routing to London, but not payout-safe without a dedicated IP. A VPS in London with a dedicated IP is the clean answer. Dedicated IPs from TradersProxy are on the roadmap.
Where MFF's MT server actually lives
MyForexFunds operates through broker partners whose infrastructure sits in London. The Equinix LD4/LD5 campus in Slough is the standard co-location hub for this category of prop firm. Your MT4 or MT5 orders go to London, not Singapore or New York.
Verify this yourself: open the MT5 platform provided by MFF, check the server hostname in the login window, and run a 60-second ping. From the US East Coast, expect 80–120 ms. From Southeast Asia, 180–250 ms. From Western Europe, 5–30 ms.
- Primary co-location: London, Equinix LD4 region (Slough, Berkshire)
- Latency from US East Coast: 80–120 ms via most ISPs
- Latency from Southeast Asia: 180–250 ms via most ISPs
- Latency from UK/Europe: 5–30 ms — effectively local
MFF's IP policy and what it means for you
MyForexFunds's publicly available terms flag accounts showing signs of IP sharing, location inconsistency, or VPN usage. The pattern is consistent with other prop firms in this tier: no login-time block in most cases, but a compliance review at the payout stage that looks for collision patterns and geographic jumps.
A shared proxy exit IP introduces collision risk — if another MFF account is on the same shared node as yours, both IP histories match at review. That match looks like account sharing. Both accounts can be held pending investigation.
TradersProxy uses a shared exit IP. This is the honest constraint: it improves your route to London, but it cannot eliminate IP-collision risk without a dedicated address per user. That tier is on the roadmap.
What to check before using any proxy or VPS with MFF
- Is the IP shared with other traders? Ask the provider directly. Shared pools carry collision risk by definition.
- Is the same IP used for both dashboard and MT logins? MFF logs both. Inconsistency between them creates a flag.
- Is the IP static for the full challenge duration? Verify it does not rotate between sessions before day one.
- Does a cleared-cache browser confirm the correct exit IP? Check in incognito before every session.
- Have you read MFF's current terms? Policy details change. Base your decision on the current published version.
What actually helps for MFF traders — in honest order
1. VPS in London (best for IP uniqueness)
A VPS near Equinix LD4 gives you a dedicated, static IP and under 10 ms to MFF's London broker environment. No collision risk. Trade-off: RDP friction and cost. Best for EA-based strategies and traders who need the cleanest IP record.
2. TradersProxy (better routing, shared IP — pair with VPS for payout safety)
TradersProxy improves the route from your location to London. Jitter absorption reduces fill anomalies. The shared exit IP creates payout-stage risk on its own. Pair with a VPS: the VPS provides the dedicated IP, TradersProxy provides the routing quality via SOCKS5.
3. Direct ISP connection (fine for European traders)
If your ISP routes cleanly to London with under 30 ms and stable jitter, doing nothing is valid. Measure before deciding.
4. Dedicated-IP tier from TradersProxy (coming)
The complete single-product answer when it ships. Read about dedicated IPs →
A dedicated IP is required for MFF payout safety. TradersProxy provides the routing; pair with a VPS for the IP layer.
MFF network FAQ
MFF's broker infrastructure is in London, at the Equinix LD4 region in Slough. Traders outside Europe see 80–250 ms depending on ISP routing to London.
MFF's terms flag IP sharing and VPN usage. There is typically no login-time block, but a payout-stage compliance review checks for collision patterns. A VPS with a dedicated IP satisfies the consistency requirement.
It can. If another MFF account is on the same shared proxy node, both histories match at review. That pattern looks like account sharing to the compliance system.
Yes, MyForexFunds continues to operate as of the date of this guide. Always verify current account availability and program status directly with MFF.
TradersProxy improves routing quality to London. The shared exit IP carries payout-stage IP-collision risk. Pair with a VPS for the dedicated IP layer. A dedicated-IP tier from TradersProxy is on the roadmap.
A VPS near Equinix LD4 in London, used consistently from day one. The VPS provides a dedicated IP and low latency. Add TradersProxy via SOCKS5 for routing quality on top of the fixed IP if needed.
No. Switching mid-challenge creates geographic inconsistency in your IP log — one of the primary compliance flags. Set up your connection before day one and leave it unchanged.