The connection between your trading terminal and the broker's server is usually filed under "infrastructure". On a prop firm evaluation it is a rule, because several of the rules that end accounts are enforced on time rather than on price. A stop that triggers on your chart and a stop that triggers on the firm's server are two different events, and latency is the distance between them.
This is worth taking seriously because the failure it produces is invisible in a backtest and looks like bad luck in a journal: the price never touched your stop, yet you were stopped out; or the daily loss limit fired and the loss you see is larger than the loss you sized.
The three rules that are actually clocks
Almost every drawdown rule that causes a surprise has a time component:
- The daily loss limit reset. It resets at a fixed server time — often the firm's midnight, sometimes the market's daily close in a specific timezone. The exact instant your "day" starts and ends is a server-defined boundary, not the one on your wall clock.
- The news window. Restrictions on opening or holding positions are defined as intervals around an event (e.g. "two minutes either side of a high-impact release"). The window is measured on the server's clock.
- The maximum trade duration / overnight cutoff. Some programmes require positions to be closed within a session or before a cutoff time. The cutoff is a server timestamp.
If your terminal's clock, your VPS's clock and the broker's clock disagree, a trade you believe is inside the window can be outside it — and there is no "close enough". The rule evaluates a timestamp.
Why a home connection is the wrong reference
Two distinct problems, and it is worth separating them:
Latency. The round-trip time between your terminal and the server. On a routed home connection in a different region this can be tens of milliseconds with high variance. That variance is the issue, not the absolute number: a variable delay means a stop order that arrives late by exactly the amount the price moved in that window, which on a fast instrument during a release can be the difference between a $200 loss and a $600 one.
Timing. Most prop-firm rule enforcement happens server-side, so latency does not change whether the rule fired — it changes the price at which your order filled relative to the trigger. But a home connection with an unstable clock can also change what your terminal thinks the time is, which matters for a manual decision near a cutoff.
A VPS fixes both by placing the client in the same datacentre region as the broker, cutting round-trip time to single-digit milliseconds and removing the domestic-connection jitter.
The arithmetic of a late fill
The reason this matters to the account rather than to comfort is that the loss from a late fill is proportional to size:
extra loss = slippage_per_unit × size (in units)
Take a scenario: during a news release, price moves 8 pips in the 40 ms between your stop triggering and your order reaching the server under a home connection, versus 1 pip on a co-located VPS. On a position where one pip is worth $10:
- Home connection: 8 pips × $10 = $80 of slippage on that single exit.
- Co-located VPS: 1 pip × $10 = $10.
Neither fills at the stop price, so both are worse than the chart suggests. The difference is $70 on one trade. Repeat it across a strategy that exits several times a day and the VPS is not a luxury — it is a direct reduction in the slippage that eats into a drawdown budget already measured in dollars.
The second-order effect is worse. A stop that fills 8 pips late is 8 pips closer to the floor than planned, and the trader's sizing assumed the planned stop. The trade was correctly sized for one loss and delivered a larger one. Over a series, that drift is exactly what "my account died earlier than my backtest" looks like.
What the firms require
Many firms make a VPS mandatory for automated trading (EAs and bots), for two reasons: to keep the strategy's latency predictable, and to satisfy the firm's own requirement that the client runs continuously. The requirement is usually stated in the automated-trading or technical section of the rules rather than on the pricing page, which is why it surprises traders who read only the marketing.
The practical checklist before running anything automated on an evaluation:
- Location. The VPS region should match the broker's server region. Latency is a function of geography, not of how much RAM you bought.
- Always-on. The client must not sleep. A dropped connection during an open position is a rule risk (some firms treat a dropped EA as a violation).
- Clock sync. NTP synchronisation, so the terminal's timestamps agree with the server's for window-based rules.
- Standby power and redundancy. A VPS that reboots on the daily boundary can miss the cutoff. The failure mode is a position held through a window that should have been closed.
What to do this week
- Measure your actual round-trip latency to the broker's server, not to a generic internet host, and note the variance over a session.
- Find the firm's reset time and news windows in server time, and convert them into the timezone your terminal displays. Put the conversions on the chart.
- Price the slippage you are currently paying. If it is a meaningful fraction of your daily drawdown allowance, co-location pays for itself faster than any strategy tweak.
- Size from the realistic stop, not the ideal one. If you know your exits slip, the budget should include the slip.
None of this is alpha. It is the difference between a rule that fires on the server at the moment it is written to fire and a rule that fires on your side of the connection at a moment you did not choose. On an account whose entire margin is a few thousand dollars of drawdown, that difference is not infrastructure — it is risk.
The practical setup — which programmes require a VPS, what region to pick for each broker, and how the timing rules are written — is in the VPS requirements breakdown. If you would rather model the cost of slippage on your own sizing before choosing, the prop firm profit calculator works in the same account currency.
Top comments (0)