NTPsec

B-ntpsec-6-hour-stats

Report generated: Thu Sep 29 13:07:32 2022 UTC
Start Time: Thu Sep 29 07:07:32 2022 UTC
End Time: Thu Sep 29 13:07:32 2022 UTC
Report published: Thu Sep 29 06:07:38 2022 PDT
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,101.000 -827.000 -609.000 -69.000 332.000 488.000 853.000 941.000 1,315.000 293.469 -100.414 ns -6.771 18.58
Local Clock Frequency Offset -5.153 -5.151 -5.145 -5.081 -5.027 -5.023 -5.022 0.118 0.128 0.037 -5.084 ppm -2.662e+06 3.69e+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 218.000 251.000 290.000 403.000 540.000 594.000 647.000 250.000 343.000 75.919 406.755 ns 96.09 481.9

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 82.000 96.000 109.000 148.000 196.000 227.000 273.000 87.000 131.000 26.941 149.630 10e-12 108.7 568.9

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,101.000 -827.000 -609.000 -69.000 332.000 488.000 853.000 941.000 1,315.000 293.469 -100.414 ns -6.771 18.58

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.153 -5.151 -5.145 -5.081 -5.027 -5.023 -5.022 0.118 0.128 0.037 -5.084 ppm -2.662e+06 3.69e+08
Temp ZONE0 47.774 47.774 48.312 48.850 49.388 49.926 49.926 1.076 2.152 0.525 48.829 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 7.000 7.000 8.000 9.000 11.000 11.000 11.000 3.000 4.000 0.931 9.395 nSat 779.3 7330
TDOP 0.600 0.620 0.640 0.850 1.320 1.350 1.440 0.680 0.730 0.187 0.892 66.13 304.4

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 2.793 2.793 2.793 3.160 3.742 3.742 3.742 0.949 0.949 0.212 3.177 ms 2796 3.98e+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 162.159.200.123

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 2.408 2.408 2.716 3.184 3.692 4.018 4.018 0.977 1.610 0.286 3.198 ms 1089 1.141e+04

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

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

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

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



Server Offset 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 1.953 1.953 2.148 2.616 2.975 3.247 3.247 0.827 1.294 0.257 2.572 ms 757.5 7069

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.587 -1.587 -1.319 -0.150 0.571 1.180 1.180 1.890 2.767 0.548 -0.219 ms -7.409 21.48

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.628 -1.628 -1.628 -1.117 -0.547 -0.547 -0.547 1.081 1.081 0.271 -1.089 ms -140.9 781.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 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 -225.518 -160.768 -86.815 110.687 300.365 368.315 468.874 387.180 529.083 119.852 107.599 µs -0.3375 2.634

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

peer offset 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.23 1.044 1.044 1.044 1.343 1.845 1.845 1.845 0.801 0.801 0.246 1.405 ms 119 633.7

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 209.50.50.228

peer offset 209.50.50.228 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.50.50.228 -912.496 -912.496 -767.131 -357.754 257.984 421.370 421.370 1,025.115 1,333.866 285.090 -317.395 µs -15.39 46.37

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 1.486 1.486 1.876 2.445 3.042 3.469 3.469 1.166 1.983 0.344 2.466 ms 254.8 1698

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 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 1.629 1.629 1.772 2.284 3.062 3.183 3.183 1.289 1.554 0.331 2.329 ms 238.1 1558

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) -405.918 -397.368 -388.638 -353.984 -329.575 -321.470 -311.891 59.063 75.898 17.358 -356.444 ms -1.005e+04 2.179e+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) -1,102.000 -828.000 -610.000 -70.000 333.000 489.000 854.000 943.000 1,317.000 294.211 -100.587 ns -6.766 18.55

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.462 0.462 0.462 0.959 1.668 1.668 1.668 1.205 1.205 0.401 1.057 ms 9.318 25.17

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

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.245 0.245 0.321 1.052 2.096 2.831 2.831 1.775 2.586 0.572 1.183 ms 5.191 14.78

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.244 0.244 0.435 1.241 1.987 27.121 27.121 1.552 26.876 3.054 1.564 ms 6.438 53.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 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.816 0.816 1.094 1.834 3.159 8.919 8.919 2.065 8.103 1.578 2.129 ms 4.717 21.35

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.449 0.449 0.449 1.555 14.152 14.152 14.152 13.703 13.703 5.206 4.101 ms 0.6812 2.04

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.078 0.112 0.141 0.297 0.878 4.114 6.526 0.737 4.002 0.595 0.407 ms 6.446 55.56

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

peer jitter 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.23 0.562 0.562 0.562 0.894 1.419 1.419 1.419 0.858 0.858 0.233 0.954 ms 39.56 157.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 209.50.50.228

peer jitter 209.50.50.228 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.50.50.228 0.275 0.275 0.578 1.168 5.770 24.853 24.853 5.192 24.578 3.938 2.013 ms 3.57 20.92

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.187 0.187 0.313 0.945 3.718 30.515 30.515 3.405 30.328 5.713 2.286 ms 2.613 14.04

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 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 0.248 0.248 0.306 1.034 1.634 1.865 1.865 1.329 1.617 0.412 0.978 ms 6.74 17.04

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) 2.138 3.155 4.837 14.047 30.670 37.449 48.424 25.833 34.294 8.161 15.405 ms 4.09 10.98

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) 82.000 155.000 201.000 357.000 657.000 817.000 1,181.000 456.000 662.000 140.904 381.007 ns 11.15 38.05

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.153 -5.151 -5.145 -5.081 -5.027 -5.023 -5.022 0.118 0.128 0.037 -5.084 ppm -2.662e+06 3.69e+08
Local Clock Time Offset -1,101.000 -827.000 -609.000 -69.000 332.000 488.000 853.000 941.000 1,315.000 293.469 -100.414 ns -6.771 18.58
Local RMS Frequency Jitter 82.000 96.000 109.000 148.000 196.000 227.000 273.000 87.000 131.000 26.941 149.630 10e-12 108.7 568.9
Local RMS Time Jitter 218.000 251.000 290.000 403.000 540.000 594.000 647.000 250.000 343.000 75.919 406.755 ns 96.09 481.9
Server Jitter 104.131.155.175 0.462 0.462 0.462 0.959 1.668 1.668 1.668 1.205 1.205 0.401 1.057 ms 9.318 25.17
Server Jitter 162.159.200.123 0.245 0.245 0.321 1.052 2.096 2.831 2.831 1.775 2.586 0.572 1.183 ms 5.191 14.78
Server Jitter 169.229.128.134 0.244 0.244 0.435 1.241 1.987 27.121 27.121 1.552 26.876 3.054 1.564 ms 6.438 53.03
Server Jitter 173.11.101.155 0.816 0.816 1.094 1.834 3.159 8.919 8.919 2.065 8.103 1.578 2.129 ms 4.717 21.35
Server Jitter 178.62.68.79 0.449 0.449 0.449 1.555 14.152 14.152 14.152 13.703 13.703 5.206 4.101 ms 0.6812 2.04
Server Jitter 192.168.1.10 0.078 0.112 0.141 0.297 0.878 4.114 6.526 0.737 4.002 0.595 0.407 ms 6.446 55.56
Server Jitter 204.17.205.23 0.562 0.562 0.562 0.894 1.419 1.419 1.419 0.858 0.858 0.233 0.954 ms 39.56 157.7
Server Jitter 209.50.50.228 0.275 0.275 0.578 1.168 5.770 24.853 24.853 5.192 24.578 3.938 2.013 ms 3.57 20.92
Server Jitter 216.218.254.202 0.187 0.187 0.313 0.945 3.718 30.515 30.515 3.405 30.328 5.713 2.286 ms 2.613 14.04
Server Jitter 66.220.9.122 0.248 0.248 0.306 1.034 1.634 1.865 1.865 1.329 1.617 0.412 0.978 ms 6.74 17.04
Server Jitter SHM(0) 2.138 3.155 4.837 14.047 30.670 37.449 48.424 25.833 34.294 8.161 15.405 ms 4.09 10.98
Server Jitter SHM(1) 82.000 155.000 201.000 357.000 657.000 817.000 1,181.000 456.000 662.000 140.904 381.007 ns 11.15 38.05
Server Offset 104.131.155.175 2.793 2.793 2.793 3.160 3.742 3.742 3.742 0.949 0.949 0.212 3.177 ms 2796 3.98e+04
Server Offset 162.159.200.123 2.408 2.408 2.716 3.184 3.692 4.018 4.018 0.977 1.610 0.286 3.198 ms 1089 1.141e+04
Server Offset 169.229.128.134 1.953 1.953 2.148 2.616 2.975 3.247 3.247 0.827 1.294 0.257 2.572 ms 757.5 7069
Server Offset 173.11.101.155 -1.587 -1.587 -1.319 -0.150 0.571 1.180 1.180 1.890 2.767 0.548 -0.219 ms -7.409 21.48
Server Offset 178.62.68.79 -1.628 -1.628 -1.628 -1.117 -0.547 -0.547 -0.547 1.081 1.081 0.271 -1.089 ms -140.9 781.3
Server Offset 192.168.1.10 -225.518 -160.768 -86.815 110.687 300.365 368.315 468.874 387.180 529.083 119.852 107.599 µs -0.3375 2.634
Server Offset 204.17.205.23 1.044 1.044 1.044 1.343 1.845 1.845 1.845 0.801 0.801 0.246 1.405 ms 119 633.7
Server Offset 209.50.50.228 -912.496 -912.496 -767.131 -357.754 257.984 421.370 421.370 1,025.115 1,333.866 285.090 -317.395 µs -15.39 46.37
Server Offset 216.218.254.202 1.486 1.486 1.876 2.445 3.042 3.469 3.469 1.166 1.983 0.344 2.466 ms 254.8 1698
Server Offset 66.220.9.122 1.629 1.629 1.772 2.284 3.062 3.183 3.183 1.289 1.554 0.331 2.329 ms 238.1 1558
Server Offset SHM(0) -405.918 -397.368 -388.638 -353.984 -329.575 -321.470 -311.891 59.063 75.898 17.358 -356.444 ms -1.005e+04 2.179e+05
Server Offset SHM(1) -1,102.000 -828.000 -610.000 -70.000 333.000 489.000 854.000 943.000 1,317.000 294.211 -100.587 ns -6.766 18.55
TDOP 0.600 0.620 0.640 0.850 1.320 1.350 1.440 0.680 0.730 0.187 0.892 66.13 304.4
Temp ZONE0 47.774 47.774 48.312 48.850 49.388 49.926 49.926 1.076 2.152 0.525 48.829 °C
nSats 7.000 7.000 8.000 9.000 11.000 11.000 11.000 3.000 4.000 0.931 9.395 nSat 779.3 7330
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!