Dead connections clear immediately
If your device drops offline, our server detects the break quickly and frees its slot. Your platform can reconnect immediately instead of hanging on a dead socket.
How it works
What happens to your order when the internet loses a piece of it.
Live trading feeds give you zero buffer. When market volatility drops a packet, your platform freezes while standard internet requests a distant resend. Our Go proxy engine routes traffic over institutional backbone paths and recovers lost packets right inside your broker’s city.
From $9 a month · Stop renewal any time in your dashboard · First payment refunded if your platform can’t connect through us
01 · The problem
Why one lost piece of data can hold up your order.
Every market order travels as discrete data packets across congested public networks you cannot control. Any intermediate router can drop a packet when volume surges. The farther you sit from your broker, the longer your platform hangs waiting on a reply.
That lost packet triggers an automatic timeout. Your platform stops processing fresh ticks until the lost packet retransmits, freezing your screen right as price breaks out.
Source from the internet standard for sending lost data again
- 01
You click Buy
Your platform fires your market order toward your broker as tiny packets of data.
- 02
Public routing drops a packet
Your traffic traverses dozens of public internet hops. A congested node drops a packet.
- 03
Your terminal stalls
Your computer waits for an acknowledgement. When none arrives, it prepares to resend from your desk.
- 04
Retransmission delay doubles
Standard network stacks double the wait interval on subsequent retries. A minor network stall turns into an order freeze.
- 05
Your price queue blocks
Packets must arrive in sequence. New quotes and trade confirmations queue up behind the missing piece.
This sequence follows published internet standards. It happens on every default retail connection.
02 · What we built
Our lean Go proxy engine connects directly to your broker.
Your trading platform connects to our entry server through its built-in proxy field. We pass your traffic across fast institutional backbone links directly to our node in your broker’s financial centre.
Built around the lean WireGuard philosophy, our Go proxy engine strips out bloated proxy overhead. We terminate lost packets locally beside the broker so stale transfers never block live trades.
Step 1 · From your desk
You connect to our nearest entry node
Your platform sends traffic to our regional node. If a packet drops on your home Wi-Fi or mobile link, it is recovered immediately on that short local hop.
Step 2 · Between trading hubs
Orders travel across institutional backbone transit
Our regional servers link directly to broker financial hubs over high-grade backbone circuits. Traffic stays off unpredictable public consumer routing.
Step 3 · Your broker’s financial centre
Our node connects directly to your broker
Our server opens a clean socket to your broker trade gateway. Dropped packets on that broker leg recover locally within that city, while your broker sees our steady shared address.
03 · Why it helps
What our server does for your orders.
A quiet market can turn volatile in a fraction of a second. Standard internet settings hold small packets back to batch them and let bulk downloads crowd out trade orders. Our servers handle live trading connections differently.
- 01
Orders leave straight away without waiting to bundle
Small messages like a market order leave our server the moment they arrive, instead of waiting to be batched with other data.
- 02
Older data never piles up in front of new orders
We keep unsent data from piling up on both server connections, so new quotes and trade executions never wait behind stale data.
- 03
Local loss recovery and no repeat-loss doubling
Data lost between our server and your broker recovers inside that city, not from your computer. On a quiet connection, a repeat loss does not double the wait.
- 04
Parallel broker address checks
When a broker name lists multiple IP addresses, our server dials them in parallel and uses the first that answers.
This covers our servers’ side only. Data lost between you and our server is replaced between those two.
Your computer and your broker keep their own default settings. The repeat-loss protection covers the first few tries on a quiet connection. The initial retry waits as normal.
If our server in your broker’s city cannot be reached, your platform shows an error. Your dashboard then asks before switching cities.
04 · When a connection drops
How our software protects you when connections drop.
Priority return from the same network
When your link drops and returns, your returning device gets a rapid re-entry window from the same network, even during peak server traffic.
Surge protection for high-impact news spikes
When heavy news volatility forces hundreds of terminals to reconnect simultaneously, our server admits the first group straight in and streams the rest smoothly.
Switching from home Wi-Fi to a mobile hotspot uses our reconnect grace window so your old session never blocks your fresh connection.
05 · What stays the same
Only your trading app uses Traders Proxy. Everything else stays as it is.
You enter four values into your platform proxy setting. Only that specific trading terminal routes through Traders Proxy. We never route general web traffic, so your browser, video calls and downloads remain on your standard internet.
Each platform maker determines which internal requests use its proxy setting. If your broker prohibits proxies, do not use one.
Through Traders Proxy
- MetaTrader 4 and MetaTrader 5
- TradingView Desktop
- Optuma, and any trading platform with a proxy setting
Your normal internet
- Your web browser
- Voice and video calls
- Streaming and personal downloads
Stays as it is
- Your local internet connection and Wi-Fi. We cannot fix a poor local signal.
- Physical distance to your broker. Physical distance sets the baseline latency.
- Your platform’s own proxy setting
- Zero software to install
06 · The maths
Why does your broker’s city matter?
Every network wait begins with the round-trip time between your machine and your broker. Greater physical distance means longer delays during retransmissions. Use the interactive calculator below to inspect where latency accumulates.
The maths in briefPhysics, not our measurement
01
Your broker’s distance sets a minimum time for every order
Light in a cable travels about 200 km every millisecond. Your order goes there and back, so every 1,000 km adds at least 10 ms.
What it means for youPhysical distance dictates your latency floor. Fibre travel times remain constant regardless of routing tools.
minimum there and back (ms) = distance (km) ÷ 100
02
One lost piece of data makes everything wait
When a packet drops, your platform pauses while requesting a retransmission across the full distance. Consecutive drops double this waiting penalty. Incoming price ticks stall during the exact seconds volatility peaks.
wait 1× → 2× → 4× → 8×
03
Our server in your broker’s city recovers lost data locally
Our server in your broker’s city opens the final connection to your broker. On a quiet connection, a repeat loss doesn’t double the wait.
What it means for youWhen a piece is lost near your broker, our server recovers lost data inside that city instead of from your computer.
distance set by physics · recovery in your broker’s city is ours
Try your own distance
Singapore to London is about 10,850 km in a straight line, so at least 108 ms there and back. No order can reach your broker and hear back in less. Real routes are longer.
We don’t promise lower ping because distance sets the minimum. Local recovery in your broker’s city covers only the connection between our server and your broker. The repeat-loss fix covers the first few tries on a quiet connection, after the first repeat try.
07 · What we see
We never record or decrypt what you send to your broker.
We never inspect order payloads or decrypt data
Your terminal encryption stays untouched from your desk to your broker. Our proxy engine passes encrypted bytes directly without inspecting order contents or trade requests.
We never store or handle your broker credentials
You authenticate to Traders Proxy using separate credentials generated in your dashboard. You never enter your broker password or private trading keys into our systems.
We never route general web traffic or personal browsing
Only the desktop trading application you configure sends traffic through our proxy. Your web browsing, emails, banking and personal downloads stay on your standard internet.
That covers your trading platform and the one-tap Telegram link. Telegram’s proprietary proxy format operates differently and is documented separately.
08 · What you do
Four values. Then trade as usual.
- 01Select a planSubscribe through Stripe or explore the free Try plan with 250 MB on our New York node.
- 02Copy your four values onceUnder Your values for your platform, copy the server, port, login and password. They are your Traders Proxy credentials. We never ask for your broker login.
- 03Paste them into your platformOpen your platform proxy settings and paste the credentials. Nothing to install. Restart your platform and confirm live price ticks.
- 04Choose your broker’s cityUnder Your broker’s city, select Change your broker’s city, choose your destination, and click Use. Your four values never change. Restart your platform to route through the new hub.
Your dashboard displays connected devices, bandwidth consumption and node status in real time.
The MetaTrader 5 setup guide →Setup guides for every platform →
Server
198.51.100.24
Port
1080
Login
tp-jonathan
Password
••••••••••••
These are your Traders Proxy credentials. We never ask for your broker account login or password.
09 · Verified forum reports
What happens on standard connections, and how our server solves it.
Every quote below links to the forum thread or vendor guide where it appeared. Underneath each quote, see which parts of our system work together on it and where our server stops.
MetaTrader 4 & 5Solves
A firewall, router or ISP drops the platform's broker connection but lets ordinary web traffic through
“The MT5 trading server mt5.metaquotes.net runs on port 1950. We have closed all the "left" ports at our company, including port 1950.”
How our system handles it. Your platform connects to our server through its built-in SOCKS5 or HTTP proxy setting, and our server opens the broker connection from inside the datacenter.
- Built-in
SOCKS5loginPrimary - Own separate connection to your brokerPrimary
- Unanswered broker server gives up fast and reportsSupporting
Where it stops. Works only if your network still lets you reach our server. We cannot repair a faulty home router or an ISP outage.
MetaTrader 4 & 5Solves
Generic or free proxies fail MetaTrader's proxy Test button
“Server — enter here the IP address and port number of the server separated by a colon. To the right of this field, select the type of proxy server: HTTP, SOCKS4 or SOCKS5. In HTTP mode, NTLM authentication is also supported”
How our system handles it. Use SOCKS5 or HTTP, whichever your platform offers. Enter our server, login and password in MetaTrader’s own Proxy window.
- Built-in
SOCKS5loginPrimary - Built-in
HTTPproxy loginSupporting
Where it stops. MetaTrader 4 and MetaTrader 5 support SOCKS5 and HTTP (not SOCKS4). A passing Test confirms the route reaches our server.
MetaTrader 4 & 5Solves
MetaTrader 5 will not use a proxy running on the same computer
“what im talking about is that mt5 cannot connect to proxy servers on the pc , it can only connect to remote proxies but when i want to connect to 127.0.0.1 it cannot connect. for some reason it rejects the loopback address”
How our system handles it. You don't need a tunnel app on your computer. Your platform connects to our server through its own Proxy setting.
- Own separate connection to your brokerPrimary
- Built-in
SOCKS5loginPrimary
Where it stops. Your platform connects through its built-in Proxy window, with no extra app to install. Some MetaTrader 5 builds have separate proxy-window bugs.
MetaTrader 4 & 5Reduces one factor
'Ping failed' and drops with disconnects every few minutes, re-login loops and dropped sessions
“hey guys,..do you have any ideas why my MT4 often disconected in a several minute or sometime ping failed reported on journal tab. By the way my internet connection doesn,t have any problem or it's always connected.”
What our system reduces. If your device drops off, our server notices quickly and frees its place, so your platform can reconnect instead of hanging.
- Dead connections found and freedPrimary
- Straight back in after a dropPrimary
- Reconnect surges admitted in a steady streamSupporting
- Own separate connection to your brokerSupporting
Where it stops. We do not prevent internet drops or fix broker faults. After a disconnect, your platform logs in again, so always use broker-side stop-loss orders.
MetaTrader 4 & 5Solves
A firewall, router or ISP drops the platform's broker connection but lets ordinary web traffic through
“Access to 443 ports is usually available in proxy servers.”
How our system handles it. Your platform connects to our server through its built-in SOCKS5 or HTTP proxy setting, and our server opens the broker connection from inside the datacenter.
- Built-in
SOCKS5loginPrimary - Own separate connection to your brokerPrimary
- Unanswered broker server gives up fast and reportsSupporting
Where it stops. Works only if your network still lets you reach our server. We cannot repair a faulty home router or an ISP outage.
cTraderReduces one factor
When a provider or country blocks the direct route to cTrader
“someone appears to be (AWS? A middle-man routing provider?) blocking, or not allowing, any addresses from the 77.90.x.x network.”
What our system reduces. If your provider blocks the route to your platform's servers, you can send your platform through a Traders Proxy server instead. It works only if your provider lets you reach us.
- Built-in
HTTPproxy loginPrimary
Where it stops. Works only if your network lets you reach our server. cTrader on Windows uses an HTTP proxy setting and does not route the installer through it.
Bring your trading route closer to home.
Get set up in under 5 minutes with four simple values and zero software installation. Time your platform with and without our route on your live charts.
From $9 a month · Stop renewal any time in your dashboard · First payment refunded if your platform can’t connect through us