NTPsec

Kong

Report generated: Fri Jun 13 13:59:01 2025 UTC
Start Time: Fri Jun 6 13:59:00 2025 UTC
End Time: Fri Jun 13 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 -4,256.446 -168.658 -59.708 0.170 59.071 179.718 1,396.145 118.779 348.376 102.240 -1.514 µs -19.46 777
Local Clock Frequency Offset 8.085 12.457 12.571 13.079 14.306 14.503 14.594 1.735 2.046 0.553 13.183 ppm 0.07744 8.395

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 4.858 11.926 14.689 28.167 63.081 262.667 1,280.623 48.392 250.741 70.231 37.564 µs 11.51 156.9

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.324 5.046 6.698 15.119 59.934 131.588 1,473.181 53.236 126.542 67.263 25.091 ppb 14.2 239.4

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 -4,256.446 -168.658 -59.708 0.170 59.071 179.718 1,396.145 118.779 348.376 102.240 -1.514 µs -19.46 777

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 8.085 12.457 12.571 13.079 14.306 14.503 14.594 1.735 2.046 0.553 13.183 ppm 0.07744 8.395
Temp /dev/nvme0n1 51.000 51.000 52.000 53.000 55.000 58.000 60.000 3.000 7.000 1.247 53.465 °C
Temp /dev/nvme1n1 64.000 68.000 69.000 72.000 74.000 74.000 76.000 5.000 6.000 1.516 72.046 °C
Temp /dev/sda 48.000 49.000 49.000 52.000 53.000 56.000 57.000 4.000 7.000 1.304 51.514 °C
Temp /dev/sdb 36.000 37.000 38.000 40.000 42.000 45.000 45.000 4.000 8.000 1.484 39.781 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 58.000 59.000 8.000 9.000 2.691 54.150 °C
Temp LM1 40.750 41.000 41.500 43.375 69.500 71.000 87.500 28.000 30.000 10.241 48.754 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.022 25.000 °C
Temp LM11 63.000 63.000 63.000 65.000 66.000 66.000 67.000 3.000 3.000 0.836 64.797 °C
Temp LM12 2.000 4.000 5.000 23.000 30.000 35.000 45.000 25.000 31.000 7.859 20.301 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.070 25.005 °C
Temp LM14 46.000 46.000 46.000 48.000 49.000 50.000 50.000 3.000 4.000 1.014 47.817 °C
Temp LM15 36.000 36.000 37.000 39.000 58.000 60.000 76.000 21.000 24.000 7.555 42.290 °C
Temp LM16 68.000 68.500 68.500 70.000 71.000 71.500 72.500 2.500 3.000 0.713 69.807 °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 40.750 41.000 41.750 44.000 68.750 71.000 85.000 27.000 30.000 9.656 48.835 °C
Temp LM20 40.750 41.000 41.500 43.375 69.500 71.000 87.375 28.000 30.000 10.235 48.741 °C
Temp LM21 68.375 68.750 68.875 70.000 71.250 71.750 72.500 2.375 3.000 0.703 69.942 °C
Temp LM22 37.000 37.000 38.000 40.000 42.000 45.000 45.000 4.000 8.000 1.442 39.937 °C
Temp LM23 63.850 67.850 68.850 71.850 73.850 73.850 75.850 5.000 6.000 1.512 71.927 °C
Temp LM3 48.000 49.000 49.000 52.000 53.000 56.000 57.000 4.000 7.000 1.303 51.519 °C
Temp LM4 50.850 50.850 51.850 52.850 54.850 57.850 59.850 3.000 7.000 1.242 53.294 °C
Temp LM5 50.850 50.850 51.850 52.850 54.850 57.850 59.850 3.000 7.000 1.246 53.319 °C
Temp LM6 58.850 59.850 59.850 61.850 65.850 74.850 78.850 6.000 15.000 2.329 62.309 °C
Temp LM7 50.850 50.850 51.850 52.850 54.850 57.850 59.850 3.000 7.000 1.246 53.317 °C
Temp LM8 46.000 46.000 46.000 48.000 49.000 50.000 50.000 3.000 4.000 1.013 47.817 °C
Temp LM9 36.500 36.500 37.000 39.000 48.500 50.500 57.000 11.500 14.000 3.821 40.490 °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) -4,478.560 -143.030 -73.036 8.689 74.693 202.562 1,220.844 147.729 345.592 134.770 3.607 µs -23.95 761

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) -2,859.124 -931.464 -499.431 -2.480 204.537 439.316 2,829.358 703.968 1,370.780 288.694 -32.019 µs -0.4377 39.63

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 -2.878 -1.317 -0.657 -0.020 0.419 0.752 2.767 1.075 2.069 0.369 -0.051 ms -0.5096 12.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.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 -1,320.058 -198.966 -90.299 -13.231 48.620 126.748 380.116 138.919 325.714 62.992 -17.138 µs -5.641 110.9

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.152 2.928 3.513 5.588 6.623 6.961 7.453 3.110 4.033 1.136 5.097 ms -0.3784 2.315

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) -2.791 0.405 0.689 1.066 1.670 1.984 3.067 0.980 1.579 0.339 1.090 ms -1.093 18.41

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.279 1.867 2.110 2.379 2.645 2.835 3.545 0.535 0.968 0.248 2.373 ms -6.11 87

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

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

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

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



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

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -0.753 1.796 2.204 2.428 2.680 2.779 3.178 0.476 0.983 0.265 2.420 ms -6.241 62.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 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 5.167 10.221 87.949 164.369 197.119 3,450.469 154.148 191.952 114.383 89.242 µs 20.17 513.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 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 3.752 6.581 35.871 133.123 182.035 2,624.187 126.542 178.283 66.284 52.374 µs 19.02 646.4

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 4.963 8.869 94.203 200.634 242.196 2,450.587 191.765 237.233 76.446 92.552 µs 8.395 237.6

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 6.059 11.715 101.404 197.019 247.578 1,345.982 185.304 241.519 74.653 101.298 µs 4.989 68.7

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.188 0.289 1.011 3.766 9.949 26.935 3.478 9.761 1.905 1.487 ms 6.666 71.03

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.170 0.259 0.740 2.674 6.493 13.232 2.415 6.323 1.312 1.104 ms 5.579 45.4

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.087 0.142 0.204 0.498 2.135 6.140 9.762 1.931 5.997 0.980 0.754 ms 5.081 35.6

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.137 0.204 0.498 1.763 7.249 103.170 1.559 7.112 5.764 1.038 ms 17.21 304.4

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 8.085 12.457 12.571 13.079 14.306 14.503 14.594 1.735 2.046 0.553 13.183 ppm 0.07744 8.395
Local Clock Time Offset -4,256.446 -168.658 -59.708 0.170 59.071 179.718 1,396.145 118.779 348.376 102.240 -1.514 µs -19.46 777
Local RMS Frequency Jitter 0.324 5.046 6.698 15.119 59.934 131.588 1,473.181 53.236 126.542 67.263 25.091 ppb 14.2 239.4
Local RMS Time Jitter 4.858 11.926 14.689 28.167 63.081 262.667 1,280.623 48.392 250.741 70.231 37.564 µs 11.51 156.9
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 5.167 10.221 87.949 164.369 197.119 3,450.469 154.148 191.952 114.383 89.242 µs 20.17 513.3
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 3.752 6.581 35.871 133.123 182.035 2,624.187 126.542 178.283 66.284 52.374 µs 19.02 646.4
Server Jitter 204.17.205.1 0.000 4.963 8.869 94.203 200.634 242.196 2,450.587 191.765 237.233 76.446 92.552 µs 8.395 237.6
Server Jitter 204.17.205.30 0.000 6.059 11.715 101.404 197.019 247.578 1,345.982 185.304 241.519 74.653 101.298 µs 4.989 68.7
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.188 0.289 1.011 3.766 9.949 26.935 3.478 9.761 1.905 1.487 ms 6.666 71.03
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.170 0.259 0.740 2.674 6.493 13.232 2.415 6.323 1.312 1.104 ms 5.579 45.4
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.087 0.142 0.204 0.498 2.135 6.140 9.762 1.931 5.997 0.980 0.754 ms 5.081 35.6
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.137 0.204 0.498 1.763 7.249 103.170 1.559 7.112 5.764 1.038 ms 17.21 304.4
Server Offset 2001:470:e815::24 (pi4.rellim.com) -4,478.560 -143.030 -73.036 8.689 74.693 202.562 1,220.844 147.729 345.592 134.770 3.607 µs -23.95 761
Server Offset 2001:470:e815::8 (spidey.rellim.com) -2,859.124 -931.464 -499.431 -2.480 204.537 439.316 2,829.358 703.968 1,370.780 288.694 -32.019 µs -0.4377 39.63
Server Offset 204.17.205.1 -2.878 -1.317 -0.657 -0.020 0.419 0.752 2.767 1.075 2.069 0.369 -0.051 ms -0.5096 12.77
Server Offset 204.17.205.30 -1,320.058 -198.966 -90.299 -13.231 48.620 126.748 380.116 138.919 325.714 62.992 -17.138 µs -5.641 110.9
Server Offset 2405:fc00::1 (robusta.dcs1.biz) 0.152 2.928 3.513 5.588 6.623 6.961 7.453 3.110 4.033 1.136 5.097 ms -0.3784 2.315
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -2.791 0.405 0.689 1.066 1.670 1.984 3.067 0.980 1.579 0.339 1.090 ms -1.093 18.41
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1.279 1.867 2.110 2.379 2.645 2.835 3.545 0.535 0.968 0.248 2.373 ms -6.11 87
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -0.753 1.796 2.204 2.428 2.680 2.779 3.178 0.476 0.983 0.265 2.420 ms -6.241 62.33
Temp /dev/nvme0n1 51.000 51.000 52.000 53.000 55.000 58.000 60.000 3.000 7.000 1.247 53.465 °C
Temp /dev/nvme1n1 64.000 68.000 69.000 72.000 74.000 74.000 76.000 5.000 6.000 1.516 72.046 °C
Temp /dev/sda 48.000 49.000 49.000 52.000 53.000 56.000 57.000 4.000 7.000 1.304 51.514 °C
Temp /dev/sdb 36.000 37.000 38.000 40.000 42.000 45.000 45.000 4.000 8.000 1.484 39.781 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 58.000 59.000 8.000 9.000 2.691 54.150 °C
Temp LM1 40.750 41.000 41.500 43.375 69.500 71.000 87.500 28.000 30.000 10.241 48.754 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.022 25.000 °C
Temp LM11 63.000 63.000 63.000 65.000 66.000 66.000 67.000 3.000 3.000 0.836 64.797 °C
Temp LM12 2.000 4.000 5.000 23.000 30.000 35.000 45.000 25.000 31.000 7.859 20.301 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.070 25.005 °C
Temp LM14 46.000 46.000 46.000 48.000 49.000 50.000 50.000 3.000 4.000 1.014 47.817 °C
Temp LM15 36.000 36.000 37.000 39.000 58.000 60.000 76.000 21.000 24.000 7.555 42.290 °C
Temp LM16 68.000 68.500 68.500 70.000 71.000 71.500 72.500 2.500 3.000 0.713 69.807 °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 40.750 41.000 41.750 44.000 68.750 71.000 85.000 27.000 30.000 9.656 48.835 °C
Temp LM20 40.750 41.000 41.500 43.375 69.500 71.000 87.375 28.000 30.000 10.235 48.741 °C
Temp LM21 68.375 68.750 68.875 70.000 71.250 71.750 72.500 2.375 3.000 0.703 69.942 °C
Temp LM22 37.000 37.000 38.000 40.000 42.000 45.000 45.000 4.000 8.000 1.442 39.937 °C
Temp LM23 63.850 67.850 68.850 71.850 73.850 73.850 75.850 5.000 6.000 1.512 71.927 °C
Temp LM3 48.000 49.000 49.000 52.000 53.000 56.000 57.000 4.000 7.000 1.303 51.519 °C
Temp LM4 50.850 50.850 51.850 52.850 54.850 57.850 59.850 3.000 7.000 1.242 53.294 °C
Temp LM5 50.850 50.850 51.850 52.850 54.850 57.850 59.850 3.000 7.000 1.246 53.319 °C
Temp LM6 58.850 59.850 59.850 61.850 65.850 74.850 78.850 6.000 15.000 2.329 62.309 °C
Temp LM7 50.850 50.850 51.850 52.850 54.850 57.850 59.850 3.000 7.000 1.246 53.317 °C
Temp LM8 46.000 46.000 46.000 48.000 49.000 50.000 50.000 3.000 4.000 1.013 47.817 °C
Temp LM9 36.500 36.500 37.000 39.000 48.500 50.500 57.000 11.500 14.000 3.821 40.490 °C
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!