NTPsec

ntp2.wiktel.com

Report generated: Thu Jun 1 01:53:02 2023 UTC
Start Time: Wed May 31 01:53:01 2023 UTC
End Time: Thu Jun 1 01:53:01 2023 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 -19.894 -9.043 -5.491 0.553 2.833 4.001 7.699 8.324 13.044 2.518 -0.002 µs -5.829 21.99
Local Clock Frequency Offset -14.187 -14.097 -14.052 -13.867 -13.692 -13.646 -13.593 0.360 0.452 0.104 -13.875 ppm -2.421e+06 3.25e+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.086 1.475 3.067 5.376 6.613 11.902 3.901 5.527 1.212 3.202 µs 10.07 31.97

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.880 1.637 2.191 4.464 7.595 9.212 14.892 5.404 7.575 1.677 4.624 ppb 11.34 36.13

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 -19.894 -9.043 -5.491 0.553 2.833 4.001 7.699 8.324 13.044 2.518 -0.002 µs -5.829 21.99

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.304 8.686 nSat 198.5 1221
TDOP 0.560 0.580 0.640 0.900 1.500 4.000 8.310 0.860 3.420 0.614 0.999 10.18 107.4

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 2.011 2.018 2.028 2.064 2.097 2.115 2.146 0.069 0.096 0.021 2.063 ms 8.62e+05 8.205e+07

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

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

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

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



Server Offset 132.246.11.227

peer offset 132.246.11.227 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.227 676.784 690.878 703.452 720.345 738.857 753.964 762.267 35.405 63.086 10.893 720.965 µs 2.772e+05 1.808e+07

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

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

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

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



Server Offset 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 -280.150 -261.934 -155.770 -14.735 76.781 133.186 136.702 232.551 395.120 73.483 -26.011 µs -7.467 23.96

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 -388.533 -387.865 -386.385 -383.940 -381.261 -379.970 -378.898 5.124 7.895 1.582 -383.858 µs -1.447e+07 3.527e+09

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

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

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

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



Server Offset 2600:2600::99 (ntp1.wiktel.com)

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) -71.234 -64.022 -60.079 -46.477 -29.577 -25.904 -24.167 30.502 38.118 9.046 -45.938 µs -242.6 1585

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) -328.941 -322.935 -242.422 -10.038 441.715 566.947 576.080 684.137 889.882 188.011 19.356 µs -2.447 5.814

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) 1.822 1.832 1.864 1.972 2.147 2.362 2.452 0.283 0.530 0.092 1.990 ms 8888 1.85e+05

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 379.588 385.351 403.574 442.481 477.465 490.322 495.130 73.891 104.971 22.153 440.757 µs 6804 1.296e+05

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) -102.674 -88.790 -73.608 -52.328 -30.991 -21.780 -12.393 42.617 67.010 13.528 -52.611 µs -131.7 722.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) -19.895 -9.044 -5.492 0.554 2.834 4.002 7.700 8.326 13.046 2.518 -0.001 µs -5.827 21.98

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.662 13.313 16.962 37.057 65.593 727.204 733.767 48.631 713.891 107.304 55.193 µs 4.15 24.97

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

peer jitter 132.246.11.227 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.227 0.007 0.009 0.019 0.071 2.077 5.196 6.523 2.058 5.187 1.007 0.399 ms 2.146 13.18

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.885 3.891 5.395 14.613 41.052 89.304 184.604 35.657 85.413 16.927 18.400 µs 5.344 44.43

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.001 0.001 0.002 0.004 1.489 5.071 7.946 1.487 5.069 0.876 0.247 ms 3.087 26.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 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) 5.759 7.143 8.395 17.164 30.513 33.792 126.708 22.118 26.649 9.077 18.253 µs 9.771 97.76

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.099 5.366 7.005 16.407 41.082 61.048 160.191 34.077 55.682 13.145 18.922 µs 6.39 57.83

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.189 6.463 10.857 34.474 103.238 238.804 4,710.777 92.381 232.341 275.102 59.245 µs 13.72 232

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.010 0.014 0.030 0.061 1.339 1.652 0.047 1.329 0.171 0.054 ms 5.868 51.94

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) 5.380 6.209 10.110 25.909 371.911 573.837 581.378 361.801 567.628 116.203 69.583 µs 1.628 7.337

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.117 0.436 0.717 2.662 6.822 9.661 21.205 6.105 9.225 1.995 3.055 µs 3.181 11.27

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.187 -14.097 -14.052 -13.867 -13.692 -13.646 -13.593 0.360 0.452 0.104 -13.875 ppm -2.421e+06 3.25e+08
Local Clock Time Offset -19.894 -9.043 -5.491 0.553 2.833 4.001 7.699 8.324 13.044 2.518 -0.002 µs -5.829 21.99
Local RMS Frequency Jitter 0.880 1.637 2.191 4.464 7.595 9.212 14.892 5.404 7.575 1.677 4.624 ppb 11.34 36.13
Local RMS Time Jitter 0.567 1.086 1.475 3.067 5.376 6.613 11.902 3.901 5.527 1.212 3.202 µs 10.07 31.97
Server Jitter 132.163.97.5 10.662 13.313 16.962 37.057 65.593 727.204 733.767 48.631 713.891 107.304 55.193 µs 4.15 24.97
Server Jitter 132.246.11.227 0.007 0.009 0.019 0.071 2.077 5.196 6.523 2.058 5.187 1.007 0.399 ms 2.146 13.18
Server Jitter 134.84.84.84 2.885 3.891 5.395 14.613 41.052 89.304 184.604 35.657 85.413 16.927 18.400 µs 5.344 44.43
Server Jitter 204.9.54.119 0.001 0.001 0.002 0.004 1.489 5.071 7.946 1.487 5.069 0.876 0.247 ms 3.087 26.3
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 5.759 7.143 8.395 17.164 30.513 33.792 126.708 22.118 26.649 9.077 18.253 µs 9.771 97.76
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 4.099 5.366 7.005 16.407 41.082 61.048 160.191 34.077 55.682 13.145 18.922 µs 6.39 57.83
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 4.189 6.463 10.857 34.474 103.238 238.804 4,710.777 92.381 232.341 275.102 59.245 µs 13.72 232
Server Jitter 2607:f128::50 0.007 0.010 0.014 0.030 0.061 1.339 1.652 0.047 1.329 0.171 0.054 ms 5.868 51.94
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 5.380 6.209 10.110 25.909 371.911 573.837 581.378 361.801 567.628 116.203 69.583 µs 1.628 7.337
Server Jitter SHM(1) 0.117 0.436 0.717 2.662 6.822 9.661 21.205 6.105 9.225 1.995 3.055 µs 3.181 11.27
Server Offset 132.163.97.5 2.011 2.018 2.028 2.064 2.097 2.115 2.146 0.069 0.096 0.021 2.063 ms 8.62e+05 8.205e+07
Server Offset 132.246.11.227 676.784 690.878 703.452 720.345 738.857 753.964 762.267 35.405 63.086 10.893 720.965 µs 2.772e+05 1.808e+07
Server Offset 134.84.84.84 -280.150 -261.934 -155.770 -14.735 76.781 133.186 136.702 232.551 395.120 73.483 -26.011 µs -7.467 23.96
Server Offset 204.9.54.119 -388.533 -387.865 -386.385 -383.940 -381.261 -379.970 -378.898 5.124 7.895 1.582 -383.858 µs -1.447e+07 3.527e+09
Server Offset 2600:2600::99 (ntp1.wiktel.com) -71.234 -64.022 -60.079 -46.477 -29.577 -25.904 -24.167 30.502 38.118 9.046 -45.938 µs -242.6 1585
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -328.941 -322.935 -242.422 -10.038 441.715 566.947 576.080 684.137 889.882 188.011 19.356 µs -2.447 5.814
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 1.822 1.832 1.864 1.972 2.147 2.362 2.452 0.283 0.530 0.092 1.990 ms 8888 1.85e+05
Server Offset 2607:f128::50 379.588 385.351 403.574 442.481 477.465 490.322 495.130 73.891 104.971 22.153 440.757 µs 6804 1.296e+05
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -102.674 -88.790 -73.608 -52.328 -30.991 -21.780 -12.393 42.617 67.010 13.528 -52.611 µs -131.7 722.2
Server Offset SHM(1) -19.895 -9.044 -5.492 0.554 2.834 4.002 7.700 8.326 13.046 2.518 -0.001 µs -5.827 21.98
TDOP 0.560 0.580 0.640 0.900 1.500 4.000 8.310 0.860 3.420 0.614 0.999 10.18 107.4
nSats 5.000 6.000 7.000 9.000 11.000 11.000 12.000 4.000 5.000 1.304 8.686 nSat 198.5 1221
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!