How to read this table
RTT = round-trip time, measured in milliseconds. Direct = without a proxy, using your home or VPS connection. Via TradersProxy = using the nearest TP node to the broker's DC. Values are typical ranges; actual numbers vary by ISP, time of day, and routing. These are realistic estimates based on typical international routing patterns and peering agreements between regional carriers and Equinix facilities.
Americas to NY4 (and LD4)
| Country | Direct to NY4 | Via TP NY4 node | Direct to LD4 | Via TP LD4 node |
|---|---|---|---|---|
| United States (East Coast) | 5–15ms | 2–5ms | 80–100ms | 8–15ms |
| United States (West Coast) | 60–90ms | 8–15ms | 150–180ms | 8–15ms |
| Canada (Toronto) | 10–20ms | 3–7ms | 85–110ms | 8–15ms |
| Canada (Vancouver) | 65–90ms | 8–15ms | 160–185ms | 8–15ms |
| Mexico | 35–65ms | 8–15ms | 120–145ms | 8–15ms |
| Brazil | 120–160ms | 15–25ms | 200–240ms | 15–25ms |
| Argentina | 140–180ms | 15–25ms | 220–260ms | 15–25ms |
Europe and Africa to LD4
| Country | Direct to LD4 | Via TP LD4 node |
|---|---|---|
| UK | 5–20ms | 2–5ms |
| Germany | 15–25ms | 3–8ms |
| France | 12–22ms | 3–8ms |
| Netherlands | 8–18ms | 3–8ms |
| Poland | 20–35ms | 5–10ms |
| Czech Republic | 22–38ms | 5–10ms |
| Austria | 22–35ms | 5–10ms |
| Sweden | 25–40ms | 5–12ms |
| Spain | 20–35ms | 5–10ms |
| Italy | 25–40ms | 5–12ms |
| Turkey | 50–80ms | 8–15ms |
| South Africa | 150–200ms | 15–25ms |
| Nigeria | 130–180ms | 15–25ms |
| Morocco | 40–70ms | 8–15ms |
| Egypt | 65–95ms | 10–18ms |
Asia-Pacific to TY3, SY4, and SG1
Note: Asia-Pacific traders should identify which DC their broker uses — TY3 (Tokyo), SY4 (Sydney), or SG1 (Singapore).
| Country | Direct to TY3 | Direct to SY4 | Direct to SG1 | Recommended TP node |
|---|---|---|---|---|
| Japan | 5–15ms | 100–130ms | 70–90ms | TY3 |
| South Korea | 10–25ms | 110–140ms | 70–90ms | TY3 |
| China (coastal) | 20–60ms | 130–160ms | 30–60ms | SG1 or TY3 |
| Hong Kong | 30–50ms | 95–120ms | 20–35ms | SG1 |
| Singapore | 70–90ms | 70–90ms | 5–15ms | SG1 |
| Thailand | 80–110ms | 90–110ms | 20–40ms | SG1 |
| Indonesia | 90–120ms | 75–100ms | 15–35ms | SG1 |
| Vietnam | 80–120ms | 100–130ms | 20–50ms | SG1 |
| India | 100–140ms | 150–190ms | 50–80ms | SG1 |
| Australia | 140–160ms | 5–20ms | 90–110ms | SY4 |
| New Zealand | 165–185ms | 25–45ms | 100–125ms | SY4 |
| UAE | 90–120ms | 120–150ms | 30–50ms | SG1 |
| Saudi Arabia | 100–130ms | 130–165ms | 40–65ms | SG1 |
How a proxy node changes these numbers
TradersProxy nodes placed at the same facilities as broker matching engines (NY4, LD4, TY3, SY4, SG1) reduce the critical last mile to 2–8ms. The benefit is largest for traders who are geographically far from the broker's DC. A trader in Brazil connecting to an NY4 broker sees 120–160ms direct; via a TradersProxy NY4 node, the "broker-side" latency is 2–5ms. This reduction applies regardless of the trader's home location. A trader in Sydney using a TradersProxy SY4 node gets 2–5ms to the broker, whether they are trading from home, a cafe, or a VPS on another continent. See latency by broker for facility assignments.