Kill Zones Explained: Why the London Open Moves Markets

If you have ever noticed that certain times of day consistently produce the sharpest, cleanest price moves in the forex market, you have already observed kill zones without knowing what to call them. The concept, popularised by the trading methodology sometimes referred to as ICT (Inner Circle Trader), describes the time windows during which institutional participants are most actively executing large orders.

Understanding why these windows exist, and how to align your trading with them rather than against them, is one of the most practical timing improvements any forex trader can make.

Why Institutional Traders Cluster Their Execution

Large institutional orders cannot be executed the way retail orders are. A fund moving 500 million dollars into EURUSD cannot simply place a market order because the size of the order would move the price against them before it filled. They need liquidity, and liquidity is not evenly distributed across the trading day.

The hours surrounding major session opens are when liquidity is deepest. Market makers are actively quoting. Banks are hedging overnight positions. News from the prior session is being repriced. The spread between bid and ask narrows. For large participants, these windows are the most efficient time to execute without causing excessive slippage. That concentration of institutional activity is what makes kill zones significant.

The Four Primary Kill Zones

The Asian kill zone runs approximately from 20:00 to 00:00 UTC. Liquidity is thinner here, and price often consolidates or builds a range that will be used as a reference point for the London session. Major pairs like USDJPY and AUDUSD are more active during this window.

The London open kill zone is widely considered the most important for major forex pairs. It runs from roughly 02:00 to 05:00 UTC. London is the largest forex trading centre in the world, handling around 38 percent of global daily FX volume. When the London session opens, resting orders from overnight accumulate, stops get cleared, and directional moves often initiate. Many experienced traders consider the move established in this window to be the directional bias for the full trading day.

The New York open kill zone runs from approximately 07:00 to 10:00 UTC. The overlap between London and New York is where the highest daily volume concentrates. Major economic data releases from the US are often scheduled in this window. False moves that reverse the London direction are not uncommon here as New York participants reprice the market based on fresh data.

The New York close kill zone, running from roughly 14:00 to 16:00 UTC, is the window during which institutional participants close or roll positions before the end of the US session. It tends to be less dramatic than the opens but can produce sharp reversions, particularly if price has been extended from its daily range.

How to Use Kill Zones Practically

The most straightforward application is to restrict your trade entries to kill zone windows. If your analysis says a setup is valid but the market is in the middle of the Asian consolidation range with no clear directional catalyst, waiting for the London open is often the more disciplined move.

Kill zones also explain why trading certain pairs at random times during the day produces inconsistent results. EURUSD at 14:00 UTC trades very differently from EURUSD at 09:00 UTC, not because the pair changed, but because the institutional participants who drive the meaningful moves are operating on a schedule.

Signal providers who understand kill zones will note their preferred execution windows in their analysis. When you see an analyst on TipLeaks specify a setup as a London open entry or a New York close reversion, they are flagging the timing as deliberate, not incidental. The timing is part of the edge.

Markets are not random. The apparent randomness that frustrates retail traders is often the result of looking at price behaviour out of its institutional context. Kill zones are one layer of that context made visible.

More from the blog