Picture an ECB rate-decision day on which a Telegram signal channel with several thousand subscribers posts a short-EUR setup four seconds after the announcement headline crossed. The signal had a 20-pip stop and a 60-pip target. The chart at signal time looked clean; the order book underneath did not.
Every account that auto-routes that signal takes the same entry into the same spread at the same moment. What separates the accounts afterwards is how each one was sized and filtered. The numbers below are illustrative of how such a minute typically plays out, not measured PipSync data.
An illustrative minute
- Bid-ask spread on EUR-USD widened from 0.5 to 12 pips for 18 seconds — the realised entry was 11 pips worse than the signalled price.
- Slippage on the 20-pip stop pushed the average exit to a 31-pip loss.
- Basket effect: subscribers running the channel alongside two correlated EUR channels were short EUR across three pairs simultaneously, magnifying the move 3x against the account.
- Several brokers paused new orders for 30–90 seconds — the late entries got worse fills than the early ones.
Where risk controls have to live
There is no "better signal" answer here. There is a "better risk control" answer. The accounts that come through such a minute in good shape tend to share three habits: staying out of the ECB window altogether, rejecting orders when the live spread is far above normal, and keeping the combined size of correlated trades small. In PipSync, the second is the per-account Max Spread setting, which rejects an order when the live spread exceeds your limit. The first is manual: PipSync has no news filter, so switch auto-trading off (signals then wait for your approval on the Signals page), pause the channel, or use the per-account session filter, which limits trading to the Asia, Europe or US sessions (it is too coarse to exclude a single news window). For the third, risk-based sizing, Max Open Positions and the guard against a second same-direction position on one instrument cap the stacking, but PipSync does not detect correlation across different pairs, so keep risk per trade low when several channels trade the same currency.
The checks that PipSync does run are server-side because the news minute is exactly when a laptop-side script tends to lose its WebSocket.