Skip to main content
Strategy — news trading

News trading execution speed — what changes on your route during the first 500 milliseconds.

NFP, CPI, FOMC — these events compress enormous price moves into under a second. Your connection has to be ready when the release hits, not scrambling to recover after a jitter spike.

The news release is when every trader hits the same broker servers simultaneously. That is also when residential ISP routing is most likely to degrade. A dedicated route stays clean while shared networks buckle under load.

See the plansScalping latency guide
<1 second
How quickly price reprices after a major news release.
Load spike
Every trader hits the same broker servers at the same moment.
Jitter spike
ISP routing degrades under the surge exactly when you need it clean.

What happens to your connection during a news release

When an NFP print or CPI number drops, two things happen simultaneously on the network side. Your broker's matching engine sees a surge in orders — every automated system, every EA, every manual trader who was positioned and waiting hits the same server within milliseconds. At the same time, the ISP transit networks carrying that traffic also spike in load. Your residential connection is sharing that transit with everyone else on your ISP segment who is also doing something with their internet connection at that moment.

The result is that jitter — the variation in your round-trip time — spikes exactly when you need stability. An order that normally arrives in 45ms might arrive in 190ms. The price has already moved. The spread has already widened. Your fill is at a level that no longer matches your intent.

What you can and cannot control at news time

You cannot change the broker's server load. You cannot change how many other traders are submitting orders at the same millisecond. What you can control is the quality of your path from your machine to the broker's matching engine.

A dedicated proxy route does not share its transit capacity with residential traffic. The path to the broker's data centre is uncongested from the node outward. The jitter that residential ISPs add under load is not present on a dedicated routing layer. That is not magic — it does not make the broker process your order faster. It makes your order arrive at a consistent time rather than a variable one, which is how you trade the news release on the same terms as your competition's infrastructure.

News event checklist
  • Test your broker route well before the event, not in the final minutes.
  • Know your broker's execution model: market execution vs instant execution behave differently under news conditions.
  • Reduce open applications and background traffic before a major release.
  • Understand spread widening at your broker for the specific pair and event.
What the route actually changes

The proxy does not make your broker faster. It makes your delivery to the broker consistent.

News traders often ask whether a proxy helps. The honest answer is: it removes route-side jitter. That means your orders arrive at the matching engine at a predictable time rather than a variable one. The broker's own queueing, spread management, and requoting behaviour are separate variables that the route does not affect.

But for traders who have already optimised their strategy and still find news fills unpredictable, route quality is often the remaining variable. It is the one that residential ISPs reliably make worse at exactly the moments that matter most.

  • Route jitter is worst during peak load — which is exactly when news events hit.
  • A dedicated proxy route is not affected by other users on your ISP segment.
  • Consistent delivery is more useful than average-fast delivery at news time.
FAQ

A proxy reduces the route-side jitter that compounds the broker-side load. It cannot fix the broker's own queue time, but it removes the ISP routing noise that makes your connection deliver orders inconsistently at exactly the moment load is highest.

Spreads widen, price moves, and the queue for your broker's matching engine grows simultaneously — usually within the first 200-500 milliseconds. Your order needs to join that queue before the spread has widened past your entry parameters.

That depends on your execution model. ECN brokers with market execution fill at whatever price the market has moved to. Limit orders give you a price guarantee but risk not filling at all if price moves past your level. Either way, route quality affects how quickly your order arrives at the matching engine.