My guess is that you are most likely trading Nifty futures or the most active traded contracts. If you trade the illiquid ones, you will spot this.
The issue here is that NSE is sending thousands/lakhs of ticks every second over internet, so most data doesn't really come through to the brokers server. The broker will use whatever data that comes through to create the O H L C. Hence different servers might receive data/ticks which is not exactly the same.
NSE gives out 2mbps dedicated leased lines today, so unless this goes to say 2gbps, I don't see how this issue will ever get fixed.
NSE gives out 2mbps dedicated leased lines today, so unless this goes to say 2gbps, I don't see how this issue will ever get fixed.
On a related note, I recollect when GFDL launched their data service, someone in the forums queried their rationale for data scheme charges being based upon number of tickers. Without understanding the basis of this practice and (of course) without them having established similar infrastructure/ data architecture then, they defended their decision by claiming that "because this is generally the practice abroad"
Since Zerodha is not an authorized pro data provider but a broker, establishing such an architecture is neither expected nor such expectations ought to be harboured
Disclaimer - Corrections and clarifications posted in public interest for educational purposes and not due to compulsions of any affiliation (commercial or otherwise) to named entities or any other similar entity