Welcome to Paryana Automation.

Leap Second Support in ntpd for Windows Even in Windows 10 there is still no leap second support in the Windows kernel, so ntpd has another built-in workaround to handle this. To insert a leap second, the approach is to reduce the timer tick value for an interval of 2 seconds such that the Windows system time increases only "half speed", so after 2 real seconds have passed the system time has only gained one second, and thus is aligned again with the UTC time after the inserted leap second.

Accuracy Determining Factors on the Network Whenever a network packet is sent from one application running on one node to another application running on a different node the network packet has to traverse a path which includes quite a number of unknown delays or latencies: All the yellow lines indicate unknown processing delays. If the packet has to go through a switch, but the output port is just busy with a different packet (red lines) then the packet is delayed. Also different link speeds on the 2 involved switch ports cause an asymmetry of the packet delay which results in a time offset. Unfortunately there are only switches available which support this for PTP, but there are no switches which support this for NTP. On the other hand, even if hardware time stamping of NTP packets was supported the current version of the NTP protocol doesn't even provide a proper way to forward the measured delays. The reference implementation of the NTP protocol, ntpd, can yield pretty goo...