NTPsec

Kong

Report generated: Sat Jun 14 03:49:01 2025 UTC
Start Time: Fri Jun 13 03:49:00 2025 UTC
End Time: Sat Jun 14 03:49:00 2025 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 -221.909 -129.948 -60.705 0.290 59.837 228.550 323.443 120.542 358.498 47.416 1.004 µs 1.422 13.74
Local Clock Frequency Offset 12.567 12.580 12.600 12.755 13.197 13.351 13.394 0.597 0.770 0.168 12.793 ppm 1.496 5.122

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 11.513 12.706 15.703 28.267 56.003 67.160 74.942 40.300 54.454 11.819 30.843 µs 1.107 4.171

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 1.856 5.944 7.503 15.627 50.032 87.919 112.258 42.529 81.975 15.348 20.091 ppb 2.749 12.19

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 -221.909 -129.948 -60.705 0.290 59.837 228.550 323.443 120.542 358.498 47.416 1.004 µs 1.422 13.74

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 12.567 12.580 12.600 12.755 13.197 13.351 13.394 0.597 0.770 0.168 12.793 ppm 1.496 5.122
Temp /dev/nvme0n1 50.000 51.000 51.000 53.000 54.000 57.000 59.000 3.000 6.000 0.967 52.625 °C
Temp /dev/nvme1n1 64.000 65.000 68.000 71.000 73.000 73.000 73.000 5.000 8.000 1.658 71.066 °C
Temp /dev/sda 48.000 48.000 49.000 51.000 51.000 51.000 51.000 2.000 3.000 0.798 50.375 °C
Temp /dev/sdb 37.000 37.000 38.000 39.000 40.000 41.000 41.000 2.000 4.000 0.855 38.809 °C
Temp LM0 48.000 49.000 50.000 53.000 58.000 58.000 59.000 8.000 9.000 2.968 53.535 °C
Temp LM1 41.250 41.250 41.500 42.375 49.125 63.500 66.000 7.625 22.250 3.368 43.382 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.059 25.003 °C
Temp LM11 63.000 63.000 64.000 64.000 65.000 65.000 65.000 1.000 2.000 0.464 64.146 °C
Temp LM12 4.000 6.000 17.000 24.000 32.000 38.000 38.000 15.000 32.000 4.447 23.896 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.059 25.003 °C
Temp LM14 46.000 46.000 46.000 47.000 48.000 48.000 48.000 2.000 2.000 0.529 46.962 °C
Temp LM15 36.000 36.000 37.000 38.000 42.000 52.000 54.000 5.000 16.000 2.243 38.042 °C
Temp LM16 68.500 68.500 69.000 69.000 69.500 70.000 70.000 0.500 1.500 0.312 69.243 °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 41.000 41.250 41.500 42.750 48.250 64.000 69.000 6.750 22.750 3.340 43.691 °C
Temp LM20 41.250 41.250 41.500 42.375 49.250 63.500 65.875 7.750 22.250 3.356 43.366 °C
Temp LM21 68.500 68.625 69.000 69.375 69.875 70.000 70.000 0.875 1.375 0.305 69.376 °C
Temp LM22 38.000 38.000 38.000 39.000 40.000 41.000 41.000 2.000 3.000 0.762 38.944 °C
Temp LM23 63.850 64.850 67.850 71.850 72.850 72.850 72.850 5.000 8.000 1.665 70.968 °C
Temp LM3 48.000 48.000 49.000 51.000 51.000 51.000 51.000 2.000 3.000 0.805 50.361 °C
Temp LM4 49.850 50.850 50.850 52.850 53.850 56.850 58.850 3.000 6.000 0.989 52.437 °C
Temp LM5 49.850 50.850 50.850 52.850 53.850 56.850 57.850 3.000 6.000 0.937 52.485 °C
Temp LM6 57.850 57.850 59.850 60.850 63.850 74.850 75.850 4.000 17.000 2.287 61.187 °C
Temp LM7 49.850 50.850 50.850 52.850 53.850 56.850 57.850 3.000 6.000 0.955 52.485 °C
Temp LM8 46.000 46.000 46.000 47.000 48.000 48.000 48.000 2.000 2.000 0.535 46.962 °C
Temp LM9 37.000 37.000 37.000 38.000 41.500 43.500 45.000 4.500 6.500 1.310 38.111 °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.



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) -195.154 -127.249 -83.078 4.306 73.096 272.479 370.370 156.174 399.728 57.878 4.685 µs 1.535 11.48

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) -466.238 -368.454 -187.642 43.182 124.510 141.712 164.701 312.152 510.166 98.419 16.456 µs -1.736 6.628

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 -440.659 -343.312 -211.255 0.637 265.732 392.626 413.891 476.987 735.938 170.989 24.270 µs 0.1353 2.125

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 -247.946 -151.614 -90.576 -5.697 53.006 167.410 251.095 143.582 319.024 48.497 -11.649 µs 0.2739 9.34

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) 4.635 5.497 5.951 6.494 7.140 7.563 7.749 1.189 2.066 0.391 6.485 ms -0.2465 5.777

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.241 0.255 0.354 0.884 1.258 1.424 1.732 0.903 1.169 0.272 0.872 ms -0.2528 2.689

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.564 1.620 1.806 2.288 2.612 2.762 2.829 0.806 1.142 0.257 2.250 ms -0.3413 2.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 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.998 2.068 2.195 2.474 2.807 2.876 3.542 0.612 0.808 0.203 2.482 ms 1.197 8.259

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 6.429 17.654 76.980 138.980 165.555 202.829 121.326 159.126 37.475 77.054 µs 0.2677 2.695

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 5.604 11.656 38.549 134.334 171.045 199.212 122.678 165.441 40.615 54.388 µs 1.326 3.779

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.975 19.394 63.516 168.709 206.820 228.380 149.315 197.845 52.025 81.422 µs 0.5015 2.14

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 5.889 19.901 91.017 167.479 248.412 260.795 147.578 242.523 47.759 90.670 µs 0.6072 3.676

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.147 0.252 0.772 3.438 7.018 26.935 3.186 6.871 1.898 1.217 ms 9.363 121

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.164 0.252 0.581 3.055 4.304 9.120 2.803 4.140 1.008 0.967 ms 3.351 20.17

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.140 0.181 0.282 0.538 2.867 6.098 6.140 2.585 5.917 0.926 0.831 ms 3.664 18.38

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.138 0.245 0.499 2.143 2.464 6.541 1.897 2.325 0.772 0.753 ms 4.248 29.11

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 12.567 12.580 12.600 12.755 13.197 13.351 13.394 0.597 0.770 0.168 12.793 ppm 1.496 5.122
Local Clock Time Offset -221.909 -129.948 -60.705 0.290 59.837 228.550 323.443 120.542 358.498 47.416 1.004 µs 1.422 13.74
Local RMS Frequency Jitter 1.856 5.944 7.503 15.627 50.032 87.919 112.258 42.529 81.975 15.348 20.091 ppb 2.749 12.19
Local RMS Time Jitter 11.513 12.706 15.703 28.267 56.003 67.160 74.942 40.300 54.454 11.819 30.843 µs 1.107 4.171
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 6.429 17.654 76.980 138.980 165.555 202.829 121.326 159.126 37.475 77.054 µs 0.2677 2.695
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 5.604 11.656 38.549 134.334 171.045 199.212 122.678 165.441 40.615 54.388 µs 1.326 3.779
Server Jitter 204.17.205.1 0.000 8.975 19.394 63.516 168.709 206.820 228.380 149.315 197.845 52.025 81.422 µs 0.5015 2.14
Server Jitter 204.17.205.30 0.000 5.889 19.901 91.017 167.479 248.412 260.795 147.578 242.523 47.759 90.670 µs 0.6072 3.676
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.147 0.252 0.772 3.438 7.018 26.935 3.186 6.871 1.898 1.217 ms 9.363 121
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.164 0.252 0.581 3.055 4.304 9.120 2.803 4.140 1.008 0.967 ms 3.351 20.17
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.140 0.181 0.282 0.538 2.867 6.098 6.140 2.585 5.917 0.926 0.831 ms 3.664 18.38
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.138 0.245 0.499 2.143 2.464 6.541 1.897 2.325 0.772 0.753 ms 4.248 29.11
Server Offset 2001:470:e815::24 (pi4.rellim.com) -195.154 -127.249 -83.078 4.306 73.096 272.479 370.370 156.174 399.728 57.878 4.685 µs 1.535 11.48
Server Offset 2001:470:e815::8 (spidey.rellim.com) -466.238 -368.454 -187.642 43.182 124.510 141.712 164.701 312.152 510.166 98.419 16.456 µs -1.736 6.628
Server Offset 204.17.205.1 -440.659 -343.312 -211.255 0.637 265.732 392.626 413.891 476.987 735.938 170.989 24.270 µs 0.1353 2.125
Server Offset 204.17.205.30 -247.946 -151.614 -90.576 -5.697 53.006 167.410 251.095 143.582 319.024 48.497 -11.649 µs 0.2739 9.34
Server Offset 2405:fc00::1 (robusta.dcs1.biz) 4.635 5.497 5.951 6.494 7.140 7.563 7.749 1.189 2.066 0.391 6.485 ms -0.2465 5.777
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.241 0.255 0.354 0.884 1.258 1.424 1.732 0.903 1.169 0.272 0.872 ms -0.2528 2.689
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 1.564 1.620 1.806 2.288 2.612 2.762 2.829 0.806 1.142 0.257 2.250 ms -0.3413 2.638
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 1.998 2.068 2.195 2.474 2.807 2.876 3.542 0.612 0.808 0.203 2.482 ms 1.197 8.259
Temp /dev/nvme0n1 50.000 51.000 51.000 53.000 54.000 57.000 59.000 3.000 6.000 0.967 52.625 °C
Temp /dev/nvme1n1 64.000 65.000 68.000 71.000 73.000 73.000 73.000 5.000 8.000 1.658 71.066 °C
Temp /dev/sda 48.000 48.000 49.000 51.000 51.000 51.000 51.000 2.000 3.000 0.798 50.375 °C
Temp /dev/sdb 37.000 37.000 38.000 39.000 40.000 41.000 41.000 2.000 4.000 0.855 38.809 °C
Temp LM0 48.000 49.000 50.000 53.000 58.000 58.000 59.000 8.000 9.000 2.968 53.535 °C
Temp LM1 41.250 41.250 41.500 42.375 49.125 63.500 66.000 7.625 22.250 3.368 43.382 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.059 25.003 °C
Temp LM11 63.000 63.000 64.000 64.000 65.000 65.000 65.000 1.000 2.000 0.464 64.146 °C
Temp LM12 4.000 6.000 17.000 24.000 32.000 38.000 38.000 15.000 32.000 4.447 23.896 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.059 25.003 °C
Temp LM14 46.000 46.000 46.000 47.000 48.000 48.000 48.000 2.000 2.000 0.529 46.962 °C
Temp LM15 36.000 36.000 37.000 38.000 42.000 52.000 54.000 5.000 16.000 2.243 38.042 °C
Temp LM16 68.500 68.500 69.000 69.000 69.500 70.000 70.000 0.500 1.500 0.312 69.243 °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 41.000 41.250 41.500 42.750 48.250 64.000 69.000 6.750 22.750 3.340 43.691 °C
Temp LM20 41.250 41.250 41.500 42.375 49.250 63.500 65.875 7.750 22.250 3.356 43.366 °C
Temp LM21 68.500 68.625 69.000 69.375 69.875 70.000 70.000 0.875 1.375 0.305 69.376 °C
Temp LM22 38.000 38.000 38.000 39.000 40.000 41.000 41.000 2.000 3.000 0.762 38.944 °C
Temp LM23 63.850 64.850 67.850 71.850 72.850 72.850 72.850 5.000 8.000 1.665 70.968 °C
Temp LM3 48.000 48.000 49.000 51.000 51.000 51.000 51.000 2.000 3.000 0.805 50.361 °C
Temp LM4 49.850 50.850 50.850 52.850 53.850 56.850 58.850 3.000 6.000 0.989 52.437 °C
Temp LM5 49.850 50.850 50.850 52.850 53.850 56.850 57.850 3.000 6.000 0.937 52.485 °C
Temp LM6 57.850 57.850 59.850 60.850 63.850 74.850 75.850 4.000 17.000 2.287 61.187 °C
Temp LM7 49.850 50.850 50.850 52.850 53.850 56.850 57.850 3.000 6.000 0.955 52.485 °C
Temp LM8 46.000 46.000 46.000 47.000 48.000 48.000 48.000 2.000 2.000 0.535 46.962 °C
Temp LM9 37.000 37.000 37.000 38.000 41.500 43.500 45.000 4.500 6.500 1.310 38.111 °C
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.
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!