ntp2.wiktel.com
Report generated: Fri Apr 19 10:53:02 2024 UTCStart Time: Thu Apr 18 10:53:01 2024 UTC
End Time: Fri Apr 19 10:53:01 2024 UTC
Report Period: 1.0 days
Top Daily Stats Weekly Stats
Local Clock Time/Frequency Offsets
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Time Offset | -20.947 | -9.165 | -5.619 | 0.503 | 2.940 | 4.197 | 8.345 | 8.559 | 13.362 | 2.568 | -0.004 | µs | -5.887 | 22.85 | ||
| Local Clock Frequency Offset | -14.021 | -13.950 | -13.894 | -13.482 | -13.251 | -13.206 | -13.144 | 0.643 | 0.745 | 0.218 | -13.552 | ppm | -2.533e+05 | 1.603e+07 | ||
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local RMS Time Jitter | 0.478 | 1.017 | 1.390 | 3.083 | 5.513 | 6.909 | 10.876 | 4.123 | 5.892 | 1.296 | 3.214 | µs | 8.405 | 25.98 | ||
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local RMS Frequency Jitter | 0.854 | 1.536 | 2.096 | 4.515 | 7.844 | 9.729 | 14.860 | 5.748 | 8.193 | 1.806 | 4.682 | ppb | 9.464 | 29.37 | ||
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Offset | -20.947 | -9.165 | -5.619 | 0.503 | 2.940 | 4.197 | 8.345 | 8.559 | 13.362 | 2.568 | -0.004 | µs | -5.887 | 22.85 | ||
The clock offsets of the local clock as a histogram.
The Local Clock Offset is field 3 from the loopstats log file.
Local GPS
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| nSats | 5.000 | 6.000 | 7.000 | 9.000 | 11.000 | 11.000 | 12.000 | 4.000 | 5.000 | 1.155 | 8.874 | nSat | 318.6 | 2265 | ||
| TDOP | 0.570 | 0.590 | 0.630 | 0.830 | 1.490 | 2.490 | 4.630 | 0.860 | 1.900 | 0.376 | 0.928 | 12.64 | 90.38 | |||
Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.
TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.
TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.
Server Offsets
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 132.163.97.5 | 1.244 | 1.253 | 1.262 | 1.288 | 1.334 | 1.352 | 1.363 | 0.072 | 0.099 | 0.022 | 1.292 | ms | 1.841e+05 | 1.048e+07 | ||
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 132.246.11.229 | -0.936 | 1.354 | 1.369 | 1.396 | 1.410 | 1.448 | 3.043 | 0.041 | 0.094 | 0.169 | 1.392 | ms | 393.7 | 3033 | ||
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 134.84.84.84 | -251.179 | -216.141 | -124.345 | -22.261 | 23.981 | 60.359 | 86.367 | 148.326 | 276.500 | 45.684 | -30.207 | µs | -11.23 | 43.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 204.9.54.119
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 204.9.54.119 | -622.393 | -620.599 | -616.988 | -612.288 | -608.462 | -606.923 | -606.598 | 8.526 | 13.676 | 2.656 | -612.456 | µs | -1.243e+07 | 2.878e+09 | ||
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)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:2600::99 (ntp1.wiktel.com) | -16.220 | -15.777 | -7.990 | 7.189 | 19.463 | 26.710 | 27.470 | 27.453 | 42.487 | 8.758 | 6.680 | µs | -0.8996 | 3.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::1 (time1.mbix.ca)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) | 17.003 | 24.686 | 45.153 | 91.515 | 624.899 | 808.732 | 856.781 | 579.746 | 784.046 | 161.072 | 138.847 | µs | 2.646 | 9.823 | ||
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)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2606:4700:f1::1 (time.cloudflare.com) | -916.079 | -834.387 | -801.325 | -716.839 | -596.505 | -546.809 | -500.834 | 204.820 | 287.578 | 60.148 | -715.460 | µs | -2182 | 2.863e+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:f128::50
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f128::50 | 1.139 | 1.172 | 1.188 | 1.221 | 1.259 | 1.273 | 1.289 | 0.071 | 0.100 | 0.022 | 1.222 | ms | 1.595e+05 | 8.659e+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 2607:f388::123:2 (ntp2.doit.wisc.edu)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) | -87.654 | -74.644 | -65.765 | -48.289 | -28.100 | -18.805 | -15.865 | 37.665 | 55.839 | 10.849 | -47.649 | µs | -173 | 1024 | ||
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)
.png)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SHM(1) | -20.948 | -9.166 | -5.620 | 0.504 | 2.941 | 4.198 | 8.346 | 8.561 | 13.364 | 2.569 | -0.004 | µs | -5.886 | 22.84 | ||
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
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 132.163.97.5 | 0.010 | 0.013 | 0.018 | 0.036 | 0.061 | 0.074 | 15.673 | 0.043 | 0.060 | 0.909 | 0.089 | ms | 13.64 | 236.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 132.246.11.229
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 132.246.11.229 | 0.000 | 0.000 | 0.005 | 0.035 | 1.600 | 29.789 | 29.789 | 1.595 | 29.789 | 3.521 | 0.680 | ms | 4.374 | 37.79 | ||
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 134.84.84.84 | 1.682 | 2.533 | 4.392 | 12.981 | 45.578 | 118.773 | 165.750 | 41.186 | 116.240 | 17.859 | 17.428 | µs | 4.231 | 27.85 | ||
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
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 204.9.54.119 | 1.713 | 1.909 | 3.280 | 7.467 | 14.316 | 17.967 | 162.525 | 11.036 | 16.058 | 9.511 | 8.559 | µs | 13.94 | 224.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Server Jitter 2600:2600::99 (ntp1.wiktel.com)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:2600::99 (ntp1.wiktel.com) | 5.962 | 6.802 | 8.085 | 16.311 | 34.097 | 121.272 | 131.104 | 26.012 | 114.470 | 13.269 | 19.013 | µs | 6.875 | 54.66 | ||
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)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) | 2.428 | 3.765 | 6.339 | 12.593 | 38.255 | 93.244 | 143.559 | 31.916 | 89.479 | 16.446 | 17.412 | µs | 4.204 | 24.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 2606:4700:f1::1 (time.cloudflare.com)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2606:4700:f1::1 (time.cloudflare.com) | 4.832 | 5.703 | 6.640 | 20.586 | 64.242 | 166.117 | 1,367.612 | 57.602 | 160.414 | 112.614 | 35.177 | µs | 8.937 | 105.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:f128::50
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f128::50 | 10.132 | 11.975 | 18.084 | 34.853 | 65.755 | 661.060 | 808.307 | 47.671 | 649.085 | 77.459 | 46.691 | µs | 6.205 | 51.21 | ||
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)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) | 2.930 | 5.333 | 8.194 | 23.209 | 257.348 | 776.863 | 1,131.242 | 249.154 | 771.530 | 109.187 | 57.875 | µs | 4.256 | 37.18 | ||
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)
.png)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SHM(1) | 0.130 | 0.410 | 0.648 | 2.626 | 7.051 | 9.799 | 20.907 | 6.403 | 9.389 | 2.089 | 3.047 | µs | 2.946 | 10.72 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Summary
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Frequency Offset | -14.021 | -13.950 | -13.894 | -13.482 | -13.251 | -13.206 | -13.144 | 0.643 | 0.745 | 0.218 | -13.552 | ppm | -2.533e+05 | 1.603e+07 | ||
| Local Clock Time Offset | -20.947 | -9.165 | -5.619 | 0.503 | 2.940 | 4.197 | 8.345 | 8.559 | 13.362 | 2.568 | -0.004 | µs | -5.887 | 22.85 | ||
| Local RMS Frequency Jitter | 0.854 | 1.536 | 2.096 | 4.515 | 7.844 | 9.729 | 14.860 | 5.748 | 8.193 | 1.806 | 4.682 | ppb | 9.464 | 29.37 | ||
| Local RMS Time Jitter | 0.478 | 1.017 | 1.390 | 3.083 | 5.513 | 6.909 | 10.876 | 4.123 | 5.892 | 1.296 | 3.214 | µs | 8.405 | 25.98 | ||
| Server Jitter 132.163.97.5 | 0.010 | 0.013 | 0.018 | 0.036 | 0.061 | 0.074 | 15.673 | 0.043 | 0.060 | 0.909 | 0.089 | ms | 13.64 | 236.8 | ||
| Server Jitter 132.246.11.229 | 0.000 | 0.000 | 0.005 | 0.035 | 1.600 | 29.789 | 29.789 | 1.595 | 29.789 | 3.521 | 0.680 | ms | 4.374 | 37.79 | ||
| Server Jitter 134.84.84.84 | 1.682 | 2.533 | 4.392 | 12.981 | 45.578 | 118.773 | 165.750 | 41.186 | 116.240 | 17.859 | 17.428 | µs | 4.231 | 27.85 | ||
| Server Jitter 204.9.54.119 | 1.713 | 1.909 | 3.280 | 7.467 | 14.316 | 17.967 | 162.525 | 11.036 | 16.058 | 9.511 | 8.559 | µs | 13.94 | 224.9 | ||
| Server Jitter 2600:2600::99 (ntp1.wiktel.com) | 5.962 | 6.802 | 8.085 | 16.311 | 34.097 | 121.272 | 131.104 | 26.012 | 114.470 | 13.269 | 19.013 | µs | 6.875 | 54.66 | ||
| Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) | 2.428 | 3.765 | 6.339 | 12.593 | 38.255 | 93.244 | 143.559 | 31.916 | 89.479 | 16.446 | 17.412 | µs | 4.204 | 24.09 | ||
| Server Jitter 2606:4700:f1::1 (time.cloudflare.com) | 4.832 | 5.703 | 6.640 | 20.586 | 64.242 | 166.117 | 1,367.612 | 57.602 | 160.414 | 112.614 | 35.177 | µs | 8.937 | 105.7 | ||
| Server Jitter 2607:f128::50 | 10.132 | 11.975 | 18.084 | 34.853 | 65.755 | 661.060 | 808.307 | 47.671 | 649.085 | 77.459 | 46.691 | µs | 6.205 | 51.21 | ||
| Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) | 2.930 | 5.333 | 8.194 | 23.209 | 257.348 | 776.863 | 1,131.242 | 249.154 | 771.530 | 109.187 | 57.875 | µs | 4.256 | 37.18 | ||
| Server Jitter SHM(1) | 0.130 | 0.410 | 0.648 | 2.626 | 7.051 | 9.799 | 20.907 | 6.403 | 9.389 | 2.089 | 3.047 | µs | 2.946 | 10.72 | ||
| Server Offset 132.163.97.5 | 1.244 | 1.253 | 1.262 | 1.288 | 1.334 | 1.352 | 1.363 | 0.072 | 0.099 | 0.022 | 1.292 | ms | 1.841e+05 | 1.048e+07 | ||
| Server Offset 132.246.11.229 | -0.936 | 1.354 | 1.369 | 1.396 | 1.410 | 1.448 | 3.043 | 0.041 | 0.094 | 0.169 | 1.392 | ms | 393.7 | 3033 | ||
| Server Offset 134.84.84.84 | -251.179 | -216.141 | -124.345 | -22.261 | 23.981 | 60.359 | 86.367 | 148.326 | 276.500 | 45.684 | -30.207 | µs | -11.23 | 43.17 | ||
| Server Offset 204.9.54.119 | -622.393 | -620.599 | -616.988 | -612.288 | -608.462 | -606.923 | -606.598 | 8.526 | 13.676 | 2.656 | -612.456 | µs | -1.243e+07 | 2.878e+09 | ||
| Server Offset 2600:2600::99 (ntp1.wiktel.com) | -16.220 | -15.777 | -7.990 | 7.189 | 19.463 | 26.710 | 27.470 | 27.453 | 42.487 | 8.758 | 6.680 | µs | -0.8996 | 3.24 | ||
| Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) | 17.003 | 24.686 | 45.153 | 91.515 | 624.899 | 808.732 | 856.781 | 579.746 | 784.046 | 161.072 | 138.847 | µs | 2.646 | 9.823 | ||
| Server Offset 2606:4700:f1::1 (time.cloudflare.com) | -916.079 | -834.387 | -801.325 | -716.839 | -596.505 | -546.809 | -500.834 | 204.820 | 287.578 | 60.148 | -715.460 | µs | -2182 | 2.863e+04 | ||
| Server Offset 2607:f128::50 | 1.139 | 1.172 | 1.188 | 1.221 | 1.259 | 1.273 | 1.289 | 0.071 | 0.100 | 0.022 | 1.222 | ms | 1.595e+05 | 8.659e+06 | ||
| Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) | -87.654 | -74.644 | -65.765 | -48.289 | -28.100 | -18.805 | -15.865 | 37.665 | 55.839 | 10.849 | -47.649 | µs | -173 | 1024 | ||
| Server Offset SHM(1) | -20.948 | -9.166 | -5.620 | 0.504 | 2.941 | 4.198 | 8.346 | 8.561 | 13.364 | 2.569 | -0.004 | µs | -5.886 | 22.84 | ||
| TDOP | 0.570 | 0.590 | 0.630 | 0.830 | 1.490 | 2.490 | 4.630 | 0.860 | 1.900 | 0.376 | 0.928 | 12.64 | 90.38 | |||
| nSats | 5.000 | 6.000 | 7.000 | 9.000 | 11.000 | 11.000 | 12.000 | 4.000 | 5.000 | 1.155 | 8.874 | nSat | 318.6 | 2265 | ||
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.
