NTPsec

ntp2.wiktel.com

Report generated: Tue Mar 28 04:45:07 2023 UTC
Start Time: Tue Mar 21 04:45:01 2023 UTC
End Time: Tue Mar 28 04:45:01 2023 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 -61.980 -11.557 -7.387 0.642 4.324 6.007 403.652 11.711 17.564 3.759 -0.008 µs 4.188 935.9
Local Clock Frequency Offset -15.180 -14.832 -14.595 -14.088 -13.352 -12.943 -6.091 1.243 1.888 0.399 -14.045 ppm -4.759e+04 1.727e+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.642 1.556 2.135 4.153 6.922 8.506 150.378 4.787 6.950 1.677 4.292 µs 23.29 1113

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 2.546 3.433 6.378 10.137 12.283 2,229.904 6.704 9.737 11.812 6.638 ppb 124.6 1.826e+04

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 -61.980 -11.557 -7.387 0.642 4.324 6.007 403.652 11.711 17.564 3.759 -0.008 µs 4.188 935.9

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 4.000 6.000 7.000 9.000 11.000 12.000 13.000 4.000 6.000 1.267 8.817 nSat 229.6 1481
TDOP 0.520 0.580 0.610 0.850 1.340 1.910 5.420 0.730 1.330 0.364 0.920 14.63 125.9

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 0.251 0.265 0.332 2.095 2.171 3.172 3.221 1.838 2.906 0.472 2.047 ms 44.93 172.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 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.989 -0.975 2.033 2.087 2.105 2.113 2.569 0.072 3.088 0.646 1.944 ms 9.887 25.54

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 -222.158 -158.376 -101.936 15.186 100.566 143.116 398.295 202.502 301.492 62.349 8.302 µs -3.501 10.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 204.9.54.119

peer offset 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.9.54.119 -2.198 -2.173 -0.428 -0.347 -0.328 3.228 5.683 0.099 5.401 0.662 -0.366 ms -5.358 31.45

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) -85.916 -63.083 -55.602 -38.663 -21.538 -14.978 -4.776 34.064 48.105 10.451 -38.523 µs -117 617.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 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) -3,359.959 -91.627 -54.844 78.863 186.658 231.055 259.270 241.502 322.682 106.659 70.120 µs -17.72 551.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 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) 0.451 0.874 1.738 1.977 2.207 2.725 3.239 0.468 1.851 0.225 1.976 ms 491.1 3984

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 -64.154 -18.571 49.857 442.043 478.846 494.881 514.119 428.989 513.452 100.788 420.283 µs 37.65 129.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: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) -88.207 -77.049 -68.523 -48.834 -27.761 -1.596 954.412 40.762 75.453 41.847 -45.991 µs 1.162 249.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 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) -1,000.005 -0.012 -0.007 0.001 0.004 0.006 0.404 0.012 0.018 35.138 -1.237 ms -32.6 931.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 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.000 0.000 29.356 70.412 949.704 1,960.794 70.412 949.704 159.279 51.949 µs 5.25 51.77

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.005 0.007 0.011 0.037 0.732 7.095 211.333 0.721 7.087 8.197 0.695 ms 17.36 415.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 1.097 4.020 5.753 17.454 62.077 116.866 389.016 56.324 112.846 22.917 24.152 µs 4.808 48.65

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.008 0.017 0.022 0.050 1.892 4.615 7.406 1.870 4.598 0.828 0.301 ms 2.468 18.06

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.357 7.525 10.324 19.930 37.339 120.825 252.575 27.015 113.300 15.267 22.516 µs 7.632 69.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)

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) 1.951 4.139 5.809 11.743 29.609 51.792 3,461.322 23.800 47.653 100.780 18.851 µs 21.99 662.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.004 0.008 0.012 0.036 0.417 1.667 4.089 0.405 1.659 0.329 0.108 ms 5.031 51.65

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.007 0.011 0.015 0.031 0.070 0.333 28.354 0.055 0.322 1.041 0.086 ms 20.37 508.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 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.006 0.010 0.018 13.010 30.287 37.988 49.052 30.269 37.978 10.079 12.943 ms 1.31 3.585

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.001 0.001 0.004 0.009 0.012 999.998 0.008 0.012 5.143 0.038 ms 157.2 2.637e+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 -15.180 -14.832 -14.595 -14.088 -13.352 -12.943 -6.091 1.243 1.888 0.399 -14.045 ppm -4.759e+04 1.727e+06
Local Clock Time Offset -61.980 -11.557 -7.387 0.642 4.324 6.007 403.652 11.711 17.564 3.759 -0.008 µs 4.188 935.9
Local RMS Frequency Jitter 1.008 2.546 3.433 6.378 10.137 12.283 2,229.904 6.704 9.737 11.812 6.638 ppb 124.6 1.826e+04
Local RMS Time Jitter 0.642 1.556 2.135 4.153 6.922 8.506 150.378 4.787 6.950 1.677 4.292 µs 23.29 1113
Server Jitter 132.163.97.5 0.000 0.000 0.000 29.356 70.412 949.704 1,960.794 70.412 949.704 159.279 51.949 µs 5.25 51.77
Server Jitter 132.246.11.238 0.005 0.007 0.011 0.037 0.732 7.095 211.333 0.721 7.087 8.197 0.695 ms 17.36 415.2
Server Jitter 134.84.84.84 1.097 4.020 5.753 17.454 62.077 116.866 389.016 56.324 112.846 22.917 24.152 µs 4.808 48.65
Server Jitter 204.9.54.119 0.008 0.017 0.022 0.050 1.892 4.615 7.406 1.870 4.598 0.828 0.301 ms 2.468 18.06
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 4.357 7.525 10.324 19.930 37.339 120.825 252.575 27.015 113.300 15.267 22.516 µs 7.632 69.66
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 1.951 4.139 5.809 11.743 29.609 51.792 3,461.322 23.800 47.653 100.780 18.851 µs 21.99 662.3
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.004 0.008 0.012 0.036 0.417 1.667 4.089 0.405 1.659 0.329 0.108 ms 5.031 51.65
Server Jitter 2607:f128::50 0.007 0.011 0.015 0.031 0.070 0.333 28.354 0.055 0.322 1.041 0.086 ms 20.37 508.8
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 0.006 0.010 0.018 13.010 30.287 37.988 49.052 30.269 37.978 10.079 12.943 ms 1.31 3.585
Server Jitter SHM(1) 0.000 0.001 0.001 0.004 0.009 0.012 999.998 0.008 0.012 5.143 0.038 ms 157.2 2.637e+04
Server Offset 132.163.97.5 0.251 0.265 0.332 2.095 2.171 3.172 3.221 1.838 2.906 0.472 2.047 ms 44.93 172.8
Server Offset 132.246.11.238 -0.989 -0.975 2.033 2.087 2.105 2.113 2.569 0.072 3.088 0.646 1.944 ms 9.887 25.54
Server Offset 134.84.84.84 -222.158 -158.376 -101.936 15.186 100.566 143.116 398.295 202.502 301.492 62.349 8.302 µs -3.501 10.08
Server Offset 204.9.54.119 -2.198 -2.173 -0.428 -0.347 -0.328 3.228 5.683 0.099 5.401 0.662 -0.366 ms -5.358 31.45
Server Offset 2600:2600::99 (ntp1.wiktel.com) -85.916 -63.083 -55.602 -38.663 -21.538 -14.978 -4.776 34.064 48.105 10.451 -38.523 µs -117 617.2
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -3,359.959 -91.627 -54.844 78.863 186.658 231.055 259.270 241.502 322.682 106.659 70.120 µs -17.72 551.4
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 0.451 0.874 1.738 1.977 2.207 2.725 3.239 0.468 1.851 0.225 1.976 ms 491.1 3984
Server Offset 2607:f128::50 -64.154 -18.571 49.857 442.043 478.846 494.881 514.119 428.989 513.452 100.788 420.283 µs 37.65 129.8
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -88.207 -77.049 -68.523 -48.834 -27.761 -1.596 954.412 40.762 75.453 41.847 -45.991 µs 1.162 249.2
Server Offset SHM(1) -1,000.005 -0.012 -0.007 0.001 0.004 0.006 0.404 0.012 0.018 35.138 -1.237 ms -32.6 931.6
TDOP 0.520 0.580 0.610 0.850 1.340 1.910 5.420 0.730 1.330 0.364 0.920 14.63 125.9
nSats 4.000 6.000 7.000 9.000 11.000 12.000 13.000 4.000 6.000 1.267 8.817 nSat 229.6 1481
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!