NTPsec

A-ntpsec-7-day-stats

Report generated: Sat May 28 16:04:30 2022 UTC
Start Time: Sat May 21 16:04:27 2022 UTC
End Time: Sat May 28 16:04:27 2022 UTC
Report published: Sat May 28 09:04:52 2022 PDT
Report Period: 7.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 -5.036 -1.038 -0.716 0.006 0.729 1.080 2.673 1.445 2.118 0.455 0.005 µs -3.917 11.48
Local Clock Frequency Offset -153.000 -114.883 -104.279 -58.838 -36.057 -32.959 -30.685 68.222 81.924 21.929 -63.938 ppb -72.48 340.9

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 217.000 310.000 362.000 513.000 712.000 816.000 2,619.000 350.000 506.000 110.968 522.029 ns 63.34 308

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 47.000 62.000 72.000 100.000 147.000 284.000 837.000 75.000 222.000 40.837 105.817 10e-12 15.43 133.8

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 -5.036 -1.038 -0.716 0.006 0.729 1.080 2.673 1.445 2.118 0.455 0.005 µs -3.917 11.48

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 -153.000 -114.883 -104.279 -58.838 -36.057 -32.959 -30.685 68.222 81.924 21.929 -63.938 ppb -72.48 340.9
Temp ZONE0 50.464 51.540 52.078 53.692 57.996 57.996 59.072 5.918 6.456 1.674 54.178 °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 6.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.021 9.411 nSat 579.8 4971
TDOP 0.490 0.540 0.610 0.820 1.420 1.500 3.150 0.810 0.960 0.234 0.875 30.18 122.5

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

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 2.784 3.019 4.595 5.122 7.177 10.083 15.425 2.582 7.064 1.093 5.287 ms 71.53 380.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 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 -2.796 1.990 2.202 2.447 4.227 6.965 14.736 2.026 4.975 0.920 2.649 ms 17.36 114

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 -12.518 -2.821 -1.187 -0.029 2.047 5.006 14.483 3.235 7.827 1.293 0.050 ms -1.796 31.75

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 -408.409 -0.145 -0.120 -0.046 0.050 0.106 0.605 0.169 0.252 9.739 -0.280 ms -45.41 1879

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 -499.579 -181.456 -154.759 -63.945 54.603 361.237 1,365.721 209.362 542.693 90.289 -54.162 µs -4.723 36.96

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

peer offset 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.79 3.180 4.087 5.072 5.644 9.600 10.256 16.207 4.528 6.169 1.389 6.156 ms 52.67 245.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 194.58.207.80

peer offset 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.80 3.680 4.141 4.983 5.587 8.066 10.652 14.117 3.083 6.511 1.326 6.263 ms 63.87 296.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 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 0.005 1.005 1.258 1.705 3.043 5.553 9.523 1.785 4.548 0.809 1.853 ms 10.5 65.32

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 -0.252 2.200 2.375 2.622 4.728 7.575 11.696 2.353 5.375 0.996 2.856 ms 16.58 93.03

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 -8.769 2.183 2.349 2.590 4.625 7.254 10.090 2.276 5.071 0.947 2.807 ms 15.49 88.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 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) -59.842 -55.607 -54.067 -49.019 -44.703 -43.266 -40.163 9.365 12.342 2.810 -49.169 ms -6387 1.192e+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 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) -5.037 -1.039 -0.717 0.007 0.730 1.081 2.674 1.447 2.120 0.456 0.005 µs -3.917 11.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 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.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.067 0.153 0.223 0.858 9.410 19.488 99.253 9.187 19.335 5.010 2.192 ms 7.911 136.6

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.000 0.138 0.219 1.013 11.451 22.396 294.175 11.233 22.258 15.092 3.212 ms 11.48 189.1

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.000 0.632 0.913 1.795 15.131 28.217 189.924 14.218 27.585 7.809 3.958 ms 12.39 287.1

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.000 0.028 0.047 0.132 0.660 3.410 337.557 0.613 3.382 5.805 0.495 ms 34.06 1640

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.000 0.031 0.049 0.138 0.713 5.262 131.387 0.664 5.230 3.419 0.453 ms 20.26 590

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

peer jitter 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.79 0.078 0.160 0.238 1.005 14.783 57.260 220.217 14.545 57.100 17.690 4.228 ms 7.251 84.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 194.58.207.80

peer jitter 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.80 0.093 0.165 0.239 0.941 16.339 36.837 213.028 16.100 36.672 9.930 3.289 ms 9.952 188

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.107 0.188 0.276 0.831 11.061 39.098 374.922 10.784 38.910 23.843 3.915 ms 11.62 183.3

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.000 0.166 0.255 1.185 9.852 22.458 195.668 9.597 22.292 10.495 2.820 ms 12.97 238

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.000 0.149 0.231 1.134 12.693 22.981 195.055 12.463 22.832 7.188 2.694 ms 14.26 369.8

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.039 0.153 0.271 0.863 2.229 3.058 6.072 1.958 2.904 0.624 1.006 ms 3.45 11.5

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.086 0.195 0.261 0.478 0.907 1.140 5.147 0.646 0.945 0.205 0.518 µs 9.775 45.6

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 -153.000 -114.883 -104.279 -58.838 -36.057 -32.959 -30.685 68.222 81.924 21.929 -63.938 ppb -72.48 340.9
Local Clock Time Offset -5.036 -1.038 -0.716 0.006 0.729 1.080 2.673 1.445 2.118 0.455 0.005 µs -3.917 11.48
Local RMS Frequency Jitter 47.000 62.000 72.000 100.000 147.000 284.000 837.000 75.000 222.000 40.837 105.817 10e-12 15.43 133.8
Local RMS Time Jitter 217.000 310.000 362.000 513.000 712.000 816.000 2,619.000 350.000 506.000 110.968 522.029 ns 63.34 308
Server Jitter 162.159.200.1 0.067 0.153 0.223 0.858 9.410 19.488 99.253 9.187 19.335 5.010 2.192 ms 7.911 136.6
Server Jitter 169.229.128.134 0.000 0.138 0.219 1.013 11.451 22.396 294.175 11.233 22.258 15.092 3.212 ms 11.48 189.1
Server Jitter 173.11.101.155 0.000 0.632 0.913 1.795 15.131 28.217 189.924 14.218 27.585 7.809 3.958 ms 12.39 287.1
Server Jitter 192.168.1.11 0.000 0.028 0.047 0.132 0.660 3.410 337.557 0.613 3.382 5.805 0.495 ms 34.06 1640
Server Jitter 192.168.1.12 0.000 0.031 0.049 0.138 0.713 5.262 131.387 0.664 5.230 3.419 0.453 ms 20.26 590
Server Jitter 194.58.207.79 0.078 0.160 0.238 1.005 14.783 57.260 220.217 14.545 57.100 17.690 4.228 ms 7.251 84.45
Server Jitter 194.58.207.80 0.093 0.165 0.239 0.941 16.339 36.837 213.028 16.100 36.672 9.930 3.289 ms 9.952 188
Server Jitter 204.17.205.24 0.107 0.188 0.276 0.831 11.061 39.098 374.922 10.784 38.910 23.843 3.915 ms 11.62 183.3
Server Jitter 216.218.192.202 0.000 0.166 0.255 1.185 9.852 22.458 195.668 9.597 22.292 10.495 2.820 ms 12.97 238
Server Jitter 216.218.254.202 0.000 0.149 0.231 1.134 12.693 22.981 195.055 12.463 22.832 7.188 2.694 ms 14.26 369.8
Server Jitter SHM(0) 0.039 0.153 0.271 0.863 2.229 3.058 6.072 1.958 2.904 0.624 1.006 ms 3.45 11.5
Server Jitter SHM(1) 0.086 0.195 0.261 0.478 0.907 1.140 5.147 0.646 0.945 0.205 0.518 µs 9.775 45.6
Server Offset 162.159.200.1 2.784 3.019 4.595 5.122 7.177 10.083 15.425 2.582 7.064 1.093 5.287 ms 71.53 380.9
Server Offset 169.229.128.134 -2.796 1.990 2.202 2.447 4.227 6.965 14.736 2.026 4.975 0.920 2.649 ms 17.36 114
Server Offset 173.11.101.155 -12.518 -2.821 -1.187 -0.029 2.047 5.006 14.483 3.235 7.827 1.293 0.050 ms -1.796 31.75
Server Offset 192.168.1.11 -408.409 -0.145 -0.120 -0.046 0.050 0.106 0.605 0.169 0.252 9.739 -0.280 ms -45.41 1879
Server Offset 192.168.1.12 -499.579 -181.456 -154.759 -63.945 54.603 361.237 1,365.721 209.362 542.693 90.289 -54.162 µs -4.723 36.96
Server Offset 194.58.207.79 3.180 4.087 5.072 5.644 9.600 10.256 16.207 4.528 6.169 1.389 6.156 ms 52.67 245.4
Server Offset 194.58.207.80 3.680 4.141 4.983 5.587 8.066 10.652 14.117 3.083 6.511 1.326 6.263 ms 63.87 296.9
Server Offset 204.17.205.24 0.005 1.005 1.258 1.705 3.043 5.553 9.523 1.785 4.548 0.809 1.853 ms 10.5 65.32
Server Offset 216.218.192.202 -0.252 2.200 2.375 2.622 4.728 7.575 11.696 2.353 5.375 0.996 2.856 ms 16.58 93.03
Server Offset 216.218.254.202 -8.769 2.183 2.349 2.590 4.625 7.254 10.090 2.276 5.071 0.947 2.807 ms 15.49 88.41
Server Offset SHM(0) -59.842 -55.607 -54.067 -49.019 -44.703 -43.266 -40.163 9.365 12.342 2.810 -49.169 ms -6387 1.192e+05
Server Offset SHM(1) -5.037 -1.039 -0.717 0.007 0.730 1.081 2.674 1.447 2.120 0.456 0.005 µs -3.917 11.46
TDOP 0.490 0.540 0.610 0.820 1.420 1.500 3.150 0.810 0.960 0.234 0.875 30.18 122.5
Temp ZONE0 50.464 51.540 52.078 53.692 57.996 57.996 59.072 5.918 6.456 1.674 54.178 °C
nSats 6.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.021 9.411 nSat 579.8 4971
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!