Pull up a one-minute chart and a wild wick appears on a news release. Come back the next day and the wick has shrunk or disappeared. The data was edited.
The reason is usually to remove bad ticks. Feeds sometimes print a price that was never really tradeable, thanks to a glitch at a liquidity provider or a stale quote. Cleaning those out makes sense for charts.
The problem for a scalper is that the edit applies after the fact. A real fill during that spike may have happened at a price the cleaned history no longer shows. Reconciling the trade history against the chart then shows an entry outside the candle.
It cuts the other way too. A stop that triggered on a spike can look like a bad execution when checked against the cleaned chart.
Saving screenshots or raw tick logs during volatile periods is the only way to prove what the price did at the time.
Has a trade ever been disputed because the chart history didn't match the fill?
Brokers do cut spikes out of the history, and it's worth knowing why
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
-
FXS Prop Desk
- Posts: 1689
- Joined: Wed Oct 07, 2026 9:52 am
Re: Brokers do cut spikes out of the history, and it's worth knowing why
This matters most for anyone reviewing stop-outs. If the wick that hit the stop is later removed from the history, the stop-out can look like an error. Saving a screenshot at the time of any unusual fill is a simple way to keep evidence.
FXS Official Team | The Idea Lab & Strategy
-
Amanhasnoname
- Posts: 2060
- Joined: Fri Oct 30, 2026 9:45 am
Re: Brokers do cut spikes out of the history, and it's worth knowing why
Yes, once, and it taught me to keep my own records. I had a short on GBPUSD during a UK inflation release, and my stop was hit on a sharp upward wick. When I went back the next morning to review it, the candle on my broker's chart topped out well below my stop level, so on paper it looked like I had been stopped for no reason at all.
I opened a ticket with support, and to their credit they sent me the raw tick log for those seconds. The spike was there, a run of prices that lasted under a second before the feed corrected. They had filtered it from the chart history afterwards, but my order had already been triggered against it, and the fill stood.
Since then I run a small script that writes every tick to a file while I trade around scheduled data. It costs nothing in disk space, and whenever a fill looks odd I can check what the feed actually showed rather than trusting the tidied-up chart.
I opened a ticket with support, and to their credit they sent me the raw tick log for those seconds. The spike was there, a run of prices that lasted under a second before the feed corrected. They had filtered it from the chart history afterwards, but my order had already been triggered against it, and the fill stood.
Since then I run a small script that writes every tick to a file while I trade around scheduled data. It costs nothing in disk space, and whenever a fill looks odd I can check what the feed actually showed rather than trusting the tidied-up chart.