NTPsec

c-ntpsec-5-day-stats

Report generated: Sun Aug 18 19:18:33 2019 UTC
Start Time: Tue Aug 13 19:18:25 2019 UTC
End Time: Sun Aug 18 19:18:25 2019 UTC
Report published: Sun Aug 18 12:20:09 2019 PDT
Report Period: 5.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.948 -0.996 -0.725 -0.014 0.752 1.059 4.187 1.477 2.055 0.457 -0.000 µs -3.698 10.48
Local Clock Frequency Offset -8.175 -8.158 -8.095 -7.958 -7.841 -7.812 -7.806 0.254 0.346 0.075 -7.967 ppm -1.246e+06 1.341e+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 95.000 131.000 156.000 243.000 388.000 492.000 1,702.000 232.000 361.000 76.194 254.247 ns 21.93 105.8

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 24.000 38.000 50.000 93.000 206.000 312.000 741.000 156.000 274.000 56.255 107.174 10e-12 6.075 32.41

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.948 -0.996 -0.725 -0.014 0.752 1.059 4.187 1.477 2.055 0.457 -0.000 µs -3.698 10.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 -8.175 -8.158 -8.095 -7.958 -7.841 -7.812 -7.806 0.254 0.346 0.075 -7.967 ppm -1.246e+06 1.341e+08
Temp ZONE0 56.920 57.996 57.996 59.610 61.224 62.300 62.838 3.228 4.304 0.966 59.531 °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 5.000 7.000 7.000 10.000 12.000 12.000 13.000 5.000 5.000 1.473 9.638 nSat 186.7 1127
TDOP 0.520 0.570 0.600 0.800 1.370 1.740 5.370 0.770 1.170 0.262 0.877 22.73 117.6

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 -0.358 -0.143 1.001 2.862 6.890 9.866 242.430 5.888 10.009 12.852 3.933 ms 15.51 285.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 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.660 -6.039 -2.283 2.227 6.397 6.881 7.348 8.680 12.920 2.701 2.026 ms -1.116 3.763

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.827 2.376 2.478 2.737 3.142 3.590 4.657 0.664 1.214 0.239 2.768 ms 1221 1.331e+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 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 -1.893 -0.706 -0.316 0.214 0.783 1.374 3.643 1.100 2.080 0.393 0.231 ms -0.1901 11.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 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 -6.794 -4.797 -3.746 2.851 6.685 8.783 22.783 10.431 13.580 3.532 2.156 ms -0.715 7.125

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 -145.735 -18.760 9.768 47.463 77.300 86.057 128.764 67.532 104.817 22.017 45.907 µs 3.702 10.42

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 -619,315,200.052 -0.003 -0.002 0.002 0.004 0.005 0.009 0.006 0.008 16,683,494.245 -449,756.862 s -41.23 1535

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.890 2.035 2.177 2.483 2.898 3.191 3.569 0.721 1.156 0.236 2.507 ms 916.8 9102

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.962 1.146 1.346 1.738 2.177 2.569 13.327 0.832 1.422 0.424 1.763 ms 56.07 738.1

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset SHM(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.187 -70.176 -67.533 -57.320 -48.028 -44.923 -42.120 19.505 25.253 5.771 -57.429 ms -1346 1.511e+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.949 -0.997 -0.725 -0.015 0.753 1.060 4.188 1.478 2.057 0.457 -0.000 µs -3.699 10.47

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.000 0.000 1.629 124.285 178.635 380.953 124.285 178.635 43.496 15.953 ms 1.867 15.03

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.104 0.176 0.282 1.508 9.707 15.996 95.190 9.426 15.820 4.990 3.128 ms 7.071 108.2

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.075 0.176 0.293 1.600 9.768 13.922 20.771 9.475 13.746 3.357 3.034 ms 1.397 5.093

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.204 0.323 0.479 1.798 10.702 15.732 24.033 10.223 15.409 3.668 3.428 ms 1.571 5.303

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.000 0.000 2.126 13.521 23.539 25.148 13.521 23.539 4.764 4.261 ms 1.434 5.597

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.007 0.015 0.026 0.095 8.663 9.785 32.432 8.637 9.770 2.785 1.191 ms 1.242 12.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 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.000 0.000 0.002 0.011 0.020 553,932,354.692 0.010 0.019 23,401,209.186 1,227,847.602 s 16.21 342.2

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.117 0.186 0.302 1.614 9.735 12.892 52.693 9.432 12.706 4.234 3.382 ms 4.235 47.74

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.190 0.291 1.411 9.913 15.653 30.875 9.622 15.463 3.646 2.943 ms 1.809 10.02

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.072 0.360 0.612 2.403 6.655 8.390 11.507 6.044 8.030 1.964 2.920 ms 2.463 6.356

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) 33.000 86.000 120.000 267.000 579.000 787.000 3,267.000 459.000 701.000 151.079 298.449 ns 5.975 34.33

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 -8.175 -8.158 -8.095 -7.958 -7.841 -7.812 -7.806 0.254 0.346 0.075 -7.967 ppm -1.246e+06 1.341e+08
Local Clock Time Offset -1.948 -0.996 -0.725 -0.014 0.752 1.059 4.187 1.477 2.055 0.457 -0.000 µs -3.698 10.48
Local RMS Frequency Jitter 24.000 38.000 50.000 93.000 206.000 312.000 741.000 156.000 274.000 56.255 107.174 10e-12 6.075 32.41
Local RMS Time Jitter 95.000 131.000 156.000 243.000 388.000 492.000 1,702.000 232.000 361.000 76.194 254.247 ns 21.93 105.8
Server Jitter 104.131.155.175 0.000 0.000 0.000 1.629 124.285 178.635 380.953 124.285 178.635 43.496 15.953 ms 1.867 15.03
Server Jitter 162.159.200.1 0.104 0.176 0.282 1.508 9.707 15.996 95.190 9.426 15.820 4.990 3.128 ms 7.071 108.2
Server Jitter 164.67.62.194 0.075 0.176 0.293 1.600 9.768 13.922 20.771 9.475 13.746 3.357 3.034 ms 1.397 5.093
Server Jitter 173.11.101.155 0.204 0.323 0.479 1.798 10.702 15.732 24.033 10.223 15.409 3.668 3.428 ms 1.571 5.303
Server Jitter 178.62.68.79 0.000 0.000 0.000 2.126 13.521 23.539 25.148 13.521 23.539 4.764 4.261 ms 1.434 5.597
Server Jitter 192.168.1.10 0.007 0.015 0.026 0.095 8.663 9.785 32.432 8.637 9.770 2.785 1.191 ms 1.242 12.8
Server Jitter 203.123.48.219 0.000 0.000 0.000 0.002 0.011 0.020 553,932,354.692 0.010 0.019 23,401,209.186 1,227,847.602 s 16.21 342.2
Server Jitter 204.123.2.5 0.117 0.186 0.302 1.614 9.735 12.892 52.693 9.432 12.706 4.234 3.382 ms 4.235 47.74
Server Jitter 204.17.205.24 0.000 0.190 0.291 1.411 9.913 15.653 30.875 9.622 15.463 3.646 2.943 ms 1.809 10.02
Server Jitter SHM(0) 0.072 0.360 0.612 2.403 6.655 8.390 11.507 6.044 8.030 1.964 2.920 ms 2.463 6.356
Server Jitter SHM(1) 33.000 86.000 120.000 267.000 579.000 787.000 3,267.000 459.000 701.000 151.079 298.449 ns 5.975 34.33
Server Offset 104.131.155.175 -0.358 -0.143 1.001 2.862 6.890 9.866 242.430 5.888 10.009 12.852 3.933 ms 15.51 285.6
Server Offset 162.159.200.1 -6.660 -6.039 -2.283 2.227 6.397 6.881 7.348 8.680 12.920 2.701 2.026 ms -1.116 3.763
Server Offset 164.67.62.194 0.827 2.376 2.478 2.737 3.142 3.590 4.657 0.664 1.214 0.239 2.768 ms 1221 1.331e+04
Server Offset 173.11.101.155 -1.893 -0.706 -0.316 0.214 0.783 1.374 3.643 1.100 2.080 0.393 0.231 ms -0.1901 11.9
Server Offset 178.62.68.79 -6.794 -4.797 -3.746 2.851 6.685 8.783 22.783 10.431 13.580 3.532 2.156 ms -0.715 7.125
Server Offset 192.168.1.10 -145.735 -18.760 9.768 47.463 77.300 86.057 128.764 67.532 104.817 22.017 45.907 µs 3.702 10.42
Server Offset 203.123.48.219 -619,315,200.052 -0.003 -0.002 0.002 0.004 0.005 0.009 0.006 0.008 16,683,494.245 -449,756.862 s -41.23 1535
Server Offset 204.123.2.5 0.890 2.035 2.177 2.483 2.898 3.191 3.569 0.721 1.156 0.236 2.507 ms 916.8 9102
Server Offset 204.17.205.24 0.962 1.146 1.346 1.738 2.177 2.569 13.327 0.832 1.422 0.424 1.763 ms 56.07 738.1
Server Offset SHM(0) -73.187 -70.176 -67.533 -57.320 -48.028 -44.923 -42.120 19.505 25.253 5.771 -57.429 ms -1346 1.511e+04
Server Offset SHM(1) -1.949 -0.997 -0.725 -0.015 0.753 1.060 4.188 1.478 2.057 0.457 -0.000 µs -3.699 10.47
TDOP 0.520 0.570 0.600 0.800 1.370 1.740 5.370 0.770 1.170 0.262 0.877 22.73 117.6
Temp ZONE0 56.920 57.996 57.996 59.610 61.224 62.300 62.838 3.228 4.304 0.966 59.531 °C
nSats 5.000 7.000 7.000 10.000 12.000 12.000 13.000 5.000 5.000 1.473 9.638 nSat 186.7 1127
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!