Who runs Traders Proxy and how missed trades built it
The short answer
Jonathan is the trader who runs Traders Proxy from Brisbane, Australia. He built it after dropped mobile connections across Asia caused missed trades during major news releases. After 12 months of Linux and Go engineering, he created our proxy software for clean broker routing.
The mobile app switching trap across Asia.
Traders Proxy began on patchy hotel Wi-Fi and congested mobile data networks across Asia. Jonathan was travelling abroad and managing live manual trades from his Android phone. He traded by hand on MetaTrader 4 and MetaTrader 5 while running his trading community on Telegram.
Switching between Telegram alerts and the trading terminal should take a second. On unstable overseas internet, each switch forced the mobile terminal to drop its socket and reconnect. Waiting for the terminal to authenticate and fetch missing chart bars felt like an eternity.
During high-impact economic news releases, erratic route delays made tick data stall on stale prices. Candles jumped ahead while the phone struggled to restore its broker connection. Jumping back and forth between chat discussions and order tickets caused critical entries to be missed entirely.
Why commercial VPNs and remote desktops fell short.
Testing standard commercial VPNs and off-the-shelf proxies proved that intermediate routing could help. Routing packets through a stable data centre cleaned up messy local ISP hops. Local dead ends and connection drops dropped away immediately.
Consumer VPN services introduced a different obstacle for active trading. A commercial VPN wraps every app on the device and shares bandwidth across hundreds of generic web users. Those shared servers are configured for bulk file downloads rather than timing-sensitive market quotes and order packets.
A remote desktop VPS was not an acceptable answer. Trading inside a remote desktop window introduces interface lag and clumsy mobile touch controls. Jonathan wanted to execute orders on his own native apps with clean routing to the broker.
12 months of Linux and Go network engineering.
That gap sparked 12 months of Linux systems research and custom Go network engineering. Jonathan studied socket timing, packet recovery and data-centre routing. He then built custom software in Go to provide a clean path through congested local networks.
Traders Proxy was engineered for traders facing ISP congestion, restrictive firewalls and unreliable routes. Your terminal opens a lean local connection to our nearest edge server. Our server then carries your orders and tick data across institutional backbones directly to the broker data centre.
Placing our servers in broker financial hubs means packet recovery happens over fast local links. Any retransmissions occur inside that city rather than over an ocean round trip to your device. Jonathan still trades daily on MetaTrader 5, TradingView Desktop and Optuma while managing Traders Proxy from Brisbane.
- Founder
- Jonathan, in Brisbane, Australia
- How it started
- 12 months of Linux and Go engineering after missed trades across Asia
- Platforms he trades on
- MetaTrader 5, TradingView Desktop and Optuma, with Telegram alongside
- What is our own code
- The trading proxy, server agent and control system, all written in Go
- Where our servers run
- 14 servers across the broker cities we list
- Payments
- Stripe handles billing and we never see your card number
What is our custom code and what is external.
The software that carries your trading connection is our own Go program, built on standard and extended libraries. Our server agent and backend orchestration system are also built in Go. Read how we built it for the complete technical breakdown.
For Telegram proxy support on plans with 2 or 5 devices, we incorporate the mtg project. Card payments run through Stripe, so we never see or store your card number. You select your broker city in the dashboard and can switch locations whenever you need.
Direct support and account ownership.
We do not send marketing emails or inspect your trading payloads. Platform traffic passes through untouched so your broker encryption remains intact. Operational notices appear directly in your dashboard, and stopping renewal takes one click.
For technical assistance or setup guidance, open Ask support on our contact page. We maintain [email protected] strictly for formal legal notices. Jonathan reads technical tickets directly and resolves setup questions himself.
Frequently asked questions
Who owns and runs Traders Proxy?
Jonathan started Traders Proxy and runs it from Brisbane, Australia. There are no outside investors and no separate support company. The service is maintained by the person who built it.
Why build a trading proxy instead of using a VPN or a VPS?
Across Asia, Jonathan found that commercial VPNs cleaned up bad local routes, but shared servers were not designed for live orders. A VPS meant trading inside a remote desktop window. Traders Proxy routes only your trading app and connects from our server in your broker city.
Did you write the proxy software yourselves?
Yes, our connection software, server agent and control system are all written by us in Go. We build our Telegram proxy on the mtg project, and Stripe handles payments. How we built it covers how each part works.
Which platforms does Traders Proxy work with?
Any trading platform with a proxy setting works, including MetaTrader 4 and MetaTrader 5, TradingView Desktop and Optuma. On Android, MetaTrader 4 and MetaTrader 5 connect through a proxy app such as AdGuard. Review the cTrader setup guide for cTrader configuration on Windows.
What if my platform can’t connect through Traders Proxy?
If your platform can’t connect through us and support can’t fix it, we refund your first payment (7 days monthly, 14 days yearly or Founder 50). Renewals are not refunded. This doesn’t affect your rights under the Australian Consumer Law.
Field reports · Verified forum threads
Real forum reports, what our system does, and where it stops.
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.
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.
'Ping failed' and drops with disconnects every few minutes, re-login loops and dropped sessions
“Is the chart freezing, or is it the terminal? If it is the terminal, then it is likely a broken indicator.”
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.
Manual trading on a Windows VPS adds a remote-desktop step that 0 ms hides
“a trader has a trading robot developed by his or her efforts or ordered from programmers; a trader has an Expert Advisor purchased from the Market; a trader has subscribed to a Signal. All these cases require constant connection to a trade server and uninterrupted power supply.”
How local trading avoids it. Your platform stays on your own computer and monitors, so clicks and hotkeys never wait on a remote-desktop window.
- Platform stays on your own computerPrimary
Where it stops. We add a step between your computer and your broker, and we do not promise lower ping. Distance between you and your broker still counts.
'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.