NTPsec

Kong

Report generated: Tue Oct 22 13:59:01 2024 UTC
Start Time: Tue Oct 15 13:59:00 2024 UTC
End Time: Tue Oct 22 13:59:00 2024 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 -47.058 -0.205 -0.045 -0.002 0.039 0.153 7.319 0.084 0.358 1.357 -0.063 ms -27.71 732
Local Clock Frequency Offset 10.245 11.778 11.851 12.487 12.935 13.559 19.722 1.084 1.781 0.378 12.463 ppm 3.281e+04 1.053e+06

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 0.000 0.010 0.012 0.021 0.050 1.523 10.861 0.038 1.514 0.589 0.080 ms 9.63 144.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 0.000 4.689 6.111 11.155 60.203 236.136 2,439.850 54.092 231.447 121.173 26.104 ppb 11.22 185.2

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 -47.058 -0.205 -0.045 -0.002 0.039 0.153 7.319 0.084 0.358 1.357 -0.063 ms -27.71 732

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 10.245 11.778 11.851 12.487 12.935 13.559 19.722 1.084 1.781 0.378 12.463 ppm 3.281e+04 1.053e+06
Temp /dev/sda 26.000 44.000 45.000 49.000 51.000 52.000 52.000 6.000 8.000 1.824 48.336 °C
Temp /dev/sdb 23.000 34.000 35.000 37.000 40.000 41.000 42.000 5.000 7.000 1.572 37.179 °C
Temp LM0 34.000 49.000 49.000 53.000 58.000 59.000 59.000 9.000 10.000 2.879 53.627 °C
Temp LM1 37.750 43.875 45.500 48.250 53.250 75.500 85.625 7.750 31.625 4.866 49.262 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.050 25.003 °C
Temp LM11 42.000 61.000 62.000 63.000 65.000 65.000 66.000 3.000 4.000 1.023 62.985 °C
Temp LM12 2.000 4.000 4.000 8.000 16.000 18.000 37.000 12.000 14.000 3.864 8.972 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.050 25.003 °C
Temp LM14 24.000 44.000 44.000 45.000 47.000 47.000 48.000 3.000 3.000 1.093 45.360 °C
Temp LM15 27.000 37.000 38.000 40.000 43.000 64.000 74.000 5.000 27.000 4.050 40.512 °C
Temp LM16 47.500 66.000 66.500 68.000 69.500 70.000 70.500 3.000 4.000 1.063 67.944 °C
Temp LM17 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM18 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM19 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM2 39.000 43.500 44.750 47.250 57.000 75.000 83.250 12.250 31.500 5.071 48.689 °C
Temp LM20 37.375 43.875 45.375 48.250 53.000 75.625 85.625 7.625 31.750 4.848 49.221 °C
Temp LM21 47.500 66.250 66.750 68.000 69.750 70.000 70.625 3.000 3.750 1.058 68.096 °C
Temp LM22 21.000 34.000 35.000 37.000 40.000 41.000 42.000 5.000 7.000 1.659 37.265 °C
Temp LM23 50.850 65.850 66.850 69.850 71.850 72.850 77.850 5.000 7.000 1.745 69.856 °C
Temp LM3 26.000 45.000 45.000 49.000 51.000 52.000 52.000 6.000 7.000 1.826 48.333 °C
Temp LM4 31.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.180 51.349 °C
Temp LM5 30.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.182 51.363 °C
Temp LM6 44.850 56.850 57.850 59.850 62.850 70.850 75.850 5.000 14.000 2.162 60.329 °C
Temp LM7 31.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.176 51.369 °C
Temp LM8 24.000 44.000 44.000 45.000 47.000 47.000 48.000 3.000 3.000 1.095 45.361 °C
Temp LM9 27.500 38.000 38.000 40.000 42.000 51.500 54.500 4.000 13.500 2.056 40.321 °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 4.000 4.000 4.000 4.000 13.000 15.000 17.000 9.000 11.000 3.852 7.456 nSat 3.997 8.857
TDOP 0.690 0.820 0.900 1.280 2.320 3.050 23.120 1.420 2.230 0.503 1.407 17.27 261.1

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 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) -162.974 -0.223 -0.064 -0.002 0.049 0.216 8.867 0.114 0.439 3.834 -0.129 ms -38.45 1411

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) -28.829 -0.400 -0.132 -0.003 0.128 0.275 285.188 0.261 0.675 8.683 0.212 ms 28.24 930.6

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:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net)

peer offset 2001:67c:1270:0:dea6:32ff:feaf:803b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) -117.673 -0.737 -0.433 0.371 2.266 3.086 167.292 2.700 3.824 7.017 0.680 ms 2.016 372.2

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

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

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

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



Server Offset 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 -6.908 -0.431 -0.330 0.010 0.329 1.123 17.303 0.659 1.554 0.617 0.026 ms 15.1 464.6

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

peer offset 204.17.205.16 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.16 -3.803 -0.193 -0.054 0.007 0.066 0.207 21.542 0.120 0.400 0.954 0.049 ms 17.65 400.1

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 -10.218 -0.172 -0.050 0.004 0.061 0.179 5.603 0.110 0.352 0.306 0.004 ms -16.9 777.9

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::1 (robusta.dcs1.biz)

peer offset 2405:fc00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -104.776 3.840 4.173 5.625 7.319 7.850 171.820 3.146 4.010 5.186 5.695 ms 8.838 681.6

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) -114.316 -8.046 -7.328 1.011 2.096 3.358 167.152 9.423 11.404 6.138 -0.003 ms -0.5537 365.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 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) -0.767 -0.469 -0.105 2.025 2.864 4.184 12.267 2.969 4.654 1.127 1.602 ms 2.006 11.88

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) -113.367 0.223 0.659 2.462 3.019 3.245 168.627 2.361 3.022 7.507 2.032 ms 2.066 322

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) -239.660 -140.748 -137.848 -131.962 -127.097 -125.311 -117.086 10.750 15.438 3.618 -132.206 ms -5.302e+04 1.995e+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 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 0.003 0.005 0.015 0.061 0.123 94.484 0.057 0.120 2.775 0.128 ms 25.38 779.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 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 0.002 0.003 0.008 0.040 0.112 20.779 0.037 0.110 0.643 0.047 ms 19.74 508

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:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net)

peer jitter 2001:67c:1270:0:dea6:32ff:feaf:803b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) 0.000 0.274 0.413 1.744 28.961 33.926 66.201 28.548 33.652 9.681 6.786 ms 0.7773 3.777

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 0.003 0.005 0.012 0.042 0.138 13.865 0.037 0.135 0.289 0.028 ms 32.85 1394

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

peer jitter 204.17.205.16 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.16 0.000 0.004 0.005 0.015 0.055 0.135 15.795 0.050 0.132 0.345 0.036 ms 30.34 1212

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 0.003 0.006 0.019 0.066 0.164 14.263 0.061 0.160 0.431 0.044 ms 23.79 705.9

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::1 (robusta.dcs1.biz)

peer jitter 2405:fc00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.249 0.349 1.119 5.938 18.338 64.248 5.590 18.089 4.462 2.098 ms 7.87 98.18

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.263 0.351 0.890 4.399 13.406 80.609 4.048 13.144 4.153 1.683 ms 10.07 156.6

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.000 0.203 0.269 0.604 4.014 8.954 27.123 3.745 8.751 2.091 1.207 ms 6.527 75.08

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.188 0.280 0.605 3.266 8.920 80.026 2.986 8.731 3.709 1.178 ms 13.51 256

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.000 0.291 0.413 1.001 2.513 5.066 37.194 2.099 4.775 1.241 1.235 ms 11.26 219.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset 10.245 11.778 11.851 12.487 12.935 13.559 19.722 1.084 1.781 0.378 12.463 ppm 3.281e+04 1.053e+06
Local Clock Time Offset -47.058 -0.205 -0.045 -0.002 0.039 0.153 7.319 0.084 0.358 1.357 -0.063 ms -27.71 732
Local RMS Frequency Jitter 0.000 4.689 6.111 11.155 60.203 236.136 2,439.850 54.092 231.447 121.173 26.104 ppb 11.22 185.2
Local RMS Time Jitter 0.000 0.010 0.012 0.021 0.050 1.523 10.861 0.038 1.514 0.589 0.080 ms 9.63 144.2
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.003 0.005 0.015 0.061 0.123 94.484 0.057 0.120 2.775 0.128 ms 25.38 779.5
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 0.002 0.003 0.008 0.040 0.112 20.779 0.037 0.110 0.643 0.047 ms 19.74 508
Server Jitter 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) 0.000 0.274 0.413 1.744 28.961 33.926 66.201 28.548 33.652 9.681 6.786 ms 0.7773 3.777
Server Jitter 204.17.205.1 0.000 0.003 0.005 0.012 0.042 0.138 13.865 0.037 0.135 0.289 0.028 ms 32.85 1394
Server Jitter 204.17.205.16 0.000 0.004 0.005 0.015 0.055 0.135 15.795 0.050 0.132 0.345 0.036 ms 30.34 1212
Server Jitter 204.17.205.30 0.000 0.003 0.006 0.019 0.066 0.164 14.263 0.061 0.160 0.431 0.044 ms 23.79 705.9
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.249 0.349 1.119 5.938 18.338 64.248 5.590 18.089 4.462 2.098 ms 7.87 98.18
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.263 0.351 0.890 4.399 13.406 80.609 4.048 13.144 4.153 1.683 ms 10.07 156.6
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.203 0.269 0.604 4.014 8.954 27.123 3.745 8.751 2.091 1.207 ms 6.527 75.08
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.188 0.280 0.605 3.266 8.920 80.026 2.986 8.731 3.709 1.178 ms 13.51 256
Server Jitter SHM(0) 0.000 0.291 0.413 1.001 2.513 5.066 37.194 2.099 4.775 1.241 1.235 ms 11.26 219.8
Server Offset 2001:470:e815::24 (pi4.rellim.com) -162.974 -0.223 -0.064 -0.002 0.049 0.216 8.867 0.114 0.439 3.834 -0.129 ms -38.45 1411
Server Offset 2001:470:e815::8 (spidey.rellim.com) -28.829 -0.400 -0.132 -0.003 0.128 0.275 285.188 0.261 0.675 8.683 0.212 ms 28.24 930.6
Server Offset 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) -117.673 -0.737 -0.433 0.371 2.266 3.086 167.292 2.700 3.824 7.017 0.680 ms 2.016 372.2
Server Offset 204.17.205.1 -6.908 -0.431 -0.330 0.010 0.329 1.123 17.303 0.659 1.554 0.617 0.026 ms 15.1 464.6
Server Offset 204.17.205.16 -3.803 -0.193 -0.054 0.007 0.066 0.207 21.542 0.120 0.400 0.954 0.049 ms 17.65 400.1
Server Offset 204.17.205.30 -10.218 -0.172 -0.050 0.004 0.061 0.179 5.603 0.110 0.352 0.306 0.004 ms -16.9 777.9
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -104.776 3.840 4.173 5.625 7.319 7.850 171.820 3.146 4.010 5.186 5.695 ms 8.838 681.6
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -114.316 -8.046 -7.328 1.011 2.096 3.358 167.152 9.423 11.404 6.138 -0.003 ms -0.5537 365.3
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -0.767 -0.469 -0.105 2.025 2.864 4.184 12.267 2.969 4.654 1.127 1.602 ms 2.006 11.88
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -113.367 0.223 0.659 2.462 3.019 3.245 168.627 2.361 3.022 7.507 2.032 ms 2.066 322
Server Offset SHM(0) -239.660 -140.748 -137.848 -131.962 -127.097 -125.311 -117.086 10.750 15.438 3.618 -132.206 ms -5.302e+04 1.995e+06
TDOP 0.690 0.820 0.900 1.280 2.320 3.050 23.120 1.420 2.230 0.503 1.407 17.27 261.1
Temp /dev/sda 26.000 44.000 45.000 49.000 51.000 52.000 52.000 6.000 8.000 1.824 48.336 °C
Temp /dev/sdb 23.000 34.000 35.000 37.000 40.000 41.000 42.000 5.000 7.000 1.572 37.179 °C
Temp LM0 34.000 49.000 49.000 53.000 58.000 59.000 59.000 9.000 10.000 2.879 53.627 °C
Temp LM1 37.750 43.875 45.500 48.250 53.250 75.500 85.625 7.750 31.625 4.866 49.262 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.050 25.003 °C
Temp LM11 42.000 61.000 62.000 63.000 65.000 65.000 66.000 3.000 4.000 1.023 62.985 °C
Temp LM12 2.000 4.000 4.000 8.000 16.000 18.000 37.000 12.000 14.000 3.864 8.972 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.050 25.003 °C
Temp LM14 24.000 44.000 44.000 45.000 47.000 47.000 48.000 3.000 3.000 1.093 45.360 °C
Temp LM15 27.000 37.000 38.000 40.000 43.000 64.000 74.000 5.000 27.000 4.050 40.512 °C
Temp LM16 47.500 66.000 66.500 68.000 69.500 70.000 70.500 3.000 4.000 1.063 67.944 °C
Temp LM17 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM18 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM19 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM2 39.000 43.500 44.750 47.250 57.000 75.000 83.250 12.250 31.500 5.071 48.689 °C
Temp LM20 37.375 43.875 45.375 48.250 53.000 75.625 85.625 7.625 31.750 4.848 49.221 °C
Temp LM21 47.500 66.250 66.750 68.000 69.750 70.000 70.625 3.000 3.750 1.058 68.096 °C
Temp LM22 21.000 34.000 35.000 37.000 40.000 41.000 42.000 5.000 7.000 1.659 37.265 °C
Temp LM23 50.850 65.850 66.850 69.850 71.850 72.850 77.850 5.000 7.000 1.745 69.856 °C
Temp LM3 26.000 45.000 45.000 49.000 51.000 52.000 52.000 6.000 7.000 1.826 48.333 °C
Temp LM4 31.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.180 51.349 °C
Temp LM5 30.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.182 51.363 °C
Temp LM6 44.850 56.850 57.850 59.850 62.850 70.850 75.850 5.000 14.000 2.162 60.329 °C
Temp LM7 31.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.176 51.369 °C
Temp LM8 24.000 44.000 44.000 45.000 47.000 47.000 48.000 3.000 3.000 1.095 45.361 °C
Temp LM9 27.500 38.000 38.000 40.000 42.000 51.500 54.500 4.000 13.500 2.056 40.321 °C
nSats 4.000 4.000 4.000 4.000 13.000 15.000 17.000 9.000 11.000 3.852 7.456 nSat 3.997 8.857
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!