Skip to main content
Trader problem · Diagnose

Broker Support Says "Check Your Internet": What They Mean

This sounds like deflection. Sometimes it is. But often, broker support is pointing at something real - and you have the tools to verify it yourself in 5 minutes without waiting for their next reply.

TL;DR

When broker support says "check your internet," they are telling you to rule out the path between your machine and their server. Brokers can see server-side logs. If your connection attempts are reaching their server cleanly, they know the problem is theirs. If they don't see clean connections, the issue is between your machine and their datacenter - your ISP, local network, or routing path. You can verify this yourself with a ping test and a mobile hotspot in under 5 minutes.

See the plansRead the latency guide
What they see
Server logs showing whether your connection attempts are reaching their server.
What they mean
Verify your ISP's path to their datacenter is not adding the problem.
How to verify
Ping test + mobile hotspot test. Takes 5 minutes. Either confirms or rules out the network.

What's actually happening

Broker support has access to server-side connection logs. They can see: which account attempted to connect, from which IP address, at what time, and whether the connection completed successfully or failed. When they see a pattern of incomplete connections or high-latency sessions from your IP, they know the problem is happening between your machine and their server - not inside their platform.

From their perspective, telling you to "check your internet" is a specific technical instruction: verify that the network path from your machine to their server is not the bottleneck. They cannot fix your ISP's routing. You can.

The frustrating part is that this response often comes without explaining how to actually check it. This page gives you that diagnostic.

Quick self-diagnosis - 5 minutes

  1. Ping your broker's hostname right now
    Open a terminal and run ping your-broker-hostname.com. If the hostname is in your MT4/MT5 Server settings. Note the RTT and any packet loss (timeouts). This is the baseline measurement for your current path.
  2. Switch to a mobile hotspot and re-test
    Connect your laptop to your phone's hotspot. Run the ping again. If RTT drops significantly or the connection issue disappears, your home ISP's routing to the broker's datacenter is the variable - not MT4 and not the broker's server.
  3. Run a traceroute to find where the path breaks
    Windows: tracert your-broker-hostname.com. Mac/Linux: traceroute your-broker-hostname.com. Identify where hops stop responding or where RTT spikes. That is where the routing problem lives.
  4. Check the MT4/MT5 journal for connection events
    Export the journal log and compare connection failure timestamps to your ping results. Simultaneous timeouts confirm the network is the cause. If the journal shows failures but ping is fine, the TCP port itself (not ICMP) is being filtered.
  5. Test at a different time of day
    If the problem only occurs at London or NY open, ISP congestion during peak hours is adding delay to the broker's datacenter. If it is consistent all day, your ISP's backbone path to that DC is structurally poor.

What actually fixes this - honest ranking

1

Ethernet over Wi-Fi

The first and cheapest thing to try. Wi-Fi adds packet loss and jitter that the broker's server sees as an unstable connection. If you're troubleshooting on Wi-Fi, switch to wired before doing anything else.

2

TradersProxy - change the path to the broker's DC

If the problem is your ISP's routing to the broker's datacenter, a trading proxy changes that path entirely. Your traffic leaves your machine, routes through a proxy node with a direct path to the broker's DC, and arrives faster and more reliably. The broker stops seeing a bad connection from your IP.

3

VPS near the broker's DC

Move MT4/MT5 to a VPS in the broker's datacenter region. The connection is now local - sub-5 ms RTT - and your ISP's routing is irrelevant. Correct tool if you also need 24/7 uptime for EAs.

4

Change ISP or use a different network

If your ISP's backbone consistently routes poorly to the broker's DC region and a proxy doesn't help, a different ISP may use a different backbone with a shorter path. Verify via mobile hotspot first.

If the route is the problem, a dedicated trading proxy is the fix at the infrastructure level — a relay node co-located near your broker's datacenter replaces the unstable public internet hops with a dedicated path. 7-day trial on Starter →

When it's not your internet

  • The broker's server is actually down. Check their status page and community forums. If multiple traders report issues simultaneously, it is broker-side regardless of what support says in automated responses.
  • Your account has been flagged or suspended. An account-level block will cause connection failures that look identical to network failures from your side. Ask support explicitly: "Is my account active and unrestricted?"
  • Platform version incompatibility. After broker migrations or platform updates, old MT4/MT5 builds can fail to connect to updated server software. Download a fresh build from the broker's website.
  • Wrong server hostname. Brokers sometimes migrate servers. If you are connecting to an outdated hostname, the server no longer accepts connections there. Get the current server list from your broker's download page.
FAQ

They mean: verify that the problem is on your side of the connection, not theirs. They can see from their server logs whether your platform connected successfully. If they see connection attempts that fail or drop, and other clients are fine, the issue is your path to their server - your ISP routing, your local network, or your machine.

Sometimes. But often they are genuinely correct. Brokers have server-side logs and can see whether the connection issue appears on their end or only on yours. If they tell you to check your internet, ask them specifically: 'Do your logs show my connection attempts reaching your server?' That narrows it down.

Test from multiple networks. If MT4 connects from your mobile hotspot but not your home connection, the problem is your home ISP's path to the broker's server - not a general internet outage. Document the test with timestamps and share with support.

Speed is irrelevant to trading connectivity. A speed test measures bandwidth to a nearby CDN server. Trading connectivity depends on the specific route to your broker's datacenter - which may add 200 ms of latency even on a 1 Gbps connection. Speed and latency are different measurements.

Yes. Run a continuous ping to your broker's hostname for 30 minutes during a session. Export the MT4/MT5 journal. Note the exact timestamps of connection failures. This gives support something concrete to match against their server logs.