NTPsec

ntp2.wiktel.com

Report generated: Tue May 20 03:53:02 2025 UTC
Start Time: Mon May 19 03:53:01 2025 UTC
End Time: Tue May 20 03:53:01 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 -18.115 -7.973 -4.750 0.380 3.008 4.457 9.123 7.758 12.430 2.350 -0.006 µs -5.377 19.23
Local Clock Frequency Offset -13.255 -13.201 -13.162 -12.816 -12.560 -12.525 -12.504 0.602 0.677 0.211 -12.859 ppm -2.368e+05 1.466e+07

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.454 0.991 1.308 2.640 4.656 5.852 8.976 3.348 4.861 1.056 2.770 µs 9.977 32.31

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 0.794 1.617 2.143 4.150 7.113 8.678 12.859 4.970 7.061 1.553 4.321 ppb 11.71 37.73

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 -18.115 -7.973 -4.750 0.380 3.008 4.457 9.123 7.758 12.430 2.350 -0.006 µs -5.377 19.23

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.130 -1.127 -1.116 -1.076 -1.046 -1.029 -1.022 0.070 0.098 0.021 -1.078 ms -1.458e+05 7.681e+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.229

peer offset 132.246.11.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.229 -880.584 -851.449 -818.437 -760.129 -694.207 -632.428 -601.322 124.230 219.021 36.608 -759.826 µs -1.036e+04 2.268e+05

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 -66.573 -52.045 -30.465 -5.693 22.782 30.594 45.108 53.247 82.639 16.137 -6.000 µs -6.889 19.66

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 -909.848 -907.389 -903.484 -893.177 -882.645 -876.271 -873.804 20.839 31.118 6.167 -892.841 µs -3.098e+06 4.517e+08

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) -367.210 -363.303 -357.632 -339.881 -322.717 -317.807 -316.568 34.915 45.496 10.067 -340.176 µs -4.222e+04 1.473e+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 2606:4700:f1::1 (time.cloudflare.com)

peer offset 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -410.101 -410.101 -364.933 -264.949 -192.410 -133.744 -133.744 172.523 276.357 47.483 -268.703 µs -315.5 2244

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) -518.627 -515.019 -499.574 -428.438 -228.538 -193.666 -190.356 271.036 321.353 77.630 -405.693 µs -258.8 1708

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 698.625 719.394 738.387 779.976 814.973 838.713 845.740 76.586 119.319 24.262 778.321 µs 3.011e+04 9.388e+05

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) -178.210 -167.300 -117.037 -15.560 38.876 61.406 85.965 155.913 228.706 43.492 -20.717 µs -8.587 28.1

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) -18.116 -7.974 -4.751 0.381 3.009 4.458 9.124 7.760 12.432 2.351 -0.006 µs -5.376 19.22

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.294 14.888 19.096 36.636 60.602 544.361 549.204 41.506 529.473 65.866 45.740 µs 6.228 45.99

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.229

peer jitter 132.246.11.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.229 51.292 63.522 83.001 187.079 643.550 953.140 2,051.252 560.549 889.618 219.657 255.509 µs 4.814 35.27

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.130 2.662 3.560 7.900 19.769 120.391 121.823 16.209 117.729 15.191 10.997 µs 5.483 38.81

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 4.645 5.107 6.122 9.725 17.088 21.132 21.878 10.966 16.025 3.350 10.369 µs 16.39 56.86

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) 3.376 5.132 7.941 18.892 37.467 444.471 457.097 29.526 439.339 68.384 30.637 µs 3.89 23.42

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::1 (time.cloudflare.com)

peer jitter 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 3.655 3.655 6.308 14.002 71.680 126.108 126.108 65.372 122.453 22.980 22.936 µs 2.488 9.948

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) 3.491 3.870 7.541 16.899 56.353 132.177 139.711 48.812 128.307 20.048 21.973 µs 3.818 19.09

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 0.012 0.013 0.017 0.036 0.085 1.018 1.702 0.069 1.004 0.156 0.065 ms 4.979 43.76

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) 7.925 9.270 12.628 25.668 77.196 104.908 112.343 64.568 95.638 18.215 30.742 µs 4.424 16.14

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.118 0.470 0.775 2.423 6.206 8.685 17.406 5.431 8.215 1.763 2.796 µs 3.524 12.9

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.255 -13.201 -13.162 -12.816 -12.560 -12.525 -12.504 0.602 0.677 0.211 -12.859 ppm -2.368e+05 1.466e+07
Local Clock Time Offset -18.115 -7.973 -4.750 0.380 3.008 4.457 9.123 7.758 12.430 2.350 -0.006 µs -5.377 19.23
Local RMS Frequency Jitter 0.794 1.617 2.143 4.150 7.113 8.678 12.859 4.970 7.061 1.553 4.321 ppb 11.71 37.73
Local RMS Time Jitter 0.454 0.991 1.308 2.640 4.656 5.852 8.976 3.348 4.861 1.056 2.770 µs 9.977 32.31
Server Jitter 132.163.97.5 10.294 14.888 19.096 36.636 60.602 544.361 549.204 41.506 529.473 65.866 45.740 µs 6.228 45.99
Server Jitter 132.246.11.229 51.292 63.522 83.001 187.079 643.550 953.140 2,051.252 560.549 889.618 219.657 255.509 µs 4.814 35.27
Server Jitter 134.84.84.84 2.130 2.662 3.560 7.900 19.769 120.391 121.823 16.209 117.729 15.191 10.997 µs 5.483 38.81
Server Jitter 204.9.54.119 4.645 5.107 6.122 9.725 17.088 21.132 21.878 10.966 16.025 3.350 10.369 µs 16.39 56.86
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 3.376 5.132 7.941 18.892 37.467 444.471 457.097 29.526 439.339 68.384 30.637 µs 3.89 23.42
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 3.655 3.655 6.308 14.002 71.680 126.108 126.108 65.372 122.453 22.980 22.936 µs 2.488 9.948
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 3.491 3.870 7.541 16.899 56.353 132.177 139.711 48.812 128.307 20.048 21.973 µs 3.818 19.09
Server Jitter 2607:f128::50 0.012 0.013 0.017 0.036 0.085 1.018 1.702 0.069 1.004 0.156 0.065 ms 4.979 43.76
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 7.925 9.270 12.628 25.668 77.196 104.908 112.343 64.568 95.638 18.215 30.742 µs 4.424 16.14
Server Jitter SHM(1) 0.118 0.470 0.775 2.423 6.206 8.685 17.406 5.431 8.215 1.763 2.796 µs 3.524 12.9
Server Offset 132.163.97.5 -1.130 -1.127 -1.116 -1.076 -1.046 -1.029 -1.022 0.070 0.098 0.021 -1.078 ms -1.458e+05 7.681e+06
Server Offset 132.246.11.229 -880.584 -851.449 -818.437 -760.129 -694.207 -632.428 -601.322 124.230 219.021 36.608 -759.826 µs -1.036e+04 2.268e+05
Server Offset 134.84.84.84 -66.573 -52.045 -30.465 -5.693 22.782 30.594 45.108 53.247 82.639 16.137 -6.000 µs -6.889 19.66
Server Offset 204.9.54.119 -909.848 -907.389 -903.484 -893.177 -882.645 -876.271 -873.804 20.839 31.118 6.167 -892.841 µs -3.098e+06 4.517e+08
Server Offset 2600:2600::99 (ntp1.wiktel.com) -367.210 -363.303 -357.632 -339.881 -322.717 -317.807 -316.568 34.915 45.496 10.067 -340.176 µs -4.222e+04 1.473e+06
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -410.101 -410.101 -364.933 -264.949 -192.410 -133.744 -133.744 172.523 276.357 47.483 -268.703 µs -315.5 2244
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -518.627 -515.019 -499.574 -428.438 -228.538 -193.666 -190.356 271.036 321.353 77.630 -405.693 µs -258.8 1708
Server Offset 2607:f128::50 698.625 719.394 738.387 779.976 814.973 838.713 845.740 76.586 119.319 24.262 778.321 µs 3.011e+04 9.388e+05
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -178.210 -167.300 -117.037 -15.560 38.876 61.406 85.965 155.913 228.706 43.492 -20.717 µs -8.587 28.1
Server Offset SHM(1) -18.116 -7.974 -4.751 0.381 3.009 4.458 9.124 7.760 12.432 2.351 -0.006 µs -5.376 19.22
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!