NTPsec

ntp2.wiktel.com

Report generated: Mon Sep 1 08:53:01 2025 UTC
Start Time: Sun Aug 31 08:53:00 2025 UTC
End Time: Mon Sep 1 08:53:00 2025 UTC
Report Period: 1.0 days

Top   Daily Stats   Weekly Stats  

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -83.935 -10.003 -6.416 0.675 3.563 4.854 23.985 9.979 14.857 3.043 -0.001 µs -5.943 34.42
Local Clock Frequency Offset -13.239 -13.097 -13.078 -13.014 -12.940 -12.920 -12.887 0.138 0.178 0.042 -13.013 ppm -2.978e+07 9.232e+09

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 0.860 1.577 2.003 3.735 6.186 7.542 43.053 4.183 5.965 1.393 3.876 µs 14.26 114.6

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 1.400 2.314 2.988 5.443 8.813 10.782 58.560 5.825 8.468 1.950 5.621 ppb 15.85 129.7

The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.

Lower is better. An ideal clock would be a horizontal line at 0ppm.

RMS Frequency Jitter is field 6 in the loopstats log file.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -83.935 -10.003 -6.416 0.675 3.563 4.854 23.985 9.979 14.857 3.043 -0.001 µs -5.943 34.42

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 132.163.97.5

peer offset 132.163.97.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.163.97.5 -1.100 -1.095 -1.083 -1.050 -1.014 -0.998 -0.991 0.069 0.096 0.021 -1.049 ms -1.27e+05 6.387e+06

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 132.246.11.237

peer offset 132.246.11.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.237 -194.342 -180.180 -169.098 -147.084 -124.552 -113.733 -108.368 44.546 66.447 13.363 -148.011 µs -1797 2.214e+04

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 134.84.84.84

peer offset 134.84.84.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 134.84.84.84 -53.711 -52.042 -33.958 -11.199 14.229 30.560 31.776 48.187 82.602 14.453 -10.767 µs -10.45 30.77

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 204.9.54.119

peer offset 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.9.54.119 -1.043 -1.040 -1.037 -1.030 -1.020 -1.015 -1.011 0.016 0.025 0.005 -1.029 ms -8.077e+06 1.621e+09

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2600:2600::99 (ntp1.wiktel.com)

peer offset 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:2600::99 (ntp1.wiktel.com) -376.007 -369.529 -362.039 -343.734 -326.440 -319.734 -313.123 35.599 49.795 10.401 -344.335 µs -3.978e+04 1.36e+06

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca)

peer offset 2602:fd53:11e:123::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -77.019 -68.683 -53.806 -25.844 2.143 19.235 28.231 55.949 87.918 17.356 -25.971 µs -23.02 79.29

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:4700:f1::123 (time.cloudflare.com)

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 37.681 129.102 220.586 357.255 466.591 561.193 666.760 246.005 432.091 83.198 353.268 µs 43.83 176.8

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f128::50

peer offset 2607:f128::50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f128::50 -238.889 -233.786 -210.892 -177.687 -145.792 -126.703 -123.862 65.100 107.083 19.475 -178.408 µs -1080 1.129e+04

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu)

peer offset 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -118.585 -111.673 -91.974 -34.863 2.012 17.040 28.353 93.986 128.713 27.629 -37.250 µs -20.57 72.13

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -83.936 -10.004 -6.417 0.676 3.564 4.855 23.986 9.981 14.859 3.044 -0.000 µs -5.942 34.41

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 132.163.97.5

peer jitter 132.163.97.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.163.97.5 10.440 13.648 16.768 33.955 60.207 72.888 86.146 43.439 59.240 13.578 36.211 µs 10.31 32.19

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 132.246.11.237

peer jitter 132.246.11.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.237 9.352 11.377 14.621 30.076 145.432 999.990 1,397.995 130.811 988.613 117.286 52.329 µs 7.001 70.83

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 134.84.84.84

peer jitter 134.84.84.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 134.84.84.84 2.588 2.829 3.659 7.648 16.855 23.742 25.426 13.196 20.913 4.137 8.595 µs 5.767 18.85

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.9.54.119

peer jitter 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.9.54.119 3.780 3.916 4.880 9.151 16.220 18.716 19.324 11.340 14.800 3.230 9.656 µs 14.5 47.77

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:2600::99 (ntp1.wiktel.com)

peer jitter 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 6.268 7.560 9.970 20.900 39.785 447.255 451.236 29.815 439.695 62.264 31.146 µs 4.601 29.92

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca)

peer jitter 2602:fd53:11e:123::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 7.656 10.619 12.288 24.292 50.555 201.722 204.469 38.267 191.103 21.178 28.516 µs 7.152 58.74

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2606:4700:f1::123 (time.cloudflare.com)

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 6.356 7.016 12.313 33.800 140.300 189.816 198.261 127.987 182.800 41.411 49.338 µs 2.126 6.332

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f128::50

peer jitter 2607:f128::50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f128::50 8.678 10.224 14.815 27.638 62.781 937.355 1,474.480 47.966 927.131 115.906 44.241 µs 7.605 82.62

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu)

peer jitter 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 5.585 8.928 11.349 22.986 69.466 105.419 114.222 58.117 96.491 18.307 27.994 µs 4.041 15.59

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.224 0.733 1.113 3.375 7.927 10.990 81.889 6.814 10.257 2.272 3.795 µs 5.146 58.89

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -13.239 -13.097 -13.078 -13.014 -12.940 -12.920 -12.887 0.138 0.178 0.042 -13.013 ppm -2.978e+07 9.232e+09
Local Clock Time Offset -83.935 -10.003 -6.416 0.675 3.563 4.854 23.985 9.979 14.857 3.043 -0.001 µs -5.943 34.42
Local RMS Frequency Jitter 1.400 2.314 2.988 5.443 8.813 10.782 58.560 5.825 8.468 1.950 5.621 ppb 15.85 129.7
Local RMS Time Jitter 0.860 1.577 2.003 3.735 6.186 7.542 43.053 4.183 5.965 1.393 3.876 µs 14.26 114.6
Server Jitter 132.163.97.5 10.440 13.648 16.768 33.955 60.207 72.888 86.146 43.439 59.240 13.578 36.211 µs 10.31 32.19
Server Jitter 132.246.11.237 9.352 11.377 14.621 30.076 145.432 999.990 1,397.995 130.811 988.613 117.286 52.329 µs 7.001 70.83
Server Jitter 134.84.84.84 2.588 2.829 3.659 7.648 16.855 23.742 25.426 13.196 20.913 4.137 8.595 µs 5.767 18.85
Server Jitter 204.9.54.119 3.780 3.916 4.880 9.151 16.220 18.716 19.324 11.340 14.800 3.230 9.656 µs 14.5 47.77
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 6.268 7.560 9.970 20.900 39.785 447.255 451.236 29.815 439.695 62.264 31.146 µs 4.601 29.92
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 7.656 10.619 12.288 24.292 50.555 201.722 204.469 38.267 191.103 21.178 28.516 µs 7.152 58.74
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 6.356 7.016 12.313 33.800 140.300 189.816 198.261 127.987 182.800 41.411 49.338 µs 2.126 6.332
Server Jitter 2607:f128::50 8.678 10.224 14.815 27.638 62.781 937.355 1,474.480 47.966 927.131 115.906 44.241 µs 7.605 82.62
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 5.585 8.928 11.349 22.986 69.466 105.419 114.222 58.117 96.491 18.307 27.994 µs 4.041 15.59
Server Jitter SHM(1) 0.224 0.733 1.113 3.375 7.927 10.990 81.889 6.814 10.257 2.272 3.795 µs 5.146 58.89
Server Offset 132.163.97.5 -1.100 -1.095 -1.083 -1.050 -1.014 -0.998 -0.991 0.069 0.096 0.021 -1.049 ms -1.27e+05 6.387e+06
Server Offset 132.246.11.237 -194.342 -180.180 -169.098 -147.084 -124.552 -113.733 -108.368 44.546 66.447 13.363 -148.011 µs -1797 2.214e+04
Server Offset 134.84.84.84 -53.711 -52.042 -33.958 -11.199 14.229 30.560 31.776 48.187 82.602 14.453 -10.767 µs -10.45 30.77
Server Offset 204.9.54.119 -1.043 -1.040 -1.037 -1.030 -1.020 -1.015 -1.011 0.016 0.025 0.005 -1.029 ms -8.077e+06 1.621e+09
Server Offset 2600:2600::99 (ntp1.wiktel.com) -376.007 -369.529 -362.039 -343.734 -326.440 -319.734 -313.123 35.599 49.795 10.401 -344.335 µs -3.978e+04 1.36e+06
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -77.019 -68.683 -53.806 -25.844 2.143 19.235 28.231 55.949 87.918 17.356 -25.971 µs -23.02 79.29
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 37.681 129.102 220.586 357.255 466.591 561.193 666.760 246.005 432.091 83.198 353.268 µs 43.83 176.8
Server Offset 2607:f128::50 -238.889 -233.786 -210.892 -177.687 -145.792 -126.703 -123.862 65.100 107.083 19.475 -178.408 µs -1080 1.129e+04
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -118.585 -111.673 -91.974 -34.863 2.012 17.040 28.353 93.986 128.713 27.629 -37.250 µs -20.57 72.13
Server Offset SHM(1) -83.936 -10.004 -6.417 0.676 3.564 4.855 23.986 9.981 14.859 3.044 -0.000 µs -5.942 34.41
Summary as CSV file


Glossary:

frequency offset:
The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
jitter, dispersion:
The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Server Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of kurtosis. A normal distribution has a kurtosis of three. NIST describes a kurtosis over three as "heavy tailed" and one under three as "light tailed".
ms, millisecond:
One thousandth of a second = 0.001 seconds, 1e-3 seconds
mu, mean:
The arithmetic mean: the sum of all the values divided by the number of values. The formula for mu is: "mu = (∑xi) / N". Where xi denotes the data points and N is the number of data points.
ns, nanosecond:
One billionth of a second, also one thousandth of a microsecond, 0.000000001 seconds and 1e-9 seconds.
percentile:
The value below which a given percentage of values fall.
ppb, parts per billion:
Ratio between two values. These following are all the same: 1 ppb, one in one billion, 1/1,000,000,000, 0.000,000,001, 1e-9 and 0.000,000,1%
ppm, parts per million:
Ratio between two values. These following are all the same: 1 ppm, one in one million, 1/1,000,000, 0.000,001, and 0.000,1%
‰, parts per thousand:
Ratio between two values. These following are all the same: 1 ‰. one in one thousand, 1/1,000, 0.001, and 0.1%
refclock:
Reference clock, a local GPS module or other local source of time.
remote clock:
Any clock reached over the network, LAN or WAN. Also called a peer or server.
time offset:
The difference between the ntpd calculated time and the local system clock's time. Also called phase offset.
σ, sigma:
Sigma denotes the standard deviation (SD) and is centered on the arithmetic mean of the data set. The SD is simply the square root of the variance of the data set. Two sigma is simply twice the standard deviation. Three sigma is three times sigma. Smaller is better.
The formula for sigma is: "σ = √[ ∑(xi-mu)^2 / N ]". Where xi denotes the data points and N is the number of data points.
skewness, Skew:
The skewness of a random variable X is the third standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
upstream clock:
Any server or reference clock used as a source of time.
µs, us, microsecond:
One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.



This page autogenerated by ntpviz, part of the NTPsec project
html 5    Valid CSS!