A scalper holds a long on EURUSD with the stop 5 pips below entry. Price grinds sideways for ten minutes. Then one print drops 8 pips for a fraction of a second and snaps straight back. Position closed, loss booked, and a minute later the chart looks perfectly normal.
Nobody can find the candle that did it. Some platforms filter odd ticks before drawing bars, so the history shows a clean low that never reached the stop. The trade log says otherwise.
Sometimes it is a thin quote from one liquidity source. Sometimes it is a feed glitch. Sometimes it is a real spike in a gap of liquidity that the chart simply smooths away. From the trader's seat all three look identical: a stop hit with no evidence on screen.
The annoying part is the argument that follows. The broker points at the server tick log, the trader points at a 1-minute chart, and the two are not even looking at the same data.
Has a bad tick ever taken out a trade for you, and did the broker show the tick that triggered it or only the closing price?
stopped out by a tick nobody else saw
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
-
FXS London Scalper
- Posts: 976
- Joined: Sun Oct 18, 2026 12:25 pm
Re: stopped out by a tick nobody else saw
The broker's tick history after the event is the first thing to check. If the print is gone from the chart the next day, that's a strong case for a complaint, since they effectively admitted it was a bad tick. Screenshots at the moment help a lot, because the chart can be "cleaned" later.
FXS Official Team | London Session Desk
-
Amanhasnoname
- Posts: 2060
- Joined: Fri Oct 30, 2026 9:45 am
Re: stopped out by a tick nobody else saw
It happened to me on AUDUSD during the quiet stretch just after the New York close. I had a short with a tight stop above a range, and I got taken out by a print about six pips above anything else that hour. The one-minute chart the next morning showed a high nowhere near my stop, so at first I assumed I had made a mistake entering the order.
When I asked support, they sent me a short extract of their server tick log for that minute, and the spike was there as a single quote that lasted under a second. They also admitted it came from one liquidity provider during a thin period. After a bit of back and forth they credited the loss, but only because I had the exact time from my trade history and asked for the ticks rather than arguing about the chart.
Since then I avoid holding tight stops through the rollover hour at all, because that is when these odd prints show up most for me. If I must hold, I give the stop a little extra room and cut size so the risk in money stays the same.
When I asked support, they sent me a short extract of their server tick log for that minute, and the spike was there as a single quote that lasted under a second. They also admitted it came from one liquidity provider during a thin period. After a bit of back and forth they credited the loss, but only because I had the exact time from my trade history and asked for the ticks rather than arguing about the chart.
Since then I avoid holding tight stops through the rollover hour at all, because that is when these odd prints show up most for me. If I must hold, I give the stop a little extra room and cut size so the risk in money stays the same.