Network Time Protocol is used to synchronize the clocks of computers on a network. How accurately it synchronizes the clocks of client computers depends on a number of factors. However, the following timings can be used as a guide:
- Public Internet NTP Servers: <10ms.
- Public Internet Servers over asymmetric connection (ADSL): <100ms.
- NTP Servers on a Local Area Network (LAN): <1ms.
Factors That Affect Timing
The accuracy to which NTP clients can synchronize their clocks to the correct time is dependent on a number of factors.
At the highest levels of the timing hierarchy, the accuracy of the root time source (Stratum 0) is important. At lower levels, the physical distance between client and server is a major factor.
Root Time Source
NTP servers rely on a source of accurate timing information, such as GPS satellites or long-wave radio broadcasts. The time source is referred to as a Stratum 0 reference. Typical accuracies of common timing references are as follows:
- Global Navigation Satellite System (GPS, Galileo, GLONASS): <50ns.
- Long wave radio time broadcasts (MSF, DCF, WWVB): <2ms.
Stratum Of Synchronizing Server
NTP implements a hierarchical system of time servers. Stratum denotes the hierarchy level of a server and represents the distance, or number of levels, between a server and the source reference clock.
At the highest level, Stratum 0 is a hardware reference clock, such as GPS or radio time sources.
Stratum 1 represents a NTP server with a hardware connection to a Stratum 0 clock.
For lower Stratum references, a server synchronized to a stratum N server automatically becomes stratum N+1. Stratum 2 servers synchronize stratum 3 servers, which in turn synchronize stratum 4 servers and so on.
The lower a server is in the stratum hierarchy, the further away it is from the root time source, the poorer accuracy becomes. Synchronizing to a higher stratum device, such as stratum 1, is best.
Asymmetric Networks
NTP incorporates complex algorithms to calculate network packet round-trip delays and latency in order to maintain accurate time. It assumes that network communication is symmetrical, i.e. that the transmission time of a packet is the same as the receive time.
NTP timing can be adversely affected by asymmetric networks, such as ADSL, where the transmit time is often much longer than the receive time.
Physical Distance
Accuracy degrades the further the signal distance of the synchronizing server is from the client. If using public Internet servers, choose one as close as possible to the location of the client. Preferably in the same country, possibly even the same city.
A GPS NTP server on local area network with low network congestion provides best results. In such circumstances, client synchronization to better than 1ms is achievable.
Network Congestion
Heavy network congestion can also adversely affect the client timing accuracy. A fast symmetric network with with plenty of spare bandwidth is best for timing.
Accurately synchronise the time on computers and network infrastructure in your organization with TimeTools TA310 GPS Network Time Server. The TA310 is designed and manufactured in the UK, and provides:
- Advanced, 92 Channel, GPS Receiver For Reliable Reception Of The GPS Satellite System.
- Security-Hardened, Enterprise-Class, Stratum-1 NTP v4 Network Time Server.
- Ultra-Fast, 50,000 NTP Polls Per Second (3M Per Minute), For Precise Client Synchronization.
- High-Stability, Temperature-Compensated Crystal Oscillator (TCXO) For Extended Stratum-1 Operation In The Event Of Any Loss of GPS Signal Lock.
- Network-Optimized Gigabit Ethernet (GbE).
- Powerful, Easy To Use, Web Interface With Command Line Interface For Advanced Users.
- CE and UKCA Compliant With Full EMC and Electrical Safety Test Reports.
| About Andrew Shinton Andrew Shinton is the joint founder and Managing Director of TimeTools Limited. He has a BSc (Hons) degree in Computer Science. Andrew has over 20 years experience of GPS systems and Network Time Protocol (NTP) in the Time and Frequency Industry. |