NTPsec

Kong

Report generated: Thu Apr 3 13:59:01 2025 UTC
Start Time: Thu Mar 27 13:59:00 2025 UTC
End Time: Thu Apr 3 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 -6.387 -0.538 -0.080 -0.001 0.076 0.412 5.021 0.157 0.950 0.338 -0.006 ms -2.665 144
Local Clock Frequency Offset 10.653 11.290 11.340 11.441 11.813 12.480 13.705 0.474 1.190 0.213 11.483 ppm 5.132 40.2

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.012 0.019 0.025 0.043 0.102 2.071 4.312 0.077 2.052 0.306 0.091 ms 8.484 84.52

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 3.814 9.681 12.782 23.259 78.859 280.619 389.341 66.077 270.938 42.082 33.133 ppb 5.212 33.54

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 -6.387 -0.538 -0.080 -0.001 0.076 0.412 5.021 0.157 0.950 0.338 -0.006 ms -2.665 144

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.653 11.290 11.340 11.441 11.813 12.480 13.705 0.474 1.190 0.213 11.483 ppm 5.132 40.2
Temp /dev/sda 44.000 45.000 45.000 47.000 49.000 51.000 52.000 4.000 6.000 1.425 47.074 °C
Temp /dev/sdb 33.000 33.000 33.000 35.000 38.000 40.000 40.000 5.000 7.000 1.388 35.263 °C
Temp LM0 48.000 49.000 50.000 55.000 58.000 58.000 59.000 8.000 9.000 2.707 54.347 °C
Temp LM1 36.000 36.875 37.250 38.625 45.625 71.750 77.250 8.375 34.875 4.426 39.723 °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 60.000 61.000 61.000 62.000 63.000 63.000 64.000 2.000 2.000 0.549 62.254 °C
Temp LM12 3.000 9.000 16.000 23.000 30.000 34.000 43.000 14.000 25.000 4.070 23.096 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM14 42.000 43.000 43.000 44.000 45.000 45.000 46.000 2.000 2.000 0.553 44.012 °C
Temp LM15 31.000 32.000 33.000 34.000 37.000 60.000 66.000 4.000 28.000 3.297 34.582 °C
Temp LM16 66.000 66.500 67.000 67.500 68.000 68.500 69.500 1.000 2.000 0.394 67.589 °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.000 36.750 37.250 39.250 44.500 71.250 78.000 7.250 34.500 4.257 40.088 °C
Temp LM20 36.000 36.875 37.250 38.625 45.500 71.750 77.125 8.250 34.875 4.418 39.718 °C
Temp LM21 66.000 66.750 67.000 67.750 68.250 68.750 69.500 1.250 2.000 0.367 67.733 °C
Temp LM22 33.000 33.000 33.000 36.000 38.000 40.000 40.000 5.000 7.000 1.353 35.344 °C
Temp LM23 62.850 65.850 66.850 69.850 70.850 70.850 73.850 4.000 5.000 1.191 69.654 °C
Temp LM3 44.000 45.000 45.000 47.000 49.000 51.000 52.000 4.000 6.000 1.415 47.080 °C
Temp LM4 47.850 48.850 48.850 50.850 50.850 52.850 56.850 2.000 4.000 0.746 50.594 °C
Temp LM5 47.850 48.850 48.850 50.850 50.850 52.850 56.850 2.000 4.000 0.744 50.601 °C
Temp LM6 54.850 56.850 56.850 58.850 60.850 65.850 73.850 4.000 9.000 1.747 58.879 °C
Temp LM7 47.850 48.850 49.850 50.850 50.850 52.850 56.850 1.000 4.000 0.735 50.607 °C
Temp LM8 42.000 43.000 43.000 44.000 45.000 45.000 46.000 2.000 2.000 0.552 44.012 °C
Temp LM9 32.000 33.000 33.000 34.500 37.000 45.000 51.500 4.000 12.000 1.979 34.670 °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 6.000 7.000 9.000 11.000 12.000 12.000 4.000 6.000 1.334 8.796 nSat 0.09545 3.079
TDOP 0.900 1.000 1.110 1.870 3.490 5.210 22.080 2.380 4.210 0.874 2.011 4.028 51.86

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) -1.042 -0.163 -0.093 -0.006 0.073 0.156 36.356 0.166 0.319 0.754 0.013 ms 41.05 1816

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) -5.023 -4.295 -1.697 0.088 1.454 6.835 8.582 3.151 11.130 1.356 0.090 ms 2.025 16.78

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 -5.429 -4.417 -1.730 0.060 1.460 6.456 8.517 3.190 10.873 1.348 0.079 ms 1.483 15.08

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

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

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

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



Server Offset 204.17.205.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 -2,894.975 -857.766 -83.605 14.676 105.799 585.529 4,558.628 189.404 1,443.295 324.384 18.396 µs 4.436 86.57

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) -0.364 1.422 1.755 2.705 4.911 7.478 15.087 3.156 6.057 1.361 3.192 ms 1.958 13

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) -11.274 -4.125 -1.150 -0.541 0.163 0.622 5.245 1.313 4.747 0.825 -0.558 ms -5.096 55.81

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.120 -0.660 -0.464 0.538 1.086 1.367 1.677 1.550 2.027 0.429 0.483 ms -0.7062 3.838

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

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

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

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



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

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -1.719 -1.182 -0.950 0.570 1.113 6.112 10.139 2.063 7.294 1.177 0.445 ms 4.037 30.26

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) -173.605 -142.336 -135.653 -127.246 -121.124 -115.991 -111.134 14.529 26.345 4.426 -127.403 ms -0.85 6.759

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.010 0.024 0.103 0.173 0.217 23.361 0.149 0.208 0.731 0.132 ms 26.22 731.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 8.392 25.907 119.488 215.120 279.205 510.220 189.213 270.813 63.485 116.142 µs 0.5561 4.226

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 8.900 23.930 119.883 222.440 300.751 749.638 198.510 291.851 66.528 119.695 µs 0.7394 6.172

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.016 0.032 0.121 0.239 1.859 4.557 0.207 1.843 0.305 0.164 ms 7.909 76.15

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.216 0.362 1.148 3.360 8.034 50.086 2.998 7.818 2.266 1.517 ms 13.39 255.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 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.247 0.362 1.027 3.237 7.379 63.726 2.875 7.132 3.165 1.463 ms 15.73 289.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.182 0.285 0.633 2.526 6.118 27.723 2.241 5.936 2.033 1.027 ms 9.891 118.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 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.100 0.178 0.243 0.550 2.743 5.310 14.430 2.500 5.132 1.030 0.854 ms 5.407 49.87

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.266 0.383 1.013 7.048 10.192 40.210 6.665 9.926 2.213 1.823 ms 3.053 18.12

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.653 11.290 11.340 11.441 11.813 12.480 13.705 0.474 1.190 0.213 11.483 ppm 5.132 40.2
Local Clock Time Offset -6.387 -0.538 -0.080 -0.001 0.076 0.412 5.021 0.157 0.950 0.338 -0.006 ms -2.665 144
Local RMS Frequency Jitter 3.814 9.681 12.782 23.259 78.859 280.619 389.341 66.077 270.938 42.082 33.133 ppb 5.212 33.54
Local RMS Time Jitter 0.012 0.019 0.025 0.043 0.102 2.071 4.312 0.077 2.052 0.306 0.091 ms 8.484 84.52
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.010 0.024 0.103 0.173 0.217 23.361 0.149 0.208 0.731 0.132 ms 26.22 731.5
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 8.392 25.907 119.488 215.120 279.205 510.220 189.213 270.813 63.485 116.142 µs 0.5561 4.226
Server Jitter 204.17.205.1 0.000 8.900 23.930 119.883 222.440 300.751 749.638 198.510 291.851 66.528 119.695 µs 0.7394 6.172
Server Jitter 204.17.205.30 0.000 0.016 0.032 0.121 0.239 1.859 4.557 0.207 1.843 0.305 0.164 ms 7.909 76.15
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.216 0.362 1.148 3.360 8.034 50.086 2.998 7.818 2.266 1.517 ms 13.39 255.9
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.247 0.362 1.027 3.237 7.379 63.726 2.875 7.132 3.165 1.463 ms 15.73 289.3
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.182 0.285 0.633 2.526 6.118 27.723 2.241 5.936 2.033 1.027 ms 9.891 118.2
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.100 0.178 0.243 0.550 2.743 5.310 14.430 2.500 5.132 1.030 0.854 ms 5.407 49.87
Server Jitter SHM(0) 0.000 0.266 0.383 1.013 7.048 10.192 40.210 6.665 9.926 2.213 1.823 ms 3.053 18.12
Server Offset 2001:470:e815::24 (pi4.rellim.com) -1.042 -0.163 -0.093 -0.006 0.073 0.156 36.356 0.166 0.319 0.754 0.013 ms 41.05 1816
Server Offset 2001:470:e815::8 (spidey.rellim.com) -5.023 -4.295 -1.697 0.088 1.454 6.835 8.582 3.151 11.130 1.356 0.090 ms 2.025 16.78
Server Offset 204.17.205.1 -5.429 -4.417 -1.730 0.060 1.460 6.456 8.517 3.190 10.873 1.348 0.079 ms 1.483 15.08
Server Offset 204.17.205.30 -2,894.975 -857.766 -83.605 14.676 105.799 585.529 4,558.628 189.404 1,443.295 324.384 18.396 µs 4.436 86.57
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -0.364 1.422 1.755 2.705 4.911 7.478 15.087 3.156 6.057 1.361 3.192 ms 1.958 13
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -11.274 -4.125 -1.150 -0.541 0.163 0.622 5.245 1.313 4.747 0.825 -0.558 ms -5.096 55.81
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1.120 -0.660 -0.464 0.538 1.086 1.367 1.677 1.550 2.027 0.429 0.483 ms -0.7062 3.838
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -1.719 -1.182 -0.950 0.570 1.113 6.112 10.139 2.063 7.294 1.177 0.445 ms 4.037 30.26
Server Offset SHM(0) -173.605 -142.336 -135.653 -127.246 -121.124 -115.991 -111.134 14.529 26.345 4.426 -127.403 ms -0.85 6.759
TDOP 0.900 1.000 1.110 1.870 3.490 5.210 22.080 2.380 4.210 0.874 2.011 4.028 51.86
Temp /dev/sda 44.000 45.000 45.000 47.000 49.000 51.000 52.000 4.000 6.000 1.425 47.074 °C
Temp /dev/sdb 33.000 33.000 33.000 35.000 38.000 40.000 40.000 5.000 7.000 1.388 35.263 °C
Temp LM0 48.000 49.000 50.000 55.000 58.000 58.000 59.000 8.000 9.000 2.707 54.347 °C
Temp LM1 36.000 36.875 37.250 38.625 45.625 71.750 77.250 8.375 34.875 4.426 39.723 °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 60.000 61.000 61.000 62.000 63.000 63.000 64.000 2.000 2.000 0.549 62.254 °C
Temp LM12 3.000 9.000 16.000 23.000 30.000 34.000 43.000 14.000 25.000 4.070 23.096 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM14 42.000 43.000 43.000 44.000 45.000 45.000 46.000 2.000 2.000 0.553 44.012 °C
Temp LM15 31.000 32.000 33.000 34.000 37.000 60.000 66.000 4.000 28.000 3.297 34.582 °C
Temp LM16 66.000 66.500 67.000 67.500 68.000 68.500 69.500 1.000 2.000 0.394 67.589 °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.000 36.750 37.250 39.250 44.500 71.250 78.000 7.250 34.500 4.257 40.088 °C
Temp LM20 36.000 36.875 37.250 38.625 45.500 71.750 77.125 8.250 34.875 4.418 39.718 °C
Temp LM21 66.000 66.750 67.000 67.750 68.250 68.750 69.500 1.250 2.000 0.367 67.733 °C
Temp LM22 33.000 33.000 33.000 36.000 38.000 40.000 40.000 5.000 7.000 1.353 35.344 °C
Temp LM23 62.850 65.850 66.850 69.850 70.850 70.850 73.850 4.000 5.000 1.191 69.654 °C
Temp LM3 44.000 45.000 45.000 47.000 49.000 51.000 52.000 4.000 6.000 1.415 47.080 °C
Temp LM4 47.850 48.850 48.850 50.850 50.850 52.850 56.850 2.000 4.000 0.746 50.594 °C
Temp LM5 47.850 48.850 48.850 50.850 50.850 52.850 56.850 2.000 4.000 0.744 50.601 °C
Temp LM6 54.850 56.850 56.850 58.850 60.850 65.850 73.850 4.000 9.000 1.747 58.879 °C
Temp LM7 47.850 48.850 49.850 50.850 50.850 52.850 56.850 1.000 4.000 0.735 50.607 °C
Temp LM8 42.000 43.000 43.000 44.000 45.000 45.000 46.000 2.000 2.000 0.552 44.012 °C
Temp LM9 32.000 33.000 33.000 34.500 37.000 45.000 51.500 4.000 12.000 1.979 34.670 °C
nSats 4.000 6.000 7.000 9.000 11.000 12.000 12.000 4.000 6.000 1.334 8.796 nSat 0.09545 3.079
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!