Communication

Say which clock a timestamp describes

Editorial edition · 16 November 2026

The idea

Arrival order is not necessarily event order. Devices can disconnect, clocks can drift and queues can delay publication. A timestamp without a defined meaning encourages readers to combine measurements that describe different moments in a process.

Design choice

Keep occurrence time and receipt time when both matter. Store an unambiguous timezone or UTC representation, and document the precision. A date-only business field should remain a date rather than acquiring an invented midnight timezone.

Worked example

A sensor records a reading at 10:00 and reconnects at 10:12. The analysis uses occurrence time; the delivery dashboard measures the twelve-minute arrival delay.

Before you ship

  • Name each timestamp by its meaning
  • Test delayed and out-of-order arrivals
  • Document precision and clock uncertainty

Examples are illustrative. Adapt the checks to your own environment.

Further reading

HTTP Semantics, RFC 9110

Search the library