NTPsec

ntp2.wiktel.com

Report generated: Thu Apr 3 16:45:07 2025 UTC
Start Time: Thu Mar 27 16:45:02 2025 UTC
End Time: Thu Apr 3 16: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 -145.733 -8.986 -5.276 0.461 3.201 4.498 35.753 8.477 13.484 2.597 -0.000 µs -6.143 55.94
Local Clock Frequency Offset -13.624 -13.486 -13.432 -13.266 -13.036 -12.955 -12.825 0.397 0.531 0.123 -13.253 ppm -1.289e+06 1.403e+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.567 1.135 1.515 3.063 5.386 6.754 73.968 3.871 5.619 1.259 3.207 µs 12.43 195.3

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.888 1.678 2.268 4.586 7.796 9.640 100.714 5.528 7.962 1.778 4.751 ppb 13.63 197

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 -145.733 -8.986 -5.276 0.461 3.201 4.498 35.753 8.477 13.484 2.597 -0.000 µs -6.143 55.94

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.130 -1.119 -1.111 -1.074 -1.041 -1.027 2.278 0.071 0.092 0.150 -1.068 ms -542.3 4567

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.238

peer offset 132.246.11.238 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.238 -2.841 -1.118 -1.090 -1.065 -1.039 -1.004 -0.751 0.050 0.114 0.127 -1.073 ms -890.3 9261

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 -183.680 -86.641 -62.163 -7.090 26.142 44.315 93.539 88.305 130.956 26.436 -10.271 µs -7.817 26.87

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 -910.510 -871.454 -865.106 -855.891 -847.996 -844.569 -839.301 17.110 26.885 6.531 -856.341 µs -2.307e+06 3.048e+08

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) -366.310 -361.086 -354.519 -339.683 -325.242 -319.061 -304.376 29.277 42.025 9.125 -339.775 µs -5.601e+04 2.146e+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) -450.355 -429.831 -412.673 -391.598 -374.155 -366.674 -356.006 38.518 63.157 11.751 -392.516 µs -4.082e+04 1.408e+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 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) -436.430 -395.759 -374.032 -315.851 -124.996 129.459 237.212 249.036 525.218 82.745 -294.851 µs -106.1 522.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 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) -726.721 -420.776 -376.899 -287.722 -114.606 -80.177 -48.378 262.293 340.599 81.027 -271.464 µs -95.17 472.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 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 69.148 104.011 119.154 152.230 185.899 201.723 239.841 66.745 97.712 20.186 152.565 µs 301.7 2111

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) -298.355 -176.588 -88.050 -30.244 23.571 51.946 87.822 111.621 228.534 38.788 -32.259 µs -13.25 54.11

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) -145.734 -8.987 -5.277 0.462 3.202 4.499 35.754 8.479 13.486 2.597 -0.000 µs -6.142 55.9

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

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

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

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



Server 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 7.336 13.613 18.151 35.173 61.099 75.281 3,310.440 42.948 61.668 132.526 43.239 µs 19.05 420.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 132.246.11.238

peer jitter 132.246.11.238 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.238 0.000 0.596 0.935 1.345 1.687 1.814 2.242 0.752 1.218 0.272 1.317 ms 67.17 296.6

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 1.667 2.815 4.009 9.360 27.986 45.555 133.399 23.977 42.740 9.248 12.027 µs 5.015 42.75

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 2.383 4.175 5.456 9.734 16.110 19.358 261.319 10.654 15.183 9.071 10.376 µs 22.68 606.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 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) 4.262 6.830 8.795 19.168 34.251 233.420 456.875 25.456 226.590 40.838 23.837 µs 8.257 82.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 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) 3.165 5.214 6.947 13.638 29.590 50.758 1,384.409 22.643 45.544 53.082 17.978 µs 19.07 440.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 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) 3.335 5.349 6.865 14.643 43.993 174.362 661.666 37.128 169.013 34.363 21.225 µs 9.098 133.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 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.003 0.004 0.007 0.015 0.046 0.166 5.387 0.040 0.161 0.277 0.037 ms 14.53 271.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: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 7.525 10.071 13.282 27.234 55.255 77.812 749.207 41.973 67.741 27.927 30.904 µs 17.94 440.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 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) 2.402 7.219 9.868 22.416 59.698 88.194 284.488 49.830 80.975 16.744 26.142 µs 5.436 44.91

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.150 0.539 0.827 2.717 6.886 9.732 146.458 6.059 9.193 2.018 3.134 µs 5.198 122.6

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.624 -13.486 -13.432 -13.266 -13.036 -12.955 -12.825 0.397 0.531 0.123 -13.253 ppm -1.289e+06 1.403e+08
Local Clock Time Offset -145.733 -8.986 -5.276 0.461 3.201 4.498 35.753 8.477 13.484 2.597 -0.000 µs -6.143 55.94
Local RMS Frequency Jitter 0.888 1.678 2.268 4.586 7.796 9.640 100.714 5.528 7.962 1.778 4.751 ppb 13.63 197
Local RMS Time Jitter 0.567 1.135 1.515 3.063 5.386 6.754 73.968 3.871 5.619 1.259 3.207 µs 12.43 195.3
Server Jitter 132.163.97.5 7.336 13.613 18.151 35.173 61.099 75.281 3,310.440 42.948 61.668 132.526 43.239 µs 19.05 420.1
Server Jitter 132.246.11.238 0.000 0.596 0.935 1.345 1.687 1.814 2.242 0.752 1.218 0.272 1.317 ms 67.17 296.6
Server Jitter 134.84.84.84 1.667 2.815 4.009 9.360 27.986 45.555 133.399 23.977 42.740 9.248 12.027 µs 5.015 42.75
Server Jitter 204.9.54.119 2.383 4.175 5.456 9.734 16.110 19.358 261.319 10.654 15.183 9.071 10.376 µs 22.68 606.7
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 4.262 6.830 8.795 19.168 34.251 233.420 456.875 25.456 226.590 40.838 23.837 µs 8.257 82.54
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 3.165 5.214 6.947 13.638 29.590 50.758 1,384.409 22.643 45.544 53.082 17.978 µs 19.07 440.9
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 3.335 5.349 6.865 14.643 43.993 174.362 661.666 37.128 169.013 34.363 21.225 µs 9.098 133.9
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.003 0.004 0.007 0.015 0.046 0.166 5.387 0.040 0.161 0.277 0.037 ms 14.53 271.2
Server Jitter 2607:f128::50 7.525 10.071 13.282 27.234 55.255 77.812 749.207 41.973 67.741 27.927 30.904 µs 17.94 440.1
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 2.402 7.219 9.868 22.416 59.698 88.194 284.488 49.830 80.975 16.744 26.142 µs 5.436 44.91
Server Jitter SHM(1) 0.150 0.539 0.827 2.717 6.886 9.732 146.458 6.059 9.193 2.018 3.134 µs 5.198 122.6
Server Offset 132.163.97.5 -1.130 -1.119 -1.111 -1.074 -1.041 -1.027 2.278 0.071 0.092 0.150 -1.068 ms -542.3 4567
Server Offset 132.246.11.238 -2.841 -1.118 -1.090 -1.065 -1.039 -1.004 -0.751 0.050 0.114 0.127 -1.073 ms -890.3 9261
Server Offset 134.84.84.84 -183.680 -86.641 -62.163 -7.090 26.142 44.315 93.539 88.305 130.956 26.436 -10.271 µs -7.817 26.87
Server Offset 204.9.54.119 -910.510 -871.454 -865.106 -855.891 -847.996 -844.569 -839.301 17.110 26.885 6.531 -856.341 µs -2.307e+06 3.048e+08
Server Offset 2600:2600::99 (ntp1.wiktel.com) -366.310 -361.086 -354.519 -339.683 -325.242 -319.061 -304.376 29.277 42.025 9.125 -339.775 µs -5.601e+04 2.146e+06
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -450.355 -429.831 -412.673 -391.598 -374.155 -366.674 -356.006 38.518 63.157 11.751 -392.516 µs -4.082e+04 1.408e+06
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -436.430 -395.759 -374.032 -315.851 -124.996 129.459 237.212 249.036 525.218 82.745 -294.851 µs -106.1 522.8
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -726.721 -420.776 -376.899 -287.722 -114.606 -80.177 -48.378 262.293 340.599 81.027 -271.464 µs -95.17 472.7
Server Offset 2607:f128::50 69.148 104.011 119.154 152.230 185.899 201.723 239.841 66.745 97.712 20.186 152.565 µs 301.7 2111
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -298.355 -176.588 -88.050 -30.244 23.571 51.946 87.822 111.621 228.534 38.788 -32.259 µs -13.25 54.11
Server Offset SHM(1) -145.734 -8.987 -5.277 0.462 3.202 4.499 35.754 8.479 13.486 2.597 -0.000 µs -6.142 55.9
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!