NTPsec

Kong

Report generated: Fri Jul 1 13:59:02 2022 UTC
Start Time: Fri Jun 24 13:59:01 2022 UTC
End Time: Fri Jul 1 13:59:01 2022 UTC
Report Period: 7.0 days

Daily stats   Weekly stats   Live GNSS Data   24 Hour Scatter Plots: ( )

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 -480.024 -69.008 -34.543 -1.037 37.148 76.415 181.372 71.691 145.423 26.862 -0.478 µs -5.551 46.28
Local Clock Frequency Offset 9.926 10.069 10.254 10.557 11.498 11.703 11.922 1.245 1.634 0.406 10.685 ppm 1.627e+04 4.136e+05

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 7.057 9.699 11.448 17.925 30.393 56.204 215.219 18.945 46.505 11.738 19.826 µs 10.79 127

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 2.682 3.840 5.092 9.358 25.166 46.473 92.309 20.074 42.633 7.936 11.403 ppb 5.211 32.19

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 -480.024 -69.008 -34.543 -1.037 37.148 76.415 181.372 71.691 145.423 26.862 -0.478 µs -5.551 46.28

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 9.926 10.069 10.254 10.557 11.498 11.703 11.922 1.245 1.634 0.406 10.685 ppm 1.627e+04 4.136e+05
Temp /dev/sda 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp /dev/sdb 46.000 47.000 48.000 50.000 52.000 54.000 55.000 4.000 7.000 1.403 49.872 °C
Temp /dev/sdc 34.000 34.000 35.000 37.000 41.000 42.000 42.000 6.000 8.000 1.800 37.575 °C
Temp /dev/sdd 25.000 25.000 26.000 29.000 33.000 35.000 37.000 7.000 10.000 2.633 29.355 °C
Temp /dev/sde 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM0 40.000 41.000 41.000 42.000 45.000 45.000 45.000 4.000 4.000 1.093 42.683 °C
Temp LM1 38.500 39.000 40.000 42.000 48.500 51.000 57.500 8.500 12.000 2.699 42.571 °C
Temp LM10 76.625 76.875 77.875 78.875 87.375 89.375 94.625 9.500 12.500 3.041 79.912 °C
Temp LM11 61.750 62.000 62.375 63.500 65.500 66.000 66.500 3.125 4.000 1.001 63.641 °C
Temp LM12 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM13 0.000 34.000 35.000 37.000 41.000 42.000 42.000 6.000 8.000 1.974 37.633 °C
Temp LM14 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM15 49.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.811 53.906 °C
Temp LM16 76.625 76.875 77.875 78.875 87.375 89.375 94.625 9.500 12.500 3.041 79.914 °C
Temp LM17 46.500 76.500 77.500 79.000 87.000 88.750 93.250 9.500 12.250 2.999 79.823 °C
Temp LM18 25.000 25.000 26.000 29.000 33.000 35.000 39.000 7.000 10.000 2.652 29.430 °C
Temp LM19 46.000 47.000 48.000 50.000 52.000 54.000 55.000 4.000 7.000 1.404 49.886 °C
Temp LM2 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM3 56.000 57.000 57.000 58.000 61.000 61.000 62.000 4.000 4.000 1.225 58.543 °C
Temp LM4 5.000 6.000 7.000 8.000 9.000 9.000 12.000 2.000 3.000 0.819 7.696 °C
Temp LM5 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM6 65.500 65.500 66.500 67.500 76.000 78.000 83.500 9.500 12.500 3.039 68.713 °C
Temp LM7 61.500 62.000 62.000 63.500 65.500 66.000 66.500 3.500 4.000 1.022 63.496 °C
Temp LM8 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM9 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °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.



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 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) -259.329 -82.329 -38.540 25.182 75.712 117.447 262.723 114.252 199.776 37.655 22.257 µs -1.662 9.509

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::8 (spidey.rellim.com)

peer offset 2001:470:e815::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e815::8 (spidey.rellim.com) -619.670 -537.564 -365.299 -33.383 391.859 633.432 777.565 757.158 1,170.996 232.450 -13.049 µs -3.975 9.691

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

peer offset 204.17.205.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.1 -728.957 -536.381 -375.054 9.462 282.879 921.963 1,192.809 657.933 1,458.344 242.027 -14.362 µs -3.667 11.08

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

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

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

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



Server Offset 204.17.205.17

peer offset 204.17.205.17 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.17 -194.401 -68.561 -28.423 26.313 87.533 119.715 259.276 115.956 188.276 36.773 27.478 µs -0.8238 5.811

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

peer offset 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.23 -268.473 -110.740 -65.102 -14.951 32.338 72.536 246.803 97.440 183.276 33.890 -15.371 µs -7.657 27.95

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

peer offset 204.17.205.30 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.30 -1,858.924 -108.871 -52.400 -3.865 43.488 185.820 3,610.046 95.888 294.691 152.311 3.221 µs 11.62 302.5

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) -2.104 -1.223 -1.051 -0.663 -0.051 0.310 1.972 1.000 1.533 0.320 -0.616 ms -32.83 119.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 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.072 1.377 1.544 1.825 2.084 2.294 2.839 0.540 0.917 0.172 1.824 ms 913.3 9056

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

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

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

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



Server Offset 2606:4700:f1::123 (time.cloudflare.com)

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 1.139 1.401 1.549 1.814 2.122 2.350 2.577 0.573 0.949 0.182 1.820 ms 762.1 7134

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

peer offset SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(2) -37.930 -28.355 9.976 4,556.391 4,987.628 5,025.959 5,035.525 4,977.652 5,054.314 2,000.149 3,523.881 s 1.605 2.702

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 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.000 5.332 8.068 22.976 71.039 119.400 4,146.213 62.971 114.068 166.475 37.934 µs 17.56 381.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 2001:470:e815::8 (spidey.rellim.com)

peer jitter 2001:470:e815::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 5.838 8.153 22.651 80.451 126.256 303.309 72.298 120.418 24.980 30.590 µs 2.92 13.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 204.17.205.1

peer jitter 204.17.205.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.1 0.000 3.886 6.165 23.244 82.882 132.988 752.685 76.717 129.102 32.270 31.483 µs 8.831 179.8

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.17.205.17

peer jitter 204.17.205.17 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.17 0.000 7.711 10.963 29.747 77.934 130.614 1,147.228 66.971 122.903 37.768 36.778 µs 12.58 271.5

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

peer jitter 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.23 0.000 6.678 10.193 28.368 75.534 126.911 1,287.056 65.341 120.233 37.800 34.993 µs 16.7 456.1

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

peer jitter 204.17.205.30 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.30 0.000 5.442 7.814 22.031 72.054 102.432 3,602.817 64.240 96.990 131.785 33.844 µs 20.04 500.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 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.000 0.296 0.421 1.341 3.994 10.290 34.701 3.573 9.993 2.049 1.787 ms 6.534 71.71

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) 0.072 0.169 0.240 0.488 1.176 2.913 8.204 0.936 2.744 0.510 0.589 ms 7.74 91.36

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2606:4700:f1::123 (time.cloudflare.com)

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.161 0.247 0.494 1.376 1.947 3.588 1.129 1.786 0.372 0.585 ms 4.662 23.17

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

peer jitter SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(2) 0.000 0.055 0.056 0.057 0.058 0.058 5,073.421 0.002 0.003 36.902 0.399 s 110 1.305e+04

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset 9.926 10.069 10.254 10.557 11.498 11.703 11.922 1.245 1.634 0.406 10.685 ppm 1.627e+04 4.136e+05
Local Clock Time Offset -480.024 -69.008 -34.543 -1.037 37.148 76.415 181.372 71.691 145.423 26.862 -0.478 µs -5.551 46.28
Local RMS Frequency Jitter 2.682 3.840 5.092 9.358 25.166 46.473 92.309 20.074 42.633 7.936 11.403 ppb 5.211 32.19
Local RMS Time Jitter 7.057 9.699 11.448 17.925 30.393 56.204 215.219 18.945 46.505 11.738 19.826 µs 10.79 127
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 5.332 8.068 22.976 71.039 119.400 4,146.213 62.971 114.068 166.475 37.934 µs 17.56 381.7
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 5.838 8.153 22.651 80.451 126.256 303.309 72.298 120.418 24.980 30.590 µs 2.92 13.3
Server Jitter 204.17.205.1 0.000 3.886 6.165 23.244 82.882 132.988 752.685 76.717 129.102 32.270 31.483 µs 8.831 179.8
Server Jitter 204.17.205.17 0.000 7.711 10.963 29.747 77.934 130.614 1,147.228 66.971 122.903 37.768 36.778 µs 12.58 271.5
Server Jitter 204.17.205.23 0.000 6.678 10.193 28.368 75.534 126.911 1,287.056 65.341 120.233 37.800 34.993 µs 16.7 456.1
Server Jitter 204.17.205.30 0.000 5.442 7.814 22.031 72.054 102.432 3,602.817 64.240 96.990 131.785 33.844 µs 20.04 500.3
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.296 0.421 1.341 3.994 10.290 34.701 3.573 9.993 2.049 1.787 ms 6.534 71.71
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.072 0.169 0.240 0.488 1.176 2.913 8.204 0.936 2.744 0.510 0.589 ms 7.74 91.36
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.161 0.247 0.494 1.376 1.947 3.588 1.129 1.786 0.372 0.585 ms 4.662 23.17
Server Jitter SHM(2) 0.000 0.055 0.056 0.057 0.058 0.058 5,073.421 0.002 0.003 36.902 0.399 s 110 1.305e+04
Server Offset 2001:470:e815::24 (pi4.rellim.com) -259.329 -82.329 -38.540 25.182 75.712 117.447 262.723 114.252 199.776 37.655 22.257 µs -1.662 9.509
Server Offset 2001:470:e815::8 (spidey.rellim.com) -619.670 -537.564 -365.299 -33.383 391.859 633.432 777.565 757.158 1,170.996 232.450 -13.049 µs -3.975 9.691
Server Offset 204.17.205.1 -728.957 -536.381 -375.054 9.462 282.879 921.963 1,192.809 657.933 1,458.344 242.027 -14.362 µs -3.667 11.08
Server Offset 204.17.205.17 -194.401 -68.561 -28.423 26.313 87.533 119.715 259.276 115.956 188.276 36.773 27.478 µs -0.8238 5.811
Server Offset 204.17.205.23 -268.473 -110.740 -65.102 -14.951 32.338 72.536 246.803 97.440 183.276 33.890 -15.371 µs -7.657 27.95
Server Offset 204.17.205.30 -1,858.924 -108.871 -52.400 -3.865 43.488 185.820 3,610.046 95.888 294.691 152.311 3.221 µs 11.62 302.5
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -2.104 -1.223 -1.051 -0.663 -0.051 0.310 1.972 1.000 1.533 0.320 -0.616 ms -32.83 119.8
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 1.072 1.377 1.544 1.825 2.084 2.294 2.839 0.540 0.917 0.172 1.824 ms 913.3 9056
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 1.139 1.401 1.549 1.814 2.122 2.350 2.577 0.573 0.949 0.182 1.820 ms 762.1 7134
Server Offset SHM(2) -37.930 -28.355 9.976 4,556.391 4,987.628 5,025.959 5,035.525 4,977.652 5,054.314 2,000.149 3,523.881 s 1.605 2.702
Temp /dev/sda 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp /dev/sdb 46.000 47.000 48.000 50.000 52.000 54.000 55.000 4.000 7.000 1.403 49.872 °C
Temp /dev/sdc 34.000 34.000 35.000 37.000 41.000 42.000 42.000 6.000 8.000 1.800 37.575 °C
Temp /dev/sdd 25.000 25.000 26.000 29.000 33.000 35.000 37.000 7.000 10.000 2.633 29.355 °C
Temp /dev/sde 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM0 40.000 41.000 41.000 42.000 45.000 45.000 45.000 4.000 4.000 1.093 42.683 °C
Temp LM1 38.500 39.000 40.000 42.000 48.500 51.000 57.500 8.500 12.000 2.699 42.571 °C
Temp LM10 76.625 76.875 77.875 78.875 87.375 89.375 94.625 9.500 12.500 3.041 79.912 °C
Temp LM11 61.750 62.000 62.375 63.500 65.500 66.000 66.500 3.125 4.000 1.001 63.641 °C
Temp LM12 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM13 0.000 34.000 35.000 37.000 41.000 42.000 42.000 6.000 8.000 1.974 37.633 °C
Temp LM14 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM15 49.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.811 53.906 °C
Temp LM16 76.625 76.875 77.875 78.875 87.375 89.375 94.625 9.500 12.500 3.041 79.914 °C
Temp LM17 46.500 76.500 77.500 79.000 87.000 88.750 93.250 9.500 12.250 2.999 79.823 °C
Temp LM18 25.000 25.000 26.000 29.000 33.000 35.000 39.000 7.000 10.000 2.652 29.430 °C
Temp LM19 46.000 47.000 48.000 50.000 52.000 54.000 55.000 4.000 7.000 1.404 49.886 °C
Temp LM2 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM3 56.000 57.000 57.000 58.000 61.000 61.000 62.000 4.000 4.000 1.225 58.543 °C
Temp LM4 5.000 6.000 7.000 8.000 9.000 9.000 12.000 2.000 3.000 0.819 7.696 °C
Temp LM5 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM6 65.500 65.500 66.500 67.500 76.000 78.000 83.500 9.500 12.500 3.039 68.713 °C
Temp LM7 61.500 62.000 62.000 63.500 65.500 66.000 66.500 3.500 4.000 1.022 63.496 °C
Temp LM8 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM9 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Summary as CSV file


This server:

Motherboard:
OS: Gentoo unstable
GPS:
GPS/PPS server: gpsd
NTP server: NTPsec
../ntp.conf

Notes:

Feb 21 03:28:57 UTC 2019: New install

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!