NTPsec

ntp2.wiktel.com

Report generated: Wed Apr 2 10:53:02 2025 UTC
Start Time: Tue Apr 1 10:53:02 2025 UTC
End Time: Wed Apr 2 10:53:02 2025 UTC
Report Period: 1.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 -20.989 -8.868 -5.250 0.463 3.214 4.442 8.076 8.464 13.310 2.571 0.002 µs -5.6 20.91
Local Clock Frequency Offset -13.483 -13.437 -13.414 -13.281 -13.040 -13.014 -12.979 0.374 0.423 0.118 -13.253 ppm -1.462e+06 1.66e+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.681 1.169 1.516 3.069 5.401 6.704 11.026 3.885 5.535 1.203 3.207 µs 10.46 34.09

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 1.008 1.676 2.256 4.583 7.763 9.550 14.767 5.507 7.874 1.691 4.729 ppb 11.9 38.78

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 -20.989 -8.868 -5.250 0.463 3.214 4.442 8.076 8.464 13.310 2.571 0.002 µs -5.6 20.91

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.126 -1.117 -1.109 -1.070 -1.036 -1.017 -1.011 0.072 0.101 0.021 -1.071 ms -1.393e+05 7.225e+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 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.095 -1.065 -1.038 -0.976 -0.805 0.057 0.142 0.109 -1.070 ms -1308 1.522e+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 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 -92.046 -77.081 -66.617 -4.279 24.720 44.626 60.016 91.337 121.707 27.977 -11.691 µs -7.685 22.27

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 -871.793 -868.234 -864.309 -855.833 -847.247 -843.284 -839.301 17.062 24.950 4.999 -855.689 µs -5.104e+06 8.789e+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) -362.697 -361.745 -357.362 -340.001 -325.167 -318.440 -304.376 32.195 43.305 9.989 -340.484 µs -4.33e+04 1.523e+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) -443.607 -427.345 -413.508 -392.085 -375.840 -364.666 -361.260 37.668 62.679 11.156 -392.868 µs -4.761e+04 1.728e+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) -435.531 -435.531 -316.363 -233.210 140.535 237.212 237.212 456.898 672.743 153.083 -163.746 µs -13.92 37.65

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) -222.816 -208.587 -197.695 -159.022 -80.215 -57.058 -48.378 117.480 151.529 38.203 -149.575 µs -132.9 719.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 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 85.067 92.509 112.745 152.182 187.907 203.571 210.684 75.162 111.062 22.797 152.145 µs 199.5 1228

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) -117.374 -111.841 -92.398 -33.585 36.249 51.359 63.490 128.647 163.200 34.045 -32.149 µs -12.95 38.36

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) -20.990 -8.869 -5.251 0.464 3.215 4.443 8.077 8.466 13.312 2.571 0.002 µs -5.599 20.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 10.452 13.390 16.126 34.493 59.550 69.948 78.436 43.424 56.558 12.719 35.586 µs 11.74 36.64

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.042 0.633 0.915 1.345 1.751 1.897 2.242 0.836 1.264 0.289 1.316 ms 54.82 231.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 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 2.520 2.973 3.883 9.929 33.793 71.393 133.399 29.910 68.420 14.395 14.215 µs 4.541 32.61

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 3.257 3.976 5.411 9.540 15.908 19.213 25.006 10.497 15.237 3.146 9.846 µs 16.99 60.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.



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.910 6.224 7.812 18.050 34.146 39.539 44.094 26.334 33.315 8.008 19.238 µs 7.506 21.42

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) 4.078 4.819 7.015 13.507 29.506 97.663 1,384.409 22.491 92.844 111.884 24.832 µs 9.107 111

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) 4.112 4.112 5.998 16.879 231.947 301.540 301.540 225.949 297.428 60.420 38.529 µs 1.988 8.326

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) 3.085 3.716 6.934 16.027 54.527 725.548 733.769 47.593 721.832 83.484 30.031 µs 5.678 48.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: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 10.049 10.093 14.764 27.271 57.787 84.332 94.562 43.023 74.239 15.070 31.291 µs 5.876 19.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 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 5.315 9.191 20.941 52.693 90.024 100.313 43.502 84.709 14.699 24.406 µs 4.369 17.42

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.211 0.559 0.840 2.728 6.866 9.538 20.737 6.026 8.979 1.962 3.136 µs 3.583 13.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -13.483 -13.437 -13.414 -13.281 -13.040 -13.014 -12.979 0.374 0.423 0.118 -13.253 ppm -1.462e+06 1.66e+08
Local Clock Time Offset -20.989 -8.868 -5.250 0.463 3.214 4.442 8.076 8.464 13.310 2.571 0.002 µs -5.6 20.91
Local RMS Frequency Jitter 1.008 1.676 2.256 4.583 7.763 9.550 14.767 5.507 7.874 1.691 4.729 ppb 11.9 38.78
Local RMS Time Jitter 0.681 1.169 1.516 3.069 5.401 6.704 11.026 3.885 5.535 1.203 3.207 µs 10.46 34.09
Server Jitter 132.163.97.5 10.452 13.390 16.126 34.493 59.550 69.948 78.436 43.424 56.558 12.719 35.586 µs 11.74 36.64
Server Jitter 132.246.11.238 0.042 0.633 0.915 1.345 1.751 1.897 2.242 0.836 1.264 0.289 1.316 ms 54.82 231.2
Server Jitter 134.84.84.84 2.520 2.973 3.883 9.929 33.793 71.393 133.399 29.910 68.420 14.395 14.215 µs 4.541 32.61
Server Jitter 204.9.54.119 3.257 3.976 5.411 9.540 15.908 19.213 25.006 10.497 15.237 3.146 9.846 µs 16.99 60.71
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 4.910 6.224 7.812 18.050 34.146 39.539 44.094 26.334 33.315 8.008 19.238 µs 7.506 21.42
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 4.078 4.819 7.015 13.507 29.506 97.663 1,384.409 22.491 92.844 111.884 24.832 µs 9.107 111
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 4.112 4.112 5.998 16.879 231.947 301.540 301.540 225.949 297.428 60.420 38.529 µs 1.988 8.326
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 3.085 3.716 6.934 16.027 54.527 725.548 733.769 47.593 721.832 83.484 30.031 µs 5.678 48.1
Server Jitter 2607:f128::50 10.049 10.093 14.764 27.271 57.787 84.332 94.562 43.023 74.239 15.070 31.291 µs 5.876 19.6
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 2.402 5.315 9.191 20.941 52.693 90.024 100.313 43.502 84.709 14.699 24.406 µs 4.369 17.42
Server Jitter SHM(1) 0.211 0.559 0.840 2.728 6.866 9.538 20.737 6.026 8.979 1.962 3.136 µs 3.583 13.51
Server Offset 132.163.97.5 -1.126 -1.117 -1.109 -1.070 -1.036 -1.017 -1.011 0.072 0.101 0.021 -1.071 ms -1.393e+05 7.225e+06
Server Offset 132.246.11.238 -2.841 -1.118 -1.095 -1.065 -1.038 -0.976 -0.805 0.057 0.142 0.109 -1.070 ms -1308 1.522e+04
Server Offset 134.84.84.84 -92.046 -77.081 -66.617 -4.279 24.720 44.626 60.016 91.337 121.707 27.977 -11.691 µs -7.685 22.27
Server Offset 204.9.54.119 -871.793 -868.234 -864.309 -855.833 -847.247 -843.284 -839.301 17.062 24.950 4.999 -855.689 µs -5.104e+06 8.789e+08
Server Offset 2600:2600::99 (ntp1.wiktel.com) -362.697 -361.745 -357.362 -340.001 -325.167 -318.440 -304.376 32.195 43.305 9.989 -340.484 µs -4.33e+04 1.523e+06
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -443.607 -427.345 -413.508 -392.085 -375.840 -364.666 -361.260 37.668 62.679 11.156 -392.868 µs -4.761e+04 1.728e+06
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -435.531 -435.531 -316.363 -233.210 140.535 237.212 237.212 456.898 672.743 153.083 -163.746 µs -13.92 37.65
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -222.816 -208.587 -197.695 -159.022 -80.215 -57.058 -48.378 117.480 151.529 38.203 -149.575 µs -132.9 719.8
Server Offset 2607:f128::50 85.067 92.509 112.745 152.182 187.907 203.571 210.684 75.162 111.062 22.797 152.145 µs 199.5 1228
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -117.374 -111.841 -92.398 -33.585 36.249 51.359 63.490 128.647 163.200 34.045 -32.149 µs -12.95 38.36
Server Offset SHM(1) -20.990 -8.869 -5.251 0.464 3.215 4.443 8.077 8.466 13.312 2.571 0.002 µs -5.599 20.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!