Trading from Mexico City
Your broker is in New York, and from Mexico City that's a long path over submarine cables. Here's what real-world latency looks like for Mexican traders, and what actually fixes it.
Mexico City is 3,360 km from New York — 17 ms of light-travel time. On Mexican consumer fibre, real-world RTT typically lands at 55–90 ms, with peak-hour spikes above 140 ms. LatAm connectivity has improved dramatically with cables like MONET and SAC, but the fallback paths are still constrained.
Where your broker actually lives
Retail brokers serving Latin America host their MT4 and MT5 servers in New York — primarily Equinix NY4 in Secaucus, NJ, the same data centre that hosts CME and a significant chunk of the US financial system. IC Markets, Pepperstone, OANDA, Exness (Americas) — all there.
New York (Equinix NY4) is the Americas broker hub. Miami (Equinix MI1) serves as the LatAm gateway for some regional brokers. TradersProxy has nodes in New York and Chicago.
Check the server hostname in your MT login window. A 60-second ping confirms the region.
Why your real latency is worse than physics says
Mexican residential ISPs — Telmex Infinitum, Izzi, Totalplay, Megacable — route international traffic through submarine cables like MAYA-1, AMX-1. Most LatAm-to-US traffic lands in Miami before moving north to NY. That extra hop through Miami costs 15–30 ms on top of the theoretical minimum.
You'll see 55–90 ms typically and up to 140 ms during peak hours or when a cable has an incident. LatAm peak hours tend to coincide with the US market open, which is exactly when you want a clean path.
In trading terms, you feel it as:
- Slippage at US market open and during major news
- Requotes on fast-moving indices and crypto
- Disconnects during NFP or FOMC events
- EA results that vary with time of day
Telmex Infinitum's speed test hits a local server in Mexico. It tells you nothing about your path to NY. Only the RTT to your broker's MT hostname matters.
What actually helps — in honest order
1. VPS in New York (Equinix NY4)
$10–20/month drops latency to sub-5 ms. Best fix for EAs and scalping. The colo is the same building as your broker.
2. TradersProxy
You keep your own machine. Your trading traffic exits through our New York node at Equinix NY4. Session stays open. The path is direct.
3. Change ISPs or upgrade to fibre
Telmex Infinitum and Izzi have different international transit contracts. If you're on copper or wireless, fibre dramatically reduces jitter.
4. Do nothing
If you swing trade, the baseline is fine. Scalpers and news traders suffer most.
For LatAm traders, we're the middle option: cheaper than a VPS, more reliable than residential transit.
Our New York node is at Equinix NY4. See plans.
How to know your connection is the real problem
Before you pay for anything — VPS, proxy, or a new ISP — prove the diagnosis. Three tests, 15 minutes.
Test 1: ping the actual broker server
Don't ping google.com. Don't ping 8.8.8.8. Ping your broker's MT server hostname for 60 seconds. Note the min, average, and max. The spread between min and max matters more than the average — a short average with wide swings is worse for trading than a steady but slightly higher line.
Test 2: traceroute the path
Run tracert your-broker-hostname on Windows or traceroute your-broker-hostname on Mac. You'll see every hop on the path. If you see unexpected detours — traffic going the wrong direction, hops in unrelated countries — that's a routing problem at your ISP.
Test 3: run the tests at three different times
Morning local, during your main trading session, and during the overlap with the US session. If you get three different pictures, your path is variable — that's your ISP choosing different routes based on load.
TradersProxy uses a shared exit IP. That's fine for retail brokers. It's not always the right fit for prop firms. If you trade FTMO or The Funded Trader from Mexico City, check their policy first.
Mexico City-specific FAQ
If you trade MT4, MT5, or cTrader with a retail broker, your server almost certainly lives in New York. Major brokers serving Mexican traders run their infrastructure at Equinix NY4 (Secaucus, NJ) or similar Tier 1 facilities. The exceptions are prop firms like FTMO and The Funded Trader (usually London-based MT servers) and a handful of regional specialists. Open your MT platform and check the server hostname in the login window to confirm.
There is no permanent answer. Telmex Infinitum, Izzi, Totalplay, and Megacable use different international transit providers, and those arrangements change every six to twelve months. Ping your broker's actual MT server hostname for 60 seconds on each ISP you're considering, and compare the min-max spread rather than the average. Jitter is what hurts your fills, not raw latency.
The 3,360 km distance from Mexico City to New York is about 17 ms of light-travel time, but residential ISPs rarely take the most direct path. Your packets often detour through regional transit points, which adds queueing delay and jitter. That's why real-world round-trip time from Mexico City typically lands at 55–90 ms rather than the theoretical minimum.
Technically yes - a VPS inside Equinix NY4 (Secaucus, NJ) drops your latency to sub-5 ms because your terminal sits metres from your broker. But you trade via remote desktop, which adds friction, and you pay $10-20 extra per month. A proxy keeps your own machine and cleans the route, which is enough for most traders who aren't running high-frequency EAs.
5G often tests faster than fibre on speed tests, but speed tests measure throughput to local servers, not routing quality to your broker. Mobile networks also have more jitter than fixed-line connections. For scalping or news trading, stick to fibre. For swing or position trading, 5G is a reasonable backup.
Some prop firms, including parts of FTMO and The Funded Trader, prefer dedicated IPs and may flag shared exit addresses. TradersProxy uses a shared exit IP, which is fine for retail brokers but not always for prop firms. Check your prop firm's terms before you commit to any proxy service.
Open MT4 or MT5 and look at the server name in the login window, for example ICMarketsSC-Live04. Then ping that hostname from a command prompt for 60 seconds. The round-trip time tells you which region you're really hitting. A traceroute shows the exact path your packets take.