timestamp" field in the tick data is consistently ~28 days ahead of my local system

naveenarya

Hello Zerodha/Kite Connect Support,

I'm using the Kite Connect API for live quotes/ticks, and I'm noticing that the "timestamp" field in the tick data is consistently ~28 days ahead of my local system time. For example, I receive ticks like:

{
"tradable": true,
"mode": "quote",
"instrument_token": 17517314,
"last_price": 151.3,
"timestamp": 1740735636.2123075,
...
}

When I convert 1740735636 into UTC, it maps to around 2025-03-28T... while my actual (real) date is only 2025-02-28. Because of that, my application’s aggregator treats these as future-dated bars, preventing any real-time alerts or trades.

Key points:
- My system clock is correct for local date/time (verified via `datetime.now()` and typical epoch times for February 2025).
- The Kite Connect feed consistently returns timestamps ~28 days in the future relative to my system date.
- This mismatch causes my “live” algorithm to skip or misalign bars, resulting in “no new trades” even though the data is supposed to be real-time.

Questions/Requests:
1. Is there a known time offset for this feed in a test environment, or any reason the timestamps might be ~1 month ahead of the real date?
2. Could there be an issue with the server’s internal clock or a bug in how timestamps are encoded?
3. Are these ticks from a replay environment or actual live environment?

Any insight or fix would be greatly appreciated, as the timestamp mismatch halts live strategy signals. Thank you for your assistance!

Best regards,

Naveen

ANL

I have checked my tick data; it's fine; no time mismatch has been noted.
Check the local time again. Use NTP server for time sync.
Convert EPOCH to IST instead of UTC.

"timestamp": 1740735636.2123075

For UTC and Epoch, it displays today's date rather than 28 days ahead.

According to your date, the actual conversion: UTC Fri Feb 28 2025 09:40:36 & IST Fri Feb 28 2025 15:10:36

I think you converted time in the wrong method.