NTPsec

ntp1.wiktel.com

Report generated: Thu Jul 3 16:45:02 2025 UTC
Start Time: Thu Jun 26 16:45:01 2025 UTC
End Time: Thu Jul 3 16:45:01 2025 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 -12.770 -5.099 -3.995 -0.281 4.641 6.193 383.411 8.636 11.292 3.010 0.002 µs 23.56 3381
Local Clock Frequency Offset 17.242 17.308 17.343 17.437 17.524 17.544 17.620 0.182 0.236 0.054 17.438 ppm 3.256e+07 1.04e+10

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.292 0.437 0.510 0.755 1.447 2.106 188.461 0.937 1.669 2.008 0.868 µs 61.15 4401

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.167 0.274 0.375 1.031 2.304 2.832 4.909 1.929 2.558 0.613 1.149 ppb 4.318 13.31

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 -12.770 -5.099 -3.995 -0.281 4.641 6.193 383.411 8.636 11.292 3.010 0.002 µs 23.56 3381

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 -566.876 -450.270 -342.312 23.561 148.523 212.747 413.685 490.835 663.017 152.066 -20.910 µs -5.986 18.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 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 -689.396 -239.210 -136.759 4.516 324.523 508.127 842.560 461.282 747.337 151.778 37.358 µs -1.945 6.974

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 -610.337 -297.615 -282.308 63.066 88.422 97.710 398.927 370.730 395.325 135.342 7.609 µs -5.2 16.25

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) -1,481.500 -866.191 -828.317 -758.997 -696.691 134.802 447.163 131.626 1,000.993 132.422 -749.319 µs -309.9 2137

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 -10.284 -3.713 -1.293 1.496 3.521 5.054 7.258 4.815 8.767 1.591 1.372 ms -1.733 10.53

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 -16.714 -4.706 -2.631 0.433 2.715 4.260 5.268 5.345 8.967 1.781 0.283 ms -5.278 30.24

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.133 -0.103 -0.085 -0.045 0.282 1.720 3.487 0.367 1.823 0.296 0.016 ms 2.598 30.62

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) -2,691.085 -248.944 -175.339 196.989 339.433 428.218 936.532 514.772 677.162 249.706 144.409 µs -8.065 87.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 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) -228.919 -168.967 -83.972 239.657 367.520 419.172 511.833 451.492 588.139 113.607 226.799 µs 2.275 7.053

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) -646.402 -418.677 -397.285 -352.308 -225.358 -195.330 94.907 171.927 223.347 58.107 -336.770 µs -333.8 2404

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) -921.871 -580.136 -451.463 -365.945 -262.770 -130.015 150.197 188.693 450.121 68.118 -364.140 µs -274.2 1864

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) -12.771 -5.100 -3.996 -0.282 4.642 6.193 10.990 8.638 11.293 2.668 -0.003 µs -3.684 8.423

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 0.000 10.593 16.194 80.830 375.973 429.461 571.351 359.779 418.868 138.714 157.515 µs 0.877 1.969

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 0.000 295.722 372.828 611.396 867.575 989.579 1,584.321 494.747 693.857 153.799 614.611 µs 36.29 143.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 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.000 8.556 12.859 30.968 357.399 380.738 606.528 344.540 372.182 143.809 137.515 µs 0.4576 1.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.



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) 4.516 8.984 11.574 21.237 51.514 396.202 1,532.996 39.940 387.218 86.502 33.186 µs 10.02 147.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 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.915 2.193 3.668 10.038 24.164 40.728 125.721 20.496 38.535 8.219 11.612 ms 5.799 53.63

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.649 3.188 11.560 81.285 153.724 231.322 78.097 152.076 29.414 18.794 ms 3.167 17.73

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 0.019 0.033 0.211 3.228 4.206 5.681 3.195 4.186 1.016 0.677 ms 1.041 4.463

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) 6.891 11.236 16.672 124.134 379.241 484.961 2,614.988 362.569 473.725 177.058 175.196 µs 4.779 62.69

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 8.827 14.133 35.060 191.388 347.039 429.111 177.255 338.212 64.236 56.815 µs 2.755 12.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 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 0.013 0.018 0.034 0.071 0.445 18.723 0.053 0.432 0.419 0.055 ms 39.83 1775

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 11.165 15.240 28.421 56.671 83.988 593.162 41.431 72.823 27.721 32.625 µs 11.47 179.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 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.289 0.391 0.810 1.866 2.687 9.827 1.475 2.398 0.510 0.933 µs 5.488 28.44

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.242 17.308 17.343 17.437 17.524 17.544 17.620 0.182 0.236 0.054 17.438 ppm 3.256e+07 1.04e+10
Local Clock Time Offset -12.770 -5.099 -3.995 -0.281 4.641 6.193 383.411 8.636 11.292 3.010 0.002 µs 23.56 3381
Local RMS Frequency Jitter 0.167 0.274 0.375 1.031 2.304 2.832 4.909 1.929 2.558 0.613 1.149 ppb 4.318 13.31
Local RMS Time Jitter 0.292 0.437 0.510 0.755 1.447 2.106 188.461 0.937 1.669 2.008 0.868 µs 61.15 4401
Server Jitter 128.101.101.101 0.000 10.593 16.194 80.830 375.973 429.461 571.351 359.779 418.868 138.714 157.515 µs 0.877 1.969
Server Jitter 128.138.141.177 0.000 295.722 372.828 611.396 867.575 989.579 1,584.321 494.747 693.857 153.799 614.611 µs 36.29 143.7
Server Jitter 199.102.46.70 0.000 8.556 12.859 30.968 357.399 380.738 606.528 344.540 372.182 143.809 137.515 µs 0.4576 1.54
Server Jitter 2001:470:0:2c8::2 (clock.nyc.he.net) 4.516 8.984 11.574 21.237 51.514 396.202 1,532.996 39.940 387.218 86.502 33.186 µs 10.02 147.4
Server Jitter 209.87.233.53 0.915 2.193 3.668 10.038 24.164 40.728 125.721 20.496 38.535 8.219 11.612 ms 5.799 53.63
Server Jitter 209.87.233.54 0.000 1.649 3.188 11.560 81.285 153.724 231.322 78.097 152.076 29.414 18.794 ms 3.167 17.73
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 0.000 0.019 0.033 0.211 3.228 4.206 5.681 3.195 4.186 1.016 0.677 ms 1.041 4.463
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 6.891 11.236 16.672 124.134 379.241 484.961 2,614.988 362.569 473.725 177.058 175.196 µs 4.779 62.69
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 8.827 14.133 35.060 191.388 347.039 429.111 177.255 338.212 64.236 56.815 µs 2.755 12.22
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 0.000 0.013 0.018 0.034 0.071 0.445 18.723 0.053 0.432 0.419 0.055 ms 39.83 1775
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 0.000 11.165 15.240 28.421 56.671 83.988 593.162 41.431 72.823 27.721 32.625 µs 11.47 179.4
Server Jitter PPS(0) 0.000 0.289 0.391 0.810 1.866 2.687 9.827 1.475 2.398 0.510 0.933 µs 5.488 28.44
Server Offset 128.101.101.101 -566.876 -450.270 -342.312 23.561 148.523 212.747 413.685 490.835 663.017 152.066 -20.910 µs -5.986 18.2
Server Offset 128.138.141.177 -689.396 -239.210 -136.759 4.516 324.523 508.127 842.560 461.282 747.337 151.778 37.358 µs -1.945 6.974
Server Offset 199.102.46.70 -610.337 -297.615 -282.308 63.066 88.422 97.710 398.927 370.730 395.325 135.342 7.609 µs -5.2 16.25
Server Offset 2001:470:0:2c8::2 (clock.nyc.he.net) -1,481.500 -866.191 -828.317 -758.997 -696.691 134.802 447.163 131.626 1,000.993 132.422 -749.319 µs -309.9 2137
Server Offset 209.87.233.53 -10.284 -3.713 -1.293 1.496 3.521 5.054 7.258 4.815 8.767 1.591 1.372 ms -1.733 10.53
Server Offset 209.87.233.54 -16.714 -4.706 -2.631 0.433 2.715 4.260 5.268 5.345 8.967 1.781 0.283 ms -5.278 30.24
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -0.133 -0.103 -0.085 -0.045 0.282 1.720 3.487 0.367 1.823 0.296 0.016 ms 2.598 30.62
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -2,691.085 -248.944 -175.339 196.989 339.433 428.218 936.532 514.772 677.162 249.706 144.409 µs -8.065 87.5
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -228.919 -168.967 -83.972 239.657 367.520 419.172 511.833 451.492 588.139 113.607 226.799 µs 2.275 7.053
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) -646.402 -418.677 -397.285 -352.308 -225.358 -195.330 94.907 171.927 223.347 58.107 -336.770 µs -333.8 2404
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -921.871 -580.136 -451.463 -365.945 -262.770 -130.015 150.197 188.693 450.121 68.118 -364.140 µs -274.2 1864
Server Offset PPS(0) -12.771 -5.100 -3.996 -0.282 4.642 6.193 10.990 8.638 11.293 2.668 -0.003 µs -3.684 8.423
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!