NTPsec

ntp2.wiktel.com

Report generated: Tue Jul 8 04:45:05 2025 UTC
Start Time: Tue Jul 1 04:45:00 2025 UTC
End Time: Tue Jul 8 04:45:00 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 -124.364 -9.143 -5.639 0.526 3.135 4.422 31.992 8.774 13.565 2.650 0.000 µs -5.967 38.25
Local Clock Frequency Offset -13.289 -13.220 -13.150 -13.033 -12.926 -12.889 -12.650 0.224 0.331 0.069 -13.035 ppm -6.893e+06 1.312e+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.630 1.248 1.622 3.229 5.577 6.916 63.782 3.955 5.668 1.270 3.367 µs 12.15 119.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.774 2.324 4.691 7.948 9.808 86.177 5.624 8.034 1.799 4.856 ppb 12.61 118.5

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 -124.364 -9.143 -5.639 0.526 3.135 4.422 31.992 8.774 13.565 2.650 0.000 µs -5.967 38.25

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.434 -1.418 -1.396 -1.038 -0.988 -0.967 -0.408 0.408 0.451 0.140 -1.087 ms -700.3 6400

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 -69.143 -52.181 272.602 333.596 367.260 508.277 385.777 436.403 203.088 137.315 µs -3.269 23.17

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 -43.250 -33.009 -6.045 21.075 35.992 744.695 54.084 79.242 42.954 -5.042 µs 2.77 213.7

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

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

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

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



Server Offset 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.042 -1.038 -1.030 -1.021 -1.011 -0.007 0.018 0.031 0.079 -1.024 ms -2797 3.96e+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) -374.369 -364.909 -358.190 -342.728 -327.573 -320.785 -306.205 30.617 44.124 9.427 -342.782 µs -5.226e+04 1.957e+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.445 -0.404 -0.383 -0.026 0.798 2.043 4.408 1.181 2.448 0.449 0.011 ms 0.149 16.47

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

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

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

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



Server Offset 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) -82.111 26.373 93.196 208.013 337.598 403.715 468.677 244.402 377.342 76.028 211.358 µs 10.98 32.79

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 -546.318 86.611 223.755 340.676 404.229 656.121 254.065 950.547 289.778 194.982 µs -9.992 101.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 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 -130.974 -102.566 -59.204 -19.559 -3.059 1,051.839 83.007 127.915 53.059 -60.552 µs -16.55 313.4

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

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

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

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



Server Offset 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 -199.127 -95.890 -32.829 51.888 110.786 774.466 147.778 309.913 74.534 -32.074 µs -13.69 204.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) -124.365 -9.144 -5.640 0.527 3.136 4.423 31.993 8.776 13.567 2.650 0.000 µs -5.966 38.22

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.551 21.148 59.759 366.771 391.219 1,051.217 345.623 375.668 141.071 157.907 µs 1.18 4.623

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.012 0.017 0.140 0.464 1.085 4.287 0.447 1.073 0.240 0.191 ms 5.697 81.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.777 4.067 8.386 18.724 28.087 980.000 14.657 25.310 42.929 12.044 µs 15.49 299.5

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 3.881 5.347 9.741 22.300 316.745 1,204.017 16.953 312.864 71.624 18.594 µs 8.466 107.8

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.153 9.408 19.505 34.252 39.878 48.981 24.844 33.725 7.513 20.330 µs 10.6 32.59

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.028 0.054 0.332 3.629 4.546 8.324 3.575 4.518 1.192 0.913 ms 1.149 4.889

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.645 8.914 29.329 122.241 211.712 346.121 113.327 205.067 41.901 43.872 µs 2.637 12.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.



Server Jitter 2606:4700:f1::123 (time.cloudflare.com)

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.006 0.009 0.027 0.153 1.844 2.979 0.145 1.838 0.239 0.070 ms 6.629 67.51

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 11.112 14.979 32.425 73.515 344.036 1,450.163 58.536 332.924 70.427 42.992 µs 9.87 140.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 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.304 14.372 30.578 98.340 178.037 1,628.038 83.968 167.733 69.370 44.086 µs 12.74 239.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 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.622 0.910 2.825 7.109 9.936 128.335 6.199 9.314 2.053 3.244 µs 4.544 71

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.289 -13.220 -13.150 -13.033 -12.926 -12.889 -12.650 0.224 0.331 0.069 -13.035 ppm -6.893e+06 1.312e+09
Local Clock Time Offset -124.364 -9.143 -5.639 0.526 3.135 4.422 31.992 8.774 13.565 2.650 0.000 µs -5.967 38.25
Local RMS Frequency Jitter 0.854 1.774 2.324 4.691 7.948 9.808 86.177 5.624 8.034 1.799 4.856 ppb 12.61 118.5
Local RMS Time Jitter 0.630 1.248 1.622 3.229 5.577 6.916 63.782 3.955 5.668 1.270 3.367 µs 12.15 119.7
Server Jitter 132.163.97.5 0.000 15.551 21.148 59.759 366.771 391.219 1,051.217 345.623 375.668 141.071 157.907 µs 1.18 4.623
Server Jitter 132.246.11.237 0.000 0.012 0.017 0.140 0.464 1.085 4.287 0.447 1.073 0.240 0.191 ms 5.697 81.3
Server Jitter 134.84.84.84 0.000 2.777 4.067 8.386 18.724 28.087 980.000 14.657 25.310 42.929 12.044 µs 15.49 299.5
Server Jitter 204.9.54.119 0.000 3.881 5.347 9.741 22.300 316.745 1,204.017 16.953 312.864 71.624 18.594 µs 8.466 107.8
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 0.000 6.153 9.408 19.505 34.252 39.878 48.981 24.844 33.725 7.513 20.330 µs 10.6 32.59
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 0.000 0.028 0.054 0.332 3.629 4.546 8.324 3.575 4.518 1.192 0.913 ms 1.149 4.889
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 6.645 8.914 29.329 122.241 211.712 346.121 113.327 205.067 41.901 43.872 µs 2.637 12.44
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.006 0.009 0.027 0.153 1.844 2.979 0.145 1.838 0.239 0.070 ms 6.629 67.51
Server Jitter 2607:f128::50 0.000 11.112 14.979 32.425 73.515 344.036 1,450.163 58.536 332.924 70.427 42.992 µs 9.87 140.2
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 0.000 10.304 14.372 30.578 98.340 178.037 1,628.038 83.968 167.733 69.370 44.086 µs 12.74 239.4
Server Jitter SHM(1) 0.000 0.622 0.910 2.825 7.109 9.936 128.335 6.199 9.314 2.053 3.244 µs 4.544 71
Server Offset 132.163.97.5 -1.434 -1.418 -1.396 -1.038 -0.988 -0.967 -0.408 0.408 0.451 0.140 -1.087 ms -700.3 6400
Server Offset 132.246.11.237 -1,554.717 -69.143 -52.181 272.602 333.596 367.260 508.277 385.777 436.403 203.088 137.315 µs -3.269 23.17
Server Offset 134.84.84.84 -641.028 -43.250 -33.009 -6.045 21.075 35.992 744.695 54.084 79.242 42.954 -5.042 µs 2.77 213.7
Server Offset 204.9.54.119 -2.000 -1.042 -1.038 -1.030 -1.021 -1.011 -0.007 0.018 0.031 0.079 -1.024 ms -2797 3.96e+04
Server Offset 2600:2600::99 (ntp1.wiktel.com) -374.369 -364.909 -358.190 -342.728 -327.573 -320.785 -306.205 30.617 44.124 9.427 -342.782 µs -5.226e+04 1.957e+06
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -0.445 -0.404 -0.383 -0.026 0.798 2.043 4.408 1.181 2.448 0.449 0.011 ms 0.149 16.47
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -82.111 26.373 93.196 208.013 337.598 403.715 468.677 244.402 377.342 76.028 211.358 µs 10.98 32.79
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -2,707.911 -546.318 86.611 223.755 340.676 404.229 656.121 254.065 950.547 289.778 194.982 µs -9.992 101.2
Server Offset 2607:f128::50 -1,119.454 -130.974 -102.566 -59.204 -19.559 -3.059 1,051.839 83.007 127.915 53.059 -60.552 µs -16.55 313.4
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -1,673.056 -199.127 -95.890 -32.829 51.888 110.786 774.466 147.778 309.913 74.534 -32.074 µs -13.69 204.6
Server Offset SHM(1) -124.365 -9.144 -5.640 0.527 3.136 4.423 31.993 8.776 13.567 2.650 0.000 µs -5.966 38.22
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!