NTPsec

c-ntpsec-7-day-stats

Report generated: Thu Apr 2 04:05:06 2020 UTC
Start Time: Thu Mar 26 04:05:04 2020 UTC
End Time: Thu Apr 2 04:05:04 2020 UTC
Report published: Wed Apr 01 21:05:20 2020 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 -4,805.000 -575.000 -411.000 -5.000 443.000 634.000 1,807.000 854.000 1,209.000 261.932 1.970 ns -3.985 13.11
Local Clock Frequency Offset -5.606 -5.603 -5.594 -5.549 -5.504 -5.492 -5.488 0.091 0.111 0.028 -5.548 ppm -8.219e+06 1.659e+09

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

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



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 72.000 110.000 129.000 187.000 261.000 298.000 2,243.000 132.000 188.000 51.265 190.294 ns 39.3 574.2

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.022 0.030 0.036 0.056 0.101 0.129 10.403 0.065 0.099 0.155 0.065 ppb 42.6 2196

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 -4,805.000 -575.000 -411.000 -5.000 443.000 634.000 1,807.000 854.000 1,209.000 261.932 1.970 ns -3.985 13.11

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 -5.606 -5.603 -5.594 -5.549 -5.504 -5.492 -5.488 0.091 0.111 0.028 -5.548 ppm -8.219e+06 1.659e+09
Temp ZONE0 62.300 63.376 63.914 65.528 66.604 66.604 67.142 2.690 3.228 0.806 65.445 °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.111 9.417 nSat 440.9 3469
TDOP 0.530 0.550 0.600 0.820 1.260 1.630 1.760 0.660 1.080 0.219 0.861 35.3 144.2

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. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



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 -6.749 -4.958 -0.285 2.937 4.546 5.663 7.189 4.832 10.621 1.693 2.709 ms -0.3152 8.212

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 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 -6.434 -5.833 -4.508 -2.160 1.444 4.046 5.260 5.953 9.879 1.915 -1.756 ms -12.15 34.18

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 164.67.62.194

peer offset 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 164.67.62.194 -0.716 2.203 2.411 2.769 3.319 3.769 5.161 0.909 1.566 0.336 2.798 ms 415 3211

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 -5.304 -1.730 -0.635 0.304 1.185 1.908 4.342 1.821 3.638 0.625 0.290 ms -2.333 14.99

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 -5.185 -1.439 0.821 4.900 9.836 12.850 17.047 9.014 14.288 2.872 5.174 ms 3.261 9.788

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 -109.598 -33.920 -13.768 43.249 110.445 134.107 223.583 124.213 168.027 37.987 44.394 µs 0.7388 3.135

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 -5.715 -2.335 -2.038 -0.520 2.347 3.191 4.689 4.385 5.526 1.446 -0.319 ms -4.965 11.15

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

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 0.310 1.943 2.296 2.657 3.489 6.372 27.878 1.193 4.430 1.448 2.843 ms 17.2 270.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 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.196 1.256 1.531 2.015 2.734 3.531 11.438 1.203 2.275 0.571 2.080 ms 32.49 228.3

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 47.51.249.154

peer offset 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 47.51.249.154 -5.908 1.861 2.497 3.401 5.762 6.407 7.455 3.265 4.546 0.922 3.565 ms 32.87 135.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 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) -73.141 -67.230 -64.322 -56.086 -47.530 -45.490 -43.806 16.792 21.740 5.013 -56.069 ms -1845 2.293e+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) -4,806.000 -577.000 -412.000 -6.000 445.000 637.000 2,141.000 857.000 1,214.000 264.252 2.182 ns -3.955 13.61

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.000 0.257 0.399 2.137 9.709 13.667 45.547 9.311 13.410 3.587 3.411 ms 3.124 27.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 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.000 0.219 0.351 1.892 9.617 16.999 161.488 9.266 16.780 6.880 3.462 ms 13.59 288

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 164.67.62.194

peer jitter 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 164.67.62.194 0.000 0.228 0.383 1.941 10.214 13.977 211.824 9.831 13.749 7.412 3.550 ms 20.58 577.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.



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.363 0.702 2.175 10.207 16.664 246.881 9.505 16.301 10.106 3.972 ms 18.4 438

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.000 0.334 0.727 3.447 10.394 20.568 34.979 9.666 20.234 3.986 4.660 ms 2.893 16.84

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.000 0.033 0.051 0.157 8.657 9.316 95.167 8.606 9.284 2.917 1.277 ms 4.632 130

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.000 0.278 0.457 2.205 10.544 17.602 80.855 10.088 17.324 5.932 3.922 ms 6.566 75.95

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

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.977 9.526 15.666 254.490 9.526 15.666 16.200 4.152 ms 12.12 187.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 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.000 0.249 0.396 1.923 9.445 14.644 52.249 9.049 14.395 3.859 3.285 ms 4.392 49.37

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 47.51.249.154

peer jitter 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 47.51.249.154 0.000 0.584 1.010 3.147 11.302 32.614 66.028 10.293 32.030 5.462 4.695 ms 5.195 44.36

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.000 0.284 0.524 2.376 6.823 8.458 13.625 6.300 8.174 2.030 2.906 ms 2.283 5.936

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.000 74.000 103.000 206.000 436.000 562.000 3,914.000 333.000 488.000 116.051 230.270 ns 9.367 147.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 -5.606 -5.603 -5.594 -5.549 -5.504 -5.492 -5.488 0.091 0.111 0.028 -5.548 ppm -8.219e+06 1.659e+09
Local Clock Time Offset -4,805.000 -575.000 -411.000 -5.000 443.000 634.000 1,807.000 854.000 1,209.000 261.932 1.970 ns -3.985 13.11
Local RMS Frequency Jitter 0.022 0.030 0.036 0.056 0.101 0.129 10.403 0.065 0.099 0.155 0.065 ppb 42.6 2196
Local RMS Time Jitter 72.000 110.000 129.000 187.000 261.000 298.000 2,243.000 132.000 188.000 51.265 190.294 ns 39.3 574.2
Server Jitter 104.131.155.175 0.000 0.257 0.399 2.137 9.709 13.667 45.547 9.311 13.410 3.587 3.411 ms 3.124 27.09
Server Jitter 162.159.200.1 0.000 0.219 0.351 1.892 9.617 16.999 161.488 9.266 16.780 6.880 3.462 ms 13.59 288
Server Jitter 164.67.62.194 0.000 0.228 0.383 1.941 10.214 13.977 211.824 9.831 13.749 7.412 3.550 ms 20.58 577.7
Server Jitter 173.11.101.155 0.000 0.363 0.702 2.175 10.207 16.664 246.881 9.505 16.301 10.106 3.972 ms 18.4 438
Server Jitter 178.62.68.79 0.000 0.334 0.727 3.447 10.394 20.568 34.979 9.666 20.234 3.986 4.660 ms 2.893 16.84
Server Jitter 192.168.1.10 0.000 0.033 0.051 0.157 8.657 9.316 95.167 8.606 9.284 2.917 1.277 ms 4.632 130
Server Jitter 203.123.48.219 0.000 0.278 0.457 2.205 10.544 17.602 80.855 10.088 17.324 5.932 3.922 ms 6.566 75.95
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.977 9.526 15.666 254.490 9.526 15.666 16.200 4.152 ms 12.12 187.6
Server Jitter 204.17.205.24 0.000 0.249 0.396 1.923 9.445 14.644 52.249 9.049 14.395 3.859 3.285 ms 4.392 49.37
Server Jitter 47.51.249.154 0.000 0.584 1.010 3.147 11.302 32.614 66.028 10.293 32.030 5.462 4.695 ms 5.195 44.36
Server Jitter SHM(0) 0.000 0.284 0.524 2.376 6.823 8.458 13.625 6.300 8.174 2.030 2.906 ms 2.283 5.936
Server Jitter SHM(1) 0.000 74.000 103.000 206.000 436.000 562.000 3,914.000 333.000 488.000 116.051 230.270 ns 9.367 147.7
Server Offset 104.131.155.175 -6.749 -4.958 -0.285 2.937 4.546 5.663 7.189 4.832 10.621 1.693 2.709 ms -0.3152 8.212
Server Offset 162.159.200.1 -6.434 -5.833 -4.508 -2.160 1.444 4.046 5.260 5.953 9.879 1.915 -1.756 ms -12.15 34.18
Server Offset 164.67.62.194 -0.716 2.203 2.411 2.769 3.319 3.769 5.161 0.909 1.566 0.336 2.798 ms 415 3211
Server Offset 173.11.101.155 -5.304 -1.730 -0.635 0.304 1.185 1.908 4.342 1.821 3.638 0.625 0.290 ms -2.333 14.99
Server Offset 178.62.68.79 -5.185 -1.439 0.821 4.900 9.836 12.850 17.047 9.014 14.288 2.872 5.174 ms 3.261 9.788
Server Offset 192.168.1.10 -109.598 -33.920 -13.768 43.249 110.445 134.107 223.583 124.213 168.027 37.987 44.394 µs 0.7388 3.135
Server Offset 203.123.48.219 -5.715 -2.335 -2.038 -0.520 2.347 3.191 4.689 4.385 5.526 1.446 -0.319 ms -4.965 11.15
Server Offset 204.123.2.5 0.310 1.943 2.296 2.657 3.489 6.372 27.878 1.193 4.430 1.448 2.843 ms 17.2 270.4
Server Offset 204.17.205.24 -1.196 1.256 1.531 2.015 2.734 3.531 11.438 1.203 2.275 0.571 2.080 ms 32.49 228.3
Server Offset 47.51.249.154 -5.908 1.861 2.497 3.401 5.762 6.407 7.455 3.265 4.546 0.922 3.565 ms 32.87 135.6
Server Offset SHM(0) -73.141 -67.230 -64.322 -56.086 -47.530 -45.490 -43.806 16.792 21.740 5.013 -56.069 ms -1845 2.293e+04
Server Offset SHM(1) -4,806.000 -577.000 -412.000 -6.000 445.000 637.000 2,141.000 857.000 1,214.000 264.252 2.182 ns -3.955 13.61
TDOP 0.530 0.550 0.600 0.820 1.260 1.630 1.760 0.660 1.080 0.219 0.861 35.3 144.2
Temp ZONE0 62.300 63.376 63.914 65.528 66.604 66.604 67.142 2.690 3.228 0.806 65.445 °C
nSats 6.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.111 9.417 nSat 440.9 3469
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!