Support Board

respectfully, i don't think you understand the problem. ppl aren't complaining about not receiving the data at the "correct time." if there's a news release at 8:30:00am EST, nobody's gonna complain about receiving the tick data at 8:30:50am EST due to latency if they're located in Tokyo. the problem is the manner in which the data is being transmitted and displayed through the front-end sc program.

if i'm located in europe or new zealand, there will be a ton of latency so the ticks may come through later than when it actually occurred. but as long as the ticks are displayed in the correctly-timed sequence as it occurred at the exchange-level (albeit with slight latency), ppl would be satisfied. 99% of us aren't running front-running algos that are latency-sensitive