NTPsec

ntp2.wiktel.com

Report generated: Fri Mar 1 00:53:02 2024 UTC
Start Time: Thu Feb 29 00:53:02 2024 UTC
End Time: Fri Mar 1 00:53:02 2024 UTC
Report Period: 1.0 days

Top   Daily Stats   Weekly Stats  

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 -25.512 -11.097 -7.166 0.699 3.625 5.103 8.934 10.791 16.200 3.223 -0.009 µs -5.802 21.58
Local Clock Frequency Offset -14.159 -14.103 -14.024 -13.827 -13.596 -13.322 -13.068 0.428 0.781 0.141 -13.816 ppm -9.604e+05 9.477e+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 0.736 1.352 1.895 3.933 6.700 8.241 14.314 4.805 6.889 1.492 4.065 µs 10.92 34.65

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 1.029 2.154 2.884 5.801 9.573 11.642 18.765 6.689 9.488 2.068 5.947 ppb 12.79 41.19

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 -25.512 -11.097 -7.166 0.699 3.625 5.103 8.934 10.791 16.200 3.223 -0.009 µs -5.802 21.58

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 6.000 6.000 7.000 9.000 11.000 11.000 12.000 4.000 5.000 1.115 8.937 nSat 366.3 2720
TDOP 0.550 0.590 0.630 0.830 1.330 1.690 2.730 0.700 1.100 0.255 0.896 26.13 120.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 132.163.97.5

peer offset 132.163.97.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.163.97.5 1.479 1.484 1.502 1.575 2.703 2.728 2.732 1.201 1.244 0.538 2.047 ms 30.67 111.7

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

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

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

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



Server Offset 132.246.11.238

peer offset 132.246.11.238 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.238 293.860 321.040 329.473 352.095 369.401 388.668 393.917 39.928 67.628 12.159 350.938 µs 2.171e+04 6.072e+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 134.84.84.84

peer offset 134.84.84.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 134.84.84.84 -224.533 -208.682 -82.176 -19.114 42.723 93.805 128.703 124.899 302.487 44.264 -20.274 µs -8.258 28.88

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

peer offset 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.9.54.119 -621.825 -621.151 -617.313 -611.317 -606.770 -605.695 -604.584 10.543 15.456 3.046 -611.538 µs -8.217e+06 1.658e+09

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 2600:2600::99 (ntp1.wiktel.com)

peer offset 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:2600::99 (ntp1.wiktel.com) -23.761 -10.888 -6.034 8.238 23.830 32.566 36.482 29.864 43.454 9.353 8.258 µs -0.2176 3.095

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 2602:fd53:11e:123::1 (time1.mbix.ca)

peer offset 2602:fd53:11e:123::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) 67.987 80.134 93.753 238.695 427.175 462.502 467.684 333.422 382.368 92.241 245.186 µs 10.04 30.27

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 2606:4700:f1::1 (time.cloudflare.com)

peer offset 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -311.622 -304.754 -214.256 90.103 706.819 796.191 829.927 921.075 1,100.945 251.693 149.851 µs -0.2835 2.943

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:f128::50

peer offset 2607:f128::50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f128::50 487.923 495.186 510.480 547.363 581.974 600.364 616.691 71.494 105.178 20.418 547.055 µs 1.724e+04 4.466e+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 2607:f388::123:2 (ntp2.doit.wisc.edu)

peer offset 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -80.373 -68.163 -58.444 -43.159 -21.877 -11.625 -5.454 36.567 56.538 11.207 -42.330 µs -123 655.6

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) -25.513 -11.098 -7.167 0.700 3.626 5.104 8.935 10.793 16.202 3.224 -0.009 µs -5.801 21.57

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 132.163.97.5

peer jitter 132.163.97.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.163.97.5 0.010 0.013 0.017 0.035 0.171 1.056 1.183 0.153 1.043 0.184 0.079 ms 2.793 15.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.



Server Jitter 132.246.11.238

peer jitter 132.246.11.238 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.238 0.008 0.010 0.014 0.053 1.913 3.554 11.027 1.899 3.544 0.889 0.353 ms 4.887 59.31

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 134.84.84.84

peer jitter 134.84.84.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 134.84.84.84 3.101 4.971 6.556 19.741 45.147 64.892 74.486 38.591 59.921 12.404 21.690 µs 3.801 11.52

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

peer jitter 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.9.54.119 1.062 2.351 4.184 8.482 14.585 20.746 282.282 10.401 18.395 22.548 10.477 µs 9.962 117.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 2600:2600::99 (ntp1.wiktel.com)

peer jitter 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 5.968 6.244 8.834 16.841 33.494 141.126 146.446 24.660 134.882 16.174 19.704 µs 6.451 48.86

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 2602:fd53:11e:123::1 (time1.mbix.ca)

peer jitter 2602:fd53:11e:123::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 5.055 5.672 7.114 14.313 31.314 52.421 192.391 24.200 46.749 12.742 16.560 µs 9.995 132.2

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 2606:4700:f1::1 (time.cloudflare.com)

peer jitter 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.004 0.006 0.009 0.024 0.168 1.351 2.856 0.159 1.345 0.275 0.075 ms 5.455 54.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 2607:f128::50

peer jitter 2607:f128::50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f128::50 6.573 10.203 14.121 29.533 59.023 80.585 110.780 44.902 70.382 14.732 32.005 µs 6.718 24.85

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:f388::123:2 (ntp2.doit.wisc.edu)

peer jitter 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 4.341 5.338 7.920 20.061 208.190 450.370 871.156 200.270 445.032 100.098 53.276 µs 3.351 26.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.



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.162 0.481 0.811 3.427 8.652 11.814 25.324 7.841 11.333 2.534 3.875 µs 3.062 10.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 -14.159 -14.103 -14.024 -13.827 -13.596 -13.322 -13.068 0.428 0.781 0.141 -13.816 ppm -9.604e+05 9.477e+07
Local Clock Time Offset -25.512 -11.097 -7.166 0.699 3.625 5.103 8.934 10.791 16.200 3.223 -0.009 µs -5.802 21.58
Local RMS Frequency Jitter 1.029 2.154 2.884 5.801 9.573 11.642 18.765 6.689 9.488 2.068 5.947 ppb 12.79 41.19
Local RMS Time Jitter 0.736 1.352 1.895 3.933 6.700 8.241 14.314 4.805 6.889 1.492 4.065 µs 10.92 34.65
Server Jitter 132.163.97.5 0.010 0.013 0.017 0.035 0.171 1.056 1.183 0.153 1.043 0.184 0.079 ms 2.793 15.53
Server Jitter 132.246.11.238 0.008 0.010 0.014 0.053 1.913 3.554 11.027 1.899 3.544 0.889 0.353 ms 4.887 59.31
Server Jitter 134.84.84.84 3.101 4.971 6.556 19.741 45.147 64.892 74.486 38.591 59.921 12.404 21.690 µs 3.801 11.52
Server Jitter 204.9.54.119 1.062 2.351 4.184 8.482 14.585 20.746 282.282 10.401 18.395 22.548 10.477 µs 9.962 117.6
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 5.968 6.244 8.834 16.841 33.494 141.126 146.446 24.660 134.882 16.174 19.704 µs 6.451 48.86
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 5.055 5.672 7.114 14.313 31.314 52.421 192.391 24.200 46.749 12.742 16.560 µs 9.995 132.2
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.004 0.006 0.009 0.024 0.168 1.351 2.856 0.159 1.345 0.275 0.075 ms 5.455 54.6
Server Jitter 2607:f128::50 6.573 10.203 14.121 29.533 59.023 80.585 110.780 44.902 70.382 14.732 32.005 µs 6.718 24.85
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 4.341 5.338 7.920 20.061 208.190 450.370 871.156 200.270 445.032 100.098 53.276 µs 3.351 26.29
Server Jitter SHM(1) 0.162 0.481 0.811 3.427 8.652 11.814 25.324 7.841 11.333 2.534 3.875 µs 3.062 10.58
Server Offset 132.163.97.5 1.479 1.484 1.502 1.575 2.703 2.728 2.732 1.201 1.244 0.538 2.047 ms 30.67 111.7
Server Offset 132.246.11.238 293.860 321.040 329.473 352.095 369.401 388.668 393.917 39.928 67.628 12.159 350.938 µs 2.171e+04 6.072e+05
Server Offset 134.84.84.84 -224.533 -208.682 -82.176 -19.114 42.723 93.805 128.703 124.899 302.487 44.264 -20.274 µs -8.258 28.88
Server Offset 204.9.54.119 -621.825 -621.151 -617.313 -611.317 -606.770 -605.695 -604.584 10.543 15.456 3.046 -611.538 µs -8.217e+06 1.658e+09
Server Offset 2600:2600::99 (ntp1.wiktel.com) -23.761 -10.888 -6.034 8.238 23.830 32.566 36.482 29.864 43.454 9.353 8.258 µs -0.2176 3.095
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) 67.987 80.134 93.753 238.695 427.175 462.502 467.684 333.422 382.368 92.241 245.186 µs 10.04 30.27
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -311.622 -304.754 -214.256 90.103 706.819 796.191 829.927 921.075 1,100.945 251.693 149.851 µs -0.2835 2.943
Server Offset 2607:f128::50 487.923 495.186 510.480 547.363 581.974 600.364 616.691 71.494 105.178 20.418 547.055 µs 1.724e+04 4.466e+05
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -80.373 -68.163 -58.444 -43.159 -21.877 -11.625 -5.454 36.567 56.538 11.207 -42.330 µs -123 655.6
Server Offset SHM(1) -25.513 -11.098 -7.167 0.700 3.626 5.104 8.935 10.793 16.202 3.224 -0.009 µs -5.801 21.57
TDOP 0.550 0.590 0.630 0.830 1.330 1.690 2.730 0.700 1.100 0.255 0.896 26.13 120.8
nSats 6.000 6.000 7.000 9.000 11.000 11.000 12.000 4.000 5.000 1.115 8.937 nSat 366.3 2720
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!