NTPsec

ntp2.wiktel.com

Report generated: Wed Nov 30 05:45:07 2022 UTC
Start Time: Wed Nov 23 05:45:01 2022 UTC
End Time: Wed Nov 30 05:45:01 2022 UTC
Report Period: 7.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 -30.172 -9.008 -5.445 0.403 3.060 4.347 9.379 8.505 13.355 2.518 0.001 µs -5.786 22.45
Local Clock Frequency Offset -14.485 -14.194 -14.086 -13.798 -12.704 -12.420 -12.259 1.382 1.774 0.412 -13.645 ppm -3.972e+04 1.357e+06

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.436 0.957 1.315 2.892 5.263 6.599 15.163 3.948 5.642 1.246 3.044 µs 8.128 25.56

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 0.794 1.517 2.079 4.420 7.652 9.482 21.199 5.573 7.965 1.757 4.595 ppb 9.734 30.59

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 -30.172 -9.008 -5.445 0.403 3.060 4.347 9.379 8.505 13.355 2.518 0.001 µs -5.786 22.45

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 4.000 6.000 7.000 9.000 11.000 12.000 13.000 4.000 6.000 1.301 8.765 nSat 206 1284
TDOP 0.520 0.560 0.620 0.860 1.380 1.960 10.910 0.760 1.400 0.402 0.924 17.74 309.5

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.707 1.726 1.753 2.009 2.959 3.021 3.132 1.205 1.295 0.241 2.028 ms 432 3449

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

peer offset 132.246.11.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.237 -4,310.786 691.305 715.709 736.598 754.365 771.890 947.111 38.656 80.585 196.610 727.323 µs 3.248 455.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 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 -359.808 -140.970 -91.306 6.318 101.893 178.782 358.250 193.199 319.752 59.859 5.547 µs -3.171 10.44

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 -511.116 -497.516 -488.331 -464.034 -452.621 -449.630 -443.621 35.710 47.886 11.329 -466.288 µs -7.505e+04 3.169e+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 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) -75.196 -64.469 -59.225 -44.348 -28.527 -23.653 -15.437 30.698 40.816 9.158 -44.147 µs -214.6 1353

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) 2.168 2.260 2.388 2.959 3.463 3.568 3.611 1.075 1.307 0.340 2.928 ms 465.7 3725

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) 0.646 0.856 1.161 1.279 1.455 1.919 2.536 0.293 1.063 0.153 1.297 ms 444 3584

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 258.607 291.066 308.531 345.656 380.048 396.028 415.292 71.517 104.962 21.795 345.251 µs 3313 4.983e+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 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) -111.731 -94.830 -82.669 -57.269 -31.861 -21.037 -2.119 50.808 73.793 15.149 -57.405 µs -124.2 666.8

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

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

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

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



Server Offset 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) -30.173 -9.009 -5.446 0.404 3.061 4.348 9.380 8.507 13.357 2.519 0.001 µs -5.784 22.44

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.000 0.000 0.000 33.687 79.271 937.408 1,109.991 79.271 937.408 149.269 60.114 µs 3.389 20.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 132.246.11.237

peer jitter 132.246.11.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.237 0.003 0.008 0.013 0.041 3.363 147.622 187.529 3.350 147.614 22.014 4.036 ms 3.377 28.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 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 1.861 3.691 5.557 16.041 51.548 82.732 218.395 45.991 79.041 16.643 20.739 µs 3.63 22.8

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 9.549 17.010 24.129 43.138 62.903 71.087 78.127 38.774 54.077 11.696 43.330 µs 27.96 100.8

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) 3.355 5.647 8.363 17.560 33.692 132.006 198.909 25.329 126.359 18.020 20.704 µs 5.877 40.79

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) 3.618 6.661 9.656 24.536 69.394 92.047 135.313 59.738 85.386 18.999 30.075 µs 3.351 10.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 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) 4.873 7.242 11.106 31.359 127.336 965.341 4,866.960 116.230 958.099 234.417 65.896 µs 10.4 181.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 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 4.863 10.442 14.143 29.902 62.286 104.094 1,374.524 48.143 93.652 62.644 37.186 µs 13.09 218.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 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) 0.004 0.009 0.016 1.028 12.836 18.228 26.903 12.821 18.219 4.522 3.500 ms 0.8071 3.94

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.103 0.409 0.630 2.421 6.806 9.529 29.953 6.176 9.120 2.024 2.873 µs 2.885 10.79

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.485 -14.194 -14.086 -13.798 -12.704 -12.420 -12.259 1.382 1.774 0.412 -13.645 ppm -3.972e+04 1.357e+06
Local Clock Time Offset -30.172 -9.008 -5.445 0.403 3.060 4.347 9.379 8.505 13.355 2.518 0.001 µs -5.786 22.45
Local RMS Frequency Jitter 0.794 1.517 2.079 4.420 7.652 9.482 21.199 5.573 7.965 1.757 4.595 ppb 9.734 30.59
Local RMS Time Jitter 0.436 0.957 1.315 2.892 5.263 6.599 15.163 3.948 5.642 1.246 3.044 µs 8.128 25.56
Server Jitter 132.163.97.5 0.000 0.000 0.000 33.687 79.271 937.408 1,109.991 79.271 937.408 149.269 60.114 µs 3.389 20.99
Server Jitter 132.246.11.237 0.003 0.008 0.013 0.041 3.363 147.622 187.529 3.350 147.614 22.014 4.036 ms 3.377 28.03
Server Jitter 134.84.84.84 1.861 3.691 5.557 16.041 51.548 82.732 218.395 45.991 79.041 16.643 20.739 µs 3.63 22.8
Server Jitter 204.9.54.119 9.549 17.010 24.129 43.138 62.903 71.087 78.127 38.774 54.077 11.696 43.330 µs 27.96 100.8
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 3.355 5.647 8.363 17.560 33.692 132.006 198.909 25.329 126.359 18.020 20.704 µs 5.877 40.79
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 3.618 6.661 9.656 24.536 69.394 92.047 135.313 59.738 85.386 18.999 30.075 µs 3.351 10.53
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 4.873 7.242 11.106 31.359 127.336 965.341 4,866.960 116.230 958.099 234.417 65.896 µs 10.4 181.1
Server Jitter 2607:f128::50 4.863 10.442 14.143 29.902 62.286 104.094 1,374.524 48.143 93.652 62.644 37.186 µs 13.09 218.2
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 0.004 0.009 0.016 1.028 12.836 18.228 26.903 12.821 18.219 4.522 3.500 ms 0.8071 3.94
Server Jitter SHM(1) 0.103 0.409 0.630 2.421 6.806 9.529 29.953 6.176 9.120 2.024 2.873 µs 2.885 10.79
Server Offset 132.163.97.5 1.707 1.726 1.753 2.009 2.959 3.021 3.132 1.205 1.295 0.241 2.028 ms 432 3449
Server Offset 132.246.11.237 -4,310.786 691.305 715.709 736.598 754.365 771.890 947.111 38.656 80.585 196.610 727.323 µs 3.248 455.2
Server Offset 134.84.84.84 -359.808 -140.970 -91.306 6.318 101.893 178.782 358.250 193.199 319.752 59.859 5.547 µs -3.171 10.44
Server Offset 204.9.54.119 -511.116 -497.516 -488.331 -464.034 -452.621 -449.630 -443.621 35.710 47.886 11.329 -466.288 µs -7.505e+04 3.169e+06
Server Offset 2600:2600::99 (ntp1.wiktel.com) -75.196 -64.469 -59.225 -44.348 -28.527 -23.653 -15.437 30.698 40.816 9.158 -44.147 µs -214.6 1353
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) 2.168 2.260 2.388 2.959 3.463 3.568 3.611 1.075 1.307 0.340 2.928 ms 465.7 3725
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 0.646 0.856 1.161 1.279 1.455 1.919 2.536 0.293 1.063 0.153 1.297 ms 444 3584
Server Offset 2607:f128::50 258.607 291.066 308.531 345.656 380.048 396.028 415.292 71.517 104.962 21.795 345.251 µs 3313 4.983e+04
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -111.731 -94.830 -82.669 -57.269 -31.861 -21.037 -2.119 50.808 73.793 15.149 -57.405 µs -124.2 666.8
Server Offset SHM(1) -30.173 -9.009 -5.446 0.404 3.061 4.348 9.380 8.507 13.357 2.519 0.001 µs -5.784 22.44
TDOP 0.520 0.560 0.620 0.860 1.380 1.960 10.910 0.760 1.400 0.402 0.924 17.74 309.5
nSats 4.000 6.000 7.000 9.000 11.000 12.000 13.000 4.000 6.000 1.301 8.765 nSat 206 1284
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!