NTPsec

ntp1.wiktel.com

Report generated: Thu Apr 3 06:53:02 2025 UTC
Start Time: Wed Apr 2 06:53:02 2025 UTC
End Time: Thu Apr 3 06:53:02 2025 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 -6.968 -1.797 -1.158 0.038 1.217 1.750 3.771 2.375 3.547 0.786 0.026 µs -4.775 19.59
Local Clock Frequency Offset 17.808 17.815 17.824 17.949 18.013 18.024 18.030 0.190 0.209 0.060 17.924 ppm 2.629e+07 7.817e+09

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.305 0.398 0.462 0.687 1.440 2.394 3.608 0.978 1.996 0.350 0.772 µs 8.355 40.01

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 136.000 180.000 207.000 329.000 626.000 853.000 1,238.000 419.000 673.000 134.806 359.819 10e-12 11.35 43.01

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 -6.968 -1.797 -1.158 0.038 1.217 1.750 3.771 2.375 3.547 0.786 0.026 µs -4.775 19.59

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

peer offset 128.101.101.101 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 128.101.101.101 -128.813 -99.493 -60.712 30.588 110.389 183.535 224.175 171.101 283.028 50.865 25.821 µs -1.409 5.475

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 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 -166.739 -144.169 -101.458 14.504 257.190 435.736 486.452 358.648 579.905 114.468 46.759 µs -1.042 3.772

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) -415.354 -406.409 -307.036 -238.108 -176.726 -149.714 -141.275 130.310 256.695 44.511 -240.791 µs -283.4 1961

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 -8.760 -4.433 -1.940 1.015 3.287 4.189 5.144 5.227 8.622 1.644 0.874 ms -2.692 11.19

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) -94.926 -93.401 -71.323 -36.552 -17.511 -12.364 -0.842 53.812 81.037 16.392 -39.036 µs -49.67 214.9

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) -353.009 -349.459 -340.816 -280.854 -228.607 -190.193 -187.086 112.209 159.266 35.211 -284.549 µs -776 7291

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) -352.492 -351.136 -339.029 -287.054 156.235 163.950 169.105 495.264 515.086 114.258 -247.311 µs -38.62 137.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 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) -349.625 -342.368 -329.583 -287.475 -247.044 -219.108 -206.799 82.539 123.260 25.345 -287.471 µs -1917 2.411e+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: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) -111.904 -106.247 -78.458 -27.285 9.245 18.394 23.081 87.703 124.641 25.655 -30.725 µs -17.85 61.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 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) -6.969 -1.798 -1.159 0.039 1.218 1.751 3.772 2.377 3.549 0.786 0.026 µs -4.773 19.56

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

peer jitter 128.101.101.101 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 128.101.101.101 6.758 7.143 10.788 24.155 60.864 71.865 83.969 50.076 64.722 15.029 27.681 µs 4.242 12.27

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 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 261.058 293.183 376.219 627.534 873.211 970.193 1,034.483 496.992 677.010 143.114 623.659 µs 48.02 198.9

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) 5.994 8.278 11.760 22.004 45.408 94.058 1,540.769 33.648 85.780 89.296 29.750 µs 14.25 238.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 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 0.968 2.233 3.505 10.409 31.403 121.521 149.226 27.898 119.288 18.432 14.461 ms 4.267 26.82

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) 4.137 6.780 10.042 21.947 37.583 50.650 189.220 27.541 43.870 13.244 22.917 µs 9.487 109

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) 5.260 5.807 8.487 21.032 60.211 99.710 147.016 51.724 93.903 19.133 25.850 µs 4.153 21.19

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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) 6.585 8.091 11.739 23.243 54.929 269.243 383.135 43.190 261.152 40.241 31.485 µs 5.809 45.36

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) 14.092 14.955 19.044 33.937 66.540 143.718 307.279 47.496 128.763 27.969 39.224 µs 7.788 70.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) 5.699 6.670 10.788 21.566 41.768 66.209 105.075 30.980 59.539 11.803 23.666 µs 6.748 35.27

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.103 0.255 0.340 0.663 1.620 2.632 7.138 1.280 2.377 0.492 0.782 µs 5.752 39.54

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.808 17.815 17.824 17.949 18.013 18.024 18.030 0.190 0.209 0.060 17.924 ppm 2.629e+07 7.817e+09
Local Clock Time Offset -6.968 -1.797 -1.158 0.038 1.217 1.750 3.771 2.375 3.547 0.786 0.026 µs -4.775 19.59
Local RMS Frequency Jitter 136.000 180.000 207.000 329.000 626.000 853.000 1,238.000 419.000 673.000 134.806 359.819 10e-12 11.35 43.01
Local RMS Time Jitter 0.305 0.398 0.462 0.687 1.440 2.394 3.608 0.978 1.996 0.350 0.772 µs 8.355 40.01
Server Jitter 128.101.101.101 6.758 7.143 10.788 24.155 60.864 71.865 83.969 50.076 64.722 15.029 27.681 µs 4.242 12.27
Server Jitter 128.138.141.177 261.058 293.183 376.219 627.534 873.211 970.193 1,034.483 496.992 677.010 143.114 623.659 µs 48.02 198.9
Server Jitter 2001:470:0:2c8::2 (clock.nyc.he.net) 5.994 8.278 11.760 22.004 45.408 94.058 1,540.769 33.648 85.780 89.296 29.750 µs 14.25 238.6
Server Jitter 209.87.233.53 0.968 2.233 3.505 10.409 31.403 121.521 149.226 27.898 119.288 18.432 14.461 ms 4.267 26.82
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 4.137 6.780 10.042 21.947 37.583 50.650 189.220 27.541 43.870 13.244 22.917 µs 9.487 109
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 5.260 5.807 8.487 21.032 60.211 99.710 147.016 51.724 93.903 19.133 25.850 µs 4.153 21.19
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 6.585 8.091 11.739 23.243 54.929 269.243 383.135 43.190 261.152 40.241 31.485 µs 5.809 45.36
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 14.092 14.955 19.044 33.937 66.540 143.718 307.279 47.496 128.763 27.969 39.224 µs 7.788 70.72
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 5.699 6.670 10.788 21.566 41.768 66.209 105.075 30.980 59.539 11.803 23.666 µs 6.748 35.27
Server Jitter PPS(0) 0.103 0.255 0.340 0.663 1.620 2.632 7.138 1.280 2.377 0.492 0.782 µs 5.752 39.54
Server Offset 128.101.101.101 -128.813 -99.493 -60.712 30.588 110.389 183.535 224.175 171.101 283.028 50.865 25.821 µs -1.409 5.475
Server Offset 128.138.141.177 -166.739 -144.169 -101.458 14.504 257.190 435.736 486.452 358.648 579.905 114.468 46.759 µs -1.042 3.772
Server Offset 2001:470:0:2c8::2 (clock.nyc.he.net) -415.354 -406.409 -307.036 -238.108 -176.726 -149.714 -141.275 130.310 256.695 44.511 -240.791 µs -283.4 1961
Server Offset 209.87.233.53 -8.760 -4.433 -1.940 1.015 3.287 4.189 5.144 5.227 8.622 1.644 0.874 ms -2.692 11.19
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -94.926 -93.401 -71.323 -36.552 -17.511 -12.364 -0.842 53.812 81.037 16.392 -39.036 µs -49.67 214.9
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -353.009 -349.459 -340.816 -280.854 -228.607 -190.193 -187.086 112.209 159.266 35.211 -284.549 µs -776 7291
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -352.492 -351.136 -339.029 -287.054 156.235 163.950 169.105 495.264 515.086 114.258 -247.311 µs -38.62 137.5
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) -349.625 -342.368 -329.583 -287.475 -247.044 -219.108 -206.799 82.539 123.260 25.345 -287.471 µs -1917 2.411e+04
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -111.904 -106.247 -78.458 -27.285 9.245 18.394 23.081 87.703 124.641 25.655 -30.725 µs -17.85 61.44
Server Offset PPS(0) -6.969 -1.798 -1.159 0.039 1.218 1.751 3.772 2.377 3.549 0.786 0.026 µs -4.773 19.56
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!