Ask any algorithmic trader who's built a multi-venue strategy across Australian markets, and they'll tell you this problem bites them exactly once — expensively. Timestamp normalisation sounds like infrastructure plumbing. Boring. Administrative. The kind of thing you deal with after the exciting stuff. Spoiler: it is the exciting stuff, because misaligned timestamps turn good signals into garbage trades.

Here's the direct answer. Australian equities trade across two primary venues — ASX and Chi-X Australia (now Cboe Australia) — and their market data feeds timestamp events using different reference clocks, precision levels, and latency offsets. Unless you normalise those timestamps to a single common timeline before your signal logic runs, you're comparing apples to tractors. A fill on Cboe that looks like it preceded an ASX quote might actually have arrived 200 microseconds later. That inversion is enough to corrupt a momentum signal entirely.

CONCEPTTimestamp normalisation forces every market event onto a single reference timeline before signal logic ever sees the data.
WARNINGComparing raw timestamps across ASX and Cboe feeds without normalisation will silently corrupt time-sensitive signals — no error thrown, wrong trades entered.
KEY IDEAThe problem isn't that clocks lie — it's that each venue's clock tells a slightly different truth, and your system must pick one truth to rule them all.

Think of it like this. Imagine you're coordinating a relay race, but each runner's coach is using a different watch — one's 80 milliseconds fast, another's slightly slow, and a third syncs to GPS only every 30 seconds. You can't meaningfully compare split times without first correcting every stopwatch to the same reference. Market data feeds are identical. ASX's ITCH feed and the Cboe equities feed both carry nanosecond-precision timestamps, but they're anchored to different NTP or PTP synchronisation cycles, with different network hop counts between the exchange matching engine and your feed handler.

Feed Timestamp Offset vs True Market TimeTime (Trading Session)Offset (µs)0+100+200ASX FeedCboe FeedTrue Time

The practical approach traders use involves three layers. First, a feed handler that records both the exchange-assigned send timestamp and the local receive timestamp for every message. Second, a calibration model — often built using Precision Time Protocol offsets — that estimates per-venue clock drift on a rolling basis throughout the session. Third, a normalisation function that adjusts all upstream timestamps before events enter the signal engine. Traders who skip layer two assume drift is constant. It isn't — temperature, network load, and NTP resync events all shift it. For deeper context on how latency affects execution quality, Investopedia's latency explainer is worth a read, and the mechanics of how fragmentation across venues creates these problems trace back to Chi-X Australia's original market structure design.

Today's takeaway: pull the last 30 days of dual-listed tick data for any liquid ASX/Cboe name and calculate the distribution of apparent quote inversions between venues. If more than 0.5% of cross-venue events appear temporally inverted, your normalisation layer needs work before you trust any cross-venue signal.

Bad timestamps don't announce themselves — they just make your edge disappear quietly, one microsecond at a time.

This content is for educational purposes only and does not constitute financial product advice. Past performance is not indicative of future results. Profit Logic Ltd (ACN 688 669 936) accepts no responsibility for errors or omissions in this content or anywhere on this website. Always seek advice from a licensed financial adviser before making investment decisions.