NTPsec

C-ntpsec-24-hour-stats

Report generated: Sun Sep 26 12:03:04 2021 UTC
Start Time: Sat Sep 25 12:03:03 2021 UTC
End Time: Sun Sep 26 12:03:03 2021 UTC
Report published: Sun Sep 26 05:03:11 2021 PDT
Report Period: 1.0 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 -1,545.000 -754.000 -563.000 -62.000 564.000 826.000 1,245.000 1,127.000 1,580.000 345.778 -41.407 ns -4.487 10.98
Local Clock Frequency Offset -4.964 -4.962 -4.951 -4.924 -4.858 -4.855 -4.854 0.093 0.107 0.033 -4.913 ppm -3.275e+06 4.864e+08

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 73.000 100.000 125.000 190.000 290.000 345.000 462.000 165.000 245.000 50.585 196.426 ns 33.44 132.9

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 27.000 35.000 42.000 75.000 145.000 206.000 313.000 103.000 171.000 34.595 82.534 10e-12 8.473 32.19

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 -1,545.000 -754.000 -563.000 -62.000 564.000 826.000 1,245.000 1,127.000 1,580.000 345.778 -41.407 ns -4.487 10.98

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 -4.964 -4.962 -4.951 -4.924 -4.858 -4.855 -4.854 0.093 0.107 0.033 -4.913 ppm -3.275e+06 4.864e+08
Temp ZONE0 57.996 57.996 58.534 59.072 60.148 60.148 60.686 1.614 2.152 0.606 59.200 °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.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 7.000 7.000 8.000 9.000 11.000 12.000 13.000 3.000 5.000 1.099 9.354 nSat 447.3 3545
TDOP 0.470 0.520 0.590 0.840 1.290 1.420 2.150 0.700 0.900 0.219 0.871 36.48 148.3

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



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 162.159.200.123

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 2.199 2.378 2.536 2.806 3.080 3.274 4.317 0.545 0.896 0.188 2.814 ms 2762 3.922e+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 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 -6.010 -5.864 -5.818 -5.615 -5.357 -5.238 -4.991 0.460 0.626 0.141 -5.605 ms -6.788e+04 2.772e+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 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -2.319 -1.193 -0.531 0.057 0.534 1.249 1.949 1.065 2.442 0.386 0.032 ms -3.768 18.46

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

peer offset 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.10 -254.349 -142.108 -58.568 90.646 217.425 312.278 422.711 275.993 454.386 86.152 86.384 µs -0.08236 3.751

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 194.58.202.211

peer offset 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.211 -16.258 -14.355 -9.804 5.442 8.872 9.115 15.034 18.676 23.470 5.301 4.743 ms -2.633 8.955

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 194.58.202.219

peer offset 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.219 -18.418 -13.545 -7.448 6.590 6.865 6.992 7.188 14.313 20.537 4.490 5.189 ms -2.705 10.36

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.226 2.391 2.586 2.866 4.475 4.643 4.888 1.888 2.252 0.767 3.311 ms 47.02 196.5

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.397 1.896 2.051 3.697 3.996 4.090 4.361 1.945 2.194 0.693 3.387 ms 69.07 302.4

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.321 2.383 2.434 2.625 2.851 2.962 3.950 0.417 0.579 0.153 2.633 ms 4271 6.997e+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 63.145.169.3

peer offset 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 63.145.169.3 -101.400 -99.945 -92.038 -67.892 0.876 2.896 3.450 92.914 102.841 24.055 -59.561 ms -51 203.2

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.390 -65.850 -63.009 -55.485 -48.630 -45.873 -43.501 14.380 19.978 4.365 -55.607 ms -2635 3.677e+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) -1,546.000 -755.000 -564.000 -63.000 565.000 827.000 1,246.000 1,129.000 1,582.000 346.540 -41.538 ns -4.488 10.97

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 162.159.200.123

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.168 0.215 0.275 1.001 20.655 74.790 75.527 20.380 74.575 10.249 5.020 ms 2.976 22.45

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 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 169.229.128.134 0.131 0.161 0.227 1.632 22.564 24.432 25.272 22.337 24.271 7.537 5.752 ms 0.6006 2.325

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 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.311 0.366 0.738 1.872 20.497 22.699 27.568 19.759 22.333 6.602 5.649 ms 0.8937 2.839

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

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 0.066 0.095 0.148 0.659 20.283 23.265 24.826 20.135 23.171 6.731 4.876 ms 0.5227 2.605

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 194.58.202.211

peer jitter 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.211 0.127 0.189 0.283 1.725 19.558 23.257 25.362 19.275 23.068 6.650 5.622 ms 0.7831 2.647

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 194.58.202.219

peer jitter 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.219 0.114 0.161 0.238 1.506 20.104 28.895 30.250 19.866 28.734 6.696 5.429 ms 0.853 3.41

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.117 0.157 0.284 1.182 20.307 23.093 47.427 20.023 22.936 7.017 4.648 ms 1.458 8.837

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.127 0.158 0.298 1.668 22.989 23.721 50.504 22.691 23.563 7.999 6.509 ms 0.8552 4.296

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.142 0.157 0.273 2.087 20.383 23.122 27.919 20.110 22.966 6.735 5.668 ms 0.7814 2.606

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 63.145.169.3

peer jitter 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 63.145.169.3 1.047 1.591 2.998 17.863 67.366 85.054 95.179 64.368 83.462 19.317 23.258 ms 2.078 6.052

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.068 0.213 0.352 0.988 3.144 5.828 8.832 2.792 5.615 1.028 1.269 ms 3.433 15.71

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) 41.000 70.000 105.000 229.000 516.000 673.000 1,565.000 411.000 603.000 131.336 259.413 ns 5.335 19.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -4.964 -4.962 -4.951 -4.924 -4.858 -4.855 -4.854 0.093 0.107 0.033 -4.913 ppm -3.275e+06 4.864e+08
Local Clock Time Offset -1,545.000 -754.000 -563.000 -62.000 564.000 826.000 1,245.000 1,127.000 1,580.000 345.778 -41.407 ns -4.487 10.98
Local RMS Frequency Jitter 27.000 35.000 42.000 75.000 145.000 206.000 313.000 103.000 171.000 34.595 82.534 10e-12 8.473 32.19
Local RMS Time Jitter 73.000 100.000 125.000 190.000 290.000 345.000 462.000 165.000 245.000 50.585 196.426 ns 33.44 132.9
Server Jitter 162.159.200.123 0.168 0.215 0.275 1.001 20.655 74.790 75.527 20.380 74.575 10.249 5.020 ms 2.976 22.45
Server Jitter 169.229.128.134 0.131 0.161 0.227 1.632 22.564 24.432 25.272 22.337 24.271 7.537 5.752 ms 0.6006 2.325
Server Jitter 173.11.101.155 0.311 0.366 0.738 1.872 20.497 22.699 27.568 19.759 22.333 6.602 5.649 ms 0.8937 2.839
Server Jitter 192.168.1.10 0.066 0.095 0.148 0.659 20.283 23.265 24.826 20.135 23.171 6.731 4.876 ms 0.5227 2.605
Server Jitter 194.58.202.211 0.127 0.189 0.283 1.725 19.558 23.257 25.362 19.275 23.068 6.650 5.622 ms 0.7831 2.647
Server Jitter 194.58.202.219 0.114 0.161 0.238 1.506 20.104 28.895 30.250 19.866 28.734 6.696 5.429 ms 0.853 3.41
Server Jitter 203.123.48.219 0.117 0.157 0.284 1.182 20.307 23.093 47.427 20.023 22.936 7.017 4.648 ms 1.458 8.837
Server Jitter 204.17.205.24 0.127 0.158 0.298 1.668 22.989 23.721 50.504 22.691 23.563 7.999 6.509 ms 0.8552 4.296
Server Jitter 216.218.254.202 0.142 0.157 0.273 2.087 20.383 23.122 27.919 20.110 22.966 6.735 5.668 ms 0.7814 2.606
Server Jitter 63.145.169.3 1.047 1.591 2.998 17.863 67.366 85.054 95.179 64.368 83.462 19.317 23.258 ms 2.078 6.052
Server Jitter SHM(0) 0.068 0.213 0.352 0.988 3.144 5.828 8.832 2.792 5.615 1.028 1.269 ms 3.433 15.71
Server Jitter SHM(1) 41.000 70.000 105.000 229.000 516.000 673.000 1,565.000 411.000 603.000 131.336 259.413 ns 5.335 19.81
Server Offset 162.159.200.123 2.199 2.378 2.536 2.806 3.080 3.274 4.317 0.545 0.896 0.188 2.814 ms 2762 3.922e+04
Server Offset 169.229.128.134 -6.010 -5.864 -5.818 -5.615 -5.357 -5.238 -4.991 0.460 0.626 0.141 -5.605 ms -6.788e+04 2.772e+06
Server Offset 173.11.101.155 -2.319 -1.193 -0.531 0.057 0.534 1.249 1.949 1.065 2.442 0.386 0.032 ms -3.768 18.46
Server Offset 192.168.1.10 -254.349 -142.108 -58.568 90.646 217.425 312.278 422.711 275.993 454.386 86.152 86.384 µs -0.08236 3.751
Server Offset 194.58.202.211 -16.258 -14.355 -9.804 5.442 8.872 9.115 15.034 18.676 23.470 5.301 4.743 ms -2.633 8.955
Server Offset 194.58.202.219 -18.418 -13.545 -7.448 6.590 6.865 6.992 7.188 14.313 20.537 4.490 5.189 ms -2.705 10.36
Server Offset 203.123.48.219 2.226 2.391 2.586 2.866 4.475 4.643 4.888 1.888 2.252 0.767 3.311 ms 47.02 196.5
Server Offset 204.17.205.24 1.397 1.896 2.051 3.697 3.996 4.090 4.361 1.945 2.194 0.693 3.387 ms 69.07 302.4
Server Offset 216.218.254.202 2.321 2.383 2.434 2.625 2.851 2.962 3.950 0.417 0.579 0.153 2.633 ms 4271 6.997e+04
Server Offset 63.145.169.3 -101.400 -99.945 -92.038 -67.892 0.876 2.896 3.450 92.914 102.841 24.055 -59.561 ms -51 203.2
Server Offset SHM(0) -69.390 -65.850 -63.009 -55.485 -48.630 -45.873 -43.501 14.380 19.978 4.365 -55.607 ms -2635 3.677e+04
Server Offset SHM(1) -1,546.000 -755.000 -564.000 -63.000 565.000 827.000 1,246.000 1,129.000 1,582.000 346.540 -41.538 ns -4.488 10.97
TDOP 0.470 0.520 0.590 0.840 1.290 1.420 2.150 0.700 0.900 0.219 0.871 36.48 148.3
Temp ZONE0 57.996 57.996 58.534 59.072 60.148 60.148 60.686 1.614 2.152 0.606 59.200 °C
nSats 7.000 7.000 8.000 9.000 11.000 12.000 13.000 3.000 5.000 1.099 9.354 nSat 447.3 3545
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!