Stop hunting, or just liquidity doing what liquidity does
Posted: Mon Nov 02, 2026 11:07 am
Stop hunting, or just liquidity doing what liquidity does
A wick spears through an obvious level, clears the stops, and reverses hard. The usual explanation on every forum: the broker hunted the stops.
Sometimes that is true. Sometimes a dealing desk really does push a quote to trigger client stops. But in most cases the story is simpler and needs no conspiracy.
Obvious levels attract clusters of resting orders. Resting orders are liquidity. Large players need liquidity to fill size without moving the market against themselves, so price drifts toward those clusters, trades through them while the size gets done, and then reverts once the need is gone.
The difference matters because the two stories lead to different fixes. If the broker is the problem, the fix is a new broker. If market structure is the problem, the fix is moving stops away from textbook levels, and no change of broker will help.
A rough test: compare the same wick on a second broker or a neutral data source. If the wick appears everywhere, it is the market. If it exists on only one feed, that deserves a pointed conversation with support and maybe a switch.
Another clue is size. A real liquidity grab usually coincides with a burst of tick volume and a visible reaction on other pairs. A broker-only spike often has no echo anywhere.
There is also the timing question. Stop clusters at round numbers get hit most often when volume is thin, such as just after the London lunch or in the late New York afternoon. A wick at a busy open points more toward real flow.
Brokers that deal against clients do have an incentive, and a few have been caught acting on it, so complete trust is not the answer either. The sensible stance sits in between: assume liquidity until the data shows otherwise, and keep the evidence ready if it does.
Has a stop ever been taken out by a wick that appeared on only one platform?
A wick spears through an obvious level, clears the stops, and reverses hard. The usual explanation on every forum: the broker hunted the stops.
Sometimes that is true. Sometimes a dealing desk really does push a quote to trigger client stops. But in most cases the story is simpler and needs no conspiracy.
Obvious levels attract clusters of resting orders. Resting orders are liquidity. Large players need liquidity to fill size without moving the market against themselves, so price drifts toward those clusters, trades through them while the size gets done, and then reverts once the need is gone.
The difference matters because the two stories lead to different fixes. If the broker is the problem, the fix is a new broker. If market structure is the problem, the fix is moving stops away from textbook levels, and no change of broker will help.
A rough test: compare the same wick on a second broker or a neutral data source. If the wick appears everywhere, it is the market. If it exists on only one feed, that deserves a pointed conversation with support and maybe a switch.
Another clue is size. A real liquidity grab usually coincides with a burst of tick volume and a visible reaction on other pairs. A broker-only spike often has no echo anywhere.
There is also the timing question. Stop clusters at round numbers get hit most often when volume is thin, such as just after the London lunch or in the late New York afternoon. A wick at a busy open points more toward real flow.
Brokers that deal against clients do have an incentive, and a few have been caught acting on it, so complete trust is not the answer either. The sensible stance sits in between: assume liquidity until the data shows otherwise, and keep the evidence ready if it does.
Has a stop ever been taken out by a wick that appeared on only one platform?