NTPsec

A-ntpsec-12-hour-stats

Report generated: Thu Apr 2 03:01:50 2020 UTC
Start Time: Wed Apr 1 15:01:49 2020 UTC
End Time: Thu Apr 2 03:01:49 2020 UTC
Report published: Wed Apr 01 20:01:56 2020 PDT
Report Period: 0.5 days

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 -2.086 -1.588 -1.193 -0.398 0.334 0.622 0.889 1.527 2.210 0.477 -0.411 µs -12.22 37.06
Local Clock Frequency Offset -877.884 -877.289 -876.068 -785.110 -614.594 -608.047 -604.065 261.474 269.242 92.760 -761.066 ppb -807.2 7677

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 288.000 347.000 390.000 507.000 647.000 710.000 801.000 257.000 363.000 78.497 510.085 ns 183 1104

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 64.000 76.000 88.000 137.000 236.000 354.000 407.000 148.000 278.000 49.343 146.158 10e-12 15.11 58.47

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 -2.086 -1.588 -1.193 -0.398 0.334 0.622 0.889 1.527 2.210 0.477 -0.411 µs -12.22 37.06

The clock offsets of the local clock as a histogram.

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



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -877.884 -877.289 -876.068 -785.110 -614.594 -608.047 -604.065 261.474 269.242 92.760 -761.066 ppb -807.2 7677
Temp ZONE0 62.300 62.300 62.300 63.914 64.990 64.990 65.528 2.690 2.690 0.846 63.750 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats 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 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 1.683 1.683 2.097 2.585 3.584 3.775 3.775 1.487 2.092 0.495 2.680 ms 99.62 505.6

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 137.190.2.4

peer offset 137.190.2.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 137.190.2.4 -6.027 -2.405 0.643 1.091 1.612 1.704 1.708 0.968 4.109 0.728 1.037 ms -5.873 55.11

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 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 -10.271 -10.271 -5.140 4.801 12.370 13.441 13.441 17.510 23.712 4.162 5.110 ms -0.4824 5.869

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 192.168.1.11

peer offset 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.11 -74.421 -55.989 -35.095 4.272 49.023 63.226 69.272 84.118 119.215 24.790 6.150 µs -2.694 7.061

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 192.168.1.12

peer offset 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.12 -113.428 -41.448 -2.534 39.167 71.724 84.495 185.042 74.258 125.943 25.681 37.892 µs 0.8671 7.488

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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 -2.238 -2.209 -2.050 -1.387 0.722 0.828 0.913 2.772 3.037 1.071 -0.880 ms -11.1 29.37

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

peer offset 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.24 1.252 1.291 1.495 1.993 2.588 2.785 2.829 1.093 1.494 0.318 2.018 ms 168.4 988.9

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 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 1.694 1.859 2.163 2.560 3.048 3.401 3.425 0.885 1.542 0.280 2.571 ms 569.7 4864

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 216.218.254.202

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.254.202 2.098 2.143 2.277 2.651 3.215 3.827 3.892 0.938 1.684 0.304 2.710 ms 521.5 4347

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(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -69.561 -59.381 -56.914 -50.269 -45.738 -44.135 -42.161 11.177 15.245 3.367 -50.613 ms -4170 6.765e+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 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) -2.087 -1.589 -1.194 -0.399 0.335 0.623 0.890 1.529 2.212 0.478 -0.412 µs -12.22 37.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 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 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.506 0.506 0.717 1.879 4.541 9.500 9.500 3.824 8.994 1.495 2.214 ms 4.593 22.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 137.190.2.4

peer jitter 137.190.2.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 137.190.2.4 0.329 0.381 0.615 1.895 8.972 17.270 17.433 8.357 16.889 2.732 2.762 ms 2.88 13.47

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 178.62.68.79

peer jitter 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.62.68.79 0.529 0.529 0.767 4.698 19.430 19.446 19.446 18.663 18.918 5.190 6.314 ms 1.864 4.799

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 192.168.1.11

peer jitter 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.11 0.012 0.015 0.026 0.127 8.624 8.694 12.448 8.598 8.680 2.745 1.365 ms 0.4789 3.341

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 192.168.1.12

peer jitter 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.12 0.010 0.024 0.046 0.127 8.647 10.245 22.927 8.602 10.221 2.731 1.270 ms 1.087 8.475

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 203.123.48.219

peer jitter 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 203.123.48.219 0.216 0.448 0.647 2.888 10.125 12.323 12.335 9.479 11.876 3.060 4.056 ms 1.975 4.664

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

peer jitter 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.24 0.302 0.493 0.782 2.659 10.566 16.190 16.285 9.784 15.698 3.451 3.947 ms 1.943 5.842

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 216.218.192.202

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.298 0.437 0.824 2.828 9.405 10.913 10.981 8.581 10.476 2.758 3.699 ms 2.223 5.591

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 216.218.254.202

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.254.202 0.375 0.379 0.794 2.143 9.512 10.439 10.492 8.719 10.059 2.473 3.038 ms 2.401 6.94

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(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.088 0.295 0.439 1.114 3.156 5.898 14.337 2.717 5.603 1.086 1.459 ms 3.575 17.88

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.129 0.242 0.299 0.499 0.850 1.029 1.378 0.551 0.787 0.174 0.530 µs 15.48 52.7

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 -877.884 -877.289 -876.068 -785.110 -614.594 -608.047 -604.065 261.474 269.242 92.760 -761.066 ppb -807.2 7677
Local Clock Time Offset -2.086 -1.588 -1.193 -0.398 0.334 0.622 0.889 1.527 2.210 0.477 -0.411 µs -12.22 37.06
Local RMS Frequency Jitter 64.000 76.000 88.000 137.000 236.000 354.000 407.000 148.000 278.000 49.343 146.158 10e-12 15.11 58.47
Local RMS Time Jitter 288.000 347.000 390.000 507.000 647.000 710.000 801.000 257.000 363.000 78.497 510.085 ns 183 1104
Server Jitter 104.131.155.175 0.506 0.506 0.717 1.879 4.541 9.500 9.500 3.824 8.994 1.495 2.214 ms 4.593 22.19
Server Jitter 137.190.2.4 0.329 0.381 0.615 1.895 8.972 17.270 17.433 8.357 16.889 2.732 2.762 ms 2.88 13.47
Server Jitter 178.62.68.79 0.529 0.529 0.767 4.698 19.430 19.446 19.446 18.663 18.918 5.190 6.314 ms 1.864 4.799
Server Jitter 192.168.1.11 0.012 0.015 0.026 0.127 8.624 8.694 12.448 8.598 8.680 2.745 1.365 ms 0.4789 3.341
Server Jitter 192.168.1.12 0.010 0.024 0.046 0.127 8.647 10.245 22.927 8.602 10.221 2.731 1.270 ms 1.087 8.475
Server Jitter 203.123.48.219 0.216 0.448 0.647 2.888 10.125 12.323 12.335 9.479 11.876 3.060 4.056 ms 1.975 4.664
Server Jitter 204.17.205.24 0.302 0.493 0.782 2.659 10.566 16.190 16.285 9.784 15.698 3.451 3.947 ms 1.943 5.842
Server Jitter 216.218.192.202 0.298 0.437 0.824 2.828 9.405 10.913 10.981 8.581 10.476 2.758 3.699 ms 2.223 5.591
Server Jitter 216.218.254.202 0.375 0.379 0.794 2.143 9.512 10.439 10.492 8.719 10.059 2.473 3.038 ms 2.401 6.94
Server Jitter SHM(0) 0.088 0.295 0.439 1.114 3.156 5.898 14.337 2.717 5.603 1.086 1.459 ms 3.575 17.88
Server Jitter SHM(1) 0.129 0.242 0.299 0.499 0.850 1.029 1.378 0.551 0.787 0.174 0.530 µs 15.48 52.7
Server Offset 104.131.155.175 1.683 1.683 2.097 2.585 3.584 3.775 3.775 1.487 2.092 0.495 2.680 ms 99.62 505.6
Server Offset 137.190.2.4 -6.027 -2.405 0.643 1.091 1.612 1.704 1.708 0.968 4.109 0.728 1.037 ms -5.873 55.11
Server Offset 178.62.68.79 -10.271 -10.271 -5.140 4.801 12.370 13.441 13.441 17.510 23.712 4.162 5.110 ms -0.4824 5.869
Server Offset 192.168.1.11 -74.421 -55.989 -35.095 4.272 49.023 63.226 69.272 84.118 119.215 24.790 6.150 µs -2.694 7.061
Server Offset 192.168.1.12 -113.428 -41.448 -2.534 39.167 71.724 84.495 185.042 74.258 125.943 25.681 37.892 µs 0.8671 7.488
Server Offset 203.123.48.219 -2.238 -2.209 -2.050 -1.387 0.722 0.828 0.913 2.772 3.037 1.071 -0.880 ms -11.1 29.37
Server Offset 204.17.205.24 1.252 1.291 1.495 1.993 2.588 2.785 2.829 1.093 1.494 0.318 2.018 ms 168.4 988.9
Server Offset 216.218.192.202 1.694 1.859 2.163 2.560 3.048 3.401 3.425 0.885 1.542 0.280 2.571 ms 569.7 4864
Server Offset 216.218.254.202 2.098 2.143 2.277 2.651 3.215 3.827 3.892 0.938 1.684 0.304 2.710 ms 521.5 4347
Server Offset SHM(0) -69.561 -59.381 -56.914 -50.269 -45.738 -44.135 -42.161 11.177 15.245 3.367 -50.613 ms -4170 6.765e+04
Server Offset SHM(1) -2.087 -1.589 -1.194 -0.399 0.335 0.623 0.890 1.529 2.212 0.478 -0.412 µs -12.22 37.04
Temp ZONE0 62.300 62.300 62.300 63.914 64.990 64.990 65.528 2.690 2.690 0.846 63.750 °C
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!