Network Time Protocol
Subject: Computer and Technology noun /ˈnɛt.wɜːrk ˈtaɪm ˈproʊ.təˌkɔːl/ 1 definition
- computer-networking
- network-protocols
- time-synchronization
- distributed-systems
-
Definition (noun)
Entry #165 · UpdatedThe Network Time Protocol (NTP) is a networking protocol that synchronizes computer system clocks across variable-latency, packet-switched networks to Coordinated Universal Time (UTC). Operating over UDP port 123, it arranges time sources into a hierarchical stratum topology where clients exchange timestamped messages to measure round-trip network delay, filter timing jitter, and gradually adjust local clock rates to offset oscillator drift. Unlike hardware-assisted standards such as the Precision Time Protocol (PTP) designed for sub-microsecond synchronization on specialized local networks, NTP runs in software over general-purpose IP networks to deliver millisecond accuracy over the public internet and sub-millisecond precision on local area networks.
Common Forms
Standard NTP (NTPv4): The full protocol specification used by servers and workstations, applying statistical clock-filtering algorithms and continuous rate adjustments to track drift and maintain long-term stability.
Simple Network Time Protocol (SNTP): A lightweight, packet-compatible subset of NTP that omits stateful drift modeling and multi-source filtering, making it well-suited for microcontrollers, IoT devices, and basic clients.
Symmetric and Broadcast Modes: Association variants where equal-stratum servers synchronize mutually as backup peers for redundancy, or a single server periodically transmits timestamps via broadcast or multicast to scale across large local subnets.
Network Time Security (NTS): A cryptographic extension that establishes session keys over TLS and authenticates timing packets, protecting NTP clients against spoofing and man-in-the-middle clock manipulation.
Example
A regional payment-processing cluster runs
chronydon each host to poll three local Stratum 1 NTP servers over UDP port 123, holding clock skew within 0.5 milliseconds of UTC. This continuous synchronization preserves accurate event ordering across distributed audit logs and prevents short-lived authentication tokens from failing validation due to clock drift.