NTPsec

ntp1.wiktel.com

Report generated: Sat Jul 13 16:45:03 2024 UTC
Start Time: Sat Jul 6 16:45:01 2024 UTC
End Time: Sat Jul 13 16:45:01 2024 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 -1,262.583 -6.665 -4.681 -0.206 5.153 6.777 209.852 9.834 13.442 5.831 -0.006 µs -138.8 2.977e+04
Local Clock Frequency Offset 17.330 17.457 17.484 17.582 17.826 17.879 17.971 0.342 0.423 0.100 17.606 ppm 5.307e+06 9.258e+08

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.119 0.346 0.461 0.752 1.698 2.273 622.682 1.237 1.927 6.717 1.024 µs 59.21 4229

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.000 0.304 0.464 1.193 2.626 3.452 50.271 2.162 3.148 0.953 1.350 ppb 18.62 718.3

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,262.583 -6.665 -4.681 -0.206 5.153 6.777 209.852 9.834 13.442 5.831 -0.006 µs -138.8 2.977e+04

The clock offsets of the local clock as a histogram.

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



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 128.138.141.177

peer offset 128.138.141.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 128.138.141.177 -851.683 -397.207 -217.973 -76.414 219.971 396.678 584.272 437.944 793.885 142.878 -48.375 µs -5.849 16.47

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:2c8::2 (clock.nyc.he.net)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:0:2c8::2 (clock.nyc.he.net) -5.268 -1.018 -0.876 -0.749 -0.596 0.633 461.460 0.280 1.651 14.396 -0.270 ms 27.92 904.3

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 209.87.233.53

peer offset 209.87.233.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.87.233.53 -7.728 -2.936 -1.902 0.413 2.048 2.943 4.039 3.950 5.880 1.193 0.338 ms -3.397 12.26

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 209.87.233.54

peer offset 209.87.233.54 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.87.233.54 -15.273 -3.361 -1.518 1.709 4.294 5.362 463.241 5.812 8.723 33.041 3.959 ms 10.21 142.5

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

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

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

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



Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -0.230 -0.120 -0.091 -0.061 -0.040 -0.028 462.245 0.051 0.092 17.671 0.613 ms 22.29 587.1

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) -1.375 -1.314 -1.223 -1.015 -0.734 -0.552 -0.463 0.489 0.762 0.137 -1.013 ms -617.2 5380

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::123 (time.cloudflare.com)

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -6.948 -0.906 -0.791 -0.661 -0.175 0.437 461.992 0.617 1.343 29.851 1.294 ms 11.62 184.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 2607:f128:1:3::dd1 (dns1.steadfast.net)

peer offset 2607:f128:1:3::dd1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) 0.041 0.135 0.162 0.356 0.606 0.627 462.474 0.444 0.492 20.302 1.310 ms 19.04 436.1

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:1 (ntp1.doit.wisc.edu)

peer offset 2607:f388::123:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -13.197 -13.068 -13.044 -13.003 -12.962 -12.942 449.304 0.082 0.126 14.355 -12.557 ms 19.93 826.4

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 PPS(0)

peer offset PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset PPS(0) -127.711 -6.660 -4.682 -0.207 5.154 6.778 209.853 9.836 13.438 3.433 0.014 µs 1.8 397.3

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 128.138.141.177

peer jitter 128.138.141.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 128.138.141.177 0.000 0.238 0.365 0.602 0.878 1.799 4.056 0.514 1.560 0.283 0.627 ms 11.51 101.4

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:2c8::2 (clock.nyc.he.net)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:0:2c8::2 (clock.nyc.he.net) 0.000 0.008 0.011 0.025 0.134 3.703 14.545 0.123 3.694 0.786 0.131 ms 7.87 113.3

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 209.87.233.53

peer jitter 209.87.233.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.87.233.53 1.129 1.780 2.858 7.622 18.253 36.253 134.189 15.394 34.473 8.152 9.136 ms 8.536 116.3

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 209.87.233.54

peer jitter 209.87.233.54 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.87.233.54 0.000 1.744 3.250 8.776 18.546 25.808 67.564 15.296 24.065 5.819 9.692 ms 6.042 45.47

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::2 (time2.mbix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 0.000 8.195 11.182 23.271 45.516 56.062 1,197.035 34.334 47.867 35.780 26.079 µs 27.14 834.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 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.247 7.633 11.288 28.077 102.558 292.150 501.682 91.270 284.517 45.850 39.835 µs 4.645 33.18

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::123 (time.cloudflare.com)

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.007 0.011 0.027 0.186 0.407 6.283 0.174 0.400 0.294 0.062 ms 15.4 302.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:1:3::dd1 (dns1.steadfast.net)

peer jitter 2607:f128:1:3::dd1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 0.000 13.513 17.929 35.085 76.109 371.448 989.797 58.180 357.935 68.740 46.744 µs 7.227 76.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.



Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu)

peer jitter 2607:f388::123:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 0.000 0.025 0.037 0.099 4.878 7.571 159.197 4.841 7.545 8.084 1.174 ms 12.56 233.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 PPS(0)

peer jitter PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter PPS(0) 0.000 0.233 0.377 0.868 2.257 3.534 111.862 1.880 3.301 1.354 1.060 µs 44.05 2834

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 17.330 17.457 17.484 17.582 17.826 17.879 17.971 0.342 0.423 0.100 17.606 ppm 5.307e+06 9.258e+08
Local Clock Time Offset -1,262.583 -6.665 -4.681 -0.206 5.153 6.777 209.852 9.834 13.442 5.831 -0.006 µs -138.8 2.977e+04
Local RMS Frequency Jitter 0.000 0.304 0.464 1.193 2.626 3.452 50.271 2.162 3.148 0.953 1.350 ppb 18.62 718.3
Local RMS Time Jitter 0.119 0.346 0.461 0.752 1.698 2.273 622.682 1.237 1.927 6.717 1.024 µs 59.21 4229
Server Jitter 128.138.141.177 0.000 0.238 0.365 0.602 0.878 1.799 4.056 0.514 1.560 0.283 0.627 ms 11.51 101.4
Server Jitter 2001:470:0:2c8::2 (clock.nyc.he.net) 0.000 0.008 0.011 0.025 0.134 3.703 14.545 0.123 3.694 0.786 0.131 ms 7.87 113.3
Server Jitter 209.87.233.53 1.129 1.780 2.858 7.622 18.253 36.253 134.189 15.394 34.473 8.152 9.136 ms 8.536 116.3
Server Jitter 209.87.233.54 0.000 1.744 3.250 8.776 18.546 25.808 67.564 15.296 24.065 5.819 9.692 ms 6.042 45.47
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 0.000 8.195 11.182 23.271 45.516 56.062 1,197.035 34.334 47.867 35.780 26.079 µs 27.14 834.8
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 4.247 7.633 11.288 28.077 102.558 292.150 501.682 91.270 284.517 45.850 39.835 µs 4.645 33.18
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.007 0.011 0.027 0.186 0.407 6.283 0.174 0.400 0.294 0.062 ms 15.4 302.6
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 0.000 13.513 17.929 35.085 76.109 371.448 989.797 58.180 357.935 68.740 46.744 µs 7.227 76.72
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 0.000 0.025 0.037 0.099 4.878 7.571 159.197 4.841 7.545 8.084 1.174 ms 12.56 233.6
Server Jitter PPS(0) 0.000 0.233 0.377 0.868 2.257 3.534 111.862 1.880 3.301 1.354 1.060 µs 44.05 2834
Server Offset 128.138.141.177 -851.683 -397.207 -217.973 -76.414 219.971 396.678 584.272 437.944 793.885 142.878 -48.375 µs -5.849 16.47
Server Offset 2001:470:0:2c8::2 (clock.nyc.he.net) -5.268 -1.018 -0.876 -0.749 -0.596 0.633 461.460 0.280 1.651 14.396 -0.270 ms 27.92 904.3
Server Offset 209.87.233.53 -7.728 -2.936 -1.902 0.413 2.048 2.943 4.039 3.950 5.880 1.193 0.338 ms -3.397 12.26
Server Offset 209.87.233.54 -15.273 -3.361 -1.518 1.709 4.294 5.362 463.241 5.812 8.723 33.041 3.959 ms 10.21 142.5
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -0.230 -0.120 -0.091 -0.061 -0.040 -0.028 462.245 0.051 0.092 17.671 0.613 ms 22.29 587.1
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1.375 -1.314 -1.223 -1.015 -0.734 -0.552 -0.463 0.489 0.762 0.137 -1.013 ms -617.2 5380
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -6.948 -0.906 -0.791 -0.661 -0.175 0.437 461.992 0.617 1.343 29.851 1.294 ms 11.62 184.7
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) 0.041 0.135 0.162 0.356 0.606 0.627 462.474 0.444 0.492 20.302 1.310 ms 19.04 436.1
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -13.197 -13.068 -13.044 -13.003 -12.962 -12.942 449.304 0.082 0.126 14.355 -12.557 ms 19.93 826.4
Server Offset PPS(0) -127.711 -6.660 -4.682 -0.207 5.154 6.778 209.853 9.836 13.438 3.433 0.014 µs 1.8 397.3
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!