NTPsec

A-ntpsec-3-hour-stats

Report generated: Sat May 28 17:02:21 2022 UTC
Start Time: Sat May 28 14:02:21 2022 UTC
End Time: Sat May 28 17:02:21 2022 UTC
Report published: Sat May 28 10:02:27 2022 PDT
Report Period: 0.1 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.020 -0.799 -0.521 0.075 0.763 1.066 1.419 1.284 1.865 0.389 0.083 µs -2.68 6.75
Local Clock Frequency Offset -73.532 -73.380 -72.937 -66.055 -59.692 -59.158 -59.021 13.245 14.222 4.099 -66.238 ppb -5105 8.849e+04

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 306.000 329.000 359.000 509.000 668.000 752.000 780.000 309.000 423.000 91.820 511.197 ns 109.2 567.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 53.000 59.000 66.000 93.000 132.000 153.000 170.000 66.000 94.000 19.611 95.168 10e-12 69.44 323.7

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.020 -0.799 -0.521 0.075 0.763 1.066 1.419 1.284 1.865 0.389 0.083 µs -2.68 6.75

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 -73.532 -73.380 -72.937 -66.055 -59.692 -59.158 -59.021 13.245 14.222 4.099 -66.238 ppb -5105 8.849e+04
Temp ZONE0 52.616 52.616 52.616 53.154 53.692 53.692 53.692 1.076 1.076 0.372 53.017 °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 8.000 8.000 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.008 9.872 nSat 705.6 6447
TDOP 0.600 0.600 0.610 0.940 1.210 1.240 1.240 0.600 0.640 0.206 0.905 49.13 202.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 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 4.746 4.746 4.779 5.124 5.319 5.365 5.365 0.541 0.620 0.152 5.103 ms 3.484e+04 1.14e+06

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 2.217 2.217 2.255 2.436 2.642 2.702 2.702 0.387 0.485 0.115 2.441 ms 8262 1.679e+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 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 -0.478 -0.478 -0.458 -0.035 0.663 1.174 1.174 1.120 1.652 0.328 0.012 ms -2.532 6.894

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

peer offset 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.11 -137.958 -117.033 -91.541 -38.660 29.242 39.519 41.545 120.783 156.552 39.142 -35.449 µs -12.65 37.2

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

peer offset 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.12 -182.622 -173.013 -159.387 -75.456 11.542 45.069 95.538 170.929 218.082 48.187 -70.912 µs -22.28 74.95

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 194.58.207.79

peer offset 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.79 5.355 5.355 5.401 5.674 5.927 5.976 5.976 0.525 0.622 0.144 5.677 ms 5.674e+04 2.183e+06

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 194.58.207.80

peer offset 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.80 5.463 5.463 7.013 7.610 7.894 8.048 8.048 0.882 2.585 0.394 7.533 ms 5988 1.092e+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 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 1.258 1.258 1.258 1.641 1.884 1.884 1.884 0.626 0.626 0.204 1.634 ms 367.6 2726

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

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 2.438 2.438 2.453 2.618 2.817 2.884 2.884 0.365 0.446 0.115 2.623 ms 1.057e+04 2.33e+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 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 2.297 2.297 2.363 2.600 2.765 3.094 3.094 0.402 0.797 0.163 2.589 ms 3343 5.047e+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(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) -56.562 -55.756 -55.224 -50.374 -46.648 -45.227 -44.593 8.576 10.529 2.640 -50.551 ms -8242 1.673e+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.021 -0.800 -0.522 0.076 0.764 1.067 1.420 1.286 1.867 0.389 0.084 µs -2.682 6.747

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.164 0.164 0.206 0.428 2.852 2.940 2.940 2.646 2.776 0.784 0.766 ms 1.798 4.751

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.101 0.101 0.133 0.894 18.092 18.170 18.170 17.959 18.069 5.095 2.675 ms 0.8469 4.013

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 1.001 1.001 1.120 1.649 2.477 16.114 16.114 1.357 15.114 2.314 2.048 ms 5.396 32.44

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

peer jitter 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.11 11.075 22.434 40.815 97.320 398.279 826.549 837.667 357.464 804.115 141.100 146.341 µs 3.027 13.19

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

peer jitter 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.12 24.417 24.728 38.845 116.881 624.101 842.681 869.862 585.256 817.953 173.267 182.345 µs 2.223 7.069

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 194.58.207.79

peer jitter 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.79 0.201 0.201 0.204 0.806 18.390 19.803 19.803 18.185 19.602 4.717 2.470 ms 1.411 5.988

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 194.58.207.80

peer jitter 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.80 0.152 0.152 0.221 0.621 20.078 20.148 20.148 19.856 19.996 6.026 2.799 ms 0.7338 3.741

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 318.520 318.520 318.520 490.390 983.350 983.350 983.350 664.830 664.830 199.297 512.777 µs 10.03 33.99

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

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.263 0.263 0.273 0.893 1.401 1.434 1.434 1.128 1.171 0.384 0.792 ms 4.437 9.786

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.145 0.145 0.236 1.175 2.698 4.064 4.064 2.462 3.918 0.859 1.391 ms 3.228 10.1

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.122 0.196 0.303 0.854 2.334 3.252 4.410 2.031 3.056 0.646 1.019 ms 3.448 11.6

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.147 0.184 0.234 0.451 0.891 1.143 1.359 0.657 0.959 0.196 0.493 µs 9.152 30.58

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 -73.532 -73.380 -72.937 -66.055 -59.692 -59.158 -59.021 13.245 14.222 4.099 -66.238 ppb -5105 8.849e+04
Local Clock Time Offset -1.020 -0.799 -0.521 0.075 0.763 1.066 1.419 1.284 1.865 0.389 0.083 µs -2.68 6.75
Local RMS Frequency Jitter 53.000 59.000 66.000 93.000 132.000 153.000 170.000 66.000 94.000 19.611 95.168 10e-12 69.44 323.7
Local RMS Time Jitter 306.000 329.000 359.000 509.000 668.000 752.000 780.000 309.000 423.000 91.820 511.197 ns 109.2 567.5
Server Jitter 162.159.200.1 0.164 0.164 0.206 0.428 2.852 2.940 2.940 2.646 2.776 0.784 0.766 ms 1.798 4.751
Server Jitter 169.229.128.134 0.101 0.101 0.133 0.894 18.092 18.170 18.170 17.959 18.069 5.095 2.675 ms 0.8469 4.013
Server Jitter 173.11.101.155 1.001 1.001 1.120 1.649 2.477 16.114 16.114 1.357 15.114 2.314 2.048 ms 5.396 32.44
Server Jitter 192.168.1.11 11.075 22.434 40.815 97.320 398.279 826.549 837.667 357.464 804.115 141.100 146.341 µs 3.027 13.19
Server Jitter 192.168.1.12 24.417 24.728 38.845 116.881 624.101 842.681 869.862 585.256 817.953 173.267 182.345 µs 2.223 7.069
Server Jitter 194.58.207.79 0.201 0.201 0.204 0.806 18.390 19.803 19.803 18.185 19.602 4.717 2.470 ms 1.411 5.988
Server Jitter 194.58.207.80 0.152 0.152 0.221 0.621 20.078 20.148 20.148 19.856 19.996 6.026 2.799 ms 0.7338 3.741
Server Jitter 204.17.205.24 318.520 318.520 318.520 490.390 983.350 983.350 983.350 664.830 664.830 199.297 512.777 µs 10.03 33.99
Server Jitter 216.218.192.202 0.263 0.263 0.273 0.893 1.401 1.434 1.434 1.128 1.171 0.384 0.792 ms 4.437 9.786
Server Jitter 216.218.254.202 0.145 0.145 0.236 1.175 2.698 4.064 4.064 2.462 3.918 0.859 1.391 ms 3.228 10.1
Server Jitter SHM(0) 0.122 0.196 0.303 0.854 2.334 3.252 4.410 2.031 3.056 0.646 1.019 ms 3.448 11.6
Server Jitter SHM(1) 0.147 0.184 0.234 0.451 0.891 1.143 1.359 0.657 0.959 0.196 0.493 µs 9.152 30.58
Server Offset 162.159.200.1 4.746 4.746 4.779 5.124 5.319 5.365 5.365 0.541 0.620 0.152 5.103 ms 3.484e+04 1.14e+06
Server Offset 169.229.128.134 2.217 2.217 2.255 2.436 2.642 2.702 2.702 0.387 0.485 0.115 2.441 ms 8262 1.679e+05
Server Offset 173.11.101.155 -0.478 -0.478 -0.458 -0.035 0.663 1.174 1.174 1.120 1.652 0.328 0.012 ms -2.532 6.894
Server Offset 192.168.1.11 -137.958 -117.033 -91.541 -38.660 29.242 39.519 41.545 120.783 156.552 39.142 -35.449 µs -12.65 37.2
Server Offset 192.168.1.12 -182.622 -173.013 -159.387 -75.456 11.542 45.069 95.538 170.929 218.082 48.187 -70.912 µs -22.28 74.95
Server Offset 194.58.207.79 5.355 5.355 5.401 5.674 5.927 5.976 5.976 0.525 0.622 0.144 5.677 ms 5.674e+04 2.183e+06
Server Offset 194.58.207.80 5.463 5.463 7.013 7.610 7.894 8.048 8.048 0.882 2.585 0.394 7.533 ms 5988 1.092e+05
Server Offset 204.17.205.24 1.258 1.258 1.258 1.641 1.884 1.884 1.884 0.626 0.626 0.204 1.634 ms 367.6 2726
Server Offset 216.218.192.202 2.438 2.438 2.453 2.618 2.817 2.884 2.884 0.365 0.446 0.115 2.623 ms 1.057e+04 2.33e+05
Server Offset 216.218.254.202 2.297 2.297 2.363 2.600 2.765 3.094 3.094 0.402 0.797 0.163 2.589 ms 3343 5.047e+04
Server Offset SHM(0) -56.562 -55.756 -55.224 -50.374 -46.648 -45.227 -44.593 8.576 10.529 2.640 -50.551 ms -8242 1.673e+05
Server Offset SHM(1) -1.021 -0.800 -0.522 0.076 0.764 1.067 1.420 1.286 1.867 0.389 0.084 µs -2.682 6.747
TDOP 0.600 0.600 0.610 0.940 1.210 1.240 1.240 0.600 0.640 0.206 0.905 49.13 202.3
Temp ZONE0 52.616 52.616 52.616 53.154 53.692 53.692 53.692 1.076 1.076 0.372 53.017 °C
nSats 8.000 8.000 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.008 9.872 nSat 705.6 6447
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!