NTPsec

ntp2.wiktel.com

Report generated: Fri Jul 4 04:45:07 2025 UTC
Start Time: Fri Jun 27 04:45:02 2025 UTC
End Time: Fri Jul 4 04:45:02 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 -160.501 -9.340 -5.701 0.543 3.228 4.556 42.683 8.929 13.896 2.735 -0.000 µs -6.44 71.58
Local Clock Frequency Offset -13.298 -13.220 -13.147 -12.998 -12.858 -12.814 -12.650 0.289 0.406 0.087 -13.004 ppm -3.423e+06 5.16e+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.630 1.276 1.662 3.314 5.741 7.188 82.843 4.079 5.912 1.358 3.459 µs 13.65 252.7

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.854 1.821 2.396 4.819 8.159 10.133 111.206 5.763 8.312 1.914 4.990 ppb 14.3 255

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 -160.501 -9.340 -5.701 0.543 3.228 4.556 42.683 8.929 13.896 2.735 -0.000 µs -6.44 71.58

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 132.163.97.5

peer offset 132.163.97.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.163.97.5 -1.438 -1.416 -1.397 -1.039 -0.987 -0.970 -0.408 0.410 0.446 0.141 -1.088 ms -695 6336

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

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

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

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



Server Offset 132.246.11.229

peer offset 132.246.11.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.229 -1.174 -1.127 -1.116 -0.771 -0.725 -0.621 -0.436 0.391 0.506 0.162 -0.864 ms -271.6 1850

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

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

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

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



Server Offset 132.246.11.237

peer offset 132.246.11.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.237 -1,554.717 -104.183 -52.220 282.808 331.865 359.885 456.178 384.085 464.068 237.524 138.445 µs -4.67 30.85

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

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

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

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



Server Offset 134.84.84.84

peer offset 134.84.84.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 134.84.84.84 -641.028 -44.564 -32.844 -5.458 21.592 32.113 744.695 54.436 76.677 42.711 -4.533 µs 2.84 215.8

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

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

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

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



Server Offset 204.9.54.119

peer offset 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.9.54.119 -2.000 -1.043 -1.038 -1.028 -1.018 -1.013 -0.007 0.019 0.030 0.068 -1.028 ms -4320 7.079e+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 2600:2600::99 (ntp1.wiktel.com)

peer offset 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:2600::99 (ntp1.wiktel.com) -373.288 -364.164 -358.343 -342.235 -327.024 -320.330 -306.205 31.319 43.834 9.521 -342.456 µs -5.064e+04 1.876e+06

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

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

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

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



Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -0.431 -0.405 -0.388 -0.039 0.278 1.587 5.311 0.667 1.992 0.399 -0.085 ms -0.3782 30.21

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) -131.087 51.736 94.721 221.254 355.870 418.388 468.677 261.149 366.652 80.541 224.332 µs 11.11 32.82

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) -2,707.911 -3.334 100.003 220.897 331.054 382.849 656.121 231.051 386.183 264.155 200.778 µs -10.64 117.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::50

peer offset 2607:f128::50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f128::50 -1,119.454 -114.537 -94.511 -57.497 -18.687 -4.044 1,051.839 75.824 110.493 51.312 -58.029 µs -16.5 342.6

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

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

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

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



Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu)

peer offset 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -1,673.056 -255.361 -121.803 -31.580 50.100 110.487 774.466 171.903 365.848 78.700 -34.573 µs -13.09 173.6

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

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

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

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



Server Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -160.502 -9.341 -5.702 0.544 3.229 4.557 42.684 8.931 13.898 2.736 0.000 µs -6.438 71.52

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

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

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

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



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 132.163.97.5

peer jitter 132.163.97.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.163.97.5 0.000 15.055 20.766 54.587 364.402 391.304 1,187.225 343.636 376.249 141.213 152.093 µs 1.242 5.488

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 132.246.11.229

peer jitter 132.246.11.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.229 5.922 13.986 20.740 287.958 429.604 767.006 1,979.970 408.864 753.020 162.282 251.584 µs 3.59 23.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 132.246.11.237

peer jitter 132.246.11.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.237 0.000 0.011 0.016 0.138 0.407 1.109 1.898 0.391 1.099 0.207 0.185 ms 2.891 18.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 134.84.84.84

peer jitter 134.84.84.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 134.84.84.84 0.000 2.405 3.784 8.327 19.832 34.991 980.000 16.048 32.586 42.880 12.125 µs 15.34 297.1

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.9.54.119

peer jitter 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.9.54.119 0.000 4.093 5.411 9.896 18.108 136.232 1,204.017 12.697 132.139 63.091 16.473 µs 10.19 150.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 2600:2600::99 (ntp1.wiktel.com)

peer jitter 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 0.000 6.268 9.390 20.000 34.907 40.926 52.920 25.517 34.658 7.774 20.716 µs 10.08 30.49

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 0.000 0.024 0.044 0.277 3.254 4.395 8.324 3.210 4.371 1.019 0.674 ms 1.596 8.136

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) 0.000 6.501 8.617 27.294 129.095 192.157 394.339 120.478 185.656 41.900 42.783 µs 2.514 12.35

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 6.065 8.480 25.541 135.301 705.975 2,979.232 126.821 699.910 218.624 62.729 µs 7.517 83.48

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f128::50

peer jitter 2607:f128::50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f128::50 0.000 10.779 14.638 30.032 62.939 530.776 1,450.163 48.301 519.997 81.022 41.671 µs 7.96 92.24

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu)

peer jitter 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 0.000 10.194 14.272 27.376 73.637 361.085 1,628.038 59.365 350.891 88.964 41.033 µs 9.996 141

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.000 0.647 0.947 2.918 7.258 10.174 158.723 6.311 9.527 2.130 3.341 µs 6.095 166.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -13.298 -13.220 -13.147 -12.998 -12.858 -12.814 -12.650 0.289 0.406 0.087 -13.004 ppm -3.423e+06 5.16e+08
Local Clock Time Offset -160.501 -9.340 -5.701 0.543 3.228 4.556 42.683 8.929 13.896 2.735 -0.000 µs -6.44 71.58
Local RMS Frequency Jitter 0.854 1.821 2.396 4.819 8.159 10.133 111.206 5.763 8.312 1.914 4.990 ppb 14.3 255
Local RMS Time Jitter 0.630 1.276 1.662 3.314 5.741 7.188 82.843 4.079 5.912 1.358 3.459 µs 13.65 252.7
Server Jitter 132.163.97.5 0.000 15.055 20.766 54.587 364.402 391.304 1,187.225 343.636 376.249 141.213 152.093 µs 1.242 5.488
Server Jitter 132.246.11.229 5.922 13.986 20.740 287.958 429.604 767.006 1,979.970 408.864 753.020 162.282 251.584 µs 3.59 23.22
Server Jitter 132.246.11.237 0.000 0.011 0.016 0.138 0.407 1.109 1.898 0.391 1.099 0.207 0.185 ms 2.891 18.73
Server Jitter 134.84.84.84 0.000 2.405 3.784 8.327 19.832 34.991 980.000 16.048 32.586 42.880 12.125 µs 15.34 297.1
Server Jitter 204.9.54.119 0.000 4.093 5.411 9.896 18.108 136.232 1,204.017 12.697 132.139 63.091 16.473 µs 10.19 150.4
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 0.000 6.268 9.390 20.000 34.907 40.926 52.920 25.517 34.658 7.774 20.716 µs 10.08 30.49
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 0.000 0.024 0.044 0.277 3.254 4.395 8.324 3.210 4.371 1.019 0.674 ms 1.596 8.136
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 6.501 8.617 27.294 129.095 192.157 394.339 120.478 185.656 41.900 42.783 µs 2.514 12.35
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 6.065 8.480 25.541 135.301 705.975 2,979.232 126.821 699.910 218.624 62.729 µs 7.517 83.48
Server Jitter 2607:f128::50 0.000 10.779 14.638 30.032 62.939 530.776 1,450.163 48.301 519.997 81.022 41.671 µs 7.96 92.24
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 0.000 10.194 14.272 27.376 73.637 361.085 1,628.038 59.365 350.891 88.964 41.033 µs 9.996 141
Server Jitter SHM(1) 0.000 0.647 0.947 2.918 7.258 10.174 158.723 6.311 9.527 2.130 3.341 µs 6.095 166.3
Server Offset 132.163.97.5 -1.438 -1.416 -1.397 -1.039 -0.987 -0.970 -0.408 0.410 0.446 0.141 -1.088 ms -695 6336
Server Offset 132.246.11.229 -1.174 -1.127 -1.116 -0.771 -0.725 -0.621 -0.436 0.391 0.506 0.162 -0.864 ms -271.6 1850
Server Offset 132.246.11.237 -1,554.717 -104.183 -52.220 282.808 331.865 359.885 456.178 384.085 464.068 237.524 138.445 µs -4.67 30.85
Server Offset 134.84.84.84 -641.028 -44.564 -32.844 -5.458 21.592 32.113 744.695 54.436 76.677 42.711 -4.533 µs 2.84 215.8
Server Offset 204.9.54.119 -2.000 -1.043 -1.038 -1.028 -1.018 -1.013 -0.007 0.019 0.030 0.068 -1.028 ms -4320 7.079e+04
Server Offset 2600:2600::99 (ntp1.wiktel.com) -373.288 -364.164 -358.343 -342.235 -327.024 -320.330 -306.205 31.319 43.834 9.521 -342.456 µs -5.064e+04 1.876e+06
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -0.431 -0.405 -0.388 -0.039 0.278 1.587 5.311 0.667 1.992 0.399 -0.085 ms -0.3782 30.21
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -131.087 51.736 94.721 221.254 355.870 418.388 468.677 261.149 366.652 80.541 224.332 µs 11.11 32.82
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -2,707.911 -3.334 100.003 220.897 331.054 382.849 656.121 231.051 386.183 264.155 200.778 µs -10.64 117.5
Server Offset 2607:f128::50 -1,119.454 -114.537 -94.511 -57.497 -18.687 -4.044 1,051.839 75.824 110.493 51.312 -58.029 µs -16.5 342.6
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -1,673.056 -255.361 -121.803 -31.580 50.100 110.487 774.466 171.903 365.848 78.700 -34.573 µs -13.09 173.6
Server Offset SHM(1) -160.502 -9.341 -5.702 0.544 3.229 4.557 42.684 8.931 13.898 2.736 0.000 µs -6.438 71.52
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!