NTPsec

Kong

Report generated: Wed Apr 8 19:49:00 2026 UTC
Start Time: Tue Apr 7 19:49:00 2026 UTC
End Time: Wed Apr 8 19:49:00 2026 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 -362.733 -282.783 -75.551 -0.741 89.354 264.944 517.599 164.905 547.727 71.912 0.098 µs 1.117 20.89
Local Clock Frequency Offset 12.185 12.193 12.239 12.468 13.762 14.517 14.524 1.522 2.323 0.461 12.597 ppm 2.883 11.44

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 7.660 8.981 11.581 23.610 56.044 102.190 130.057 44.463 93.209 16.577 26.828 µs 2.687 12.96

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 4.868 5.536 6.757 15.479 98.497 136.179 167.903 91.740 130.643 28.401 26.024 ppb 2.578 9.727

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 -362.733 -282.783 -75.551 -0.741 89.354 264.944 517.599 164.905 547.727 71.912 0.098 µs 1.117 20.89

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.185 12.193 12.239 12.468 13.762 14.517 14.524 1.522 2.323 0.461 12.597 ppm 2.883 11.44
Temp /dev/nvme0n1 61.000 61.000 67.000 71.000 72.000 73.000 73.000 5.000 12.000 2.268 70.146 °C
Temp /dev/nvme1n1 46.000 47.000 51.000 54.000 58.000 59.000 60.000 7.000 12.000 2.181 53.976 °C
Temp /dev/sda 47.000 47.000 47.000 50.000 51.000 51.000 51.000 4.000 4.000 1.050 49.300 °C
Temp /dev/sdb 35.000 36.000 36.000 37.000 40.000 40.000 40.000 4.000 4.000 1.323 37.571 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.461 54.024 °C
Temp LM1 39.375 39.500 39.875 43.250 62.625 76.625 78.625 22.750 37.125 7.578 44.602 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.339 25.132 °C
Temp LM11 73.000 73.000 78.000 80.000 81.000 81.000 82.000 3.000 8.000 1.322 80.178 °C
Temp LM12 3.000 9.000 13.000 22.000 34.000 42.000 48.000 21.000 33.000 6.777 22.307 °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 40.000 40.000 41.000 42.000 43.000 45.000 45.000 2.000 5.000 0.843 41.972 °C
Temp LM15 34.000 35.000 35.000 37.000 49.000 65.000 67.000 14.000 30.000 5.999 38.355 °C
Temp LM16 80.500 80.500 87.500 91.000 92.500 92.500 93.000 5.000 12.000 1.905 90.796 °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 39.250 39.500 40.000 42.750 62.250 75.750 77.500 22.250 36.250 7.304 44.493 °C
Temp LM20 39.375 39.500 39.875 43.125 61.250 76.750 78.750 21.375 37.250 7.571 44.589 °C
Temp LM21 80.500 80.500 87.750 91.250 92.500 92.750 93.000 4.750 12.250 1.910 90.949 °C
Temp LM22 36.000 36.000 36.000 37.000 40.000 40.000 40.000 4.000 4.000 1.303 37.596 °C
Temp LM23 60.850 60.850 66.850 70.850 71.850 72.850 72.850 5.000 12.000 2.265 70.031 °C
Temp LM3 47.000 47.000 47.000 50.000 51.000 51.000 51.000 4.000 4.000 1.078 49.314 °C
Temp LM4 46.850 46.850 50.850 53.850 57.850 58.850 59.850 7.000 12.000 2.168 53.801 °C
Temp LM5 46.850 46.850 50.850 53.850 57.850 58.850 58.850 7.000 12.000 2.142 53.801 °C
Temp LM6 54.850 54.850 58.850 61.850 69.850 75.850 76.850 11.000 21.000 3.750 63.247 °C
Temp LM7 46.850 46.850 50.850 53.850 56.850 58.850 59.850 6.000 12.000 2.159 53.801 °C
Temp LM8 40.000 40.000 41.000 42.000 43.000 45.000 45.000 2.000 5.000 0.837 41.976 °C
Temp LM9 35.000 35.500 35.500 37.000 41.500 53.000 53.000 6.000 17.500 3.342 37.882 °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 12.000 12.000 12.000 12.000 12.000 12.000 12.000 0.000 0.000 0.000 12.000 nSat nan nan
TDOP 1.530 1.530 1.530 1.530 1.530 1.530 1.530 0.000 0.000 0.000 1.530 nan nan

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) -388.618 -221.540 -81.349 9.905 106.073 334.258 640.788 187.422 555.798 79.587 11.318 µs 1.807 22.07

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) -528.547 -443.349 -211.885 14.150 173.605 258.241 334.532 385.490 701.590 128.134 -4.922 µs -0.9157 4.702

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 -1,025.941 -697.876 -347.601 76.498 333.616 471.021 496.322 681.217 1,168.897 222.427 32.868 µs -1.082 5.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 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 -339.856 -242.124 -112.157 -14.962 77.965 210.830 451.759 190.122 452.954 68.500 -17.744 µs 0.6665 15.21

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.522 -0.157 0.523 1.011 1.934 2.610 2.752 1.411 2.768 0.440 1.084 ms 0.6277 5.308

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.150 1.073 1.341 1.728 2.458 3.441 3.774 1.117 2.369 0.388 1.787 ms 1.125 9.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 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) 0.752 1.051 1.271 1.664 2.648 3.196 3.309 1.377 2.145 0.390 1.733 ms 1.713 7.419

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) -407.689 -399.617 -396.631 -392.406 -388.484 -386.273 -383.253 8.147 13.344 2.569 -392.471 ms -0.3943 4.856

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) 1.431 3.951 6.902 86.771 173.194 206.254 232.339 166.292 202.303 55.694 82.082 µs 0.2025 1.989

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) 2.035 3.696 5.740 34.021 150.394 194.534 244.496 144.654 190.838 47.100 53.171 µs 1.197 3.854

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 2.678 4.300 7.572 108.684 210.734 255.638 315.494 203.162 251.338 71.098 97.304 µs 0.271 1.994

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 5.116 5.704 7.849 91.362 191.507 224.070 243.733 183.658 218.366 61.134 91.230 µs 0.286 2.003

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.237 0.311 0.526 1.331 11.234 48.779 48.902 10.708 48.468 5.629 2.363 ms 6.643 51.42

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.152 0.251 0.408 1.157 2.179 3.472 4.901 1.771 3.221 0.588 1.212 ms 2.083 12.79

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.092 0.146 0.410 1.108 2.002 11.489 20.439 1.591 11.342 1.938 1.368 ms 7.539 67.47

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.246 0.456 0.648 1.450 3.838 6.806 11.195 3.190 6.350 1.180 1.793 ms 2.519 13.04

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.185 12.193 12.239 12.468 13.762 14.517 14.524 1.522 2.323 0.461 12.597 ppm 2.883 11.44
Local Clock Time Offset -362.733 -282.783 -75.551 -0.741 89.354 264.944 517.599 164.905 547.727 71.912 0.098 µs 1.117 20.89
Local RMS Frequency Jitter 4.868 5.536 6.757 15.479 98.497 136.179 167.903 91.740 130.643 28.401 26.024 ppb 2.578 9.727
Local RMS Time Jitter 7.660 8.981 11.581 23.610 56.044 102.190 130.057 44.463 93.209 16.577 26.828 µs 2.687 12.96
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 1.431 3.951 6.902 86.771 173.194 206.254 232.339 166.292 202.303 55.694 82.082 µs 0.2025 1.989
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 2.035 3.696 5.740 34.021 150.394 194.534 244.496 144.654 190.838 47.100 53.171 µs 1.197 3.854
Server Jitter 204.17.205.1 2.678 4.300 7.572 108.684 210.734 255.638 315.494 203.162 251.338 71.098 97.304 µs 0.271 1.994
Server Jitter 204.17.205.30 5.116 5.704 7.849 91.362 191.507 224.070 243.733 183.658 218.366 61.134 91.230 µs 0.286 2.003
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.237 0.311 0.526 1.331 11.234 48.779 48.902 10.708 48.468 5.629 2.363 ms 6.643 51.42
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.152 0.251 0.408 1.157 2.179 3.472 4.901 1.771 3.221 0.588 1.212 ms 2.083 12.79
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.092 0.146 0.410 1.108 2.002 11.489 20.439 1.591 11.342 1.938 1.368 ms 7.539 67.47
Server Jitter SHM(0) 0.246 0.456 0.648 1.450 3.838 6.806 11.195 3.190 6.350 1.180 1.793 ms 2.519 13.04
Server Offset 2001:470:e815::24 (pi4.rellim.com) -388.618 -221.540 -81.349 9.905 106.073 334.258 640.788 187.422 555.798 79.587 11.318 µs 1.807 22.07
Server Offset 2001:470:e815::8 (spidey.rellim.com) -528.547 -443.349 -211.885 14.150 173.605 258.241 334.532 385.490 701.590 128.134 -4.922 µs -0.9157 4.702
Server Offset 204.17.205.1 -1,025.941 -697.876 -347.601 76.498 333.616 471.021 496.322 681.217 1,168.897 222.427 32.868 µs -1.082 5.34
Server Offset 204.17.205.30 -339.856 -242.124 -112.157 -14.962 77.965 210.830 451.759 190.122 452.954 68.500 -17.744 µs 0.6665 15.21
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -0.522 -0.157 0.523 1.011 1.934 2.610 2.752 1.411 2.768 0.440 1.084 ms 0.6277 5.308
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.150 1.073 1.341 1.728 2.458 3.441 3.774 1.117 2.369 0.388 1.787 ms 1.125 9.26
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 0.752 1.051 1.271 1.664 2.648 3.196 3.309 1.377 2.145 0.390 1.733 ms 1.713 7.419
Server Offset SHM(0) -407.689 -399.617 -396.631 -392.406 -388.484 -386.273 -383.253 8.147 13.344 2.569 -392.471 ms -0.3943 4.856
TDOP 1.530 1.530 1.530 1.530 1.530 1.530 1.530 0.000 0.000 0.000 1.530 nan nan
Temp /dev/nvme0n1 61.000 61.000 67.000 71.000 72.000 73.000 73.000 5.000 12.000 2.268 70.146 °C
Temp /dev/nvme1n1 46.000 47.000 51.000 54.000 58.000 59.000 60.000 7.000 12.000 2.181 53.976 °C
Temp /dev/sda 47.000 47.000 47.000 50.000 51.000 51.000 51.000 4.000 4.000 1.050 49.300 °C
Temp /dev/sdb 35.000 36.000 36.000 37.000 40.000 40.000 40.000 4.000 4.000 1.323 37.571 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.461 54.024 °C
Temp LM1 39.375 39.500 39.875 43.250 62.625 76.625 78.625 22.750 37.125 7.578 44.602 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.339 25.132 °C
Temp LM11 73.000 73.000 78.000 80.000 81.000 81.000 82.000 3.000 8.000 1.322 80.178 °C
Temp LM12 3.000 9.000 13.000 22.000 34.000 42.000 48.000 21.000 33.000 6.777 22.307 °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 40.000 40.000 41.000 42.000 43.000 45.000 45.000 2.000 5.000 0.843 41.972 °C
Temp LM15 34.000 35.000 35.000 37.000 49.000 65.000 67.000 14.000 30.000 5.999 38.355 °C
Temp LM16 80.500 80.500 87.500 91.000 92.500 92.500 93.000 5.000 12.000 1.905 90.796 °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 39.250 39.500 40.000 42.750 62.250 75.750 77.500 22.250 36.250 7.304 44.493 °C
Temp LM20 39.375 39.500 39.875 43.125 61.250 76.750 78.750 21.375 37.250 7.571 44.589 °C
Temp LM21 80.500 80.500 87.750 91.250 92.500 92.750 93.000 4.750 12.250 1.910 90.949 °C
Temp LM22 36.000 36.000 36.000 37.000 40.000 40.000 40.000 4.000 4.000 1.303 37.596 °C
Temp LM23 60.850 60.850 66.850 70.850 71.850 72.850 72.850 5.000 12.000 2.265 70.031 °C
Temp LM3 47.000 47.000 47.000 50.000 51.000 51.000 51.000 4.000 4.000 1.078 49.314 °C
Temp LM4 46.850 46.850 50.850 53.850 57.850 58.850 59.850 7.000 12.000 2.168 53.801 °C
Temp LM5 46.850 46.850 50.850 53.850 57.850 58.850 58.850 7.000 12.000 2.142 53.801 °C
Temp LM6 54.850 54.850 58.850 61.850 69.850 75.850 76.850 11.000 21.000 3.750 63.247 °C
Temp LM7 46.850 46.850 50.850 53.850 56.850 58.850 59.850 6.000 12.000 2.159 53.801 °C
Temp LM8 40.000 40.000 41.000 42.000 43.000 45.000 45.000 2.000 5.000 0.837 41.976 °C
Temp LM9 35.000 35.500 35.500 37.000 41.500 53.000 53.000 6.000 17.500 3.342 37.882 °C
nSats 12.000 12.000 12.000 12.000 12.000 12.000 12.000 0.000 0.000 0.000 12.000 nSat nan nan
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!