Trade Copier Latency: How Fast Does Copying Need to Be?

Fast enough is a copier that sends the follower order the moment the source fill reaches it, without waiting for a timer. After that, the copier is usually not the slow part: the follower broker's own execution is normally the binding constraint, and no copier, cloud or local, can shorten it. A second either way matters for scalps and news trades, and changes nothing you can measure on a position held for hours. This guide lists what adds the delay, in order, and when the gap genuinely changes a trade.

What adds delay to a copied trade, in order

A copied trade meets five delays in this order. The copier controls the second and third, and its choice of connection shapes the fourth:

1. The source broker reporting the fill. Your order fills on the source account and the broker reports it to the connection watching that account. The copier cannot start before this, and a figure measured from the copier's side does not include it.
2. Fill detection. How the copier learns the source position opened or closed. A copier subscribed to a real-time stream hears the fill as it happens; one polling on a timer can sit on a full poll interval of dead time before it even starts. This is the stage where copier design genuinely differs.
3. Dispatch. Scaling the lot, applying any symbol remap and allowlist check, and sending the order to each follower; Trepeat sends to every follower at once, not one after another. The arithmetic itself is trivial.
4. The route to the follower broker. The order crosses the network to the broker, through any connection service on the way: a MetaTrader order in Trepeat goes through MetaApi, a cTrader order goes straight to cTrader.
5. The follower broker's execution. The order arrives, queues, is priced against that broker's liquidity, and may be requoted or rejected. Outside any copier's control, and typically both the largest leg and the most variable.

Put plainly: a copier competes on detection, barely on dispatch, and not at all on the follower broker. Any comparison that ignores the last leg is comparing the small parts. In Trepeat, every copy on your Trades page shows its own time from the fill reaching Trepeat to the follower broker confirming and, where both parts were recorded, split into Trepeat engine and Broker latency, so you can see which leg your own accounts spend it in. The parts of a copier that a fill passes through are laid out in copy trading platform components and data flow.

Why "milliseconds" in the marketing is mostly meaningless

A copier's published latency figure is mostly meaningless, because it rarely says what it measured. Whether the number covers only the tool's internal processing or the whole path to the broker, whether it is a single run or a distribution, and what the market was doing at the time are usually all left unstated. None can include the follower broker, because that number belongs to a different company and changes with the session and the instrument. So a copier advertising a headline figure and one advertising nothing may put your order at the same broker at the same moment.

If a vendor quotes a number, ask what it measures and what it excludes. If the answer is vague, treat the figure as decoration. We don't publish an engine-only headline number for Trepeat: a number with the broker leg stripped out would flatter us and tell you nothing useful about your own accounts. When we show a copy time, it is the end-to-end figure measured on customers' own copies (our own test accounts excluded), and every copy shows its own time on your Trades page.

A different fill price usually isn't lag

When a follower fills at a different price from the source, the gap is usually spread and liquidity, not copier lag: two brokers quoting the same instrument at the same instant print different prices, and each fills against its own book. The most common misreading is a source filling at 1.24010 and a follower at 1.24022, and concluding the copier is slow.

A rough test: if the difference is consistent, in the same direction, and roughly the size of the spread gap between the two brokers, that's pricing. If it's large, erratic, and only on fast moves, timing is a plausible suspect. Why follower fills differ works through the full list of causes, including requotes and news-time slippage.

When latency genuinely matters

Copy latency matters most in four cases: scalping, news releases, very fast round trips, and exits.

• Scalping: positions held for seconds to a few minutes over a handful of pips. Any delay is a meaningful fraction of the whole move, so the dispatch stage earns real attention; the scalping trade copier page lists what to check.
• News releases: spreads widen and requotes get common in the seconds around a print. Delay compounds with slippage here, though it's the broker leg that dominates, which is exactly the part no tool can fix.
• Very fast round trips: a position opened and closed inside seconds can see the close arrive while the copy is still opening. What matters is that the copier handles that rather than leaving a position behind on the follower.
• Exits in general: a late entry costs you a slightly worse price; a late exit can cost considerably more. Judge exit handling harder than entry speed.

One rules note: some brokers' terms restrict latency-based tactics such as arbitrage between venues. That's a different activity from repeating your own trades, but the line is drawn by your broker's agreement, not by us and not by this page. Read it, and see is copying your own trades allowed for how to approach the question. Nothing here is legal advice.

When it doesn't matter much

Copy latency matters little if you hold positions for hours or days and enter at levels rather than ticks: a second either way changes nothing you can measure. Swing traders routinely over-index on speed and under-index on faithfulness. What actually decides whether copying works for that style is whether closes andpartial closes copy as reliably as opens, whether sizing lands correctly on accounts of different sizes, and whether a symbol name mismatch quietly drops trades. Start from what a trade copier actually does if you're weighing that up.

Cloud vs VPS isn't the deciding factor

Whether a copier runs in the cloud or on a VPS beside the broker's server matters far less for speed than two other things: event-driven versus polled fill detection, and the broker's own execution, which is identical either way. A common assumption is that the VPS must be quicker, but physical distance is the small part. A local copier still sends its order over the internet, and carries constraints of its own: terminal open, machine awake, process running. Cloud vs local (VPS) copiers compares the two on uptime, cost and upkeep, which are the differences that show up in practice.

What to check instead of a speed number

Instead of a speed number, check how a copier detects fills, what it copies, and how it tells you when a copy doesn't land.

• Is fill detection event-driven, or polled on a timer? Ask directly.
• Are closes and partial closes copied, or only opens?
• Can one action close the source position and every copy of it, or do you unwind followers by hand?
• When a copy doesn't land, do you find out immediately, with the reason the broker gave, or notice it at the end of the week?
• Can you see each follower's actual fill, rather than assuming it matched?

Trepeat dispatches on real-time streams rather than a polling timer, copies opens, closes and partial closes, and raises an alert naming what the broker reported when a copy doesn't land. It currently connects MetaTrader and cTrader demo accounts (the type prop firm evaluations and funded accounts usually run on) and refuses live accounts at connect time. What it can't do is set your broker's execution speed, and any tool claiming otherwise is describing something it doesn't own.