NTPsec

ntp1.wiktel.com

Report generated: Fri Jul 11 21:53:01 2025 UTC
Start Time: Thu Jul 10 21:53:01 2025 UTC
End Time: Fri Jul 11 21:53:01 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 -13.089 -8.147 -5.962 0.008 6.081 8.345 14.606 12.043 16.492 3.645 0.014 µs -3.964 9.833
Local Clock Frequency Offset 17.393 17.433 17.490 17.628 17.717 17.745 17.765 0.227 0.311 0.072 17.617 ppm 1.464e+07 3.58e+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.255 0.412 0.489 0.759 2.066 2.650 3.872 1.577 2.238 0.508 0.959 µs 4.999 16.59

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.183 0.267 0.398 1.391 3.255 3.974 5.125 2.857 3.707 0.881 1.548 ppb 3.515 9.521

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 -13.089 -8.147 -5.962 0.008 6.081 8.345 14.606 12.043 16.492 3.645 0.014 µs -3.964 9.833

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 -431.783 -395.270 -343.800 24.616 114.282 147.545 190.916 458.082 542.815 164.760 -54.717 µs -7.202 20.39

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 -193.596 -140.593 -115.527 8.279 294.076 502.798 643.876 409.603 643.391 137.526 41.026 µs -1.057 4.809

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 199.102.46.70

peer offset 199.102.46.70 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 199.102.46.70 -1,743.407 -303.744 -290.864 63.212 90.821 99.612 106.434 381.685 403.356 186.462 -39.596 µs -8.252 47.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 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.996 -4.179 -2.537 1.303 3.857 4.899 6.059 6.394 9.078 1.913 1.104 ms -2.384 8.937

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) -102.623 -96.948 -88.316 -47.729 -18.456 -5.605 4.731 69.860 91.343 20.867 -48.977 µs -47.73 197.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) -229.578 -212.831 -189.679 122.332 284.359 321.032 330.967 474.038 533.863 182.358 47.546 µs -2.717 5.144

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) -287.047 -266.858 -248.428 -119.736 238.979 252.725 283.652 487.407 519.583 169.797 -49.433 µs -5.47 11.68

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) -307.131 -295.182 -284.099 -244.023 -199.788 -180.195 -172.383 84.311 114.987 25.860 -242.183 µs -1145 1.218e+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) -660.110 -646.534 -514.729 -381.969 -280.203 -152.529 -138.800 234.526 494.005 75.242 -385.920 µs -249.3 1659

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) -13.090 -8.148 -5.963 0.009 6.082 8.346 14.607 12.045 16.494 3.646 0.014 µs -3.964 9.832

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 7.270 9.168 11.696 32.189 328.303 360.427 425.595 316.607 351.259 89.812 65.675 µs 1.548 5.22

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 178.064 212.131 346.274 617.008 834.508 974.176 1,091.419 488.234 762.045 147.056 612.913 µs 41.08 161.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 199.102.46.70

peer jitter 199.102.46.70 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 199.102.46.70 0.007 0.009 0.012 0.026 0.325 0.368 43.033 0.313 0.360 2.389 0.193 ms 14.32 260.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 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.786 2.160 3.571 12.086 104.574 212.408 221.073 101.003 210.248 38.953 24.559 ms 2.414 11.64

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) 6.609 8.524 12.937 25.908 46.859 54.081 56.493 33.922 45.557 10.375 27.446 µs 10.01 30.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 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.879 6.600 13.550 31.584 276.950 449.078 461.290 263.400 442.478 82.131 60.409 µs 2.207 9.233

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) 8.274 9.404 13.529 34.659 361.626 649.860 652.565 348.097 640.456 127.352 90.769 µs 1.635 7.178

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) 11.744 15.925 20.366 37.312 84.761 545.877 806.880 64.395 529.952 73.258 50.026 µs 6.372 53.7

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) 4.543 9.674 14.412 27.270 55.959 71.337 78.651 41.547 61.663 12.516 29.761 µs 8.018 27.09

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.081 0.253 0.367 0.870 3.788 6.043 9.240 3.421 5.790 1.182 1.310 µs 2.655 10.42

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.393 17.433 17.490 17.628 17.717 17.745 17.765 0.227 0.311 0.072 17.617 ppm 1.464e+07 3.58e+09
Local Clock Time Offset -13.089 -8.147 -5.962 0.008 6.081 8.345 14.606 12.043 16.492 3.645 0.014 µs -3.964 9.833
Local RMS Frequency Jitter 0.183 0.267 0.398 1.391 3.255 3.974 5.125 2.857 3.707 0.881 1.548 ppb 3.515 9.521
Local RMS Time Jitter 0.255 0.412 0.489 0.759 2.066 2.650 3.872 1.577 2.238 0.508 0.959 µs 4.999 16.59
Server Jitter 128.101.101.101 7.270 9.168 11.696 32.189 328.303 360.427 425.595 316.607 351.259 89.812 65.675 µs 1.548 5.22
Server Jitter 128.138.141.177 178.064 212.131 346.274 617.008 834.508 974.176 1,091.419 488.234 762.045 147.056 612.913 µs 41.08 161.4
Server Jitter 199.102.46.70 0.007 0.009 0.012 0.026 0.325 0.368 43.033 0.313 0.360 2.389 0.193 ms 14.32 260.2
Server Jitter 209.87.233.53 1.786 2.160 3.571 12.086 104.574 212.408 221.073 101.003 210.248 38.953 24.559 ms 2.414 11.64
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 6.609 8.524 12.937 25.908 46.859 54.081 56.493 33.922 45.557 10.375 27.446 µs 10.01 30.52
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 5.879 6.600 13.550 31.584 276.950 449.078 461.290 263.400 442.478 82.131 60.409 µs 2.207 9.233
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 8.274 9.404 13.529 34.659 361.626 649.860 652.565 348.097 640.456 127.352 90.769 µs 1.635 7.178
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 11.744 15.925 20.366 37.312 84.761 545.877 806.880 64.395 529.952 73.258 50.026 µs 6.372 53.7
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 4.543 9.674 14.412 27.270 55.959 71.337 78.651 41.547 61.663 12.516 29.761 µs 8.018 27.09
Server Jitter PPS(0) 0.081 0.253 0.367 0.870 3.788 6.043 9.240 3.421 5.790 1.182 1.310 µs 2.655 10.42
Server Offset 128.101.101.101 -431.783 -395.270 -343.800 24.616 114.282 147.545 190.916 458.082 542.815 164.760 -54.717 µs -7.202 20.39
Server Offset 128.138.141.177 -193.596 -140.593 -115.527 8.279 294.076 502.798 643.876 409.603 643.391 137.526 41.026 µs -1.057 4.809
Server Offset 199.102.46.70 -1,743.407 -303.744 -290.864 63.212 90.821 99.612 106.434 381.685 403.356 186.462 -39.596 µs -8.252 47.2
Server Offset 209.87.233.53 -8.996 -4.179 -2.537 1.303 3.857 4.899 6.059 6.394 9.078 1.913 1.104 ms -2.384 8.937
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -102.623 -96.948 -88.316 -47.729 -18.456 -5.605 4.731 69.860 91.343 20.867 -48.977 µs -47.73 197.9
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -229.578 -212.831 -189.679 122.332 284.359 321.032 330.967 474.038 533.863 182.358 47.546 µs -2.717 5.144
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -287.047 -266.858 -248.428 -119.736 238.979 252.725 283.652 487.407 519.583 169.797 -49.433 µs -5.47 11.68
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) -307.131 -295.182 -284.099 -244.023 -199.788 -180.195 -172.383 84.311 114.987 25.860 -242.183 µs -1145 1.218e+04
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -660.110 -646.534 -514.729 -381.969 -280.203 -152.529 -138.800 234.526 494.005 75.242 -385.920 µs -249.3 1659
Server Offset PPS(0) -13.090 -8.148 -5.963 0.009 6.082 8.346 14.607 12.045 16.494 3.646 0.014 µs -3.964 9.832
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!