NTP: Clock Synchronization and Packet Timestamps
Network Time Protocol exchanges timestamps so systems can estimate clock offset and network delay. A response is an input to clock discipline, not proof that the local clock is correct.
Updated · Editorial approach and simulation limits
Four timestamps describe one time exchange
An NTP client records the local transmit time, the server records its receive and transmit times, and the client records the response arrival time. With these values, the client estimates round-trip delay and clock offset, subject to assumptions about path symmetry and timestamp quality.
The packet fields also include mode, leap indicator, version, stratum, poll interval and precision. In client-server mode the response corresponds to a request; association state and repeated samples matter more than a single packet when evaluating clock behavior.
Stratum describes distance from a reference
Stratum numbers describe the server’s position in the synchronization hierarchy. A lower stratum is closer to a reference source, but it does not guarantee lower error or better service for every client. Network delay, server quality, local oscillator behavior and filtering all affect the result.
NTP clients sample peers over time and discipline their local clocks gradually. A clock that jumps or drifts can result from bad source selection, asymmetric routing, poor timestamps or system policy even when individual packets appear valid.
Use timestamps with care in packet captures
Capture timestamps are made by the observing device and can use a different clock from the NTP client or server. They are useful for ordering and approximate latency, but should not be substituted for the NTP message’s own timestamp fields without checking clock source and capture accuracy.
NTP is commonly carried over UDP. Firewalls, captive networks and incorrect system time can affect access to time servers; accurate time can also matter when validating TLS certificates. Protocol Explorer shows a simplified exchange rather than measuring a real clock.
Explore NTP interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 5905: Network Time Protocol Version 4. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all network protocols · Read packet timestamps without mixing clock sources