NTPsec

C-ntpsec-12-hour-stats

Report generated: Wed Nov 20 16:07:03 2019 UTC
Start Time: Wed Nov 20 04:07:02 2019 UTC
End Time: Wed Nov 20 16:07:02 2019 UTC
Report published: Wed Nov 20 08:08:11 2019 PST
Report Period: 0.5 days

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 -852.000 -467.000 -306.000 57.000 481.000 662.000 845.000 787.000 1,129.000 235.434 68.309 ns -2.343 5.971
Local Clock Frequency Offset -6.827 -6.826 -6.824 -6.789 -6.779 -6.778 -6.778 0.044 0.048 0.0155 -6.795 ppm -8.543e+07 3.763e+10

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 88.000 103.000 123.000 181.000 250.000 287.000 372.000 127.000 184.000 39.173 182.627 ns 60.53 270.2

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 24.000 28.000 33.000 54.000 95.000 116.000 142.000 62.000 88.000 19.182 57.214 10e-12 14.78 51.46

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 -852.000 -467.000 -306.000 57.000 481.000 662.000 845.000 787.000 1,129.000 235.434 68.309 ns -2.343 5.971

The clock offsets of the local clock as a histogram.

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



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -6.827 -6.826 -6.824 -6.789 -6.779 -6.778 -6.778 0.044 0.048 0.0155 -6.795 ppm -8.543e+07 3.763e+10
Temp ZONE0 62.838 63.376 63.376 64.452 65.528 65.528 65.528 2.152 2.152 0.736 64.309 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 6.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.317 9.125 nSat 226.3 1450
TDOP 0.500 0.550 0.610 0.870 1.490 1.740 1.770 0.880 1.190 0.271 0.921 21.94 81.01

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. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



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 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -13.249 -13.034 -12.833 -4.860 -1.510 -1.302 -0.417 11.323 11.732 3.427 -5.318 ms -25.37 96.11

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

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

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

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



Server Offset 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -1.609 -1.413 -0.352 0.301 1.152 2.027 2.280 1.505 3.441 0.504 0.314 ms -1.053 7.012

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 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 0.953 0.953 1.437 4.889 10.620 10.920 10.920 9.183 9.967 2.225 5.315 ms 7.424 21.91

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 192.168.1.10

peer offset 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.10 -20.400 21.175 50.887 92.418 128.373 158.140 226.368 77.486 136.965 26.152 91.080 µs 22.74 79.92

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 2001:470:e815::24 (pi4.rellim.com)

peer offset 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.288 3.456 3.784 4.283 5.043 5.392 5.467 1.259 1.937 0.381 4.327 ms 1144 1.219e+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 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 1.546 1.546 2.041 2.365 2.833 3.062 3.062 0.792 1.516 0.252 2.380 ms 630.4 5545

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 2405:fc00:0:1::123

peer offset 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00:0:1::123 -2.868 -2.703 -2.387 -1.974 0.413 0.945 1.813 2.800 3.648 1.053 -1.438 ms -19.41 58.51

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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.074 0.426 1.233 2.062 3.034 4.139 4.150 1.801 3.712 0.560 2.070 ms 28.3 109.3

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(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -68.348 -66.085 -63.791 -53.750 -44.843 -42.954 -42.128 18.948 23.130 5.507 -53.971 ms -1292 1.431e+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 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) -853.000 -468.000 -307.000 58.000 482.000 663.000 846.000 789.000 1,131.000 236.159 68.514 ns -2.347 5.968

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 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.201 0.221 0.298 2.360 11.362 16.059 16.178 11.064 15.837 3.845 4.102 ms 1.522 4.626

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 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.174 0.309 0.566 1.718 9.165 13.514 16.572 8.598 13.205 3.017 3.058 ms 1.898 6.41

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 178.62.68.79

peer jitter 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.62.68.79 0.449 0.449 0.540 2.179 11.331 12.410 12.410 10.791 11.961 2.780 3.049 ms 2.255 7.417

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 192.168.1.10

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 0.014 0.024 0.042 0.151 8.667 9.219 12.223 8.625 9.195 2.902 1.623 ms 0.3876 2.698

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 2001:470:e815::24 (pi4.rellim.com)

peer jitter 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.135 0.138 0.294 2.203 12.129 16.470 23.938 11.835 16.332 3.776 3.404 ms 1.957 8.414

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

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.208 0.208 0.251 2.254 12.269 13.494 13.494 12.018 13.286 3.763 3.877 ms 1.265 3.087

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 2405:fc00:0:1::123

peer jitter 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2405:fc00:0:1::123 0.252 0.367 0.540 2.157 9.038 12.834 13.187 8.498 12.467 2.746 3.037 ms 1.998 6.065

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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer jitter 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.203 0.221 0.456 2.233 23.462 189.994 190.016 23.005 189.772 34.628 11.014 ms 2.26 13.31

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(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.194 0.412 0.587 2.596 7.214 8.842 10.723 6.627 8.430 2.142 3.103 ms 2.263 5.616

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) 36.000 70.000 97.000 202.000 434.000 566.000 720.000 337.000 496.000 106.592 227.302 ns 6.001 19

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 -6.827 -6.826 -6.824 -6.789 -6.779 -6.778 -6.778 0.044 0.048 0.0155 -6.795 ppm -8.543e+07 3.763e+10
Local Clock Time Offset -852.000 -467.000 -306.000 57.000 481.000 662.000 845.000 787.000 1,129.000 235.434 68.309 ns -2.343 5.971
Local RMS Frequency Jitter 24.000 28.000 33.000 54.000 95.000 116.000 142.000 62.000 88.000 19.182 57.214 10e-12 14.78 51.46
Local RMS Time Jitter 88.000 103.000 123.000 181.000 250.000 287.000 372.000 127.000 184.000 39.173 182.627 ns 60.53 270.2
Server Jitter 162.159.200.1 0.201 0.221 0.298 2.360 11.362 16.059 16.178 11.064 15.837 3.845 4.102 ms 1.522 4.626
Server Jitter 173.11.101.155 0.174 0.309 0.566 1.718 9.165 13.514 16.572 8.598 13.205 3.017 3.058 ms 1.898 6.41
Server Jitter 178.62.68.79 0.449 0.449 0.540 2.179 11.331 12.410 12.410 10.791 11.961 2.780 3.049 ms 2.255 7.417
Server Jitter 192.168.1.10 0.014 0.024 0.042 0.151 8.667 9.219 12.223 8.625 9.195 2.902 1.623 ms 0.3876 2.698
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.135 0.138 0.294 2.203 12.129 16.470 23.938 11.835 16.332 3.776 3.404 ms 1.957 8.414
Server Jitter 204.123.2.5 0.208 0.208 0.251 2.254 12.269 13.494 13.494 12.018 13.286 3.763 3.877 ms 1.265 3.087
Server Jitter 2405:fc00:0:1::123 0.252 0.367 0.540 2.157 9.038 12.834 13.187 8.498 12.467 2.746 3.037 ms 1.998 6.065
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.203 0.221 0.456 2.233 23.462 189.994 190.016 23.005 189.772 34.628 11.014 ms 2.26 13.31
Server Jitter SHM(0) 0.194 0.412 0.587 2.596 7.214 8.842 10.723 6.627 8.430 2.142 3.103 ms 2.263 5.616
Server Jitter SHM(1) 36.000 70.000 97.000 202.000 434.000 566.000 720.000 337.000 496.000 106.592 227.302 ns 6.001 19
Server Offset 162.159.200.1 -13.249 -13.034 -12.833 -4.860 -1.510 -1.302 -0.417 11.323 11.732 3.427 -5.318 ms -25.37 96.11
Server Offset 173.11.101.155 -1.609 -1.413 -0.352 0.301 1.152 2.027 2.280 1.505 3.441 0.504 0.314 ms -1.053 7.012
Server Offset 178.62.68.79 0.953 0.953 1.437 4.889 10.620 10.920 10.920 9.183 9.967 2.225 5.315 ms 7.424 21.91
Server Offset 192.168.1.10 -20.400 21.175 50.887 92.418 128.373 158.140 226.368 77.486 136.965 26.152 91.080 µs 22.74 79.92
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.288 3.456 3.784 4.283 5.043 5.392 5.467 1.259 1.937 0.381 4.327 ms 1144 1.219e+04
Server Offset 204.123.2.5 1.546 1.546 2.041 2.365 2.833 3.062 3.062 0.792 1.516 0.252 2.380 ms 630.4 5545
Server Offset 2405:fc00:0:1::123 -2.868 -2.703 -2.387 -1.974 0.413 0.945 1.813 2.800 3.648 1.053 -1.438 ms -19.41 58.51
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.074 0.426 1.233 2.062 3.034 4.139 4.150 1.801 3.712 0.560 2.070 ms 28.3 109.3
Server Offset SHM(0) -68.348 -66.085 -63.791 -53.750 -44.843 -42.954 -42.128 18.948 23.130 5.507 -53.971 ms -1292 1.431e+04
Server Offset SHM(1) -853.000 -468.000 -307.000 58.000 482.000 663.000 846.000 789.000 1,131.000 236.159 68.514 ns -2.347 5.968
TDOP 0.500 0.550 0.610 0.870 1.490 1.740 1.770 0.880 1.190 0.271 0.921 21.94 81.01
Temp ZONE0 62.838 63.376 63.376 64.452 65.528 65.528 65.528 2.152 2.152 0.736 64.309 °C
nSats 6.000 7.000 7.000 9.000 11.000 12.000 12.000 4.000 5.000 1.317 9.125 nSat 226.3 1450
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!