NTPsec

B-ntpsec-12-hour-stats

Report generated: Sat Nov 26 18:09:46 2022 UTC
Start Time: Sat Nov 26 06:09:45 2022 UTC
End Time: Sat Nov 26 18:09:45 2022 UTC
Report published: Sat Nov 26 10:09:53 2022 PST
Report Period: 0.5 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,601.000 -764.000 -584.000 -46.000 502.000 690.000 929.000 1,086.000 1,454.000 324.669 -44.930 ns -4.88 12.21
Local Clock Frequency Offset -5.377 -5.376 -5.375 -5.260 -5.106 -5.099 -5.097 0.269 0.277 0.085 -5.254 ppm -2.495e+05 1.572e+07

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 162.000 207.000 249.000 388.000 519.000 575.000 679.000 270.000 368.000 81.940 386.038 ns 62.28 275.5

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 64.000 87.000 107.000 155.000 211.000 245.000 332.000 104.000 158.000 32.483 157.272 10e-12 68.67 317.2

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,601.000 -764.000 -584.000 -46.000 502.000 690.000 929.000 1,086.000 1,454.000 324.669 -44.930 ns -4.88 12.21

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.377 -5.376 -5.375 -5.260 -5.106 -5.099 -5.097 0.269 0.277 0.085 -5.254 ppm -2.495e+05 1.572e+07
Temp ZONE0 45.622 45.622 46.160 47.236 48.850 49.388 49.388 2.690 3.766 0.885 47.242 °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 12.000 12.000 12.000 3.000 4.000 1.017 10.125 nSat 744.4 6906
TDOP 0.540 0.550 0.590 0.810 1.150 1.280 1.460 0.560 0.730 0.176 0.835 64.39 293.3

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.767 1.767 1.886 2.890 3.719 3.803 3.803 1.833 2.037 0.530 2.793 ms 90.84 444.8

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.013 2.200 2.428 2.888 3.360 3.734 3.741 0.932 1.534 0.303 2.898 ms 652.1 5803

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 -0.433 2.022 2.185 2.612 3.037 3.394 3.551 0.852 1.372 0.351 2.601 ms 277.8 1862

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 -3.261 -2.657 -2.088 -0.243 0.732 1.454 1.982 2.820 4.112 0.772 -0.360 ms -8.362 27.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 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.863 -5.863 -1.745 1.921 4.325 4.328 4.328 6.070 10.192 2.100 1.510 ms -2.802 10.13

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 -362.353 -133.455 -58.627 183.055 355.182 403.424 469.683 413.809 536.879 129.846 167.122 µs 0.4492 2.911

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.489 1.914 2.143 2.586 3.075 3.351 3.433 0.931 1.437 0.285 2.600 ms 560.9 4755

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 2.066 2.182 2.372 2.745 3.254 3.412 3.513 0.882 1.230 0.259 2.749 ms 914.7 9075

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) -442.113 -422.540 -406.992 -360.608 -330.089 -318.797 -306.663 76.904 103.742 23.331 -363.535 ms -4609 7.728e+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,602.000 -765.000 -585.000 -47.000 503.000 691.000 930.000 1,088.000 1,456.000 325.436 -45.038 ns -4.879 12.19

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.416 0.416 0.520 1.025 1.866 9.930 9.930 1.346 9.514 1.528 1.263 ms 4.659 26.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.



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.213 0.239 0.381 0.959 2.909 8.647 8.687 2.528 8.408 1.106 1.241 ms 4.728 29.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 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.179 0.262 0.314 0.863 7.390 15.377 15.552 7.076 15.115 2.962 1.742 ms 2.292 10.41

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.287 0.443 0.869 1.837 15.221 17.887 19.401 14.352 17.444 4.509 3.656 ms 1.477 4.552

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.391 0.391 0.684 1.313 6.403 6.593 6.593 5.719 6.202 1.882 2.464 ms 1.811 4.037

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.072 0.098 0.138 0.306 1.678 9.843 16.713 1.540 9.746 1.551 0.646 ms 4.469 35.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 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.216 0.224 0.402 1.126 2.691 8.488 11.513 2.289 8.263 1.607 1.430 ms 3.83 19.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 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.106 0.238 0.380 1.091 3.726 7.375 7.409 3.346 7.137 1.209 1.331 ms 3.605 16.82

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) 1.953 3.175 5.025 15.720 33.690 41.106 54.309 28.665 37.931 8.970 16.982 ms 4.102 11.11

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) 78.000 141.000 184.000 340.000 598.000 715.000 1,327.000 414.000 574.000 126.700 358.898 ns 12.54 42.29

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.377 -5.376 -5.375 -5.260 -5.106 -5.099 -5.097 0.269 0.277 0.085 -5.254 ppm -2.495e+05 1.572e+07
Local Clock Time Offset -1,601.000 -764.000 -584.000 -46.000 502.000 690.000 929.000 1,086.000 1,454.000 324.669 -44.930 ns -4.88 12.21
Local RMS Frequency Jitter 64.000 87.000 107.000 155.000 211.000 245.000 332.000 104.000 158.000 32.483 157.272 10e-12 68.67 317.2
Local RMS Time Jitter 162.000 207.000 249.000 388.000 519.000 575.000 679.000 270.000 368.000 81.940 386.038 ns 62.28 275.5
Server Jitter 104.131.155.175 0.416 0.416 0.520 1.025 1.866 9.930 9.930 1.346 9.514 1.528 1.263 ms 4.659 26.15
Server Jitter 162.159.200.123 0.213 0.239 0.381 0.959 2.909 8.647 8.687 2.528 8.408 1.106 1.241 ms 4.728 29.84
Server Jitter 169.229.128.134 0.179 0.262 0.314 0.863 7.390 15.377 15.552 7.076 15.115 2.962 1.742 ms 2.292 10.41
Server Jitter 173.11.101.155 0.287 0.443 0.869 1.837 15.221 17.887 19.401 14.352 17.444 4.509 3.656 ms 1.477 4.552
Server Jitter 178.62.68.79 0.391 0.391 0.684 1.313 6.403 6.593 6.593 5.719 6.202 1.882 2.464 ms 1.811 4.037
Server Jitter 192.168.1.10 0.072 0.098 0.138 0.306 1.678 9.843 16.713 1.540 9.746 1.551 0.646 ms 4.469 35.95
Server Jitter 216.218.254.202 0.216 0.224 0.402 1.126 2.691 8.488 11.513 2.289 8.263 1.607 1.430 ms 3.83 19.56
Server Jitter 66.220.9.122 0.106 0.238 0.380 1.091 3.726 7.375 7.409 3.346 7.137 1.209 1.331 ms 3.605 16.82
Server Jitter SHM(0) 1.953 3.175 5.025 15.720 33.690 41.106 54.309 28.665 37.931 8.970 16.982 ms 4.102 11.11
Server Jitter SHM(1) 78.000 141.000 184.000 340.000 598.000 715.000 1,327.000 414.000 574.000 126.700 358.898 ns 12.54 42.29
Server Offset 104.131.155.175 1.767 1.767 1.886 2.890 3.719 3.803 3.803 1.833 2.037 0.530 2.793 ms 90.84 444.8
Server Offset 162.159.200.123 2.013 2.200 2.428 2.888 3.360 3.734 3.741 0.932 1.534 0.303 2.898 ms 652.1 5803
Server Offset 169.229.128.134 -0.433 2.022 2.185 2.612 3.037 3.394 3.551 0.852 1.372 0.351 2.601 ms 277.8 1862
Server Offset 173.11.101.155 -3.261 -2.657 -2.088 -0.243 0.732 1.454 1.982 2.820 4.112 0.772 -0.360 ms -8.362 27.05
Server Offset 178.62.68.79 -5.863 -5.863 -1.745 1.921 4.325 4.328 4.328 6.070 10.192 2.100 1.510 ms -2.802 10.13
Server Offset 192.168.1.10 -362.353 -133.455 -58.627 183.055 355.182 403.424 469.683 413.809 536.879 129.846 167.122 µs 0.4492 2.911
Server Offset 216.218.254.202 1.489 1.914 2.143 2.586 3.075 3.351 3.433 0.931 1.437 0.285 2.600 ms 560.9 4755
Server Offset 66.220.9.122 2.066 2.182 2.372 2.745 3.254 3.412 3.513 0.882 1.230 0.259 2.749 ms 914.7 9075
Server Offset SHM(0) -442.113 -422.540 -406.992 -360.608 -330.089 -318.797 -306.663 76.904 103.742 23.331 -363.535 ms -4609 7.728e+04
Server Offset SHM(1) -1,602.000 -765.000 -585.000 -47.000 503.000 691.000 930.000 1,088.000 1,456.000 325.436 -45.038 ns -4.879 12.19
TDOP 0.540 0.550 0.590 0.810 1.150 1.280 1.460 0.560 0.730 0.176 0.835 64.39 293.3
Temp ZONE0 45.622 45.622 46.160 47.236 48.850 49.388 49.388 2.690 3.766 0.885 47.242 °C
nSats 7.000 8.000 9.000 10.000 12.000 12.000 12.000 3.000 4.000 1.017 10.125 nSat 744.4 6906
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!