Advertisement IC Markets

Feed throttling: not every tick reaches the screen

Share, develop, and backtest custom MQL4/MQL5 Expert Advisors, Python data-scraping scripts, trading bots, and automated market alert systems.
Post Reply
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

Feed throttling: not every tick reaches the screen

Post by Fairman »

Feed throttling: not every tick reaches the screen

Some brokers do not send every quote. To save bandwidth, they limit the update rate, sending perhaps a few ticks per second at most. A busy market produces many more internally.

The effect on a chart is a smoothed version of reality. Short spikes may disappear. Highs and lows are less extreme than on a faster feed, and the exact timing of moves is blurred.

For a strategy that relies on fine timing, the throttled feed is a handicap. Signals arrive late and slightly distorted, and the platform's idea of the market lags behind the broker's own.

There is no easy way to know how much is being filtered. Comparing tick counts with another broker or a vendor over the same period gives a rough measure.

Asking support about quote throttling is a reasonable step. Some brokers offer a faster feed on certain account types or through different connection methods.

A rough test: record the number of ticks per minute for the same pair at two brokers during the same busy hour. A large difference in counts shows that one of them is smoothing the feed.

How many ticks per minute does the broker deliver compared with others for the same pair?
It’s Fairman :geek:
Recommended broker for automated trading & scalping IC Markets
Amanhasnoname
Posts: 2060
Joined: Fri Oct 30, 2026 9:45 am

Re: Feed throttling: not every tick reaches the screen

Post by Amanhasnoname »

I counted ticks for the eight to nine London hour on two brokers in the same week, both watching EURUSD. Broker A, which I use only for data, averaged about ninety-four ticks a minute. Broker B, the account I was actually trading, averaged thirty-one. During one payroll minute A printed four hundred and twenty ticks and a fourteen-pip high to low, while B showed sixty-seven ticks and a nine-pip range. The wick that would have tagged my stop on A never appeared on B, but the fill still happened inside that missing stretch.

I asked support about it. They said the web terminal is capped at around two updates a second and that a direct connection would be faster. I did not move the account, but I did open a second window on the faster feed so I can see the real range while I execute on B.

On quiet stretches the gap shrinks and both names sit around twenty to twenty-five ticks a minute through the London lunch lull. I still add a pip to the stop on the throttled account, because trading a smoothed chart with a tight stop kept surprising me.
Post Reply