Protocols
Saved & recent

NTP

Also called: Network Time Protocol, NTPv4, network clock synchronization

Network Time Protocol estimates how a computer’s clock differs from time sources and helps adjust it. An exchange uses four timestamps: client send, server receive, server send, and client receive. Together they estimate clock offset and network round-trip delay while accounting for the time spent processing the request at the server.

For example, servers can synchronize clocks so logs from different machines are easier to compare. Repeated measurements and clock-selection algorithms improve the estimate, but unequal delays in the two directions introduce uncertainty. NTP does not discover exact time by simply halving a round trip, and synchronized timestamps alone cannot prove the causal order of closely spaced events.

Related
PTP, Syslog, UDP
Further reading
RFC 5905 — Network Time Protocol Version 4: Protocol and Algorithms Specification
client clock server clock T1 = 0 ms T2 = 15 ms T3 = 16 ms T4 = 21 ms request reply 1 ms processing offset estimate: +5 ms network round trip: 20 ms assuming symmetric network paths
Illustrative clock readings T1=0, T2=15, T3=16 and T4=21 milliseconds give an estimated server offset of +5 ms and a 20 ms network round trip after subtracting 1 ms server processing. The offset assumes symmetric path delays; the timeline spacing is schematic.

View in the full Protocols collection