NTPsec

ntp2.wiktel.com

Report generated: Fri Mar 29 04:45:06 2024 UTC
Start Time: Fri Mar 22 04:45:00 2024 UTC
End Time: Fri Mar 29 04:45:00 2024 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 -29.776 -10.404 -6.625 0.581 3.435 4.865 20.251 10.060 15.269 2.990 -0.001 µs -5.831 22.36
Local Clock Frequency Offset -14.140 -13.959 -13.854 -13.526 -12.814 -12.526 -12.212 1.040 1.433 0.316 -13.460 ppm -8.302e+04 3.626e+06

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.119 1.129 1.599 3.573 6.404 7.999 14.594 4.805 6.870 1.497 3.728 µs 8.502 26.42

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.000 1.760 2.452 5.277 9.127 11.358 22.134 6.675 9.598 2.079 5.459 ppb 9.856 31.09

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 -29.776 -10.404 -6.625 0.581 3.435 4.865 20.251 10.060 15.269 2.990 -0.001 µs -5.831 22.36

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 5.000 6.000 7.000 9.000 11.000 11.000 12.000 4.000 5.000 1.152 8.894 nSat 324 2316
TDOP 0.550 0.590 0.620 0.820 1.320 1.680 4.300 0.700 1.090 0.254 0.893 26.16 129.7

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

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.463 1.483 1.496 1.542 2.683 2.714 2.745 1.187 1.231 0.447 1.774 ms 36.46 149.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 132.246.11.229

peer offset 132.246.11.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.229 1.371 1.371 1.371 1.392 2.238 2.238 2.238 0.867 0.867 0.371 1.596 ms 47.06 201.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 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 0.311 0.361 0.374 0.393 0.409 0.418 215.336 0.035 0.057 4.764 0.498 ms 41.67 1877

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 -0.625 -0.348 -0.138 -0.020 0.052 0.088 214.820 0.189 0.437 8.183 0.282 ms 22.38 591.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 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 -0.814 -0.623 -0.619 -0.612 -0.607 -0.605 214.281 0.012 0.018 4.730 -0.508 ms 40.71 1869

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) -0.014 -0.008 -0.003 0.012 0.028 0.035 214.942 0.031 0.043 9.505 0.433 ms 18.79 428.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 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.723 -0.548 -0.342 0.095 0.378 0.747 215.064 0.720 1.294 9.496 0.497 ms 18.84 430

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) -0.778 -0.660 -0.397 1.229 1.463 1.627 216.315 1.860 2.287 9.421 1.524 ms 19.6 446.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 -0.101 0.768 0.793 0.833 0.868 0.883 215.724 0.076 0.116 6.675 1.038 ms 28.99 929.6

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

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

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

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



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

peer offset 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -0.099 -0.077 -0.066 -0.044 -0.020 -0.008 215.445 0.046 0.068 6.755 0.184 ms 27.5 879.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 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) -0.030 -0.010 -0.007 0.001 0.003 0.005 214.885 0.010 0.015 0.957 0.004 ms 220.5 4.95e+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 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 0.014 0.019 0.037 0.828 1.104 1.189 0.810 1.091 0.230 0.101 ms 1.659 8.009

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 132.246.11.229

peer jitter 132.246.11.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.229 0.000 0.000 0.000 605.878 866.711 866.711 866.711 866.711 866.711 314.421 490.246 µs 1.346 2.838

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.008 0.013 0.046 1.226 6.873 165.165 1.213 6.865 6.378 0.710 ms 13.41 276.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 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 3.501 5.430 16.828 82.043 210.814 326.181 76.613 207.313 35.439 27.277 µs 3.586 22.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 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 2.669 4.033 8.134 14.597 18.890 480.193 10.564 16.221 21.756 9.884 µs 15.6 289.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.416 9.255 18.541 33.347 46.016 559.967 24.092 39.600 20.268 20.677 µs 19.31 491.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 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 5.014 7.740 15.763 41.085 86.709 1,140.271 33.345 81.695 44.619 20.948 µs 20.62 504.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 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 0.005 0.009 0.030 0.167 0.571 8.425 0.158 0.566 0.506 0.088 ms 10.73 160.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 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 9.638 13.169 29.225 65.802 123.015 1,273.223 52.633 113.377 81.588 39.640 µs 10.21 131.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 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 0.007 0.010 0.026 0.263 0.876 40.399 0.252 0.869 1.777 0.196 ms 12.01 218.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 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.000 0.001 0.003 0.008 0.011 214.870 0.007 0.011 0.629 0.006 ms 244 6.702e+04

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 -14.140 -13.959 -13.854 -13.526 -12.814 -12.526 -12.212 1.040 1.433 0.316 -13.460 ppm -8.302e+04 3.626e+06
Local Clock Time Offset -29.776 -10.404 -6.625 0.581 3.435 4.865 20.251 10.060 15.269 2.990 -0.001 µs -5.831 22.36
Local RMS Frequency Jitter 0.000 1.760 2.452 5.277 9.127 11.358 22.134 6.675 9.598 2.079 5.459 ppb 9.856 31.09
Local RMS Time Jitter 0.119 1.129 1.599 3.573 6.404 7.999 14.594 4.805 6.870 1.497 3.728 µs 8.502 26.42
Server Jitter 132.163.97.5 0.000 0.014 0.019 0.037 0.828 1.104 1.189 0.810 1.091 0.230 0.101 ms 1.659 8.009
Server Jitter 132.246.11.229 0.000 0.000 0.000 605.878 866.711 866.711 866.711 866.711 866.711 314.421 490.246 µs 1.346 2.838
Server Jitter 132.246.11.238 0.000 0.008 0.013 0.046 1.226 6.873 165.165 1.213 6.865 6.378 0.710 ms 13.41 276.7
Server Jitter 134.84.84.84 0.000 3.501 5.430 16.828 82.043 210.814 326.181 76.613 207.313 35.439 27.277 µs 3.586 22.9
Server Jitter 204.9.54.119 0.000 2.669 4.033 8.134 14.597 18.890 480.193 10.564 16.221 21.756 9.884 µs 15.6 289.8
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 0.000 6.416 9.255 18.541 33.347 46.016 559.967 24.092 39.600 20.268 20.677 µs 19.31 491.6
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 0.000 5.014 7.740 15.763 41.085 86.709 1,140.271 33.345 81.695 44.619 20.948 µs 20.62 504.7
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.005 0.009 0.030 0.167 0.571 8.425 0.158 0.566 0.506 0.088 ms 10.73 160.4
Server Jitter 2607:f128::50 0.000 9.638 13.169 29.225 65.802 123.015 1,273.223 52.633 113.377 81.588 39.640 µs 10.21 131.5
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 0.000 0.007 0.010 0.026 0.263 0.876 40.399 0.252 0.869 1.777 0.196 ms 12.01 218.5
Server Jitter SHM(1) 0.000 0.000 0.001 0.003 0.008 0.011 214.870 0.007 0.011 0.629 0.006 ms 244 6.702e+04
Server Offset 132.163.97.5 1.463 1.483 1.496 1.542 2.683 2.714 2.745 1.187 1.231 0.447 1.774 ms 36.46 149.4
Server Offset 132.246.11.229 1.371 1.371 1.371 1.392 2.238 2.238 2.238 0.867 0.867 0.371 1.596 ms 47.06 201.9
Server Offset 132.246.11.238 0.311 0.361 0.374 0.393 0.409 0.418 215.336 0.035 0.057 4.764 0.498 ms 41.67 1877
Server Offset 134.84.84.84 -0.625 -0.348 -0.138 -0.020 0.052 0.088 214.820 0.189 0.437 8.183 0.282 ms 22.38 591.6
Server Offset 204.9.54.119 -0.814 -0.623 -0.619 -0.612 -0.607 -0.605 214.281 0.012 0.018 4.730 -0.508 ms 40.71 1869
Server Offset 2600:2600::99 (ntp1.wiktel.com) -0.014 -0.008 -0.003 0.012 0.028 0.035 214.942 0.031 0.043 9.505 0.433 ms 18.79 428.6
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -0.723 -0.548 -0.342 0.095 0.378 0.747 215.064 0.720 1.294 9.496 0.497 ms 18.84 430
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -0.778 -0.660 -0.397 1.229 1.463 1.627 216.315 1.860 2.287 9.421 1.524 ms 19.6 446.2
Server Offset 2607:f128::50 -0.101 0.768 0.793 0.833 0.868 0.883 215.724 0.076 0.116 6.675 1.038 ms 28.99 929.6
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -0.099 -0.077 -0.066 -0.044 -0.020 -0.008 215.445 0.046 0.068 6.755 0.184 ms 27.5 879.4
Server Offset SHM(1) -0.030 -0.010 -0.007 0.001 0.003 0.005 214.885 0.010 0.015 0.957 0.004 ms 220.5 4.95e+04
TDOP 0.550 0.590 0.620 0.820 1.320 1.680 4.300 0.700 1.090 0.254 0.893 26.16 129.7
nSats 5.000 6.000 7.000 9.000 11.000 11.000 12.000 4.000 5.000 1.152 8.894 nSat 324 2316
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!