NTPsec

Dell-2018

Report generated: Sun Dec 21 01:40:04 2025 UTC
Start Time: Sun Nov 16 01:40:01 2025 UTC
End Time: Sun Dec 21 01:40:01 2025 UTC
Report Period: 35.0 days

Stats for the last 1, 7, 35, 98, 371, some days, or live gps data.

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 -15.340 -8.723 -8.434 -4.845 -0.007 0.152 84.304 8.427 8.875 2.881 -5.382 ms 8.652 235.7
Local Clock Frequency Offset -135.511 11.074 11.376 19.272 25.681 26.213 61.826 14.306 15.139 4.241 20.452 ppm -2.749 85.17

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 0.000 0.165 0.188 0.250 0.338 0.413 36.141 0.149 0.248 0.919 0.297 ms 27.26 806.7

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.0000 0.0036 0.0043 0.181 0.379 0.704 73.177 0.375 0.700 1.498 0.262 ppm 31.55 1167

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 -15.340 -8.723 -8.434 -4.845 -0.007 0.152 84.304 8.427 8.875 2.881 -5.382 ms 8.652 235.7

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 -135.511 11.074 11.376 19.272 25.681 26.213 61.826 14.306 15.139 4.241 20.452 ppm -2.749 85.17
Temp /dev/sda 18.000 18.000 20.000 25.000 26.000 26.000 36.000 6.000 8.000 2.072 24.023 °C
Temp LM0 29.000 31.000 32.000 40.000 45.000 47.000 50.000 13.000 16.000 4.175 38.994 °C
Temp LM1 27.000 28.000 29.000 30.000 39.000 39.000 41.000 10.000 11.000 2.525 30.800 °C
Temp LM2 0.000 19.000 19.000 34.000 35.000 36.000 45.000 16.000 17.000 4.696 32.421 °C
Temp LM3 29.000 29.000 31.000 38.000 39.000 40.000 44.000 8.000 11.000 2.149 37.421 °C
Temp LM4 0.000 0.000 0.000 0.000 40.000 44.000 54.000 40.000 44.000 11.373 3.548 °C
Temp LM5 27.000 28.000 29.000 30.000 31.000 33.000 40.000 2.000 5.000 0.908 30.147 °C
Temp LM6 29.000 31.000 31.000 33.000 34.000 35.000 45.000 3.000 4.000 1.004 32.717 °C
Temp LM7 31.000 33.000 33.000 35.000 36.000 37.000 46.000 3.000 4.000 1.069 34.563 °C
Temp LM8 31.000 33.000 33.000 35.000 36.000 37.000 46.000 3.000 4.000 1.079 34.578 °C
Temp LM9 31.000 33.000 33.000 35.000 36.000 37.000 46.000 3.000 4.000 1.079 34.578 °C
Temp ZONE0 20.000 20.000 20.000 20.000 20.000 20.000 20.000 0.000 0.000 0.000 20.000 °C
Temp ZONE1 30.000 32.000 32.000 34.000 35.000 37.000 45.000 3.000 5.000 1.017 33.800 °C
Temp ZONE2 27.000 28.000 29.000 30.000 31.000 33.000 40.000 2.000 5.000 0.905 30.144 °C
Temp ZONE3 30.000 32.000 32.000 34.000 35.000 37.000 47.000 3.000 5.000 1.035 33.806 °C
Temp ZONE4 30.000 32.000 32.000 34.000 35.000 37.000 45.000 3.000 5.000 1.017 33.800 °C
Temp ZONE5 29.000 31.000 32.000 40.000 45.000 47.000 54.000 13.000 16.000 4.040 39.522 °C
Temp ZONE6 27.000 28.000 29.000 30.000 31.000 33.000 40.000 2.000 5.000 0.910 30.139 °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 8.000 8.000 9.000 11.000 13.000 14.000 16.000 4.000 6.000 1.296 11.128 nSat 0.2123 2.936
TDOP 0.490 0.520 0.600 0.880 1.450 2.110 2.520 0.850 1.590 0.273 0.932 1.771 8.528

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 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 -2.525 -2.525 -2.525 2.779 11.107 11.107 11.107 13.632 13.632 3.750 3.054 ms 0.5869 2.765

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 104.152.220.5

peer offset 104.152.220.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.152.220.5 1.461 1.461 1.461 2.919 4.887 4.887 4.887 3.425 3.425 1.020 2.874 ms 0.6553 2.767

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 137.190.2.4

peer offset 137.190.2.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 137.190.2.4 -13.886 -13.886 -13.886 73.703 432.020 432.020 432.020 445.906 445.906 141.512 93.930 ms 1.772 4.593

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 148.163.226.148

peer offset 148.163.226.148 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 148.163.226.148 -76.672 -76.672 -76.672 2.891 6.433 6.433 6.433 83.105 83.105 25.184 -5.515 ms -2.465 7.097

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 155.248.196.28

peer offset 155.248.196.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 155.248.196.28 -1.736 -1.736 -1.736 0.032 3.369 3.369 3.369 5.105 5.105 1.769 0.391 ms 0.5292 1.767

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 166.88.142.52

peer offset 166.88.142.52 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 166.88.142.52 2.966 2.966 2.966 4.246 7.638 7.638 7.638 4.671 4.671 1.508 4.329 ms 1.273 3.521

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 172.233.177.198

peer offset 172.233.177.198 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.177.198 -5.527 -5.527 -5.527 3.622 7.415 7.415 7.415 12.942 12.942 3.634 2.383 ms -0.9084 3.103

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 172.234.25.10

peer offset 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.25.10 -0.488 -0.488 -0.488 0.948 5.051 5.051 5.051 5.539 5.539 1.848 1.545 ms 0.8338 2.298

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 172.234.37.140

peer offset 172.234.37.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.37.140 -9.587 -9.587 -9.587 2.879 11.157 11.157 11.157 20.745 20.745 5.228 2.639 ms -0.8929 4.146

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 194.0.5.123

peer offset 194.0.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.0.5.123 -3.549 -3.333 -2.021 0.711 3.049 5.915 6.281 5.070 9.248 1.611 0.678 ms 0.3202 4.501

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:559:2be:3::1001

peer offset 2001:559:2be:3::1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:559:2be:3::1001 2.838 2.838 2.838 6.118 9.658 9.658 9.658 6.820 6.820 2.006 6.562 ms -0.1996 2.201

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:678:8::123 (any.time.nl)

peer offset 2001:678:8::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:678:8::123 (any.time.nl) -56.834 -30.249 -15.716 -6.510 -2.731 0.765 5.894 12.985 31.014 5.608 -7.483 ms -4.421 34.13

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 23.111.186.186

peer offset 23.111.186.186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.111.186.186 0.800 0.800 0.800 2.292 3.617 3.617 3.617 2.817 2.817 0.849 2.280 ms -0.2598 2.078

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 23.155.40.38

peer offset 23.155.40.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.155.40.38 -6.002 -6.002 -4.912 -2.083 2.268 3.591 3.591 7.180 9.593 2.109 -1.817 ms 0.6088 3.28

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 23.186.168.129

peer offset 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.129 -23.022 -23.022 -23.022 79.126 423.814 423.814 423.814 446.837 446.837 122.871 79.712 ms 2.037 6.27

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 23.186.168.130

peer offset 23.186.168.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.130 -4.461 -4.461 -4.461 -2.134 7.796 7.796 7.796 12.257 12.257 3.265 -1.278 ms 1.43 4.608

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 23.186.168.131

peer offset 23.186.168.131 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.131 -3.617 -3.617 -3.617 0.658 4.423 4.423 4.423 8.040 8.040 1.815 0.563 ms -0.185 4.155

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 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl)

peer offset 2401:c080:3000:2945:5400:4ff:fe69:f923 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) -70.714 -47.724 -33.815 -10.046 26.468 30.320 33.265 60.283 78.044 14.535 -10.605 ms 0.5037 6.049

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 240b:4004:108:200:8314:1a08:4cee:26d8

peer offset 240b:4004:108:200:8314:1a08:4cee:26d8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 240b:4004:108:200:8314:1a08:4cee:26d8 -10.660 -10.660 -1.669 2.211 424.412 425.724 425.724 426.080 436.384 113.328 48.896 ms 2.876 9.733

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 240b:4004:108:200:8314:1a08:4cee:2acf

peer offset 240b:4004:108:200:8314:1a08:4cee:2acf plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 240b:4004:108:200:8314:1a08:4cee:2acf -55.272 -55.272 -55.272 0.474 2.640 2.640 2.640 57.912 57.912 17.808 -5.000 ms -2.456 7.073

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 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com)

peer offset 2600:1900:4060:2e7:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com) -26.834 -16.012 -8.969 1.963 6.113 8.686 10.839 15.082 24.697 4.691 1.079 ms -2.114 9.97

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 2600:1f13:2c1:2e00::be00:5

peer offset 2600:1f13:2c1:2e00::be00:5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f13:2c1:2e00::be00:5 1.672 1.672 1.672 5.591 19.969 19.969 19.969 18.297 18.297 5.131 6.284 ms 1.945 5.754

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 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com)

peer offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) -29.237 -8.071 -6.721 -2.782 2.970 4.626 110.743 9.692 12.697 4.208 -2.520 ms 11.24 254.3

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 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com)

peer offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) -23.935 -6.970 -4.877 -0.514 5.276 6.669 422.200 10.153 13.639 7.681 -0.237 ms 39.48 2107

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 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com)

peer offset 2600:1f18:4c51:e200:e142:210a:306d:4872 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) -35.802 -20.283 -7.449 -0.804 5.355 7.399 415.823 12.804 27.682 8.424 -0.805 ms 29.04 1392

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 2600:1f18:7927:8b00:123::

peer offset 2600:1f18:7927:8b00:123:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f18:7927:8b00:123:: 4.710 4.710 4.710 6.720 8.399 8.399 8.399 3.689 3.689 1.160 6.461 ms 0.06963 2.058

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 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com)

peer offset 2600:3c01::f03c:93ff:fedd:5a1f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com) -16.936 -16.936 -5.885 2.642 423.840 424.816 424.816 429.725 441.752 116.114 50.434 ms 2.724 8.986

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 2600:3c01:e000:7e6::123 (time1.sigi.net)

peer offset 2600:3c01:e000:7e6::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c01:e000:7e6::123 (time1.sigi.net) -0.759 -0.759 -0.759 2.211 3.558 3.558 3.558 4.317 4.317 1.267 1.976 ms -1.099 3.486

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 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net)

peer offset 2600:3c03::f03c:91ff:fedf:1e98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) -24.915 -24.915 -24.915 67.309 423.497 423.497 423.497 448.412 448.412 136.652 85.591 ms 1.84 4.92

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 2602:80b:5000::36 (time.meme.holdings)

peer offset 2602:80b:5000::36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:80b:5000::36 (time.meme.holdings) -0.850 -0.850 -0.850 3.327 13.389 13.389 13.389 14.239 14.239 3.855 4.450 ms 1.162 3.726

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 2602:81b:9000::c10c (time.sea.ordinaladvisors.com)

peer offset 2602:81b:9000::c10c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) -2.396 -2.396 -2.396 0.924 11.083 11.083 11.083 13.479 13.479 4.287 2.602 ms 0.7321 2.194

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 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net)

peer offset 2602:f9ba:69::210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) 4.298 4.298 4.298 6.373 7.842 7.842 7.842 3.544 3.544 1.099 6.237 ms -0.09612 2.22

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 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com)

peer offset 2602:fd50:100:108:3491:d3b2:eef8:f324 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) -2.937 -2.937 -1.379 2.434 7.512 9.493 9.493 8.892 12.430 2.905 2.389 ms 0.4696 3.021

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 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de)

peer offset 2605:6f01:2000:18::94ee:fcbe plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) -1.370 -1.370 -1.370 3.697 9.921 9.921 9.921 11.292 11.292 2.854 4.172 ms 0.1428 3.178

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) -10.517 -7.412 -5.892 -1.611 5.485 7.351 10.236 11.377 14.763 3.494 -1.141 ms 0.474 2.627

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) -30.959 -5.033 -3.983 -0.834 3.885 6.307 429.230 7.867 11.340 19.462 0.516 ms 20.37 438.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 2606:82c0:21::e (time1.lshiy.com)

peer offset 2606:82c0:21::e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:82c0:21::e (time1.lshiy.com) -0.347 -0.347 -0.347 2.470 5.026 5.026 5.026 5.373 5.373 1.632 2.157 ms 0.07044 2.391

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 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at)

peer offset 2607:f1c0:f06b:5000::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) -1.407 -1.407 -1.407 3.805 10.246 10.246 10.246 11.653 11.653 3.063 4.635 ms -0.1037 3.023

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 2607:f1c0:f075:9900::1

peer offset 2607:f1c0:f075:9900::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f075:9900::1 -11.364 -11.364 -11.364 62.462 429.472 429.472 429.472 440.836 440.836 142.546 88.428 ms 1.844 4.744

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 2607:f298:5:101d:f816:3eff:fefd:8817

peer offset 2607:f298:5:101d:f816:3eff:fefd:8817 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f298:5:101d:f816:3eff:fefd:8817 1.052 1.052 1.052 3.678 8.611 8.611 8.611 7.559 7.559 2.139 4.559 ms 0.3897 2.465

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 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se)

peer offset 2a01:3f7:2:44::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) -90.881 -26.556 -11.995 -1.256 4.735 6.953 425.774 16.730 33.510 13.737 -1.574 ms 23.69 737

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 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se)

peer offset 2a01:3f7:2:44::9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) -75.694 -15.935 -5.578 -1.716 1.484 3.368 106.144 7.062 19.302 4.688 -2.006 ms 2.228 203.8

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 45.63.54.13

peer offset 45.63.54.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.63.54.13 2.092 2.092 2.092 4.924 6.910 6.910 6.910 4.818 4.818 1.426 4.715 ms -0.0539 2.339

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 66.118.231.14

peer offset 66.118.231.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.118.231.14 -0.952 -0.952 -0.952 0.349 4.672 4.672 4.672 5.623 5.623 1.689 0.982 ms 1.225 3.534

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 67.217.246.204

peer offset 67.217.246.204 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 67.217.246.204 -11.181 -11.181 -11.181 47.769 423.145 423.145 423.145 434.326 434.326 174.280 121.772 ms 1.099 2.292

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 69.176.84.38

peer offset 69.176.84.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.176.84.38 -4.887 -4.887 -3.512 1.450 3.073 4.499 4.499 6.585 9.386 2.266 0.622 ms -0.718 2.493

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 69.89.207.199

peer offset 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.89.207.199 -11.403 -11.403 -11.403 44.730 425.249 425.249 425.249 436.653 436.653 139.058 78.387 ms 1.964 5.196

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 69.89.207.99

peer offset 69.89.207.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.89.207.99 -82.728 -82.728 -82.728 -0.965 3.942 3.942 3.942 86.670 86.670 19.565 -5.202 ms -3.631 14.51

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 77.37.97.124

peer offset 77.37.97.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 77.37.97.124 -28.059 -28.059 -10.002 5.495 11.506 23.808 23.808 21.508 51.867 6.958 3.767 ms -1.571 8.198

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) -193.907 -188.372 -186.103 -179.313 -122.306 -118.880 -66.245 63.798 69.492 19.014 -173.033 ms 2.158 6.006

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(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -43.998 -8.849 -8.482 -5.910 -3.472 -2.078 52.678 5.010 6.771 1.954 -5.926 ms 1.16 52.68

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(2)

peer offset SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(2) -192.688 -184.315 -179.668 -168.955 -151.228 -145.886 1,940.513 28.440 38.429 22.592 -168.004 ms 80.09 7303

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(3)

peer offset SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(3) -13.801 -8.901 -8.551 -5.956 -3.532 -2.164 2,061.810 5.019 6.737 20.823 -5.762 ms 96.08 9315

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 SOCK(0)

peer offset SOCK(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SOCK(0) -180.583 -178.322 -176.181 -172.068 -168.305 -166.725 -164.264 7.876 11.596 2.460 -172.140 ms -0.1743 3.087

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 SOCK(1)

peer offset SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SOCK(1) -489.762 -433.183 -386.296 -29.022 302.627 386.991 466.635 688.923 820.174 232.318 -16.223 µs -0.07358 1.719

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 SOCK(2)

peer offset SOCK(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SOCK(2) -181.156 -178.007 -173.059 -163.641 -157.179 -155.100 -151.658 15.880 22.907 4.872 -164.199 ms -0.5505 3.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 SOCK(3)

peer offset SOCK(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SOCK(3) -560.863 -493.512 -438.746 -81.107 236.850 326.708 408.839 675.596 820.220 229.645 -76.459 µs -0.1042 1.712

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 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.000 0.000 0.000 3.656 18.171 18.171 18.171 18.171 18.171 5.828 6.234 ms 1.278 3.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 104.152.220.5

peer jitter 104.152.220.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.152.220.5 0.000 0.000 0.000 0.888 2.438 2.438 2.438 2.438 2.438 0.710 1.068 ms 0.5336 2.756

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 137.190.2.4

peer jitter 137.190.2.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 137.190.2.4 0.000 0.000 0.000 8.346 83.883 83.883 83.883 83.883 83.883 25.677 16.869 ms 1.958 5.07

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 148.163.226.148

peer jitter 148.163.226.148 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 148.163.226.148 0.000 0.000 0.000 0.817 80.131 80.131 80.131 80.131 80.131 25.414 13.052 ms 1.993 5.456

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 155.248.196.28

peer jitter 155.248.196.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 155.248.196.28 0.000 0.000 0.000 1.667 4.694 4.694 4.694 4.694 4.694 1.616 1.873 ms 0.573 1.838

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 166.88.142.52

peer jitter 166.88.142.52 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 166.88.142.52 0.000 0.000 0.000 1.075 3.927 3.927 3.927 3.927 3.927 1.133 1.349 ms 1.419 4.128

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 172.233.177.198

peer jitter 172.233.177.198 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.177.198 0.000 0.000 0.000 5.156 9.581 9.581 9.581 9.581 9.581 2.646 5.415 ms -0.2803 2.993

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 172.234.25.10

peer jitter 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.25.10 0.000 0.000 0.000 1.017 4.280 4.280 4.280 4.280 4.280 1.424 1.561 ms 0.8819 2.346

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 172.234.37.140

peer jitter 172.234.37.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.37.140 0.000 0.000 0.000 5.919 13.618 13.618 13.618 13.618 13.618 3.724 6.816 ms 0.1098 2.73

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 194.0.5.123

peer jitter 194.0.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.0.5.123 0.000 0.821 1.146 2.620 7.449 15.773 23.766 6.302 14.952 2.932 3.409 ms 3.836 22.82

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:559:2be:3::1001

peer jitter 2001:559:2be:3::1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:559:2be:3::1001 0.000 0.000 0.000 2.623 4.670 4.670 4.670 4.670 4.670 1.301 2.709 ms -0.4538 2.918

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:678:8::123 (any.time.nl)

peer jitter 2001:678:8::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:678:8::123 (any.time.nl) 0.000 1.299 1.944 37.972 98.634 112.395 114.872 96.690 111.096 33.675 42.507 ms 0.3112 1.755

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 23.111.186.186

peer jitter 23.111.186.186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.111.186.186 0.000 0.000 0.000 1.132 1.974 1.974 1.974 1.974 1.974 0.537 1.129 ms -0.4905 3.028

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 23.155.40.38

peer jitter 23.155.40.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.155.40.38 0.000 0.000 0.772 3.992 20.453 21.589 21.589 19.681 21.589 6.722 6.714 ms 1.046 2.685

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 23.186.168.129

peer jitter 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.129 0.000 0.000 0.000 8.998 105.774 105.774 105.774 105.774 105.774 35.588 26.046 ms 1.375 3.246

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 23.186.168.130

peer jitter 23.186.168.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.130 0.000 0.000 0.000 5.372 73.994 73.994 73.994 73.994 73.994 23.652 13.804 ms 2.127 5.583

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 23.186.168.131

peer jitter 23.186.168.131 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.131 0.000 0.000 0.000 2.546 4.715 4.715 4.715 4.715 4.715 1.189 2.650 ms -0.08618 3.584

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 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl)

peer jitter 2401:c080:3000:2945:5400:4ff:fe69:f923 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) 0.000 3.069 12.204 50.122 83.984 93.823 100.416 71.779 90.754 21.693 49.300 ms -0.06403 2.376

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 240b:4004:108:200:8314:1a08:4cee:26d8

peer jitter 240b:4004:108:200:8314:1a08:4cee:26d8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d8 0.000 0.000 0.000 3.953 46.649 52.232 52.232 46.649 52.232 15.473 10.747 ms 1.58 4.101

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 240b:4004:108:200:8314:1a08:4cee:2acf

peer jitter 240b:4004:108:200:8314:1a08:4cee:2acf plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 240b:4004:108:200:8314:1a08:4cee:2acf 0.000 0.000 0.000 1.911 56.765 56.765 56.765 56.765 56.765 17.704 9.838 ms 2.016 5.544

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 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com)

peer jitter 2600:1900:4060:2e7:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com) 0.000 0.636 5.384 52.642 93.922 105.814 115.333 88.538 105.178 28.933 49.386 ms -0.007048 1.9

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 2600:1f13:2c1:2e00::be00:5

peer jitter 2600:1f13:2c1:2e00::be00:5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f13:2c1:2e00::be00:5 0.000 0.000 0.000 2.102 15.060 15.060 15.060 15.060 15.060 4.508 4.272 ms 1.493 3.915

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 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com)

peer jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.000 0.811 1.113 2.957 13.180 28.917 185.361 12.067 28.106 8.526 4.708 ms 11.78 193.2

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 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com)

peer jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) 0.000 0.807 1.148 3.026 16.683 37.595 282.893 15.535 36.787 8.020 5.154 ms 12.53 348.8

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 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com)

peer jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) 0.000 0.792 1.169 4.015 29.580 56.518 141.710 28.411 55.725 11.112 8.353 ms 3.665 24.44

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 2600:1f18:7927:8b00:123::

peer jitter 2600:1f18:7927:8b00:123:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f18:7927:8b00:123:: 0.000 0.000 0.000 0.873 2.440 2.440 2.440 2.440 2.440 0.788 1.166 ms 0.2839 1.935

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 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com)

peer jitter 2600:3c01::f03c:93ff:fedd:5a1f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com) 0.000 0.000 0.000 7.022 69.185 74.278 74.278 69.185 74.278 19.927 15.358 ms 1.999 5.824

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 2600:3c01:e000:7e6::123 (time1.sigi.net)

peer jitter 2600:3c01:e000:7e6::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c01:e000:7e6::123 (time1.sigi.net) 0.000 0.000 0.000 1.694 2.687 2.687 2.687 2.687 2.687 0.793 1.697 ms -1.027 3.417

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 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net)

peer jitter 2600:3c03::f03c:91ff:fedf:1e98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) 0.000 0.000 0.000 11.029 94.476 94.476 94.476 94.476 94.476 27.639 20.489 ms 1.645 4.285

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 2602:80b:5000::36 (time.meme.holdings)

peer jitter 2602:80b:5000::36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:80b:5000::36 (time.meme.holdings) 0.000 0.000 0.000 5.351 14.239 14.239 14.239 14.239 14.239 3.718 5.746 ms 0.828 3.761

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 2602:81b:9000::c10c (time.sea.ordinaladvisors.com)

peer jitter 2602:81b:9000::c10c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) 0.000 0.000 0.000 4.593 9.349 9.349 9.349 9.349 9.349 2.587 4.904 ms -0.09123 2.375

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 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net)

peer jitter 2602:f9ba:69::210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) 0.000 0.000 0.000 1.311 2.166 2.166 2.166 2.166 2.166 0.660 1.305 ms -0.4584 2.634

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 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com)

peer jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) 0.000 0.000 0.000 1.961 5.599 9.370 9.370 5.599 9.370 2.184 2.731 ms 1.202 4.547

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 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de)

peer jitter 2605:6f01:2000:18::94ee:fcbe plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) 0.000 0.000 0.000 3.793 7.878 7.878 7.878 7.878 7.878 2.024 4.070 ms 0.0771 3.251

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.489 0.820 1.126 3.090 13.861 32.456 196.069 12.735 31.636 8.801 4.862 ms 12.61 229.5

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.759 1.113 3.088 13.582 23.065 114.990 12.469 22.306 5.816 4.526 ms 8.216 117

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:82c0:21::e (time1.lshiy.com)

peer jitter 2606:82c0:21::e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:82c0:21::e (time1.lshiy.com) 0.000 0.000 0.000 1.883 3.565 3.565 3.565 3.565 3.565 1.027 1.940 ms -0.3172 2.792

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 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at)

peer jitter 2607:f1c0:f06b:5000::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) 0.000 0.000 0.000 4.159 8.671 8.671 8.671 8.671 8.671 2.395 3.886 ms 0.1154 2.987

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 2607:f1c0:f075:9900::1

peer jitter 2607:f1c0:f075:9900::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f075:9900::1 0.000 0.000 0.000 5.383 70.431 70.431 70.431 70.431 70.431 22.237 14.508 ms 1.748 4.483

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 2607:f298:5:101d:f816:3eff:fefd:8817

peer jitter 2607:f298:5:101d:f816:3eff:fefd:8817 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f298:5:101d:f816:3eff:fefd:8817 0.000 0.000 0.000 2.720 5.235 5.235 5.235 5.235 5.235 1.474 2.934 ms -0.2774 2.751

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 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se)

peer jitter 2a01:3f7:2:44::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 0.000 1.320 2.743 34.384 84.802 102.760 242.000 82.059 101.440 27.383 36.352 ms 1.044 5.821

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 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se)

peer jitter 2a01:3f7:2:44::9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) 0.000 1.597 2.634 16.612 64.744 96.902 234.358 62.110 95.305 21.873 23.139 ms 2.428 14.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 45.63.54.13

peer jitter 45.63.54.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.63.54.13 0.000 0.000 0.000 1.137 3.288 3.288 3.288 3.288 3.288 1.000 1.442 ms 0.4076 1.963

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 66.118.231.14

peer jitter 66.118.231.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.118.231.14 0.000 0.000 0.000 1.084 4.383 4.383 4.383 4.383 4.383 1.272 1.490 ms 1.426 4.099

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 67.217.246.204

peer jitter 67.217.246.204 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 67.217.246.204 0.000 0.000 0.000 12.593 47.481 47.481 47.481 47.481 47.481 18.695 18.270 ms 0.4955 1.478

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 69.176.84.38

peer jitter 69.176.84.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.176.84.38 0.000 0.000 0.084 1.877 4.514 6.761 6.761 4.430 6.761 1.315 2.063 ms 1.34 5.848

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 69.89.207.199

peer jitter 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.89.207.199 0.000 0.000 0.000 8.052 65.312 65.312 65.312 65.312 65.312 20.904 16.467 ms 1.566 4.007

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 69.89.207.99

peer jitter 69.89.207.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.89.207.99 0.000 0.000 0.000 1.893 81.250 81.250 81.250 81.250 81.250 19.485 8.176 ms 3.151 11.74

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 77.37.97.124

peer jitter 77.37.97.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.37.97.124 0.000 0.000 5.136 45.779 85.781 100.698 100.698 80.645 100.698 23.793 47.242 ms 0.00759 2.217

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.000 0.456 0.689 1.679 3.934 5.281 93.743 3.245 4.825 1.385 1.935 ms 21.24 1165

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(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.000 0.184 0.208 0.303 0.460 0.605 96.676 0.252 0.421 0.997 0.339 ms 65.96 5338

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(2)

peer jitter SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(2) 0.000 0.672 1.001 2.461 5.817 7.607 2,002.029 4.816 6.935 26.711 3.319 ms 57.26 3478

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(3)

peer jitter SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(3) 0.000 0.188 0.213 0.308 0.471 0.611 2,001.141 0.258 0.423 26.629 0.826 ms 57.59 3509

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 SOCK(0)

peer jitter SOCK(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SOCK(0) 0.255 0.380 0.619 1.505 3.552 4.411 7.964 2.933 4.030 0.908 1.696 ms 1.287 5.606

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 SOCK(1)

peer jitter SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SOCK(1) 172.539 199.329 222.140 317.030 447.723 492.978 538.233 225.583 293.649 73.141 322.241 µs 0.355 2.286

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 SOCK(2)

peer jitter SOCK(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SOCK(2) 0.235 0.567 0.923 2.318 5.621 7.429 9.165 4.698 6.862 1.475 2.673 ms 1.195 4.598

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 SOCK(3)

peer jitter SOCK(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SOCK(3) 152.457 191.417 216.191 314.406 445.399 479.730 542.084 229.208 288.313 71.032 318.190 µs 0.3217 2.382

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 -135.511 11.074 11.376 19.272 25.681 26.213 61.826 14.306 15.139 4.241 20.452 ppm -2.749 85.17
Local Clock Time Offset -15.340 -8.723 -8.434 -4.845 -0.007 0.152 84.304 8.427 8.875 2.881 -5.382 ms 8.652 235.7
Local RMS Frequency Jitter 0.0000 0.0036 0.0043 0.181 0.379 0.704 73.177 0.375 0.700 1.498 0.262 ppm 31.55 1167
Local RMS Time Jitter 0.000 0.165 0.188 0.250 0.338 0.413 36.141 0.149 0.248 0.919 0.297 ms 27.26 806.7
Server Jitter 104.131.155.175 0.000 0.000 0.000 3.656 18.171 18.171 18.171 18.171 18.171 5.828 6.234 ms 1.278 3.15
Server Jitter 104.152.220.5 0.000 0.000 0.000 0.888 2.438 2.438 2.438 2.438 2.438 0.710 1.068 ms 0.5336 2.756
Server Jitter 137.190.2.4 0.000 0.000 0.000 8.346 83.883 83.883 83.883 83.883 83.883 25.677 16.869 ms 1.958 5.07
Server Jitter 148.163.226.148 0.000 0.000 0.000 0.817 80.131 80.131 80.131 80.131 80.131 25.414 13.052 ms 1.993 5.456
Server Jitter 155.248.196.28 0.000 0.000 0.000 1.667 4.694 4.694 4.694 4.694 4.694 1.616 1.873 ms 0.573 1.838
Server Jitter 166.88.142.52 0.000 0.000 0.000 1.075 3.927 3.927 3.927 3.927 3.927 1.133 1.349 ms 1.419 4.128
Server Jitter 172.233.177.198 0.000 0.000 0.000 5.156 9.581 9.581 9.581 9.581 9.581 2.646 5.415 ms -0.2803 2.993
Server Jitter 172.234.25.10 0.000 0.000 0.000 1.017 4.280 4.280 4.280 4.280 4.280 1.424 1.561 ms 0.8819 2.346
Server Jitter 172.234.37.140 0.000 0.000 0.000 5.919 13.618 13.618 13.618 13.618 13.618 3.724 6.816 ms 0.1098 2.73
Server Jitter 194.0.5.123 0.000 0.821 1.146 2.620 7.449 15.773 23.766 6.302 14.952 2.932 3.409 ms 3.836 22.82
Server Jitter 2001:559:2be:3::1001 0.000 0.000 0.000 2.623 4.670 4.670 4.670 4.670 4.670 1.301 2.709 ms -0.4538 2.918
Server Jitter 2001:678:8::123 (any.time.nl) 0.000 1.299 1.944 37.972 98.634 112.395 114.872 96.690 111.096 33.675 42.507 ms 0.3112 1.755
Server Jitter 23.111.186.186 0.000 0.000 0.000 1.132 1.974 1.974 1.974 1.974 1.974 0.537 1.129 ms -0.4905 3.028
Server Jitter 23.155.40.38 0.000 0.000 0.772 3.992 20.453 21.589 21.589 19.681 21.589 6.722 6.714 ms 1.046 2.685
Server Jitter 23.186.168.129 0.000 0.000 0.000 8.998 105.774 105.774 105.774 105.774 105.774 35.588 26.046 ms 1.375 3.246
Server Jitter 23.186.168.130 0.000 0.000 0.000 5.372 73.994 73.994 73.994 73.994 73.994 23.652 13.804 ms 2.127 5.583
Server Jitter 23.186.168.131 0.000 0.000 0.000 2.546 4.715 4.715 4.715 4.715 4.715 1.189 2.650 ms -0.08618 3.584
Server Jitter 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) 0.000 3.069 12.204 50.122 83.984 93.823 100.416 71.779 90.754 21.693 49.300 ms -0.06403 2.376
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d8 0.000 0.000 0.000 3.953 46.649 52.232 52.232 46.649 52.232 15.473 10.747 ms 1.58 4.101
Server Jitter 240b:4004:108:200:8314:1a08:4cee:2acf 0.000 0.000 0.000 1.911 56.765 56.765 56.765 56.765 56.765 17.704 9.838 ms 2.016 5.544
Server Jitter 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com) 0.000 0.636 5.384 52.642 93.922 105.814 115.333 88.538 105.178 28.933 49.386 ms -0.007048 1.9
Server Jitter 2600:1f13:2c1:2e00::be00:5 0.000 0.000 0.000 2.102 15.060 15.060 15.060 15.060 15.060 4.508 4.272 ms 1.493 3.915
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.000 0.811 1.113 2.957 13.180 28.917 185.361 12.067 28.106 8.526 4.708 ms 11.78 193.2
Server Jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) 0.000 0.807 1.148 3.026 16.683 37.595 282.893 15.535 36.787 8.020 5.154 ms 12.53 348.8
Server Jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) 0.000 0.792 1.169 4.015 29.580 56.518 141.710 28.411 55.725 11.112 8.353 ms 3.665 24.44
Server Jitter 2600:1f18:7927:8b00:123:: 0.000 0.000 0.000 0.873 2.440 2.440 2.440 2.440 2.440 0.788 1.166 ms 0.2839 1.935
Server Jitter 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com) 0.000 0.000 0.000 7.022 69.185 74.278 74.278 69.185 74.278 19.927 15.358 ms 1.999 5.824
Server Jitter 2600:3c01:e000:7e6::123 (time1.sigi.net) 0.000 0.000 0.000 1.694 2.687 2.687 2.687 2.687 2.687 0.793 1.697 ms -1.027 3.417
Server Jitter 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) 0.000 0.000 0.000 11.029 94.476 94.476 94.476 94.476 94.476 27.639 20.489 ms 1.645 4.285
Server Jitter 2602:80b:5000::36 (time.meme.holdings) 0.000 0.000 0.000 5.351 14.239 14.239 14.239 14.239 14.239 3.718 5.746 ms 0.828 3.761
Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) 0.000 0.000 0.000 4.593 9.349 9.349 9.349 9.349 9.349 2.587 4.904 ms -0.09123 2.375
Server Jitter 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) 0.000 0.000 0.000 1.311 2.166 2.166 2.166 2.166 2.166 0.660 1.305 ms -0.4584 2.634
Server Jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) 0.000 0.000 0.000 1.961 5.599 9.370 9.370 5.599 9.370 2.184 2.731 ms 1.202 4.547
Server Jitter 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) 0.000 0.000 0.000 3.793 7.878 7.878 7.878 7.878 7.878 2.024 4.070 ms 0.0771 3.251
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.489 0.820 1.126 3.090 13.861 32.456 196.069 12.735 31.636 8.801 4.862 ms 12.61 229.5
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.759 1.113 3.088 13.582 23.065 114.990 12.469 22.306 5.816 4.526 ms 8.216 117
Server Jitter 2606:82c0:21::e (time1.lshiy.com) 0.000 0.000 0.000 1.883 3.565 3.565 3.565 3.565 3.565 1.027 1.940 ms -0.3172 2.792
Server Jitter 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) 0.000 0.000 0.000 4.159 8.671 8.671 8.671 8.671 8.671 2.395 3.886 ms 0.1154 2.987
Server Jitter 2607:f1c0:f075:9900::1 0.000 0.000 0.000 5.383 70.431 70.431 70.431 70.431 70.431 22.237 14.508 ms 1.748 4.483
Server Jitter 2607:f298:5:101d:f816:3eff:fefd:8817 0.000 0.000 0.000 2.720 5.235 5.235 5.235 5.235 5.235 1.474 2.934 ms -0.2774 2.751
Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 0.000 1.320 2.743 34.384 84.802 102.760 242.000 82.059 101.440 27.383 36.352 ms 1.044 5.821
Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) 0.000 1.597 2.634 16.612 64.744 96.902 234.358 62.110 95.305 21.873 23.139 ms 2.428 14.88
Server Jitter 45.63.54.13 0.000 0.000 0.000 1.137 3.288 3.288 3.288 3.288 3.288 1.000 1.442 ms 0.4076 1.963
Server Jitter 66.118.231.14 0.000 0.000 0.000 1.084 4.383 4.383 4.383 4.383 4.383 1.272 1.490 ms 1.426 4.099
Server Jitter 67.217.246.204 0.000 0.000 0.000 12.593 47.481 47.481 47.481 47.481 47.481 18.695 18.270 ms 0.4955 1.478
Server Jitter 69.176.84.38 0.000 0.000 0.084 1.877 4.514 6.761 6.761 4.430 6.761 1.315 2.063 ms 1.34 5.848
Server Jitter 69.89.207.199 0.000 0.000 0.000 8.052 65.312 65.312 65.312 65.312 65.312 20.904 16.467 ms 1.566 4.007
Server Jitter 69.89.207.99 0.000 0.000 0.000 1.893 81.250 81.250 81.250 81.250 81.250 19.485 8.176 ms 3.151 11.74
Server Jitter 77.37.97.124 0.000 0.000 5.136 45.779 85.781 100.698 100.698 80.645 100.698 23.793 47.242 ms 0.00759 2.217
Server Jitter SHM(0) 0.000 0.456 0.689 1.679 3.934 5.281 93.743 3.245 4.825 1.385 1.935 ms 21.24 1165
Server Jitter SHM(1) 0.000 0.184 0.208 0.303 0.460 0.605 96.676 0.252 0.421 0.997 0.339 ms 65.96 5338
Server Jitter SHM(2) 0.000 0.672 1.001 2.461 5.817 7.607 2,002.029 4.816 6.935 26.711 3.319 ms 57.26 3478
Server Jitter SHM(3) 0.000 0.188 0.213 0.308 0.471 0.611 2,001.141 0.258 0.423 26.629 0.826 ms 57.59 3509
Server Jitter SOCK(0) 0.255 0.380 0.619 1.505 3.552 4.411 7.964 2.933 4.030 0.908 1.696 ms 1.287 5.606
Server Jitter SOCK(1) 172.539 199.329 222.140 317.030 447.723 492.978 538.233 225.583 293.649 73.141 322.241 µs 0.355 2.286
Server Jitter SOCK(2) 0.235 0.567 0.923 2.318 5.621 7.429 9.165 4.698 6.862 1.475 2.673 ms 1.195 4.598
Server Jitter SOCK(3) 152.457 191.417 216.191 314.406 445.399 479.730 542.084 229.208 288.313 71.032 318.190 µs 0.3217 2.382
Server Offset 104.131.155.175 -2.525 -2.525 -2.525 2.779 11.107 11.107 11.107 13.632 13.632 3.750 3.054 ms 0.5869 2.765
Server Offset 104.152.220.5 1.461 1.461 1.461 2.919 4.887 4.887 4.887 3.425 3.425 1.020 2.874 ms 0.6553 2.767
Server Offset 137.190.2.4 -13.886 -13.886 -13.886 73.703 432.020 432.020 432.020 445.906 445.906 141.512 93.930 ms 1.772 4.593
Server Offset 148.163.226.148 -76.672 -76.672 -76.672 2.891 6.433 6.433 6.433 83.105 83.105 25.184 -5.515 ms -2.465 7.097
Server Offset 155.248.196.28 -1.736 -1.736 -1.736 0.032 3.369 3.369 3.369 5.105 5.105 1.769 0.391 ms 0.5292 1.767
Server Offset 166.88.142.52 2.966 2.966 2.966 4.246 7.638 7.638 7.638 4.671 4.671 1.508 4.329 ms 1.273 3.521
Server Offset 172.233.177.198 -5.527 -5.527 -5.527 3.622 7.415 7.415 7.415 12.942 12.942 3.634 2.383 ms -0.9084 3.103
Server Offset 172.234.25.10 -0.488 -0.488 -0.488 0.948 5.051 5.051 5.051 5.539 5.539 1.848 1.545 ms 0.8338 2.298
Server Offset 172.234.37.140 -9.587 -9.587 -9.587 2.879 11.157 11.157 11.157 20.745 20.745 5.228 2.639 ms -0.8929 4.146
Server Offset 194.0.5.123 -3.549 -3.333 -2.021 0.711 3.049 5.915 6.281 5.070 9.248 1.611 0.678 ms 0.3202 4.501
Server Offset 2001:559:2be:3::1001 2.838 2.838 2.838 6.118 9.658 9.658 9.658 6.820 6.820 2.006 6.562 ms -0.1996 2.201
Server Offset 2001:678:8::123 (any.time.nl) -56.834 -30.249 -15.716 -6.510 -2.731 0.765 5.894 12.985 31.014 5.608 -7.483 ms -4.421 34.13
Server Offset 23.111.186.186 0.800 0.800 0.800 2.292 3.617 3.617 3.617 2.817 2.817 0.849 2.280 ms -0.2598 2.078
Server Offset 23.155.40.38 -6.002 -6.002 -4.912 -2.083 2.268 3.591 3.591 7.180 9.593 2.109 -1.817 ms 0.6088 3.28
Server Offset 23.186.168.129 -23.022 -23.022 -23.022 79.126 423.814 423.814 423.814 446.837 446.837 122.871 79.712 ms 2.037 6.27
Server Offset 23.186.168.130 -4.461 -4.461 -4.461 -2.134 7.796 7.796 7.796 12.257 12.257 3.265 -1.278 ms 1.43 4.608
Server Offset 23.186.168.131 -3.617 -3.617 -3.617 0.658 4.423 4.423 4.423 8.040 8.040 1.815 0.563 ms -0.185 4.155
Server Offset 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) -70.714 -47.724 -33.815 -10.046 26.468 30.320 33.265 60.283 78.044 14.535 -10.605 ms 0.5037 6.049
Server Offset 240b:4004:108:200:8314:1a08:4cee:26d8 -10.660 -10.660 -1.669 2.211 424.412 425.724 425.724 426.080 436.384 113.328 48.896 ms 2.876 9.733
Server Offset 240b:4004:108:200:8314:1a08:4cee:2acf -55.272 -55.272 -55.272 0.474 2.640 2.640 2.640 57.912 57.912 17.808 -5.000 ms -2.456 7.073
Server Offset 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com) -26.834 -16.012 -8.969 1.963 6.113 8.686 10.839 15.082 24.697 4.691 1.079 ms -2.114 9.97
Server Offset 2600:1f13:2c1:2e00::be00:5 1.672 1.672 1.672 5.591 19.969 19.969 19.969 18.297 18.297 5.131 6.284 ms 1.945 5.754
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) -29.237 -8.071 -6.721 -2.782 2.970 4.626 110.743 9.692 12.697 4.208 -2.520 ms 11.24 254.3
Server Offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) -23.935 -6.970 -4.877 -0.514 5.276 6.669 422.200 10.153 13.639 7.681 -0.237 ms 39.48 2107
Server Offset 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) -35.802 -20.283 -7.449 -0.804 5.355 7.399 415.823 12.804 27.682 8.424 -0.805 ms 29.04 1392
Server Offset 2600:1f18:7927:8b00:123:: 4.710 4.710 4.710 6.720 8.399 8.399 8.399 3.689 3.689 1.160 6.461 ms 0.06963 2.058
Server Offset 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com) -16.936 -16.936 -5.885 2.642 423.840 424.816 424.816 429.725 441.752 116.114 50.434 ms 2.724 8.986
Server Offset 2600:3c01:e000:7e6::123 (time1.sigi.net) -0.759 -0.759 -0.759 2.211 3.558 3.558 3.558 4.317 4.317 1.267 1.976 ms -1.099 3.486
Server Offset 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) -24.915 -24.915 -24.915 67.309 423.497 423.497 423.497 448.412 448.412 136.652 85.591 ms 1.84 4.92
Server Offset 2602:80b:5000::36 (time.meme.holdings) -0.850 -0.850 -0.850 3.327 13.389 13.389 13.389 14.239 14.239 3.855 4.450 ms 1.162 3.726
Server Offset 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) -2.396 -2.396 -2.396 0.924 11.083 11.083 11.083 13.479 13.479 4.287 2.602 ms 0.7321 2.194
Server Offset 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) 4.298 4.298 4.298 6.373 7.842 7.842 7.842 3.544 3.544 1.099 6.237 ms -0.09612 2.22
Server Offset 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) -2.937 -2.937 -1.379 2.434 7.512 9.493 9.493 8.892 12.430 2.905 2.389 ms 0.4696 3.021
Server Offset 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) -1.370 -1.370 -1.370 3.697 9.921 9.921 9.921 11.292 11.292 2.854 4.172 ms 0.1428 3.178
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -10.517 -7.412 -5.892 -1.611 5.485 7.351 10.236 11.377 14.763 3.494 -1.141 ms 0.474 2.627
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -30.959 -5.033 -3.983 -0.834 3.885 6.307 429.230 7.867 11.340 19.462 0.516 ms 20.37 438.5
Server Offset 2606:82c0:21::e (time1.lshiy.com) -0.347 -0.347 -0.347 2.470 5.026 5.026 5.026 5.373 5.373 1.632 2.157 ms 0.07044 2.391
Server Offset 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) -1.407 -1.407 -1.407 3.805 10.246 10.246 10.246 11.653 11.653 3.063 4.635 ms -0.1037 3.023
Server Offset 2607:f1c0:f075:9900::1 -11.364 -11.364 -11.364 62.462 429.472 429.472 429.472 440.836 440.836 142.546 88.428 ms 1.844 4.744
Server Offset 2607:f298:5:101d:f816:3eff:fefd:8817 1.052 1.052 1.052 3.678 8.611 8.611 8.611 7.559 7.559 2.139 4.559 ms 0.3897 2.465
Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) -90.881 -26.556 -11.995 -1.256 4.735 6.953 425.774 16.730 33.510 13.737 -1.574 ms 23.69 737
Server Offset 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) -75.694 -15.935 -5.578 -1.716 1.484 3.368 106.144 7.062 19.302 4.688 -2.006 ms 2.228 203.8
Server Offset 45.63.54.13 2.092 2.092 2.092 4.924 6.910 6.910 6.910 4.818 4.818 1.426 4.715 ms -0.0539 2.339
Server Offset 66.118.231.14 -0.952 -0.952 -0.952 0.349 4.672 4.672 4.672 5.623 5.623 1.689 0.982 ms 1.225 3.534
Server Offset 67.217.246.204 -11.181 -11.181 -11.181 47.769 423.145 423.145 423.145 434.326 434.326 174.280 121.772 ms 1.099 2.292
Server Offset 69.176.84.38 -4.887 -4.887 -3.512 1.450 3.073 4.499 4.499 6.585 9.386 2.266 0.622 ms -0.718 2.493
Server Offset 69.89.207.199 -11.403 -11.403 -11.403 44.730 425.249 425.249 425.249 436.653 436.653 139.058 78.387 ms 1.964 5.196
Server Offset 69.89.207.99 -82.728 -82.728 -82.728 -0.965 3.942 3.942 3.942 86.670 86.670 19.565 -5.202 ms -3.631 14.51
Server Offset 77.37.97.124 -28.059 -28.059 -10.002 5.495 11.506 23.808 23.808 21.508 51.867 6.958 3.767 ms -1.571 8.198
Server Offset SHM(0) -193.907 -188.372 -186.103 -179.313 -122.306 -118.880 -66.245 63.798 69.492 19.014 -173.033 ms 2.158 6.006
Server Offset SHM(1) -43.998 -8.849 -8.482 -5.910 -3.472 -2.078 52.678 5.010 6.771 1.954 -5.926 ms 1.16 52.68
Server Offset SHM(2) -192.688 -184.315 -179.668 -168.955 -151.228 -145.886 1,940.513 28.440 38.429 22.592 -168.004 ms 80.09 7303
Server Offset SHM(3) -13.801 -8.901 -8.551 -5.956 -3.532 -2.164 2,061.810 5.019 6.737 20.823 -5.762 ms 96.08 9315
Server Offset SOCK(0) -180.583 -178.322 -176.181 -172.068 -168.305 -166.725 -164.264 7.876 11.596 2.460 -172.140 ms -0.1743 3.087
Server Offset SOCK(1) -489.762 -433.183 -386.296 -29.022 302.627 386.991 466.635 688.923 820.174 232.318 -16.223 µs -0.07358 1.719
Server Offset SOCK(2) -181.156 -178.007 -173.059 -163.641 -157.179 -155.100 -151.658 15.880 22.907 4.872 -164.199 ms -0.5505 3.26
Server Offset SOCK(3) -560.863 -493.512 -438.746 -81.107 236.850 326.708 408.839 675.596 820.220 229.645 -76.459 µs -0.1042 1.712
TDOP 0.490 0.520 0.600 0.880 1.450 2.110 2.520 0.850 1.590 0.273 0.932 1.771 8.528
Temp /dev/sda 18.000 18.000 20.000 25.000 26.000 26.000 36.000 6.000 8.000 2.072 24.023 °C
Temp LM0 29.000 31.000 32.000 40.000 45.000 47.000 50.000 13.000 16.000 4.175 38.994 °C
Temp LM1 27.000 28.000 29.000 30.000 39.000 39.000 41.000 10.000 11.000 2.525 30.800 °C
Temp LM2 0.000 19.000 19.000 34.000 35.000 36.000 45.000 16.000 17.000 4.696 32.421 °C
Temp LM3 29.000 29.000 31.000 38.000 39.000 40.000 44.000 8.000 11.000 2.149 37.421 °C
Temp LM4 0.000 0.000 0.000 0.000 40.000 44.000 54.000 40.000 44.000 11.373 3.548 °C
Temp LM5 27.000 28.000 29.000 30.000 31.000 33.000 40.000 2.000 5.000 0.908 30.147 °C
Temp LM6 29.000 31.000 31.000 33.000 34.000 35.000 45.000 3.000 4.000 1.004 32.717 °C
Temp LM7 31.000 33.000 33.000 35.000 36.000 37.000 46.000 3.000 4.000 1.069 34.563 °C
Temp LM8 31.000 33.000 33.000 35.000 36.000 37.000 46.000 3.000 4.000 1.079 34.578 °C
Temp LM9 31.000 33.000 33.000 35.000 36.000 37.000 46.000 3.000 4.000 1.079 34.578 °C
Temp ZONE0 20.000 20.000 20.000 20.000 20.000 20.000 20.000 0.000 0.000 0.000 20.000 °C
Temp ZONE1 30.000 32.000 32.000 34.000 35.000 37.000 45.000 3.000 5.000 1.017 33.800 °C
Temp ZONE2 27.000 28.000 29.000 30.000 31.000 33.000 40.000 2.000 5.000 0.905 30.144 °C
Temp ZONE3 30.000 32.000 32.000 34.000 35.000 37.000 47.000 3.000 5.000 1.035 33.806 °C
Temp ZONE4 30.000 32.000 32.000 34.000 35.000 37.000 45.000 3.000 5.000 1.017 33.800 °C
Temp ZONE5 29.000 31.000 32.000 40.000 45.000 47.000 54.000 13.000 16.000 4.040 39.522 °C
Temp ZONE6 27.000 28.000 29.000 30.000 31.000 33.000 40.000 2.000 5.000 0.910 30.139 °C
nSats 8.000 8.000 9.000 11.000 13.000 14.000 16.000 4.000 6.000 1.296 11.128 nSat 0.2123 2.936
Summary as CSV file

Stats for the last 1, 7, 35, 98, 371, some days, or live gps data.

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!