NTPsec

Kong

Report generated: Fri Sep 22 17:49:01 2023 UTC
Start Time: Thu Sep 21 17:49:01 2023 UTC
End Time: Fri Sep 22 17:49:01 2023 UTC
Report Period: 1.0 days
Warning: plots clipped

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 -194.051 -141.015 -54.318 -0.730 37.135 105.795 282.850 91.453 246.810 38.227 -3.433 µs -4.197 23.15
Local Clock Frequency Offset 11.222 11.237 11.272 11.394 11.925 12.434 12.583 0.653 1.198 0.252 11.486 ppm 8.909e+04 3.983e+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.060 0.060 12.778 22.932 43.127 60.506 68.116 30.349 60.446 10.042 24.528 µs 8.552 30.16

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 0.000 5.393 10.385 50.909 71.536 97.899 45.516 71.536 14.349 14.627 ppb 3.068 12.85

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 -194.051 -141.015 -54.318 -0.730 37.135 105.795 282.850 91.453 246.810 38.227 -3.433 µs -4.197 23.15

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.222 11.237 11.272 11.394 11.925 12.434 12.583 0.653 1.198 0.252 11.486 ppm 8.909e+04 3.983e+06
Temp /dev/sda 44.000 45.000 45.000 47.000 48.000 49.000 49.000 3.000 4.000 0.905 46.915 °C
Temp /dev/sdb 34.000 34.000 34.000 35.000 36.000 36.000 37.000 2.000 2.000 0.686 34.922 °C
Temp LM0 40.000 42.000 49.000 54.000 58.000 59.000 59.000 9.000 17.000 3.331 53.601 °C
Temp LM1 71.875 72.125 72.250 73.000 74.250 84.375 85.500 2.000 12.250 2.038 73.301 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM11 55.000 55.000 59.000 60.000 61.000 61.000 62.000 2.000 6.000 0.761 60.028 °C
Temp LM12 6.000 7.000 8.000 8.000 8.000 9.000 9.000 0.000 2.000 0.230 8.018 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 26.000 26.000 0.000 1.000 0.118 25.014 °C
Temp LM14 60.500 61.000 61.000 62.000 63.000 73.000 74.500 2.000 12.000 2.047 62.094 °C
Temp LM15 60.000 60.500 64.000 64.500 66.000 66.500 66.500 2.000 6.000 0.770 64.737 °C
Temp LM16 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °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 71.875 72.125 72.250 73.000 74.250 84.375 85.500 2.000 12.250 2.038 73.301 °C
Temp LM19 60.250 60.875 64.250 64.750 66.250 66.500 66.500 2.000 5.625 0.741 64.892 °C
Temp LM2 68.750 71.250 71.750 72.750 74.250 84.500 85.500 2.500 13.250 2.010 73.104 °C
Temp LM20 33.000 34.000 34.000 35.000 36.000 36.000 37.000 2.000 2.000 0.753 35.141 °C
Temp LM21 59.850 60.850 63.850 66.850 67.850 67.850 68.850 4.000 7.000 1.413 66.366 °C
Temp LM3 44.000 45.000 45.000 47.000 48.000 49.000 49.000 3.000 4.000 0.912 46.908 °C
Temp LM4 43.850 45.850 46.850 47.850 49.850 51.850 51.850 3.000 6.000 1.126 47.811 °C
Temp LM5 44.850 45.850 46.850 47.850 49.850 51.850 51.850 3.000 6.000 1.094 47.811 °C
Temp LM6 52.850 52.850 53.850 54.850 60.850 68.850 68.850 7.000 16.000 2.562 55.426 °C
Temp LM7 43.850 45.850 46.850 47.850 50.850 51.850 52.850 4.000 6.000 1.118 47.857 °C
Temp LM8 35.000 37.000 42.000 43.000 43.000 44.000 44.000 1.000 7.000 0.830 42.735 °C
Temp LM9 38.500 39.500 39.500 40.500 42.000 49.000 51.000 2.500 9.500 1.587 40.894 °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 7.000 9.000 10.000 13.000 16.000 17.000 19.000 6.000 8.000 1.775 13.100 nSat 279 1910
TDOP 0.650 0.720 0.780 1.160 1.810 2.390 5.010 1.030 1.670 0.367 1.212 20.95 87.58

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) -0.181 -0.100 -0.052 0.022 0.095 430.893 452.898 0.147 430.993 48.961 5.523 ms 5.43 52.44

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) -0.246 -0.144 -0.097 -0.031 0.144 451.830 452.600 0.241 451.974 90.642 19.463 ms 1.596 10.84

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 -0.565 -0.526 -0.475 -0.033 0.192 430.454 452.501 0.668 430.980 47.845 5.175 ms 5.614 55.31

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 -0.210 -0.182 -0.099 -0.027 0.035 441.147 452.627 0.133 441.329 64.289 9.552 ms 3.392 26.62

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) -5.966 3.140 5.112 6.192 10.377 453.726 471.620 5.265 450.586 70.303 17.994 ms 3.358 22.92

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

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

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

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



Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -0.478 -0.352 -0.232 0.264 1.014 445.979 454.008 1.247 446.331 64.953 10.022 ms 3.383 26.33

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.527 1.555 1.705 2.147 2.594 2.908 4.428 0.888 1.353 0.298 2.152 ms 260.8 1788

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) 2.030 2.030 2.030 2.365 456.561 456.561 456.561 454.531 454.531 187.154 102.462 ms -0.1136 1.638

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) -155.793 -139.376 -137.038 -132.406 -128.626 -127.285 319.299 8.413 12.091 17.616 -131.869 ms -612.2 5399

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.000 3.479 14.076 62.945 98.586 173.457 59.466 98.586 20.134 20.841 µs 2.453 11.77

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.000 2.640 7.959 27.592 55.702 100.886 24.952 55.702 10.881 10.886 µs 4.193 27.81

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.000 3.613 12.183 37.665 67.894 120.788 34.052 67.894 12.716 15.507 µs 3.801 22.88

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.000 3.270 13.298 49.381 125.617 177.050 46.111 125.617 22.128 19.534 µs 3.116 16.88

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.000 0.449 12.773 26.033 31.462 40.552 25.584 31.462 7.622 12.657 ms 2.594 6.411

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.000 0.174 2.239 6.292 7.488 7.728 6.118 7.488 1.863 2.647 ms 2.06 5.086

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.000 0.316 2.027 5.462 6.275 6.971 5.146 6.275 1.631 2.332 ms 2.094 5.071

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.000 0.000 0.000 4.996 4.996 4.996 4.996 4.996 2.025 1.215 ms 0.0342 1.648

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.251 0.386 0.986 2.544 12.097 451.267 2.158 11.846 25.554 3.439 ms 9.27 135.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 11.222 11.237 11.272 11.394 11.925 12.434 12.583 0.653 1.198 0.252 11.486 ppm 8.909e+04 3.983e+06
Local Clock Time Offset -194.051 -141.015 -54.318 -0.730 37.135 105.795 282.850 91.453 246.810 38.227 -3.433 µs -4.197 23.15
Local RMS Frequency Jitter 0.000 0.000 5.393 10.385 50.909 71.536 97.899 45.516 71.536 14.349 14.627 ppb 3.068 12.85
Local RMS Time Jitter 0.060 0.060 12.778 22.932 43.127 60.506 68.116 30.349 60.446 10.042 24.528 µs 8.552 30.16
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.000 3.479 14.076 62.945 98.586 173.457 59.466 98.586 20.134 20.841 µs 2.453 11.77
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 0.000 2.640 7.959 27.592 55.702 100.886 24.952 55.702 10.881 10.886 µs 4.193 27.81
Server Jitter 204.17.205.1 0.000 0.000 3.613 12.183 37.665 67.894 120.788 34.052 67.894 12.716 15.507 µs 3.801 22.88
Server Jitter 204.17.205.30 0.000 0.000 3.270 13.298 49.381 125.617 177.050 46.111 125.617 22.128 19.534 µs 3.116 16.88
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.000 0.449 12.773 26.033 31.462 40.552 25.584 31.462 7.622 12.657 ms 2.594 6.411
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.000 0.174 2.239 6.292 7.488 7.728 6.118 7.488 1.863 2.647 ms 2.06 5.086
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.000 0.316 2.027 5.462 6.275 6.971 5.146 6.275 1.631 2.332 ms 2.094 5.071
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.000 0.000 0.000 4.996 4.996 4.996 4.996 4.996 2.025 1.215 ms 0.0342 1.648
Server Jitter SHM(0) 0.000 0.251 0.386 0.986 2.544 12.097 451.267 2.158 11.846 25.554 3.439 ms 9.27 135.8
Server Offset 2001:470:e815::24 (pi4.rellim.com) -0.181 -0.100 -0.052 0.022 0.095 430.893 452.898 0.147 430.993 48.961 5.523 ms 5.43 52.44
Server Offset 2001:470:e815::8 (spidey.rellim.com) -0.246 -0.144 -0.097 -0.031 0.144 451.830 452.600 0.241 451.974 90.642 19.463 ms 1.596 10.84
Server Offset 204.17.205.1 -0.565 -0.526 -0.475 -0.033 0.192 430.454 452.501 0.668 430.980 47.845 5.175 ms 5.614 55.31
Server Offset 204.17.205.30 -0.210 -0.182 -0.099 -0.027 0.035 441.147 452.627 0.133 441.329 64.289 9.552 ms 3.392 26.62
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -5.966 3.140 5.112 6.192 10.377 453.726 471.620 5.265 450.586 70.303 17.994 ms 3.358 22.92
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -0.478 -0.352 -0.232 0.264 1.014 445.979 454.008 1.247 446.331 64.953 10.022 ms 3.383 26.33
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 1.527 1.555 1.705 2.147 2.594 2.908 4.428 0.888 1.353 0.298 2.152 ms 260.8 1788
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 2.030 2.030 2.030 2.365 456.561 456.561 456.561 454.531 454.531 187.154 102.462 ms -0.1136 1.638
Server Offset SHM(0) -155.793 -139.376 -137.038 -132.406 -128.626 -127.285 319.299 8.413 12.091 17.616 -131.869 ms -612.2 5399
TDOP 0.650 0.720 0.780 1.160 1.810 2.390 5.010 1.030 1.670 0.367 1.212 20.95 87.58
Temp /dev/sda 44.000 45.000 45.000 47.000 48.000 49.000 49.000 3.000 4.000 0.905 46.915 °C
Temp /dev/sdb 34.000 34.000 34.000 35.000 36.000 36.000 37.000 2.000 2.000 0.686 34.922 °C
Temp LM0 40.000 42.000 49.000 54.000 58.000 59.000 59.000 9.000 17.000 3.331 53.601 °C
Temp LM1 71.875 72.125 72.250 73.000 74.250 84.375 85.500 2.000 12.250 2.038 73.301 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM11 55.000 55.000 59.000 60.000 61.000 61.000 62.000 2.000 6.000 0.761 60.028 °C
Temp LM12 6.000 7.000 8.000 8.000 8.000 9.000 9.000 0.000 2.000 0.230 8.018 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 26.000 26.000 0.000 1.000 0.118 25.014 °C
Temp LM14 60.500 61.000 61.000 62.000 63.000 73.000 74.500 2.000 12.000 2.047 62.094 °C
Temp LM15 60.000 60.500 64.000 64.500 66.000 66.500 66.500 2.000 6.000 0.770 64.737 °C
Temp LM16 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °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 71.875 72.125 72.250 73.000 74.250 84.375 85.500 2.000 12.250 2.038 73.301 °C
Temp LM19 60.250 60.875 64.250 64.750 66.250 66.500 66.500 2.000 5.625 0.741 64.892 °C
Temp LM2 68.750 71.250 71.750 72.750 74.250 84.500 85.500 2.500 13.250 2.010 73.104 °C
Temp LM20 33.000 34.000 34.000 35.000 36.000 36.000 37.000 2.000 2.000 0.753 35.141 °C
Temp LM21 59.850 60.850 63.850 66.850 67.850 67.850 68.850 4.000 7.000 1.413 66.366 °C
Temp LM3 44.000 45.000 45.000 47.000 48.000 49.000 49.000 3.000 4.000 0.912 46.908 °C
Temp LM4 43.850 45.850 46.850 47.850 49.850 51.850 51.850 3.000 6.000 1.126 47.811 °C
Temp LM5 44.850 45.850 46.850 47.850 49.850 51.850 51.850 3.000 6.000 1.094 47.811 °C
Temp LM6 52.850 52.850 53.850 54.850 60.850 68.850 68.850 7.000 16.000 2.562 55.426 °C
Temp LM7 43.850 45.850 46.850 47.850 50.850 51.850 52.850 4.000 6.000 1.118 47.857 °C
Temp LM8 35.000 37.000 42.000 43.000 43.000 44.000 44.000 1.000 7.000 0.830 42.735 °C
Temp LM9 38.500 39.500 39.500 40.500 42.000 49.000 51.000 2.500 9.500 1.587 40.894 °C
nSats 7.000 9.000 10.000 13.000 16.000 17.000 19.000 6.000 8.000 1.775 13.100 nSat 279 1910
Summary as CSV file


This server:

Motherboard:
OS: Gentoo unstable
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!