Clock offset and quote age: how to interpret timing data

A fast response can contain an old quote. Round-trip latency, clock offset and quote age describe different parts of a request. Mixing them can make a clock mismatch look like a delayed market feed.

Follow one request through time

Suppose a request leaves at 12:00:00.000 and returns at 12:00:00.200. The round trip is 200 ms and its local midpoint is 12:00:00.100. If the returned server time is 12:00:00.130, a midpoint estimate gives +30 ms. These are illustrative values, not measurements of a named venue.

Understand uncertainty before ranking

The server is not proven to be exactly 30 ms fast. Outbound and return paths can differ, processing takes time and timestamps may be generated at different stages. Half the round trip helps describe uncertainty in this simple estimate; it is not a universal precision limit for every clock-measurement method. This site uses lower-latency clock samples and a cross-venue median reference, which is a relative baseline rather than a certified UTC reference.

An older timestamp does not prove a worse execution price

Quote age combines the quote timestamp, receipt time and clock differences. Check whether the timestamp describes a trade, a snapshot or a message event. An old last trade on a quiet market does not necessarily mean a frozen API. Likewise, a fresh book does not promise that its orders remain available when your order arrives. Time differences alone cannot be converted into a monetary loss.

When an API rejects a timestamp

Check local time synchronization, timestamp units and the endpoint’s allowed request window. Do not adjust your clock solely from a cross-venue ranking. Shared movement across venues can suggest a reference-clock issue, but it does not prove which clock is wrong.

Check these in order

1. Confirm when the observation was collected.
2. Separate round-trip latency from quote age.
3. Read the timestamp definition and time unit.
4. Look for repeated behavior across multiple periods.
5. For real orders, verify account status and the venue’s response.

Related reading: How to compare funding rates: intervals, direction and position costs · How to read exchange API uptime and incident records · Market-order costs: trading fees, spread and average fill price

Rules and sources

Binance · Spot REST API · Measurement method · About this site

These examples are hypothetical, not live prices. Check venue rules and account records for actual charges or execution.