NTPsec

Kong

Report generated: Wed Apr 2 13:59:01 2025 UTC
Start Time: Wed Mar 26 13:59:00 2025 UTC
End Time: Wed Apr 2 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.473 -0.080 -0.000 0.077 0.329 5.021 0.158 0.802 0.340 -0.006 ms -2.685 144.4
Local Clock Frequency Offset 10.653 11.287 11.339 11.451 11.851 12.697 13.449 0.511 1.410 0.229 11.504 ppm 4.448 31.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.012 0.018 0.024 0.043 0.088 2.102 4.312 0.064 2.084 0.307 0.088 ms 8.63 86.21

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.660 12.385 23.004 86.810 244.965 389.341 74.425 235.305 38.793 32.522 ppb 5.332 36.77

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.473 -0.080 -0.000 0.077 0.329 5.021 0.158 0.802 0.340 -0.006 ms -2.685 144.4

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.287 11.339 11.451 11.851 12.697 13.449 0.511 1.410 0.229 11.504 ppm 4.448 31.06
Temp /dev/sda 44.000 45.000 45.000 47.000 49.000 50.000 51.000 4.000 5.000 1.350 47.214 °C
Temp /dev/sdb 33.000 33.000 33.000 36.000 38.000 39.000 40.000 5.000 6.000 1.305 35.406 °C
Temp LM0 48.000 49.000 50.000 55.000 58.000 58.000 59.000 8.000 9.000 2.704 54.345 °C
Temp LM1 36.000 36.875 37.375 38.875 45.250 68.500 76.125 7.875 31.625 4.380 39.832 °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 62.000 62.000 63.000 64.000 65.000 1.000 3.000 0.590 62.368 °C
Temp LM12 3.000 9.000 17.000 23.000 30.000 35.000 43.000 13.000 26.000 4.076 23.180 °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 46.000 47.000 2.000 3.000 0.669 44.194 °C
Temp LM15 31.000 32.000 33.000 34.000 37.000 57.000 65.000 4.000 25.000 3.273 34.718 °C
Temp LM16 66.000 66.500 67.000 67.500 68.500 69.000 69.500 1.500 2.500 0.447 67.691 °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.500 39.250 44.500 69.000 77.000 7.000 32.250 4.175 40.212 °C
Temp LM20 36.000 36.875 37.375 38.875 45.250 68.500 76.125 7.875 31.625 4.378 39.829 °C
Temp LM21 66.000 66.750 67.125 67.750 68.500 69.000 69.750 1.375 2.250 0.426 67.834 °C
Temp LM22 33.000 33.000 33.000 36.000 38.000 39.000 40.000 5.000 6.000 1.276 35.487 °C
Temp LM23 63.850 65.850 67.850 69.850 70.850 71.850 73.850 3.000 6.000 1.171 69.779 °C
Temp LM3 44.000 45.000 45.000 47.000 49.000 50.000 51.000 4.000 5.000 1.341 47.219 °C
Temp LM4 47.850 48.850 49.850 50.850 51.850 53.850 56.850 2.000 5.000 0.800 50.705 °C
Temp LM5 47.850 48.850 49.850 50.850 51.850 53.850 56.850 2.000 5.000 0.794 50.711 °C
Temp LM6 55.850 56.850 56.850 58.850 61.850 68.850 74.850 5.000 12.000 1.884 59.080 °C
Temp LM7 47.850 48.850 49.850 50.850 51.850 53.850 56.850 2.000 5.000 0.782 50.716 °C
Temp LM8 42.000 43.000 43.000 44.000 45.000 46.000 47.000 2.000 3.000 0.664 44.193 °C
Temp LM9 32.000 33.000 33.000 34.500 37.000 44.000 51.500 4.000 11.000 1.939 34.806 °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 12.000 13.000 14.000 5.000 7.000 1.702 9.312 nSat 0.1594 2.819
TDOP 0.730 0.870 1.040 1.650 3.470 5.110 87.840 2.430 4.240 1.748 1.889 31.12 1291

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.759 -0.163 -0.094 -0.006 0.072 0.173 36.356 0.166 0.336 0.639 0.005 ms 54.85 3108

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.298 -1.701 0.088 1.455 6.873 8.582 3.155 11.171 1.357 0.099 ms 2.015 16.77

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.056 1.487 6.456 8.517 3.217 10.873 1.345 0.082 ms 1.491 15.24

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 16.736 111.639 585.529 4,558.628 195.244 1,443.295 326.556 21.054 µs 4.374 85.03

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.429 1.793 3.945 4.973 7.603 15.087 3.180 6.175 1.336 3.552 ms 1.514 12.29

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.531 0.171 0.655 5.245 1.321 4.780 0.829 -0.554 ms -5.054 55.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 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.658 -0.443 0.479 1.069 1.360 1.677 1.513 2.018 0.408 0.450 ms -0.5599 4.005

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.197 -0.975 0.544 1.151 8.062 10.139 2.126 9.259 1.240 0.411 ms 3.951 27.97

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) -178.505 -144.201 -139.219 -127.723 -121.258 -115.991 -111.134 17.962 28.210 5.094 -128.132 ms -1.063 6.674

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.009 0.025 0.103 0.171 0.198 23.361 0.146 0.189 0.631 0.120 ms 34.1 1185

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 9.271 27.624 120.231 215.120 279.568 510.220 187.496 270.297 63.313 117.336 µs 0.5452 4.216

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 10.905 26.747 120.459 220.754 293.784 749.638 194.007 282.879 64.671 120.703 µs 0.7558 6.539

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.017 0.032 0.122 0.243 1.859 4.557 0.211 1.842 0.307 0.165 ms 7.872 75.43

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.233 0.383 1.179 3.384 8.034 50.086 3.000 7.801 2.272 1.555 ms 13.44 256.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.238 0.369 1.050 3.353 7.794 63.726 2.984 7.556 3.240 1.502 ms 14.96 265.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 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.200 0.294 0.642 2.743 19.440 53.294 2.450 19.240 4.234 1.294 ms 10.55 123

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.103 0.176 0.255 0.550 2.772 4.958 14.430 2.517 4.782 1.043 0.864 ms 5.499 51.67

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.280 0.406 1.144 8.404 11.273 40.210 7.998 10.993 2.720 2.334 ms 2.398 12.93

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.287 11.339 11.451 11.851 12.697 13.449 0.511 1.410 0.229 11.504 ppm 4.448 31.06
Local Clock Time Offset -6.387 -0.473 -0.080 -0.000 0.077 0.329 5.021 0.158 0.802 0.340 -0.006 ms -2.685 144.4
Local RMS Frequency Jitter 3.814 9.660 12.385 23.004 86.810 244.965 389.341 74.425 235.305 38.793 32.522 ppb 5.332 36.77
Local RMS Time Jitter 0.012 0.018 0.024 0.043 0.088 2.102 4.312 0.064 2.084 0.307 0.088 ms 8.63 86.21
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.009 0.025 0.103 0.171 0.198 23.361 0.146 0.189 0.631 0.120 ms 34.1 1185
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 9.271 27.624 120.231 215.120 279.568 510.220 187.496 270.297 63.313 117.336 µs 0.5452 4.216
Server Jitter 204.17.205.1 0.000 10.905 26.747 120.459 220.754 293.784 749.638 194.007 282.879 64.671 120.703 µs 0.7558 6.539
Server Jitter 204.17.205.30 0.000 0.017 0.032 0.122 0.243 1.859 4.557 0.211 1.842 0.307 0.165 ms 7.872 75.43
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.233 0.383 1.179 3.384 8.034 50.086 3.000 7.801 2.272 1.555 ms 13.44 256.5
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.238 0.369 1.050 3.353 7.794 63.726 2.984 7.556 3.240 1.502 ms 14.96 265.5
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.200 0.294 0.642 2.743 19.440 53.294 2.450 19.240 4.234 1.294 ms 10.55 123
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.103 0.176 0.255 0.550 2.772 4.958 14.430 2.517 4.782 1.043 0.864 ms 5.499 51.67
Server Jitter SHM(0) 0.000 0.280 0.406 1.144 8.404 11.273 40.210 7.998 10.993 2.720 2.334 ms 2.398 12.93
Server Offset 2001:470:e815::24 (pi4.rellim.com) -0.759 -0.163 -0.094 -0.006 0.072 0.173 36.356 0.166 0.336 0.639 0.005 ms 54.85 3108
Server Offset 2001:470:e815::8 (spidey.rellim.com) -5.023 -4.298 -1.701 0.088 1.455 6.873 8.582 3.155 11.171 1.357 0.099 ms 2.015 16.77
Server Offset 204.17.205.1 -5.429 -4.417 -1.730 0.056 1.487 6.456 8.517 3.217 10.873 1.345 0.082 ms 1.491 15.24
Server Offset 204.17.205.30 -2,894.975 -857.766 -83.605 16.736 111.639 585.529 4,558.628 195.244 1,443.295 326.556 21.054 µs 4.374 85.03
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -0.364 1.429 1.793 3.945 4.973 7.603 15.087 3.180 6.175 1.336 3.552 ms 1.514 12.29
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -11.274 -4.125 -1.150 -0.531 0.171 0.655 5.245 1.321 4.780 0.829 -0.554 ms -5.054 55.08
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1.120 -0.658 -0.443 0.479 1.069 1.360 1.677 1.513 2.018 0.408 0.450 ms -0.5599 4.005
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -1.719 -1.197 -0.975 0.544 1.151 8.062 10.139 2.126 9.259 1.240 0.411 ms 3.951 27.97
Server Offset SHM(0) -178.505 -144.201 -139.219 -127.723 -121.258 -115.991 -111.134 17.962 28.210 5.094 -128.132 ms -1.063 6.674
TDOP 0.730 0.870 1.040 1.650 3.470 5.110 87.840 2.430 4.240 1.748 1.889 31.12 1291
Temp /dev/sda 44.000 45.000 45.000 47.000 49.000 50.000 51.000 4.000 5.000 1.350 47.214 °C
Temp /dev/sdb 33.000 33.000 33.000 36.000 38.000 39.000 40.000 5.000 6.000 1.305 35.406 °C
Temp LM0 48.000 49.000 50.000 55.000 58.000 58.000 59.000 8.000 9.000 2.704 54.345 °C
Temp LM1 36.000 36.875 37.375 38.875 45.250 68.500 76.125 7.875 31.625 4.380 39.832 °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 62.000 62.000 63.000 64.000 65.000 1.000 3.000 0.590 62.368 °C
Temp LM12 3.000 9.000 17.000 23.000 30.000 35.000 43.000 13.000 26.000 4.076 23.180 °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 46.000 47.000 2.000 3.000 0.669 44.194 °C
Temp LM15 31.000 32.000 33.000 34.000 37.000 57.000 65.000 4.000 25.000 3.273 34.718 °C
Temp LM16 66.000 66.500 67.000 67.500 68.500 69.000 69.500 1.500 2.500 0.447 67.691 °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.500 39.250 44.500 69.000 77.000 7.000 32.250 4.175 40.212 °C
Temp LM20 36.000 36.875 37.375 38.875 45.250 68.500 76.125 7.875 31.625 4.378 39.829 °C
Temp LM21 66.000 66.750 67.125 67.750 68.500 69.000 69.750 1.375 2.250 0.426 67.834 °C
Temp LM22 33.000 33.000 33.000 36.000 38.000 39.000 40.000 5.000 6.000 1.276 35.487 °C
Temp LM23 63.850 65.850 67.850 69.850 70.850 71.850 73.850 3.000 6.000 1.171 69.779 °C
Temp LM3 44.000 45.000 45.000 47.000 49.000 50.000 51.000 4.000 5.000 1.341 47.219 °C
Temp LM4 47.850 48.850 49.850 50.850 51.850 53.850 56.850 2.000 5.000 0.800 50.705 °C
Temp LM5 47.850 48.850 49.850 50.850 51.850 53.850 56.850 2.000 5.000 0.794 50.711 °C
Temp LM6 55.850 56.850 56.850 58.850 61.850 68.850 74.850 5.000 12.000 1.884 59.080 °C
Temp LM7 47.850 48.850 49.850 50.850 51.850 53.850 56.850 2.000 5.000 0.782 50.716 °C
Temp LM8 42.000 43.000 43.000 44.000 45.000 46.000 47.000 2.000 3.000 0.664 44.193 °C
Temp LM9 32.000 33.000 33.000 34.500 37.000 44.000 51.500 4.000 11.000 1.939 34.806 °C
nSats 4.000 6.000 7.000 9.000 12.000 13.000 14.000 5.000 7.000 1.702 9.312 nSat 0.1594 2.819
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!