NTPsec

Kong

Report generated: Fri Apr 10 08:49:01 2026 UTC
Start Time: Thu Apr 9 08:49:00 2026 UTC
End Time: Fri Apr 10 08: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 -550.584 -231.618 -73.246 -3.078 68.057 219.871 385.966 141.303 451.489 68.907 -3.752 µs -1.49 24.92
Local Clock Frequency Offset 12.209 12.218 12.284 12.472 13.157 14.418 14.539 0.873 2.200 0.380 12.589 ppm 2.864 12.8

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 5.885 6.902 9.411 25.534 61.378 95.584 117.209 51.967 88.682 17.053 29.311 µs 1.769 7.6

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.299 3.848 5.680 17.019 99.414 178.181 207.269 93.734 174.333 31.418 25.757 ppb 3.487 15.69

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 -550.584 -231.618 -73.246 -3.078 68.057 219.871 385.966 141.303 451.489 68.907 -3.752 µs -1.49 24.92

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.209 12.218 12.284 12.472 13.157 14.418 14.539 0.873 2.200 0.380 12.589 ppm 2.864 12.8
Temp /dev/nvme0n1 61.000 61.000 63.000 71.000 72.000 73.000 74.000 9.000 12.000 2.746 69.733 °C
Temp /dev/nvme1n1 47.000 47.000 50.000 55.000 58.000 59.000 60.000 8.000 12.000 2.396 54.264 °C
Temp /dev/sda 46.000 46.000 47.000 49.000 50.000 50.000 50.000 3.000 4.000 1.332 48.726 °C
Temp /dev/sdb 35.000 35.000 35.000 37.000 40.000 40.000 41.000 5.000 5.000 1.506 37.125 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.488 53.868 °C
Temp LM1 39.500 39.625 40.000 43.375 62.000 77.375 81.000 22.000 37.750 7.297 44.722 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.248 25.066 °C
Temp LM11 73.000 73.000 77.000 80.000 81.000 82.000 82.000 4.000 9.000 1.551 79.920 °C
Temp LM12 3.000 6.000 15.000 23.000 40.000 45.000 54.000 25.000 39.000 7.581 24.153 °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.937 42.215 °C
Temp LM15 35.000 35.000 36.000 37.000 51.000 66.000 70.000 15.000 31.000 5.742 38.271 °C
Temp LM16 81.000 81.500 85.000 91.000 92.500 93.000 93.000 7.500 11.500 2.309 90.398 °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.500 39.750 40.000 42.000 55.500 76.750 80.750 15.500 37.000 6.792 44.078 °C
Temp LM20 39.500 39.625 40.000 43.375 62.250 77.250 81.000 22.250 37.625 7.319 44.724 °C
Temp LM21 81.375 81.625 85.375 91.250 92.500 93.000 93.000 7.125 11.375 2.295 90.547 °C
Temp LM22 35.000 35.000 35.000 37.000 40.000 40.000 40.000 5.000 5.000 1.504 37.184 °C
Temp LM23 60.850 60.850 63.850 70.850 71.850 72.850 73.850 8.000 12.000 2.748 69.558 °C
Temp LM3 46.000 46.000 47.000 49.000 50.000 50.000 51.000 3.000 4.000 1.338 48.726 °C
Temp LM4 46.850 46.850 49.850 54.850 57.850 58.850 59.850 8.000 12.000 2.400 54.117 °C
Temp LM5 46.850 46.850 49.850 54.850 56.850 58.850 59.850 7.000 12.000 2.381 54.138 °C
Temp LM6 54.850 54.850 57.850 61.850 69.850 73.850 76.850 12.000 19.000 4.322 64.152 °C
Temp LM7 46.850 46.850 49.850 54.850 57.850 58.850 59.850 8.000 12.000 2.407 54.138 °C
Temp LM8 40.000 40.000 41.000 42.000 43.000 45.000 45.000 2.000 5.000 0.937 42.205 °C
Temp LM9 35.500 35.500 36.000 37.000 41.500 53.500 53.500 5.500 18.000 3.101 37.722 °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) -567.881 -316.154 -76.609 6.639 91.566 274.209 428.044 168.175 590.363 75.716 7.262 µs -1.167 23.54

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) -763.894 -357.476 -224.382 -4.925 140.060 184.536 207.051 364.442 542.012 121.164 -29.297 µs -1.583 9.263

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 -699.875 -471.712 -391.903 -35.022 183.546 219.216 245.668 575.449 690.928 166.051 -66.833 µs -0.6172 3.241

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 -507.194 -464.181 -88.461 -15.531 56.930 292.444 377.131 145.391 756.625 81.610 -18.885 µs -1.424 18.7

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.228 0.530 0.855 1.308 1.760 2.084 2.127 0.905 1.554 0.284 1.304 ms -0.05525 4.106

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.873 1.115 1.354 1.730 2.162 2.999 3.029 0.807 1.884 0.302 1.752 ms 1.379 7.475

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.128 1.210 1.304 1.615 1.979 2.121 2.724 0.675 0.911 0.207 1.630 ms 0.5955 5.043

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) -406.586 -399.681 -396.529 -392.240 -388.440 -386.896 -383.234 8.089 12.785 2.572 -392.367 ms -0.4744 4.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 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) 5.353 7.250 13.129 97.116 168.800 183.627 417.120 155.671 176.377 48.519 92.983 µs 0.3615 5.238

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) 1.820 4.996 8.345 41.808 153.372 197.748 280.656 145.027 192.752 48.205 61.803 µs 0.979 3.335

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 1.933 4.641 9.907 113.469 197.937 225.673 261.177 188.030 221.032 62.430 104.317 µs -0.05303 1.88

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 10.439 12.698 22.113 113.805 212.904 251.690 345.507 190.791 238.992 57.917 109.901 µs 0.3206 3.165

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.239 0.290 0.474 1.205 3.711 24.336 29.042 3.237 24.046 3.890 2.017 ms 5.523 33.83

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.088 0.151 0.344 1.133 2.862 9.075 23.815 2.518 8.924 2.196 1.488 ms 7.973 77.15

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.203 0.212 0.331 0.894 1.659 2.199 2.346 1.329 1.987 0.393 0.934 ms 0.6912 3.718

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.179 0.473 0.651 1.455 3.970 7.150 12.048 3.319 6.676 1.221 1.798 ms 2.485 12.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.209 12.218 12.284 12.472 13.157 14.418 14.539 0.873 2.200 0.380 12.589 ppm 2.864 12.8
Local Clock Time Offset -550.584 -231.618 -73.246 -3.078 68.057 219.871 385.966 141.303 451.489 68.907 -3.752 µs -1.49 24.92
Local RMS Frequency Jitter 3.299 3.848 5.680 17.019 99.414 178.181 207.269 93.734 174.333 31.418 25.757 ppb 3.487 15.69
Local RMS Time Jitter 5.885 6.902 9.411 25.534 61.378 95.584 117.209 51.967 88.682 17.053 29.311 µs 1.769 7.6
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 5.353 7.250 13.129 97.116 168.800 183.627 417.120 155.671 176.377 48.519 92.983 µs 0.3615 5.238
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 1.820 4.996 8.345 41.808 153.372 197.748 280.656 145.027 192.752 48.205 61.803 µs 0.979 3.335
Server Jitter 204.17.205.1 1.933 4.641 9.907 113.469 197.937 225.673 261.177 188.030 221.032 62.430 104.317 µs -0.05303 1.88
Server Jitter 204.17.205.30 10.439 12.698 22.113 113.805 212.904 251.690 345.507 190.791 238.992 57.917 109.901 µs 0.3206 3.165
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.239 0.290 0.474 1.205 3.711 24.336 29.042 3.237 24.046 3.890 2.017 ms 5.523 33.83
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.088 0.151 0.344 1.133 2.862 9.075 23.815 2.518 8.924 2.196 1.488 ms 7.973 77.15
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.203 0.212 0.331 0.894 1.659 2.199 2.346 1.329 1.987 0.393 0.934 ms 0.6912 3.718
Server Jitter SHM(0) 0.179 0.473 0.651 1.455 3.970 7.150 12.048 3.319 6.676 1.221 1.798 ms 2.485 12.11
Server Offset 2001:470:e815::24 (pi4.rellim.com) -567.881 -316.154 -76.609 6.639 91.566 274.209 428.044 168.175 590.363 75.716 7.262 µs -1.167 23.54
Server Offset 2001:470:e815::8 (spidey.rellim.com) -763.894 -357.476 -224.382 -4.925 140.060 184.536 207.051 364.442 542.012 121.164 -29.297 µs -1.583 9.263
Server Offset 204.17.205.1 -699.875 -471.712 -391.903 -35.022 183.546 219.216 245.668 575.449 690.928 166.051 -66.833 µs -0.6172 3.241
Server Offset 204.17.205.30 -507.194 -464.181 -88.461 -15.531 56.930 292.444 377.131 145.391 756.625 81.610 -18.885 µs -1.424 18.7
Server Offset 2405:fc00::1 (robusta.dcs1.biz) 0.228 0.530 0.855 1.308 1.760 2.084 2.127 0.905 1.554 0.284 1.304 ms -0.05525 4.106
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.873 1.115 1.354 1.730 2.162 2.999 3.029 0.807 1.884 0.302 1.752 ms 1.379 7.475
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 1.128 1.210 1.304 1.615 1.979 2.121 2.724 0.675 0.911 0.207 1.630 ms 0.5955 5.043
Server Offset SHM(0) -406.586 -399.681 -396.529 -392.240 -388.440 -386.896 -383.234 8.089 12.785 2.572 -392.367 ms -0.4744 4.08
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 63.000 71.000 72.000 73.000 74.000 9.000 12.000 2.746 69.733 °C
Temp /dev/nvme1n1 47.000 47.000 50.000 55.000 58.000 59.000 60.000 8.000 12.000 2.396 54.264 °C
Temp /dev/sda 46.000 46.000 47.000 49.000 50.000 50.000 50.000 3.000 4.000 1.332 48.726 °C
Temp /dev/sdb 35.000 35.000 35.000 37.000 40.000 40.000 41.000 5.000 5.000 1.506 37.125 °C
Temp LM0 49.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.488 53.868 °C
Temp LM1 39.500 39.625 40.000 43.375 62.000 77.375 81.000 22.000 37.750 7.297 44.722 °C
Temp LM10 25.000 25.000 25.000 25.000 26.000 26.000 26.000 1.000 1.000 0.248 25.066 °C
Temp LM11 73.000 73.000 77.000 80.000 81.000 82.000 82.000 4.000 9.000 1.551 79.920 °C
Temp LM12 3.000 6.000 15.000 23.000 40.000 45.000 54.000 25.000 39.000 7.581 24.153 °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.937 42.215 °C
Temp LM15 35.000 35.000 36.000 37.000 51.000 66.000 70.000 15.000 31.000 5.742 38.271 °C
Temp LM16 81.000 81.500 85.000 91.000 92.500 93.000 93.000 7.500 11.500 2.309 90.398 °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.500 39.750 40.000 42.000 55.500 76.750 80.750 15.500 37.000 6.792 44.078 °C
Temp LM20 39.500 39.625 40.000 43.375 62.250 77.250 81.000 22.250 37.625 7.319 44.724 °C
Temp LM21 81.375 81.625 85.375 91.250 92.500 93.000 93.000 7.125 11.375 2.295 90.547 °C
Temp LM22 35.000 35.000 35.000 37.000 40.000 40.000 40.000 5.000 5.000 1.504 37.184 °C
Temp LM23 60.850 60.850 63.850 70.850 71.850 72.850 73.850 8.000 12.000 2.748 69.558 °C
Temp LM3 46.000 46.000 47.000 49.000 50.000 50.000 51.000 3.000 4.000 1.338 48.726 °C
Temp LM4 46.850 46.850 49.850 54.850 57.850 58.850 59.850 8.000 12.000 2.400 54.117 °C
Temp LM5 46.850 46.850 49.850 54.850 56.850 58.850 59.850 7.000 12.000 2.381 54.138 °C
Temp LM6 54.850 54.850 57.850 61.850 69.850 73.850 76.850 12.000 19.000 4.322 64.152 °C
Temp LM7 46.850 46.850 49.850 54.850 57.850 58.850 59.850 8.000 12.000 2.407 54.138 °C
Temp LM8 40.000 40.000 41.000 42.000 43.000 45.000 45.000 2.000 5.000 0.937 42.205 °C
Temp LM9 35.500 35.500 36.000 37.000 41.500 53.500 53.500 5.500 18.000 3.101 37.722 °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!