Skip to main content
Trader problem · Diagnose

Order Rejected Due to Timeout: What That Actually Means

Your platform sent the order. The broker's server didn't confirm it fast enough. That gap - the round-trip time between your machine and the broker - is what you can actually fix.

TL;DR

MT4 and MT5 send your order to the broker's server and wait for a confirmation ("fill" or "reject") within a fixed timeout window. If the round-trip takes too long - because your route is slow, the server is busy, or both - the platform cancels the request on your side. You see "rejected - timeout." The order usually did not fill. Network latency is the lever you control.

See the plansRead the latency guide
Error
"Order rejected - timeout" or "Request timed out" in MT4/MT5.
Cause
Round-trip latency exceeded the broker's confirmation window.
Fix
Reduce the route time between your machine and the broker's DC.

What's actually happening

When you click "Buy" or an EA fires an order, MT4 or MT5 sends an order request packet to the broker's trading server. The server processes that request - checks your margin, finds a fill at the current price, logs the execution - and sends back a confirmation packet.

The platform has a timeout window: if the confirmation doesn't arrive within that window, it assumes something went wrong and rejects the order on the client side. That timeout is not adjustable from the platform UI. The window is short - typically a few hundred milliseconds to a few seconds depending on the broker's configuration.

So the question becomes: how much of that window does the network eat? If your route adds 200 ms of latency each way, you've already consumed 400 ms before the broker's server even starts processing. On a busy news day, that can exceed the full window - and the order times out before the confirmation makes it back.

Quick self-diagnosis - 5 minutes

  1. Check the MT4/MT5 journal tab
    The Journal tab in MT4/MT5 logs every order event with a timestamp. Look at the gap between "send order" and the rejection - if you see it at all. A long gap confirms the network is the bottleneck.
  2. Ping your broker's hostname and note RTT
    Run ping your-broker-hostname.com. If your round-trip time is over 100 ms, you're already eating a significant portion of the fill window before the broker even sees your order.
  3. Reproduce at different times of day
    If timeouts only happen during London or NY open, the broker's server is under load and your latency headroom matters more. If it happens all day, your route is the primary problem.
  4. Test via mobile hotspot
    If orders go through on mobile data but timeout on your main connection, your ISP is routing traffic to the broker's DC through a congested path.
  5. Run a traceroute during a timeout event
    Windows: tracert your-broker-hostname.com. Count the hops and note where RTT spikes. That spike is where the route is adding time.

What actually fixes this - honest ranking

1

Ethernet over Wi-Fi

Wi-Fi adds variable latency that directly cuts into your order timeout window. Wired is always the first step - it removes the single biggest source of unpredictable delay from your local setup.

2

TradersProxy - shorter route to the broker's DC

If your ISP's path to the broker's datacenter is adding 100-200 ms, a trading proxy that routes through infrastructure physically closer to that DC can cut that significantly. Less round-trip time means more of the timeout window is available for actual order processing.

3

VPS near the broker's datacenter (for EAs)

An EA running on a VPS co-located near the broker's server can achieve 1-5 ms round-trip times - essentially eliminating the network timeout risk. The tradeoff is cost, management overhead, and the fact that your MT4 is now on a remote machine.

4

Change ISP or use a different network

Some ISPs route through upstream providers that add significant latency to specific datacenter regions. A different ISP may use a shorter backbone path. Test with a mobile hotspot first to see whether the network change alone fixes the problem.

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 a network problem

  • Broker server overload during news. If every trader in the pool is hitting the server simultaneously during NFP, the processing queue backs up regardless of your network speed. Your order arrives fast but waits in line. This is a broker-side bottleneck, not a routing one.
  • Wrong account type. Some broker account types have slower execution by design (market execution vs instant execution). Check which execution model your account uses - it affects how the server processes and confirms orders.
  • Insufficient margin. If a timeout rejection happens alongside a margin error in the logs, the server rejected on its own for margin reasons - not latency.
  • EA logic errors. An EA sending orders in rapid succession may be hitting the broker's rate limiter. That will also produce rejections that look like timeouts.
FAQ

Usually no. A timeout rejection means the platform waited for confirmation from the broker's server and did not receive it within the timeout window. The order was sent but not acknowledged, so the platform treats it as rejected. Check your broker's trade history to confirm - occasionally the order did fill at the server but the confirmation was lost.

No, but news events make it worse. During high-impact news, the broker's server is processing thousands of orders simultaneously. Any extra latency in your route means your order sits in the queue longer - increasing the chance it times out before confirmation arrives.

Partially. The broker sets the timeout window. But the time it takes your order to reach the broker's server is determined by your network path. A faster, more direct route means the order arrives sooner and has more of that timeout window available for processing.

MT4 and MT5 have a fixed request timeout that you cannot change from the platform settings. The only lever you control is reducing the round-trip time between your machine and the broker's server - which is a routing problem.

A requote means the broker received your order but the price moved before they could fill it - they offer you a new price. A timeout means the broker never confirmed the order within the time limit. Requotes are a market condition; timeouts are a network condition.