NTPsec

A-ntpsec-72-hour-stats

Report generated: Tue May 21 18:07:48 2024 UTC
Start Time: Sat May 18 18:07:46 2024 UTC
End Time: Tue May 21 18:07:46 2024 UTC
Report published: Tue May 21 11:08:03 AM 2024 PDT
Report Period: 3.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 -3.821 -1.829 -1.204 0.065 1.013 1.413 3.478 2.217 3.242 0.681 0.005 µs -4.443 12.49
Local Clock Frequency Offset -451.004 -447.418 -427.917 -261.703 -121.475 -110.046 -106.400 306.442 337.372 93.143 -271.150 ppb -71.69 329.8

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 0.353 0.483 0.571 0.843 1.244 1.471 2.240 0.673 0.988 0.211 0.869 µs 40.63 167.6

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 70.000 187.000 219.000 314.000 459.000 558.000 1,755.000 240.000 371.000 82.397 324.838 10e-12 36.88 184.6

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 -3.821 -1.829 -1.204 0.065 1.013 1.413 3.478 2.217 3.242 0.681 0.005 µs -4.443 12.49

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 -451.004 -447.418 -427.917 -261.703 -121.475 -110.046 -106.400 306.442 337.372 93.143 -271.150 ppb -71.69 329.8
Temp ZONE0 45.084 45.084 45.622 47.236 48.850 49.388 49.388 3.228 4.304 1.045 47.294 °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 8.000 10.000 12.000 13.000 14.000 4.000 5.000 1.146 9.747 nSat 446.4 3535
TDOP 0.480 0.520 0.560 0.820 1.230 1.400 2.070 0.670 0.880 0.208 0.849 39.29 160.8

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 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 3.562 3.581 3.719 3.962 4.517 4.746 4.772 0.797 1.166 0.236 4.004 ms 4114 6.648e+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 -0.555 0.684 1.203 2.355 2.691 2.876 4.996 1.488 2.192 0.468 2.237 ms 64.22 282

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

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

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

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



Server Offset 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -5.858 -2.862 -1.238 0.519 2.679 4.429 6.094 3.917 7.291 1.368 0.704 ms -1.623 6.243

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

peer offset 192.12.19.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.12.19.20 0.252 1.754 2.169 3.248 3.525 3.596 5.497 1.356 1.842 0.427 3.102 ms 263 1746

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 35.155.231.77

peer offset 35.155.231.77 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 35.155.231.77 2.971 2.971 2.971 3.382 3.383 3.383 3.383 0.412 0.412 0.194 3.245 ms 3936 6.262e+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 5.161.184.148

peer offset 5.161.184.148 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.184.148 4.553 5.643 5.774 6.084 6.325 6.683 7.203 0.551 1.040 0.211 6.072 ms 2.147e+04 5.983e+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 50.116.42.84

peer offset 50.116.42.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.116.42.84 1.815 1.897 2.552 3.434 4.178 4.910 5.027 1.626 3.014 0.549 3.375 ms 152 866.5

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 52.10.183.132

peer offset 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 52.10.183.132 1.960 1.973 2.170 3.297 4.391 5.308 5.508 2.221 3.336 0.635 3.315 ms 88.45 438.5

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 64.142.122.36

peer offset 64.142.122.36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.142.122.36 0.376 0.885 1.405 2.637 2.909 2.974 5.843 1.504 2.089 0.471 2.472 ms 88.6 428.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 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 0.373 1.918 2.337 3.409 3.664 3.764 5.677 1.327 1.846 0.443 3.257 ms 273.4 1838

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) -135.803 -134.622 -133.198 -130.233 -128.302 -127.505 -126.483 4.896 7.116 1.425 -130.478 ms -7.928e+05 7.339e+07

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) -3.822 -1.830 -1.205 0.066 1.014 1.414 3.479 2.219 3.244 0.681 0.006 µs -4.442 12.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 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 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.000 0.101 0.201 0.949 5.400 10.344 10.611 5.199 10.243 1.620 1.398 ms 2.481 11.96

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.000 0.113 0.178 0.861 5.543 15.274 16.706 5.366 15.161 2.209 1.554 ms 2.994 18.83

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.000 0.523 0.877 2.289 7.558 14.084 22.745 6.682 13.561 2.378 2.916 ms 3.839 20.87

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

peer jitter 192.12.19.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.12.19.20 0.000 0.107 0.197 1.018 6.513 10.898 32.238 6.316 10.791 2.760 1.818 ms 4.52 42.27

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 35.155.231.77

peer jitter 35.155.231.77 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 35.155.231.77 0.000 0.000 0.000 410.927 969.769 969.769 969.769 969.769 969.769 397.439 460.232 µs 0.6621 1.767

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 5.161.184.148

peer jitter 5.161.184.148 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.184.148 0.000 0.143 0.213 0.762 3.866 4.892 6.149 3.653 4.749 1.187 1.238 ms 1.793 5.814

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 50.116.42.84

peer jitter 50.116.42.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.116.42.84 0.000 0.156 0.227 1.079 5.545 7.440 12.399 5.317 7.284 1.816 1.696 ms 2.028 8.705

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 52.10.183.132

peer jitter 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 52.10.183.132 0.000 0.098 0.185 0.886 4.528 5.456 6.031 4.343 5.358 1.251 1.324 ms 1.956 6.25

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 64.142.122.36

peer jitter 64.142.122.36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.142.122.36 0.000 0.102 0.171 0.943 5.205 15.075 22.105 5.034 14.973 2.485 1.634 ms 3.854 28.54

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.000 0.106 0.210 0.996 5.971 19.810 23.320 5.761 19.704 2.700 1.759 ms 3.828 27.46

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.000 0.079 0.112 0.296 0.876 1.226 2.453 0.764 1.147 0.251 0.371 ms 3.196 11.32

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.000 0.300 0.412 0.810 1.619 2.133 4.627 1.207 1.833 0.384 0.885 µs 7.504 26.53

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 -451.004 -447.418 -427.917 -261.703 -121.475 -110.046 -106.400 306.442 337.372 93.143 -271.150 ppb -71.69 329.8
Local Clock Time Offset -3.821 -1.829 -1.204 0.065 1.013 1.413 3.478 2.217 3.242 0.681 0.005 µs -4.443 12.49
Local RMS Frequency Jitter 70.000 187.000 219.000 314.000 459.000 558.000 1,755.000 240.000 371.000 82.397 324.838 10e-12 36.88 184.6
Local RMS Time Jitter 0.353 0.483 0.571 0.843 1.244 1.471 2.240 0.673 0.988 0.211 0.869 µs 40.63 167.6
Server Jitter 162.159.200.1 0.000 0.101 0.201 0.949 5.400 10.344 10.611 5.199 10.243 1.620 1.398 ms 2.481 11.96
Server Jitter 169.229.128.134 0.000 0.113 0.178 0.861 5.543 15.274 16.706 5.366 15.161 2.209 1.554 ms 2.994 18.83
Server Jitter 173.11.101.155 0.000 0.523 0.877 2.289 7.558 14.084 22.745 6.682 13.561 2.378 2.916 ms 3.839 20.87
Server Jitter 192.12.19.20 0.000 0.107 0.197 1.018 6.513 10.898 32.238 6.316 10.791 2.760 1.818 ms 4.52 42.27
Server Jitter 35.155.231.77 0.000 0.000 0.000 410.927 969.769 969.769 969.769 969.769 969.769 397.439 460.232 µs 0.6621 1.767
Server Jitter 5.161.184.148 0.000 0.143 0.213 0.762 3.866 4.892 6.149 3.653 4.749 1.187 1.238 ms 1.793 5.814
Server Jitter 50.116.42.84 0.000 0.156 0.227 1.079 5.545 7.440 12.399 5.317 7.284 1.816 1.696 ms 2.028 8.705
Server Jitter 52.10.183.132 0.000 0.098 0.185 0.886 4.528 5.456 6.031 4.343 5.358 1.251 1.324 ms 1.956 6.25
Server Jitter 64.142.122.36 0.000 0.102 0.171 0.943 5.205 15.075 22.105 5.034 14.973 2.485 1.634 ms 3.854 28.54
Server Jitter 66.220.9.122 0.000 0.106 0.210 0.996 5.971 19.810 23.320 5.761 19.704 2.700 1.759 ms 3.828 27.46
Server Jitter SHM(0) 0.000 0.079 0.112 0.296 0.876 1.226 2.453 0.764 1.147 0.251 0.371 ms 3.196 11.32
Server Jitter SHM(1) 0.000 0.300 0.412 0.810 1.619 2.133 4.627 1.207 1.833 0.384 0.885 µs 7.504 26.53
Server Offset 162.159.200.1 3.562 3.581 3.719 3.962 4.517 4.746 4.772 0.797 1.166 0.236 4.004 ms 4114 6.648e+04
Server Offset 169.229.128.134 -0.555 0.684 1.203 2.355 2.691 2.876 4.996 1.488 2.192 0.468 2.237 ms 64.22 282
Server Offset 173.11.101.155 -5.858 -2.862 -1.238 0.519 2.679 4.429 6.094 3.917 7.291 1.368 0.704 ms -1.623 6.243
Server Offset 192.12.19.20 0.252 1.754 2.169 3.248 3.525 3.596 5.497 1.356 1.842 0.427 3.102 ms 263 1746
Server Offset 35.155.231.77 2.971 2.971 2.971 3.382 3.383 3.383 3.383 0.412 0.412 0.194 3.245 ms 3936 6.262e+04
Server Offset 5.161.184.148 4.553 5.643 5.774 6.084 6.325 6.683 7.203 0.551 1.040 0.211 6.072 ms 2.147e+04 5.983e+05
Server Offset 50.116.42.84 1.815 1.897 2.552 3.434 4.178 4.910 5.027 1.626 3.014 0.549 3.375 ms 152 866.5
Server Offset 52.10.183.132 1.960 1.973 2.170 3.297 4.391 5.308 5.508 2.221 3.336 0.635 3.315 ms 88.45 438.5
Server Offset 64.142.122.36 0.376 0.885 1.405 2.637 2.909 2.974 5.843 1.504 2.089 0.471 2.472 ms 88.6 428.9
Server Offset 66.220.9.122 0.373 1.918 2.337 3.409 3.664 3.764 5.677 1.327 1.846 0.443 3.257 ms 273.4 1838
Server Offset SHM(0) -135.803 -134.622 -133.198 -130.233 -128.302 -127.505 -126.483 4.896 7.116 1.425 -130.478 ms -7.928e+05 7.339e+07
Server Offset SHM(1) -3.822 -1.830 -1.205 0.066 1.014 1.414 3.479 2.219 3.244 0.681 0.006 µs -4.442 12.48
TDOP 0.480 0.520 0.560 0.820 1.230 1.400 2.070 0.670 0.880 0.208 0.849 39.29 160.8
Temp ZONE0 45.084 45.084 45.622 47.236 48.850 49.388 49.388 3.228 4.304 1.045 47.294 °C
nSats 7.000 8.000 8.000 10.000 12.000 13.000 14.000 4.000 5.000 1.146 9.747 nSat 446.4 3535
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!