NTPsec

Kong

Report generated: Fri Apr 25 13:59:00 2025 UTC
Start Time: Fri Apr 18 13:59:00 2025 UTC
End Time: Fri Apr 25 13:59:00 2025 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 -469.784 -214.021 -88.100 -1.684 82.532 255.193 662.533 170.632 469.214 68.364 -0.625 µs 1.143 20.63
Local Clock Frequency Offset 11.474 11.550 11.586 11.905 13.732 13.926 14.511 2.146 2.376 0.636 12.116 ppm 1.676 4.869

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.001 10.573 13.735 27.531 69.514 114.249 278.330 55.779 103.676 21.300 33.125 µs 3.46 24.18

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.942 6.679 15.706 89.160 153.775 221.983 82.481 148.833 29.349 26.518 ppb 2.829 12.22

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 -469.784 -214.021 -88.100 -1.684 82.532 255.193 662.533 170.632 469.214 68.364 -0.625 µs 1.143 20.63

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 11.474 11.550 11.586 11.905 13.732 13.926 14.511 2.146 2.376 0.636 12.116 ppm 1.676 4.869
Temp /dev/nvme0n1 63.000 65.000 66.000 70.000 71.000 72.000 74.000 5.000 7.000 1.534 69.643 °C
Temp /dev/nvme1n1 48.000 49.000 50.000 51.000 53.000 55.000 57.000 3.000 6.000 1.026 51.118 °C
Temp /dev/sda 44.000 45.000 45.000 48.000 49.000 50.000 51.000 4.000 5.000 1.411 47.447 °C
Temp /dev/sdb 33.000 33.000 33.000 36.000 38.000 39.000 39.000 5.000 6.000 1.364 35.723 °C
Temp LM0 48.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.743 54.232 °C
Temp LM1 37.125 37.750 38.250 43.000 74.000 76.750 84.875 35.750 39.000 11.068 46.729 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 26.000 26.000 0.000 1.000 0.141 25.020 °C
Temp LM11 61.000 62.000 62.000 63.000 64.000 64.000 65.000 2.000 2.000 0.602 62.736 °C
Temp LM12 4.000 6.000 9.000 17.000 27.000 32.000 37.000 18.000 26.000 5.444 18.435 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.055 25.003 °C
Temp LM14 43.000 43.000 43.000 45.000 46.000 46.000 46.000 3.000 3.000 0.692 44.548 °C
Temp LM15 32.000 33.000 34.000 37.000 63.000 65.000 73.000 29.000 32.000 8.936 39.827 °C
Temp LM16 66.500 67.000 67.500 68.000 69.000 69.500 69.500 1.500 2.500 0.515 68.079 °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 36.750 37.500 38.500 43.000 73.250 76.750 83.500 34.750 39.250 10.611 46.576 °C
Temp LM20 37.000 37.750 38.250 43.000 74.000 76.750 84.875 35.750 39.000 11.052 46.706 °C
Temp LM21 66.500 67.250 67.500 68.250 69.250 69.750 69.750 1.750 2.500 0.495 68.221 °C
Temp LM22 33.000 33.000 33.000 36.000 38.000 39.000 39.000 5.000 6.000 1.320 35.766 °C
Temp LM23 62.850 64.850 65.850 69.850 70.850 71.850 73.850 5.000 7.000 1.541 69.500 °C
Temp LM3 44.000 45.000 45.000 48.000 49.000 50.000 51.000 4.000 5.000 1.400 47.446 °C
Temp LM4 47.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.037 50.958 °C
Temp LM5 47.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.032 50.973 °C
Temp LM6 55.850 56.850 57.850 58.850 64.850 70.850 74.850 7.000 14.000 2.499 59.800 °C
Temp LM7 47.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.022 50.971 °C
Temp LM8 43.000 43.000 43.000 45.000 46.000 46.000 46.000 3.000 3.000 0.693 44.550 °C
Temp LM9 33.000 33.500 34.000 37.000 51.000 52.000 54.500 17.000 18.500 4.813 38.235 °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 3.000 4.000 6.000 9.000 11.000 12.000 14.000 5.000 8.000 1.648 8.592 nSat -0.1299 3.207
TDOP 0.710 0.880 1.040 1.670 4.270 10.310 114.400 3.230 9.430 3.240 2.171 14.88 313.5

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) -150.177 -0.230 -0.095 0.009 0.111 0.302 17.533 0.205 0.532 2.350 -0.026 ms -62.51 4000

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) -150.554 -0.493 -0.367 0.016 0.216 0.313 0.574 0.582 0.807 4.573 -0.156 ms -32.81 1079

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 -150.686 -0.713 -0.552 -0.020 0.355 0.489 0.743 0.907 1.203 2.353 -0.072 ms -63.08 4038

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 -150.525 -0.290 -0.133 0.023 0.162 0.370 1.125 0.295 0.660 8.501 -0.457 ms -17.58 310.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.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 -150.536 -0.282 -0.112 -0.017 0.076 0.248 0.628 0.188 0.530 3.379 -0.093 ms -44.47 1980

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) -147.332 2.078 2.541 3.098 4.948 12.200 22.383 2.407 10.122 3.850 3.274 ms -34.19 1350

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) -150.466 -1.484 -1.115 -0.536 0.080 0.447 2.721 1.195 1.931 3.363 -0.609 ms -43.94 1958

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.950 -0.543 -0.298 0.574 1.053 2.177 4.881 1.351 2.719 0.480 0.555 ms 2.46 25.56

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) -0.933 -0.508 -0.141 0.529 0.866 9.979 19.536 1.007 10.487 1.282 0.642 ms 7.983 77.96

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) -272.564 -132.995 -131.078 -126.956 -122.490 -120.629 -117.476 8.589 12.366 2.898 -126.924 ms -4.147 179.7

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.004 0.005 0.032 0.145 2.181 82.029 0.140 2.177 1.876 0.168 ms 29.61 1095

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 2.499 3.863 22.048 127.030 170.214 260.053 123.167 167.715 41.438 37.685 µs 1.748 5.64

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 2.848 4.896 28.610 160.168 194.091 349.537 155.272 191.243 51.845 50.993 µs 1.318 4.094

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 6.532 9.968 28.937 126.219 367.450 4,960.479 116.251 360.918 328.793 71.425 µs 11.6 145.2

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 3.697 6.818 38.234 177.932 330.745 2,288.680 171.114 327.048 97.630 66.274 µs 12.67 269.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 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.236 0.389 1.221 4.993 12.304 135.042 4.604 12.068 5.762 2.028 ms 14.47 258.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 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.177 0.280 0.761 2.746 11.959 107.245 2.466 11.782 5.026 1.424 ms 14.04 242.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 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.148 0.231 0.537 3.145 5.864 7.370 2.914 5.716 1.049 0.856 ms 3.506 16.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.170 0.235 0.516 2.019 7.593 56.910 1.784 7.423 2.121 0.863 ms 17.07 411.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 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.250 0.361 0.890 2.368 6.553 152.238 2.008 6.303 1.777 1.156 ms 33.85 2110

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 11.474 11.550 11.586 11.905 13.732 13.926 14.511 2.146 2.376 0.636 12.116 ppm 1.676 4.869
Local Clock Time Offset -469.784 -214.021 -88.100 -1.684 82.532 255.193 662.533 170.632 469.214 68.364 -0.625 µs 1.143 20.63
Local RMS Frequency Jitter 0.000 4.942 6.679 15.706 89.160 153.775 221.983 82.481 148.833 29.349 26.518 ppb 2.829 12.22
Local RMS Time Jitter 0.001 10.573 13.735 27.531 69.514 114.249 278.330 55.779 103.676 21.300 33.125 µs 3.46 24.18
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.004 0.005 0.032 0.145 2.181 82.029 0.140 2.177 1.876 0.168 ms 29.61 1095
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 2.499 3.863 22.048 127.030 170.214 260.053 123.167 167.715 41.438 37.685 µs 1.748 5.64
Server Jitter 204.17.205.1 0.000 2.848 4.896 28.610 160.168 194.091 349.537 155.272 191.243 51.845 50.993 µs 1.318 4.094
Server Jitter 204.17.205.17 0.000 6.532 9.968 28.937 126.219 367.450 4,960.479 116.251 360.918 328.793 71.425 µs 11.6 145.2
Server Jitter 204.17.205.30 0.000 3.697 6.818 38.234 177.932 330.745 2,288.680 171.114 327.048 97.630 66.274 µs 12.67 269.6
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.236 0.389 1.221 4.993 12.304 135.042 4.604 12.068 5.762 2.028 ms 14.47 258.5
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.177 0.280 0.761 2.746 11.959 107.245 2.466 11.782 5.026 1.424 ms 14.04 242.1
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.148 0.231 0.537 3.145 5.864 7.370 2.914 5.716 1.049 0.856 ms 3.506 16.36
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.170 0.235 0.516 2.019 7.593 56.910 1.784 7.423 2.121 0.863 ms 17.07 411.1
Server Jitter SHM(0) 0.000 0.250 0.361 0.890 2.368 6.553 152.238 2.008 6.303 1.777 1.156 ms 33.85 2110
Server Offset 2001:470:e815::24 (pi4.rellim.com) -150.177 -0.230 -0.095 0.009 0.111 0.302 17.533 0.205 0.532 2.350 -0.026 ms -62.51 4000
Server Offset 2001:470:e815::8 (spidey.rellim.com) -150.554 -0.493 -0.367 0.016 0.216 0.313 0.574 0.582 0.807 4.573 -0.156 ms -32.81 1079
Server Offset 204.17.205.1 -150.686 -0.713 -0.552 -0.020 0.355 0.489 0.743 0.907 1.203 2.353 -0.072 ms -63.08 4038
Server Offset 204.17.205.17 -150.525 -0.290 -0.133 0.023 0.162 0.370 1.125 0.295 0.660 8.501 -0.457 ms -17.58 310.2
Server Offset 204.17.205.30 -150.536 -0.282 -0.112 -0.017 0.076 0.248 0.628 0.188 0.530 3.379 -0.093 ms -44.47 1980
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -147.332 2.078 2.541 3.098 4.948 12.200 22.383 2.407 10.122 3.850 3.274 ms -34.19 1350
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -150.466 -1.484 -1.115 -0.536 0.080 0.447 2.721 1.195 1.931 3.363 -0.609 ms -43.94 1958
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1.950 -0.543 -0.298 0.574 1.053 2.177 4.881 1.351 2.719 0.480 0.555 ms 2.46 25.56
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -0.933 -0.508 -0.141 0.529 0.866 9.979 19.536 1.007 10.487 1.282 0.642 ms 7.983 77.96
Server Offset SHM(0) -272.564 -132.995 -131.078 -126.956 -122.490 -120.629 -117.476 8.589 12.366 2.898 -126.924 ms -4.147 179.7
TDOP 0.710 0.880 1.040 1.670 4.270 10.310 114.400 3.230 9.430 3.240 2.171 14.88 313.5
Temp /dev/nvme0n1 63.000 65.000 66.000 70.000 71.000 72.000 74.000 5.000 7.000 1.534 69.643 °C
Temp /dev/nvme1n1 48.000 49.000 50.000 51.000 53.000 55.000 57.000 3.000 6.000 1.026 51.118 °C
Temp /dev/sda 44.000 45.000 45.000 48.000 49.000 50.000 51.000 4.000 5.000 1.411 47.447 °C
Temp /dev/sdb 33.000 33.000 33.000 36.000 38.000 39.000 39.000 5.000 6.000 1.364 35.723 °C
Temp LM0 48.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.743 54.232 °C
Temp LM1 37.125 37.750 38.250 43.000 74.000 76.750 84.875 35.750 39.000 11.068 46.729 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 26.000 26.000 0.000 1.000 0.141 25.020 °C
Temp LM11 61.000 62.000 62.000 63.000 64.000 64.000 65.000 2.000 2.000 0.602 62.736 °C
Temp LM12 4.000 6.000 9.000 17.000 27.000 32.000 37.000 18.000 26.000 5.444 18.435 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.055 25.003 °C
Temp LM14 43.000 43.000 43.000 45.000 46.000 46.000 46.000 3.000 3.000 0.692 44.548 °C
Temp LM15 32.000 33.000 34.000 37.000 63.000 65.000 73.000 29.000 32.000 8.936 39.827 °C
Temp LM16 66.500 67.000 67.500 68.000 69.000 69.500 69.500 1.500 2.500 0.515 68.079 °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 36.750 37.500 38.500 43.000 73.250 76.750 83.500 34.750 39.250 10.611 46.576 °C
Temp LM20 37.000 37.750 38.250 43.000 74.000 76.750 84.875 35.750 39.000 11.052 46.706 °C
Temp LM21 66.500 67.250 67.500 68.250 69.250 69.750 69.750 1.750 2.500 0.495 68.221 °C
Temp LM22 33.000 33.000 33.000 36.000 38.000 39.000 39.000 5.000 6.000 1.320 35.766 °C
Temp LM23 62.850 64.850 65.850 69.850 70.850 71.850 73.850 5.000 7.000 1.541 69.500 °C
Temp LM3 44.000 45.000 45.000 48.000 49.000 50.000 51.000 4.000 5.000 1.400 47.446 °C
Temp LM4 47.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.037 50.958 °C
Temp LM5 47.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.032 50.973 °C
Temp LM6 55.850 56.850 57.850 58.850 64.850 70.850 74.850 7.000 14.000 2.499 59.800 °C
Temp LM7 47.850 48.850 49.850 50.850 52.850 54.850 56.850 3.000 6.000 1.022 50.971 °C
Temp LM8 43.000 43.000 43.000 45.000 46.000 46.000 46.000 3.000 3.000 0.693 44.550 °C
Temp LM9 33.000 33.500 34.000 37.000 51.000 52.000 54.500 17.000 18.500 4.813 38.235 °C
nSats 3.000 4.000 6.000 9.000 11.000 12.000 14.000 5.000 8.000 1.648 8.592 nSat -0.1299 3.207
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.
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 FIsher-Pearson moment of skewness. There are other different ways to calculate Skewness Wikipedia describes Skewness best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
Kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses standard Kurtosis. There are other different ways to calculate 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".
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!