NTPsec

C-ntpsec-24-hour-stats

Report generated: Wed Nov 20 16:09:01 2019 UTC
Start Time: Tue Nov 19 16:09:00 2019 UTC
End Time: Wed Nov 20 16:09:00 2019 UTC
Report published: Wed Nov 20 08:10:11 2019 PST
Report Period: 1.0 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 -500.000 -352.000 5.000 412.000 605.000 845.000 764.000 1,105.000 233.527 13.542 ns -3.471 8.439
Local Clock Frequency Offset -6.828 -6.828 -6.828 -6.805 -6.780 -6.778 -6.778 0.048 0.050 0.0164 -6.805 ppm -7.191e+07 2.99e+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 84.000 106.000 125.000 180.000 247.000 277.000 372.000 122.000 171.000 37.402 182.498 ns 70.45 326.9

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 29.000 34.000 52.000 87.000 108.000 142.000 53.000 79.000 16.473 55.206 10e-12 21.23 79.75

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 -500.000 -352.000 5.000 412.000 605.000 845.000 764.000 1,105.000 233.527 13.542 ns -3.471 8.439

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.828 -6.828 -6.828 -6.805 -6.780 -6.778 -6.778 0.048 0.050 0.0164 -6.805 ppm -7.191e+07 2.99e+10
Temp ZONE0 62.838 63.376 63.376 64.452 65.528 65.528 66.066 2.152 2.152 0.727 64.544 °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 0.000 7.000 7.000 10.000 11.000 12.000 12.000 4.000 5.000 1.285 9.432 nSat 273.3 1850
TDOP 0.500 0.560 0.600 0.800 1.370 1.730 1.770 0.770 1.170 0.254 0.875 23.21 87.8

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.449 -13.264 -13.023 -6.265 -1.607 -1.421 -0.417 11.416 11.842 3.978 -7.602 ms -33.57 126.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 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 -0.977 -0.352 0.291 1.060 2.013 2.280 1.412 2.990 0.445 0.297 ms -0.7019 6.788

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.528 0.528 0.878 4.087 9.345 12.386 12.386 8.467 11.858 2.435 4.276 ms 3.732 11.23

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 -75.730 21.175 52.592 94.683 132.924 167.417 226.368 80.332 146.242 27.352 93.705 µs 21.32 73.66

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.114 3.409 3.784 4.299 4.876 5.381 5.467 1.092 1.972 0.338 4.303 ms 1646 1.972e+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.731 2.096 2.412 2.866 3.152 3.578 0.770 1.421 0.258 2.435 ms 628.5 5544

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.574 -2.333 -0.166 0.469 0.945 1.813 2.802 3.519 1.088 -0.716 ms -9.944 28.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 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.059 2.040 3.102 3.727 4.150 2.044 3.300 0.591 2.016 ms 21.6 76.24

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) -72.920 -67.826 -65.212 -55.637 -46.411 -43.308 -42.128 18.801 24.518 5.609 -55.748 ms -1342 1.504e+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 -501.000 -353.000 6.000 413.000 606.000 846.000 766.000 1,107.000 234.292 13.557 ns -3.473 8.433

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.199 0.221 0.351 2.687 10.042 16.178 114.158 9.691 15.957 9.623 4.581 ms 8.208 93.59

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.327 0.612 1.949 9.907 15.890 186.180 9.295 15.564 11.068 3.890 ms 12.81 210.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 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.255 0.255 0.529 1.735 9.733 12.410 12.410 9.204 12.155 2.972 3.050 ms 1.561 4.407

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.029 0.047 0.162 8.674 9.415 13.510 8.627 9.386 2.920 1.673 ms 0.4302 2.85

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.238 0.382 2.013 10.239 77.980 178.478 9.857 77.741 12.978 4.501 ms 8.171 102

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.215 0.268 1.946 9.957 12.547 13.494 9.688 12.331 3.362 3.562 ms 1.378 3.542

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.221 0.252 0.462 2.119 9.493 12.834 16.332 9.031 12.582 3.110 3.218 ms 1.736 5.409

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.193 0.221 0.390 1.966 20.265 188.899 190.016 19.874 188.677 29.760 9.197 ms 2.869 18.28

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.189 0.412 0.594 2.649 7.193 8.657 10.723 6.599 8.246 2.094 3.134 ms 2.416 6.016

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 98.000 201.000 429.000 554.000 720.000 331.000 484.000 103.896 225.387 ns 6.238 19.72

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.828 -6.828 -6.828 -6.805 -6.780 -6.778 -6.778 0.048 0.050 0.0164 -6.805 ppm -7.191e+07 2.99e+10
Local Clock Time Offset -852.000 -500.000 -352.000 5.000 412.000 605.000 845.000 764.000 1,105.000 233.527 13.542 ns -3.471 8.439
Local RMS Frequency Jitter 24.000 29.000 34.000 52.000 87.000 108.000 142.000 53.000 79.000 16.473 55.206 10e-12 21.23 79.75
Local RMS Time Jitter 84.000 106.000 125.000 180.000 247.000 277.000 372.000 122.000 171.000 37.402 182.498 ns 70.45 326.9
Server Jitter 162.159.200.1 0.199 0.221 0.351 2.687 10.042 16.178 114.158 9.691 15.957 9.623 4.581 ms 8.208 93.59
Server Jitter 173.11.101.155 0.174 0.327 0.612 1.949 9.907 15.890 186.180 9.295 15.564 11.068 3.890 ms 12.81 210.7
Server Jitter 178.62.68.79 0.255 0.255 0.529 1.735 9.733 12.410 12.410 9.204 12.155 2.972 3.050 ms 1.561 4.407
Server Jitter 192.168.1.10 0.014 0.029 0.047 0.162 8.674 9.415 13.510 8.627 9.386 2.920 1.673 ms 0.4302 2.85
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.135 0.238 0.382 2.013 10.239 77.980 178.478 9.857 77.741 12.978 4.501 ms 8.171 102
Server Jitter 204.123.2.5 0.208 0.215 0.268 1.946 9.957 12.547 13.494 9.688 12.331 3.362 3.562 ms 1.378 3.542
Server Jitter 2405:fc00:0:1::123 0.221 0.252 0.462 2.119 9.493 12.834 16.332 9.031 12.582 3.110 3.218 ms 1.736 5.409
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.193 0.221 0.390 1.966 20.265 188.899 190.016 19.874 188.677 29.760 9.197 ms 2.869 18.28
Server Jitter SHM(0) 0.189 0.412 0.594 2.649 7.193 8.657 10.723 6.599 8.246 2.094 3.134 ms 2.416 6.016
Server Jitter SHM(1) 36.000 70.000 98.000 201.000 429.000 554.000 720.000 331.000 484.000 103.896 225.387 ns 6.238 19.72
Server Offset 162.159.200.1 -13.449 -13.264 -13.023 -6.265 -1.607 -1.421 -0.417 11.416 11.842 3.978 -7.602 ms -33.57 126.4
Server Offset 173.11.101.155 -1.609 -0.977 -0.352 0.291 1.060 2.013 2.280 1.412 2.990 0.445 0.297 ms -0.7019 6.788
Server Offset 178.62.68.79 0.528 0.528 0.878 4.087 9.345 12.386 12.386 8.467 11.858 2.435 4.276 ms 3.732 11.23
Server Offset 192.168.1.10 -75.730 21.175 52.592 94.683 132.924 167.417 226.368 80.332 146.242 27.352 93.705 µs 21.32 73.66
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.114 3.409 3.784 4.299 4.876 5.381 5.467 1.092 1.972 0.338 4.303 ms 1646 1.972e+04
Server Offset 204.123.2.5 1.546 1.731 2.096 2.412 2.866 3.152 3.578 0.770 1.421 0.258 2.435 ms 628.5 5544
Server Offset 2405:fc00:0:1::123 -2.868 -2.574 -2.333 -0.166 0.469 0.945 1.813 2.802 3.519 1.088 -0.716 ms -9.944 28.4
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.074 0.426 1.059 2.040 3.102 3.727 4.150 2.044 3.300 0.591 2.016 ms 21.6 76.24
Server Offset SHM(0) -72.920 -67.826 -65.212 -55.637 -46.411 -43.308 -42.128 18.801 24.518 5.609 -55.748 ms -1342 1.504e+04
Server Offset SHM(1) -853.000 -501.000 -353.000 6.000 413.000 606.000 846.000 766.000 1,107.000 234.292 13.557 ns -3.473 8.433
TDOP 0.500 0.560 0.600 0.800 1.370 1.730 1.770 0.770 1.170 0.254 0.875 23.21 87.8
Temp ZONE0 62.838 63.376 63.376 64.452 65.528 65.528 66.066 2.152 2.152 0.727 64.544 °C
nSats 0.000 7.000 7.000 10.000 11.000 12.000 12.000 4.000 5.000 1.285 9.432 nSat 273.3 1850
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!