NTPsec

C-ntpsec-6-hour-stats

Report generated: Thu Mar 4 15:01:28 2021 UTC
Start Time: Thu Mar 4 09:01:27 2021 UTC
End Time: Thu Mar 4 15:01:27 2021 UTC
Report published: Thu Mar 04 07:01:36 2021 PST
Report Period: 0.2 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.483 -1.059 -0.826 -0.370 0.213 0.550 1.273 1.039 1.609 0.327 -0.345 µs -14.24 42.96
Local Clock Frequency Offset -5.239 -5.239 -5.233 -5.167 -5.110 -5.109 -5.108 0.122 0.130 0.039 -5.168 ppm -2.351e+06 3.127e+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 101.000 109.000 122.000 191.000 326.000 440.000 595.000 204.000 331.000 66.658 202.160 ns 16 60.77

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 43.000 48.000 62.000 115.000 230.000 342.000 456.000 168.000 294.000 55.854 125.047 10e-12 7.432 28.46

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.483 -1.059 -0.826 -0.370 0.213 0.550 1.273 1.039 1.609 0.327 -0.345 µs -14.24 42.96

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.239 -5.239 -5.233 -5.167 -5.110 -5.109 -5.108 0.122 0.130 0.039 -5.168 ppm -2.351e+06 3.127e+08
Temp ZONE0 56.920 56.920 57.458 57.996 58.534 59.072 59.072 1.076 2.152 0.422 57.954 °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 8.000 9.000 10.000 11.000 12.000 12.000 2.000 4.000 0.854 9.682 nSat 1136 1.209e+04
TDOP 0.520 0.530 0.600 0.810 1.120 1.470 1.580 0.520 0.940 0.182 0.867 65.38 298.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. 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 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 1.094 1.094 1.094 1.689 2.207 2.207 2.207 1.113 1.113 0.251 1.695 ms 208.7 1304

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 1.224 1.224 1.961 2.331 2.689 3.094 3.094 0.729 1.870 0.248 2.330 ms 615.7 5372

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.110 -1.110 -0.816 0.131 0.743 2.751 2.751 1.559 3.861 0.494 0.119 ms -1.231 11.31

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 1.716 1.716 2.572 4.169 4.797 4.797 4.797 2.225 3.081 0.809 3.891 ms 65.7 285.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 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 22.298 43.622 80.184 132.339 209.738 233.533 254.845 129.554 189.911 37.147 133.391 µs 25.57 93.71

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

peer offset 192.53.103.98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.53.103.98 1.763 1.763 1.763 2.273 2.471 2.471 2.471 0.708 0.708 0.159 2.239 ms 2294 3.056e+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 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 2.024 2.024 2.086 2.246 2.586 2.639 2.639 0.500 0.615 0.156 2.276 ms 2536 3.497e+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 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 2.984 2.984 3.181 3.557 4.091 4.501 4.501 0.911 1.517 0.266 3.572 ms 1966 2.497e+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 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 -3.465 -3.465 -2.675 0.023 10.211 11.397 11.397 12.887 14.862 3.880 1.603 ms -0.8201 2.722

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) -71.438 -69.052 -67.290 -59.627 -54.142 -50.502 -49.310 13.148 18.550 4.106 -60.135 ms -3878 6.142e+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.484 -1.060 -0.827 -0.371 0.214 0.550 1.274 1.041 1.610 0.328 -0.346 µs -14.25 42.98

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.721 0.721 0.721 1.698 12.015 12.015 12.015 11.294 11.294 3.685 3.636 ms 1.075 2.547

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.162 0.162 0.636 1.664 8.947 19.808 19.808 8.310 19.646 3.425 3.189 ms 1.893 7.836

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.753 0.753 1.037 1.747 9.629 10.028 10.028 8.592 9.275 3.126 3.521 ms 1.445 3.018

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.884 0.884 1.171 1.874 8.917 8.917 8.917 7.746 8.033 3.061 3.755 ms 1.361 2.51

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.029 0.040 0.059 0.190 8.677 8.852 9.275 8.618 8.812 2.261 1.069 ms 0.9884 5.087

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

peer jitter 192.53.103.98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.53.103.98 0.755 0.755 0.755 1.559 8.062 8.062 8.062 7.308 7.308 2.168 2.388 ms 2.122 5.636

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.447 0.447 0.644 1.560 13.508 13.508 13.508 12.864 13.061 3.500 2.927 ms 1.806 5.572

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.382 0.382 0.478 1.510 12.477 13.199 13.199 11.999 12.817 4.117 4.191 ms 0.7853 1.968

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.406 0.406 0.986 2.188 9.582 15.736 15.736 8.597 15.330 3.314 3.585 ms 2.142 6.665

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.110 0.202 0.329 1.099 3.489 5.800 8.194 3.161 5.599 1.076 1.376 ms 3.166 13.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 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) 28.000 76.000 101.000 228.000 568.000 815.000 1,269.000 467.000 739.000 154.719 269.551 ns 4.344 16.15

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.239 -5.239 -5.233 -5.167 -5.110 -5.109 -5.108 0.122 0.130 0.039 -5.168 ppm -2.351e+06 3.127e+08
Local Clock Time Offset -1.483 -1.059 -0.826 -0.370 0.213 0.550 1.273 1.039 1.609 0.327 -0.345 µs -14.24 42.96
Local RMS Frequency Jitter 43.000 48.000 62.000 115.000 230.000 342.000 456.000 168.000 294.000 55.854 125.047 10e-12 7.432 28.46
Local RMS Time Jitter 101.000 109.000 122.000 191.000 326.000 440.000 595.000 204.000 331.000 66.658 202.160 ns 16 60.77
Server Jitter 104.131.155.175 0.721 0.721 0.721 1.698 12.015 12.015 12.015 11.294 11.294 3.685 3.636 ms 1.075 2.547
Server Jitter 162.159.200.1 0.162 0.162 0.636 1.664 8.947 19.808 19.808 8.310 19.646 3.425 3.189 ms 1.893 7.836
Server Jitter 173.11.101.155 0.753 0.753 1.037 1.747 9.629 10.028 10.028 8.592 9.275 3.126 3.521 ms 1.445 3.018
Server Jitter 178.62.68.79 0.884 0.884 1.171 1.874 8.917 8.917 8.917 7.746 8.033 3.061 3.755 ms 1.361 2.51
Server Jitter 192.168.1.10 0.029 0.040 0.059 0.190 8.677 8.852 9.275 8.618 8.812 2.261 1.069 ms 0.9884 5.087
Server Jitter 192.53.103.98 0.755 0.755 0.755 1.559 8.062 8.062 8.062 7.308 7.308 2.168 2.388 ms 2.122 5.636
Server Jitter 204.123.2.5 0.447 0.447 0.644 1.560 13.508 13.508 13.508 12.864 13.061 3.500 2.927 ms 1.806 5.572
Server Jitter 204.17.205.24 0.382 0.382 0.478 1.510 12.477 13.199 13.199 11.999 12.817 4.117 4.191 ms 0.7853 1.968
Server Jitter 47.51.249.154 0.406 0.406 0.986 2.188 9.582 15.736 15.736 8.597 15.330 3.314 3.585 ms 2.142 6.665
Server Jitter SHM(0) 0.110 0.202 0.329 1.099 3.489 5.800 8.194 3.161 5.599 1.076 1.376 ms 3.166 13.2
Server Jitter SHM(1) 28.000 76.000 101.000 228.000 568.000 815.000 1,269.000 467.000 739.000 154.719 269.551 ns 4.344 16.15
Server Offset 104.131.155.175 1.094 1.094 1.094 1.689 2.207 2.207 2.207 1.113 1.113 0.251 1.695 ms 208.7 1304
Server Offset 162.159.200.1 1.224 1.224 1.961 2.331 2.689 3.094 3.094 0.729 1.870 0.248 2.330 ms 615.7 5372
Server Offset 173.11.101.155 -1.110 -1.110 -0.816 0.131 0.743 2.751 2.751 1.559 3.861 0.494 0.119 ms -1.231 11.31
Server Offset 178.62.68.79 1.716 1.716 2.572 4.169 4.797 4.797 4.797 2.225 3.081 0.809 3.891 ms 65.7 285.4
Server Offset 192.168.1.10 22.298 43.622 80.184 132.339 209.738 233.533 254.845 129.554 189.911 37.147 133.391 µs 25.57 93.71
Server Offset 192.53.103.98 1.763 1.763 1.763 2.273 2.471 2.471 2.471 0.708 0.708 0.159 2.239 ms 2294 3.056e+04
Server Offset 204.123.2.5 2.024 2.024 2.086 2.246 2.586 2.639 2.639 0.500 0.615 0.156 2.276 ms 2536 3.497e+04
Server Offset 204.17.205.24 2.984 2.984 3.181 3.557 4.091 4.501 4.501 0.911 1.517 0.266 3.572 ms 1966 2.497e+04
Server Offset 47.51.249.154 -3.465 -3.465 -2.675 0.023 10.211 11.397 11.397 12.887 14.862 3.880 1.603 ms -0.8201 2.722
Server Offset SHM(0) -71.438 -69.052 -67.290 -59.627 -54.142 -50.502 -49.310 13.148 18.550 4.106 -60.135 ms -3878 6.142e+04
Server Offset SHM(1) -1.484 -1.060 -0.827 -0.371 0.214 0.550 1.274 1.041 1.610 0.328 -0.346 µs -14.25 42.98
TDOP 0.520 0.530 0.600 0.810 1.120 1.470 1.580 0.520 0.940 0.182 0.867 65.38 298.2
Temp ZONE0 56.920 56.920 57.458 57.996 58.534 59.072 59.072 1.076 2.152 0.422 57.954 °C
nSats 7.000 8.000 9.000 10.000 11.000 12.000 12.000 2.000 4.000 0.854 9.682 nSat 1136 1.209e+04
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!