NTPsec

B-ntpsec-3-hour-stats

Report generated: Wed Nov 20 17:03:49 2019 UTC
Start Time: Wed Nov 20 14:03:48 2019 UTC
End Time: Wed Nov 20 17:03:48 2019 UTC
Report published: Wed Nov 20 09:04:01 2019 PST
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 -644.000 -559.000 -397.000 -85.000 277.000 388.000 612.000 674.000 947.000 205.622 -80.933 ns -6.771 17.61
Local Clock Frequency Offset -5.628 -5.627 -5.627 -5.619 -5.612 -5.611 -5.611 0.0151 0.0162 0.0049 -5.619 ppm -1.506e+09 1.726e+12

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 122.000 139.000 153.000 201.000 276.000 318.000 348.000 123.000 179.000 38.144 206.726 ns 100.3 514

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 29.000 32.000 36.000 51.000 78.000 90.000 104.000 42.000 58.000 12.669 53.066 10e-12 42.93 180.5

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 -644.000 -559.000 -397.000 -85.000 277.000 388.000 612.000 674.000 947.000 205.622 -80.933 ns -6.771 17.61

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.628 -5.627 -5.627 -5.619 -5.612 -5.611 -5.611 0.0151 0.0162 0.0049 -5.619 ppm -1.506e+09 1.726e+12
Temp ZONE0 58.534 58.534 59.072 59.610 60.148 60.148 60.148 1.076 1.614 0.410 59.425 °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 11.000 11.000 12.000 3.000 3.000 0.781 9.601 nSat 1472 1.699e+04
TDOP 0.500 0.570 0.600 0.780 1.140 1.340 1.350 0.540 0.770 0.193 0.842 49.14 209.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. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



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 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 -51.694 -41.438 -16.088 36.514 67.151 82.255 164.928 83.239 123.693 24.680 33.891 µs 1.259 10.11

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 2001:470:0:50::2 (clock.fmt.he.net)

peer offset 2001:470:0:50::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 1.958 1.958 2.092 2.478 2.937 2.950 2.950 0.845 0.992 0.263 2.467 ms 615.8 5386

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 2001:470:e815::24 (pi4.rellim.com)

peer offset 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.123 3.123 3.526 4.040 4.799 4.959 4.959 1.273 1.836 0.324 4.031 ms 1528 1.787e+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 2405:fc00:0:1::123

peer offset 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00:0:1::123 -1.459 -1.459 -1.420 -1.002 -0.474 -0.236 -0.236 0.947 1.223 0.266 -0.999 ms -121 638

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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 1.907 1.907 2.087 2.349 3.474 3.581 3.581 1.386 1.674 0.317 2.395 ms 303.2 2170

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 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu)

peer offset 2607:f140:ffff:8000:0:8006:0:a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 1.699 1.699 1.818 2.285 2.561 3.042 3.042 0.743 1.343 0.227 2.278 ms 764.6 7170

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 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com)

peer offset 2a03:b0c0:1:d0::1f9:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -9.031 -9.031 -6.790 1.274 2.410 2.438 2.438 9.200 11.469 2.166 0.869 ms -5.738 27.24

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 76.14.161.109

peer offset 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 76.14.161.109 -3.065 -3.065 -3.002 -0.634 0.217 0.314 0.314 3.219 3.379 0.888 -0.943 ms -15.68 52.35

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) -415.852 -406.547 -396.770 -369.731 -339.010 -328.632 -305.416 57.759 77.915 17.564 -368.815 ms -1.071e+04 2.371e+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) -645.000 -560.000 -398.000 -86.000 278.000 389.000 613.000 676.000 949.000 206.355 -81.227 ns -6.768 17.58

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 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.045 0.081 0.127 1.121 6.187 9.917 10.026 6.060 9.836 1.849 1.664 ms 1.982 8.244

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 2001:470:0:50::2 (clock.fmt.he.net)

peer jitter 2001:470:0:50::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.551 0.551 0.809 1.849 8.383 19.155 19.155 7.574 18.604 4.075 3.377 ms 2.058 8.106

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 2001:470:e815::24 (pi4.rellim.com)

peer jitter 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.516 0.516 0.547 1.704 57.092 57.232 57.232 56.544 56.716 16.424 9.500 ms 0.7712 3.737

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 2405:fc00:0:1::123

peer jitter 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2405:fc00:0:1::123 0.596 0.596 0.730 1.578 5.072 7.090 7.090 4.342 6.494 1.493 2.091 ms 2.9 8.865

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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer jitter 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.557 0.557 0.832 2.499 19.611 19.769 19.769 18.779 19.212 4.764 4.327 ms 1.684 5.629

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 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu)

peer jitter 2607:f140:ffff:8000:0:8006:0:a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.871 0.871 0.900 2.287 6.621 8.489 8.489 5.722 7.618 1.880 2.840 ms 2.879 7.983

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 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com)

peer jitter 2a03:b0c0:1:d0::1f9:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 1.137 1.137 1.234 2.215 9.245 11.576 11.576 8.010 10.439 2.500 3.367 ms 2.84 8.397

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 76.14.161.109

peer jitter 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 76.14.161.109 1.446 1.446 1.944 14.277 94.102 123.123 123.123 92.159 121.677 33.147 27.104 ms 0.8557 2.905

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) 3.321 5.061 6.588 12.114 24.200 32.859 50.895 17.612 27.798 5.726 13.372 ms 7.925 29.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 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) 53.000 87.000 113.000 203.000 394.000 475.000 545.000 281.000 388.000 84.245 218.544 ns 9.9 32.72

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.628 -5.627 -5.627 -5.619 -5.612 -5.611 -5.611 0.0151 0.0162 0.0049 -5.619 ppm -1.506e+09 1.726e+12
Local Clock Time Offset -644.000 -559.000 -397.000 -85.000 277.000 388.000 612.000 674.000 947.000 205.622 -80.933 ns -6.771 17.61
Local RMS Frequency Jitter 29.000 32.000 36.000 51.000 78.000 90.000 104.000 42.000 58.000 12.669 53.066 10e-12 42.93 180.5
Local RMS Time Jitter 122.000 139.000 153.000 201.000 276.000 318.000 348.000 123.000 179.000 38.144 206.726 ns 100.3 514
Server Jitter 192.168.1.10 0.045 0.081 0.127 1.121 6.187 9.917 10.026 6.060 9.836 1.849 1.664 ms 1.982 8.244
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.551 0.551 0.809 1.849 8.383 19.155 19.155 7.574 18.604 4.075 3.377 ms 2.058 8.106
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.516 0.516 0.547 1.704 57.092 57.232 57.232 56.544 56.716 16.424 9.500 ms 0.7712 3.737
Server Jitter 2405:fc00:0:1::123 0.596 0.596 0.730 1.578 5.072 7.090 7.090 4.342 6.494 1.493 2.091 ms 2.9 8.865
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.557 0.557 0.832 2.499 19.611 19.769 19.769 18.779 19.212 4.764 4.327 ms 1.684 5.629
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.871 0.871 0.900 2.287 6.621 8.489 8.489 5.722 7.618 1.880 2.840 ms 2.879 7.983
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 1.137 1.137 1.234 2.215 9.245 11.576 11.576 8.010 10.439 2.500 3.367 ms 2.84 8.397
Server Jitter 76.14.161.109 1.446 1.446 1.944 14.277 94.102 123.123 123.123 92.159 121.677 33.147 27.104 ms 0.8557 2.905
Server Jitter SHM(0) 3.321 5.061 6.588 12.114 24.200 32.859 50.895 17.612 27.798 5.726 13.372 ms 7.925 29.03
Server Jitter SHM(1) 53.000 87.000 113.000 203.000 394.000 475.000 545.000 281.000 388.000 84.245 218.544 ns 9.9 32.72
Server Offset 192.168.1.10 -51.694 -41.438 -16.088 36.514 67.151 82.255 164.928 83.239 123.693 24.680 33.891 µs 1.259 10.11
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 1.958 1.958 2.092 2.478 2.937 2.950 2.950 0.845 0.992 0.263 2.467 ms 615.8 5386
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.123 3.123 3.526 4.040 4.799 4.959 4.959 1.273 1.836 0.324 4.031 ms 1528 1.787e+04
Server Offset 2405:fc00:0:1::123 -1.459 -1.459 -1.420 -1.002 -0.474 -0.236 -0.236 0.947 1.223 0.266 -0.999 ms -121 638
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 1.907 1.907 2.087 2.349 3.474 3.581 3.581 1.386 1.674 0.317 2.395 ms 303.2 2170
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 1.699 1.699 1.818 2.285 2.561 3.042 3.042 0.743 1.343 0.227 2.278 ms 764.6 7170
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -9.031 -9.031 -6.790 1.274 2.410 2.438 2.438 9.200 11.469 2.166 0.869 ms -5.738 27.24
Server Offset 76.14.161.109 -3.065 -3.065 -3.002 -0.634 0.217 0.314 0.314 3.219 3.379 0.888 -0.943 ms -15.68 52.35
Server Offset SHM(0) -415.852 -406.547 -396.770 -369.731 -339.010 -328.632 -305.416 57.759 77.915 17.564 -368.815 ms -1.071e+04 2.371e+05
Server Offset SHM(1) -645.000 -560.000 -398.000 -86.000 278.000 389.000 613.000 676.000 949.000 206.355 -81.227 ns -6.768 17.58
TDOP 0.500 0.570 0.600 0.780 1.140 1.340 1.350 0.540 0.770 0.193 0.842 49.14 209.3
Temp ZONE0 58.534 58.534 59.072 59.610 60.148 60.148 60.148 1.076 1.614 0.410 59.425 °C
nSats 8.000 8.000 8.000 10.000 11.000 11.000 12.000 3.000 3.000 0.781 9.601 nSat 1472 1.699e+04
Summary as CSV file


Glossary:

frequency offset:
The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
jitter, dispersion:
The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Server Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of kurtosis. A normal distribution has a kurtosis of three. NIST describes a kurtosis over three as "heavy tailed" and one under three as "light tailed".
ms, millisecond:
One thousandth of a second = 0.001 seconds, 1e-3 seconds
mu, mean:
The arithmetic mean: the sum of all the values divided by the number of values. The formula for mu is: "mu = (∑xi) / N". Where xi denotes the data points and N is the number of data points.
ns, nanosecond:
One billionth of a second, also one thousandth of a microsecond, 0.000000001 seconds and 1e-9 seconds.
percentile:
The value below which a given percentage of values fall.
ppb, parts per billion:
Ratio between two values. These following are all the same: 1 ppb, one in one billion, 1/1,000,000,000, 0.000,000,001, 1e-9 and 0.000,000,1%
ppm, parts per million:
Ratio between two values. These following are all the same: 1 ppm, one in one million, 1/1,000,000, 0.000,001, and 0.000,1%
‰, parts per thousand:
Ratio between two values. These following are all the same: 1 ‰. one in one thousand, 1/1,000, 0.001, and 0.1%
refclock:
Reference clock, a local GPS module or other local source of time.
remote clock:
Any clock reached over the network, LAN or WAN. Also called a peer or server.
time offset:
The difference between the ntpd calculated time and the local system clock's time. Also called phase offset.
σ, sigma:
Sigma denotes the standard deviation (SD) and is centered on the arithmetic mean of the data set. The SD is simply the square root of the variance of the data set. Two sigma is simply twice the standard deviation. Three sigma is three times sigma. Smaller is better.
The formula for sigma is: "σ = √[ ∑(xi-mu)^2 / N ]". Where xi denotes the data points and N is the number of data points.
skewness, Skew:
The skewness of a random variable X is the third standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
upstream clock:
Any server or reference clock used as a source of time.
µs, us, microsecond:
One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.



This page autogenerated by ntpviz, part of the NTPsec project
html 5    Valid CSS!