NTPsec

Kong

Report generated: Wed Nov 20 14:59:01 2024 UTC
Start Time: Wed Nov 13 14:59:00 2024 UTC
End Time: Wed Nov 20 14:59:00 2024 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 -532.577 -190.741 -49.617 -2.533 45.003 187.964 617.944 94.620 378.705 59.256 -1.702 µs -2.816 40.31
Local Clock Frequency Offset 11.371 11.409 11.447 11.637 12.381 13.654 13.756 0.934 2.246 0.409 11.755 ppm 2.143e+04 5.97e+05

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.808 8.450 10.921 20.452 53.166 120.002 215.189 42.245 111.552 18.619 24.750 µs 5.32 33.27

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 2.459 4.510 5.849 11.679 80.838 154.772 242.886 74.989 150.262 27.872 19.968 ppb 3.014 15.67

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 -532.577 -190.741 -49.617 -2.533 45.003 187.964 617.944 94.620 378.705 59.256 -1.702 µs -2.816 40.31

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 11.371 11.409 11.447 11.637 12.381 13.654 13.756 0.934 2.246 0.409 11.755 ppm 2.143e+04 5.97e+05
Temp /dev/sda 43.000 43.000 44.000 46.000 49.000 49.000 50.000 5.000 6.000 1.363 46.065 °C
Temp /dev/sdb 32.000 32.000 33.000 35.000 37.000 39.000 39.000 4.000 7.000 1.339 34.949 °C
Temp LM0 48.000 49.000 49.000 54.000 58.000 59.000 60.000 9.000 10.000 2.916 53.891 °C
Temp LM1 39.500 40.125 40.875 42.750 51.875 75.125 83.125 11.000 35.000 6.567 44.442 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.086 25.007 °C
Temp LM11 59.000 60.000 60.000 61.000 62.000 63.000 63.000 2.000 3.000 0.709 60.858 °C
Temp LM12 3.000 4.000 6.000 12.000 18.000 21.000 23.000 12.000 17.000 3.726 12.149 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.055 25.003 °C
Temp LM14 41.000 41.000 42.000 43.000 44.000 45.000 45.000 2.000 4.000 0.818 42.951 °C
Temp LM15 33.000 34.000 35.000 36.000 40.000 64.000 72.000 5.000 30.000 5.448 37.368 °C
Temp LM16 64.000 64.500 65.000 66.000 67.000 67.500 67.500 2.000 3.000 0.557 65.847 °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 40.250 41.000 43.000 51.250 75.000 84.000 10.250 34.750 6.358 44.654 °C
Temp LM20 39.625 40.125 40.875 42.750 51.625 75.250 83.125 10.750 35.125 6.562 44.430 °C
Temp LM21 64.250 64.875 65.125 66.000 67.000 67.750 67.875 1.875 2.875 0.551 65.997 °C
Temp LM22 32.000 32.000 33.000 35.000 37.000 38.000 39.000 4.000 6.000 1.272 35.012 °C
Temp LM23 62.850 64.850 65.850 68.850 69.850 70.850 73.850 4.000 6.000 1.380 68.203 °C
Temp LM3 43.000 43.000 44.000 46.000 49.000 49.000 50.000 5.000 6.000 1.366 46.050 °C
Temp LM4 46.850 47.850 47.850 49.850 50.850 53.850 55.850 3.000 6.000 1.068 49.587 °C
Temp LM5 46.850 47.850 47.850 49.850 50.850 53.850 55.850 3.000 6.000 1.062 49.600 °C
Temp LM6 54.850 55.850 55.850 57.850 60.850 68.850 72.850 5.000 13.000 2.020 58.035 °C
Temp LM7 46.850 47.850 47.850 49.850 50.850 53.850 55.850 3.000 6.000 1.063 49.607 °C
Temp LM8 41.000 41.000 42.000 43.000 44.000 45.000 45.000 2.000 4.000 0.820 42.950 °C
Temp LM9 33.500 34.500 35.000 36.500 39.000 51.000 52.500 4.000 16.500 2.810 37.015 °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) -512.364 -189.287 -65.437 3.029 71.601 254.914 764.475 137.038 444.201 70.449 5.474 µs -1.402 31.95

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) -752.973 -543.554 -424.087 9.685 221.909 295.823 851.327 645.996 839.377 188.212 -29.219 µs -5.776 17.09

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:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net)

peer offset 2001:67c:1270:0:dea6:32ff:feaf:803b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) -7.287 -1.373 -0.783 -0.227 0.386 4.248 65.240 1.169 5.621 2.467 -0.095 ms 17.25 444.2

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.140 -1.009 -0.655 0.012 0.374 0.584 1.072 1.029 1.593 0.310 -0.038 ms -5.534 16.5

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.16

peer offset 204.17.205.16 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.16 -544.153 -181.916 -69.170 3.942 70.531 211.640 675.504 139.701 393.556 64.475 3.982 µs -3.198 31.06

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 -581.118 -212.158 -76.403 -9.213 45.246 199.935 599.210 121.649 412.093 64.786 -10.679 µs -4.148 38.73

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) -29.297 2.450 4.212 4.997 5.807 8.907 101.931 1.595 6.457 4.015 5.203 ms 17.67 366

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.246 -0.908 -0.713 -0.336 0.148 0.519 150.728 0.862 1.427 4.885 -0.080 ms 19.78 536.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 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.211 0.470 0.555 0.815 1.114 1.297 1.602 0.559 0.827 0.170 0.823 ms 68.04 313

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.050 0.373 0.554 0.851 1.214 3.067 82.669 0.660 2.694 3.470 1.081 ms 17.01 350.6

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) -177.354 -139.647 -136.553 -129.953 -124.029 -122.296 -117.934 12.524 17.351 4.006 -130.111 ms -3.761e+04 1.262e+06

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.838 4.112 6.476 24.416 76.596 129.248 404.610 70.120 125.136 27.686 32.230 µs 3.713 27.1

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.958 2.148 3.345 12.346 57.461 127.770 449.440 54.116 125.622 27.324 20.245 µs 5.584 60.21

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:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net)

peer jitter 2001:67c:1270:0:dea6:32ff:feaf:803b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) 0.139 0.230 0.315 0.675 7.080 16.808 244.081 6.765 16.578 12.409 2.505 ms 10.26 164.1

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.748 3.799 5.369 14.652 46.547 126.982 326.826 41.178 123.183 23.075 19.923 µs 6.264 62.61

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.16

peer jitter 204.17.205.16 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.16 1.839 4.109 5.784 16.042 61.522 135.048 453.893 55.738 130.939 26.819 23.394 µs 5.144 47.99

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 1.280 2.943 5.011 15.814 69.019 231.466 1,671.231 64.008 228.523 65.463 27.139 µs 15.2 362.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 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.108 0.236 0.324 0.780 6.879 69.103 268.411 6.556 68.866 15.587 3.336 ms 7.782 99.78

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.137 0.214 0.281 0.550 2.752 11.096 234.682 2.471 10.882 12.933 1.888 ms 10.8 169

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.149 0.189 0.285 0.505 1.423 3.544 7.458 1.138 3.355 0.604 0.654 ms 5.37 41

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.101 0.210 0.277 0.510 4.877 82.563 200.610 4.600 82.352 14.879 2.643 ms 6.656 77.12

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.089 0.265 0.377 0.933 2.706 7.719 39.009 2.329 7.453 1.377 1.245 ms 6.485 79.27

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 11.371 11.409 11.447 11.637 12.381 13.654 13.756 0.934 2.246 0.409 11.755 ppm 2.143e+04 5.97e+05
Local Clock Time Offset -532.577 -190.741 -49.617 -2.533 45.003 187.964 617.944 94.620 378.705 59.256 -1.702 µs -2.816 40.31
Local RMS Frequency Jitter 2.459 4.510 5.849 11.679 80.838 154.772 242.886 74.989 150.262 27.872 19.968 ppb 3.014 15.67
Local RMS Time Jitter 5.808 8.450 10.921 20.452 53.166 120.002 215.189 42.245 111.552 18.619 24.750 µs 5.32 33.27
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 1.838 4.112 6.476 24.416 76.596 129.248 404.610 70.120 125.136 27.686 32.230 µs 3.713 27.1
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.958 2.148 3.345 12.346 57.461 127.770 449.440 54.116 125.622 27.324 20.245 µs 5.584 60.21
Server Jitter 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) 0.139 0.230 0.315 0.675 7.080 16.808 244.081 6.765 16.578 12.409 2.505 ms 10.26 164.1
Server Jitter 204.17.205.1 1.748 3.799 5.369 14.652 46.547 126.982 326.826 41.178 123.183 23.075 19.923 µs 6.264 62.61
Server Jitter 204.17.205.16 1.839 4.109 5.784 16.042 61.522 135.048 453.893 55.738 130.939 26.819 23.394 µs 5.144 47.99
Server Jitter 204.17.205.30 1.280 2.943 5.011 15.814 69.019 231.466 1,671.231 64.008 228.523 65.463 27.139 µs 15.2 362.4
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.108 0.236 0.324 0.780 6.879 69.103 268.411 6.556 68.866 15.587 3.336 ms 7.782 99.78
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.137 0.214 0.281 0.550 2.752 11.096 234.682 2.471 10.882 12.933 1.888 ms 10.8 169
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.149 0.189 0.285 0.505 1.423 3.544 7.458 1.138 3.355 0.604 0.654 ms 5.37 41
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.101 0.210 0.277 0.510 4.877 82.563 200.610 4.600 82.352 14.879 2.643 ms 6.656 77.12
Server Jitter SHM(0) 0.089 0.265 0.377 0.933 2.706 7.719 39.009 2.329 7.453 1.377 1.245 ms 6.485 79.27
Server Offset 2001:470:e815::24 (pi4.rellim.com) -512.364 -189.287 -65.437 3.029 71.601 254.914 764.475 137.038 444.201 70.449 5.474 µs -1.402 31.95
Server Offset 2001:470:e815::8 (spidey.rellim.com) -752.973 -543.554 -424.087 9.685 221.909 295.823 851.327 645.996 839.377 188.212 -29.219 µs -5.776 17.09
Server Offset 2001:67c:1270:0:dea6:32ff:feaf:803b (khronos.mikieboy.net) -7.287 -1.373 -0.783 -0.227 0.386 4.248 65.240 1.169 5.621 2.467 -0.095 ms 17.25 444.2
Server Offset 204.17.205.1 -1.140 -1.009 -0.655 0.012 0.374 0.584 1.072 1.029 1.593 0.310 -0.038 ms -5.534 16.5
Server Offset 204.17.205.16 -544.153 -181.916 -69.170 3.942 70.531 211.640 675.504 139.701 393.556 64.475 3.982 µs -3.198 31.06
Server Offset 204.17.205.30 -581.118 -212.158 -76.403 -9.213 45.246 199.935 599.210 121.649 412.093 64.786 -10.679 µs -4.148 38.73
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -29.297 2.450 4.212 4.997 5.807 8.907 101.931 1.595 6.457 4.015 5.203 ms 17.67 366
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -2.246 -0.908 -0.713 -0.336 0.148 0.519 150.728 0.862 1.427 4.885 -0.080 ms 19.78 536.9
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 0.211 0.470 0.555 0.815 1.114 1.297 1.602 0.559 0.827 0.170 0.823 ms 68.04 313
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -0.050 0.373 0.554 0.851 1.214 3.067 82.669 0.660 2.694 3.470 1.081 ms 17.01 350.6
Server Offset SHM(0) -177.354 -139.647 -136.553 -129.953 -124.029 -122.296 -117.934 12.524 17.351 4.006 -130.111 ms -3.761e+04 1.262e+06
Temp /dev/sda 43.000 43.000 44.000 46.000 49.000 49.000 50.000 5.000 6.000 1.363 46.065 °C
Temp /dev/sdb 32.000 32.000 33.000 35.000 37.000 39.000 39.000 4.000 7.000 1.339 34.949 °C
Temp LM0 48.000 49.000 49.000 54.000 58.000 59.000 60.000 9.000 10.000 2.916 53.891 °C
Temp LM1 39.500 40.125 40.875 42.750 51.875 75.125 83.125 11.000 35.000 6.567 44.442 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.086 25.007 °C
Temp LM11 59.000 60.000 60.000 61.000 62.000 63.000 63.000 2.000 3.000 0.709 60.858 °C
Temp LM12 3.000 4.000 6.000 12.000 18.000 21.000 23.000 12.000 17.000 3.726 12.149 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.055 25.003 °C
Temp LM14 41.000 41.000 42.000 43.000 44.000 45.000 45.000 2.000 4.000 0.818 42.951 °C
Temp LM15 33.000 34.000 35.000 36.000 40.000 64.000 72.000 5.000 30.000 5.448 37.368 °C
Temp LM16 64.000 64.500 65.000 66.000 67.000 67.500 67.500 2.000 3.000 0.557 65.847 °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 40.250 41.000 43.000 51.250 75.000 84.000 10.250 34.750 6.358 44.654 °C
Temp LM20 39.625 40.125 40.875 42.750 51.625 75.250 83.125 10.750 35.125 6.562 44.430 °C
Temp LM21 64.250 64.875 65.125 66.000 67.000 67.750 67.875 1.875 2.875 0.551 65.997 °C
Temp LM22 32.000 32.000 33.000 35.000 37.000 38.000 39.000 4.000 6.000 1.272 35.012 °C
Temp LM23 62.850 64.850 65.850 68.850 69.850 70.850 73.850 4.000 6.000 1.380 68.203 °C
Temp LM3 43.000 43.000 44.000 46.000 49.000 49.000 50.000 5.000 6.000 1.366 46.050 °C
Temp LM4 46.850 47.850 47.850 49.850 50.850 53.850 55.850 3.000 6.000 1.068 49.587 °C
Temp LM5 46.850 47.850 47.850 49.850 50.850 53.850 55.850 3.000 6.000 1.062 49.600 °C
Temp LM6 54.850 55.850 55.850 57.850 60.850 68.850 72.850 5.000 13.000 2.020 58.035 °C
Temp LM7 46.850 47.850 47.850 49.850 50.850 53.850 55.850 3.000 6.000 1.063 49.607 °C
Temp LM8 41.000 41.000 42.000 43.000 44.000 45.000 45.000 2.000 4.000 0.820 42.950 °C
Temp LM9 33.500 34.500 35.000 36.500 39.000 51.000 52.500 4.000 16.500 2.810 37.015 °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.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of 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".
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 Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
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!