NTPsec

C-ntpsec-3-hour-stats

Report generated: Sun Jan 26 15:01:29 2020 UTC
Start Time: Sun Jan 26 12:01:29 2020 UTC
End Time: Sun Jan 26 15:01:29 2020 UTC
Report published: Sun Jan 26 07:01:33 2020 PST
Report Period: 0.1 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 -553.000 -336.000 -234.000 64.000 451.000 614.000 746.000 685.000 950.000 207.773 82.056 ns -1.66 4.461
Local Clock Frequency Offset -5.935 -5.935 -5.935 -5.927 -5.920 -5.920 -5.920 0.0145 0.0151 0.0041 -5.928 ppm -2.945e+09 4.221e+12

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 98.000 102.000 117.000 166.000 243.000 284.000 316.000 126.000 182.000 37.702 171.436 ns 55.99 247.6

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 48.000 94.000 162.000 188.000 61.000 134.000 22.434 54.001 10e-12 9.654 43.5

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 -553.000 -336.000 -234.000 64.000 451.000 614.000 746.000 685.000 950.000 207.773 82.056 ns -1.66 4.461

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 -5.935 -5.935 -5.935 -5.927 -5.920 -5.920 -5.920 0.0145 0.0151 0.0041 -5.928 ppm -2.945e+09 4.221e+12
Temp ZONE0 64.452 64.452 64.452 64.990 65.528 65.528 65.528 1.076 1.076 0.373 65.038 °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 8.000 8.000 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.079 9.944 nSat 580.2 4982
TDOP 0.560 0.560 0.570 0.860 1.310 1.510 1.510 0.740 0.950 0.219 0.858 34.52 137.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. 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 0.095 0.095 0.146 0.681 1.116 1.218 1.218 0.970 1.124 0.300 0.645 ms 4.811 11.25

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 -290.782 -290.782 -60.014 340.654 861.934 875.179 875.179 921.948 1,165.961 275.075 359.827 µs 1.001 3.364

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 58.570 74.940 82.098 117.986 140.491 165.642 171.372 58.393 90.702 18.776 115.637 µs 152.4 863.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 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.567 3.567 3.955 4.268 4.590 4.666 4.666 0.636 1.099 0.202 4.287 ms 8359 1.704e+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 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 2.484 2.484 2.484 2.646 3.088 3.088 3.088 0.604 0.604 0.147 2.665 ms 5056 8.742e+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 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 -5.045 -5.045 -5.044 -4.812 -4.583 -4.438 -4.438 0.461 0.607 0.155 -4.812 ms -3.318e+04 1.068e+06

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.064 -0.064 -0.023 1.223 2.446 2.453 2.453 2.469 2.517 0.612 1.305 ms 4.64 11.17

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 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com)

peer offset 2a03:b0c0:1:d0::1f9:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -1.349 -1.349 1.220 3.506 4.279 4.713 4.713 3.059 6.062 1.007 3.362 ms 16.63 47.52

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) -66.020 -65.734 -64.795 -55.954 -47.470 -46.173 -45.739 17.324 19.561 4.945 -56.239 ms -1931 2.435e+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) -554.000 -337.000 -235.000 65.000 452.000 615.000 747.000 687.000 952.000 208.466 82.316 ns -1.666 4.462

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.246 0.246 0.339 1.235 10.076 12.662 12.662 9.738 12.416 3.937 3.362 ms 0.74 2.203

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.450 0.450 0.536 1.239 18.553 18.557 18.557 18.017 18.107 4.384 2.739 ms 1.709 6.927

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.009 0.020 0.032 0.118 8.651 10.376 11.430 8.620 10.356 2.764 1.269 ms 0.4965 3.498

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.270 0.270 0.380 0.679 10.532 10.608 10.608 10.152 10.338 3.083 2.164 ms 0.9391 3.147

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.259 0.259 0.259 1.128 18.223 18.223 18.223 17.965 17.965 5.100 4.203 ms 0.7508 3.053

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.326 0.326 0.335 0.895 9.111 10.511 10.511 8.776 10.186 2.793 2.464 ms 1.034 3.207

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.396 0.396 0.415 1.720 168.706 183.712 183.712 168.291 183.316 46.127 18.104 ms 0.9684 5.368

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 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com)

peer jitter 2a03:b0c0:1:d0::1f9:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.332 0.332 0.340 1.048 182.988 189.465 189.465 182.648 189.132 46.187 15.890 ms 0.8919 5.739

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.180 0.258 0.783 2.275 6.784 8.725 8.796 6.001 8.467 2.011 2.996 ms 2.446 5.982

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) 43.000 62.000 98.000 194.000 387.000 489.000 694.000 289.000 427.000 90.857 210.126 ns 7.337 24.29

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 -5.935 -5.935 -5.935 -5.927 -5.920 -5.920 -5.920 0.0145 0.0151 0.0041 -5.928 ppm -2.945e+09 4.221e+12
Local Clock Time Offset -553.000 -336.000 -234.000 64.000 451.000 614.000 746.000 685.000 950.000 207.773 82.056 ns -1.66 4.461
Local RMS Frequency Jitter 24.000 28.000 33.000 48.000 94.000 162.000 188.000 61.000 134.000 22.434 54.001 10e-12 9.654 43.5
Local RMS Time Jitter 98.000 102.000 117.000 166.000 243.000 284.000 316.000 126.000 182.000 37.702 171.436 ns 55.99 247.6
Server Jitter 162.159.200.1 0.246 0.246 0.339 1.235 10.076 12.662 12.662 9.738 12.416 3.937 3.362 ms 0.74 2.203
Server Jitter 173.11.101.155 0.450 0.450 0.536 1.239 18.553 18.557 18.557 18.017 18.107 4.384 2.739 ms 1.709 6.927
Server Jitter 192.168.1.10 0.009 0.020 0.032 0.118 8.651 10.376 11.430 8.620 10.356 2.764 1.269 ms 0.4965 3.498
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.270 0.270 0.380 0.679 10.532 10.608 10.608 10.152 10.338 3.083 2.164 ms 0.9391 3.147
Server Jitter 204.123.2.5 0.259 0.259 0.259 1.128 18.223 18.223 18.223 17.965 17.965 5.100 4.203 ms 0.7508 3.053
Server Jitter 2405:fc00:0:1::123 0.326 0.326 0.335 0.895 9.111 10.511 10.511 8.776 10.186 2.793 2.464 ms 1.034 3.207
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.396 0.396 0.415 1.720 168.706 183.712 183.712 168.291 183.316 46.127 18.104 ms 0.9684 5.368
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.332 0.332 0.340 1.048 182.988 189.465 189.465 182.648 189.132 46.187 15.890 ms 0.8919 5.739
Server Jitter SHM(0) 0.180 0.258 0.783 2.275 6.784 8.725 8.796 6.001 8.467 2.011 2.996 ms 2.446 5.982
Server Jitter SHM(1) 43.000 62.000 98.000 194.000 387.000 489.000 694.000 289.000 427.000 90.857 210.126 ns 7.337 24.29
Server Offset 162.159.200.1 0.095 0.095 0.146 0.681 1.116 1.218 1.218 0.970 1.124 0.300 0.645 ms 4.811 11.25
Server Offset 173.11.101.155 -290.782 -290.782 -60.014 340.654 861.934 875.179 875.179 921.948 1,165.961 275.075 359.827 µs 1.001 3.364
Server Offset 192.168.1.10 58.570 74.940 82.098 117.986 140.491 165.642 171.372 58.393 90.702 18.776 115.637 µs 152.4 863.8
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.567 3.567 3.955 4.268 4.590 4.666 4.666 0.636 1.099 0.202 4.287 ms 8359 1.704e+05
Server Offset 204.123.2.5 2.484 2.484 2.484 2.646 3.088 3.088 3.088 0.604 0.604 0.147 2.665 ms 5056 8.742e+04
Server Offset 2405:fc00:0:1::123 -5.045 -5.045 -5.044 -4.812 -4.583 -4.438 -4.438 0.461 0.607 0.155 -4.812 ms -3.318e+04 1.068e+06
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -0.064 -0.064 -0.023 1.223 2.446 2.453 2.453 2.469 2.517 0.612 1.305 ms 4.64 11.17
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -1.349 -1.349 1.220 3.506 4.279 4.713 4.713 3.059 6.062 1.007 3.362 ms 16.63 47.52
Server Offset SHM(0) -66.020 -65.734 -64.795 -55.954 -47.470 -46.173 -45.739 17.324 19.561 4.945 -56.239 ms -1931 2.435e+04
Server Offset SHM(1) -554.000 -337.000 -235.000 65.000 452.000 615.000 747.000 687.000 952.000 208.466 82.316 ns -1.666 4.462
TDOP 0.560 0.560 0.570 0.860 1.310 1.510 1.510 0.740 0.950 0.219 0.858 34.52 137.4
Temp ZONE0 64.452 64.452 64.452 64.990 65.528 65.528 65.528 1.076 1.076 0.373 65.038 °C
nSats 8.000 8.000 8.000 10.000 12.000 12.000 12.000 4.000 4.000 1.079 9.944 nSat 580.2 4982
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!