NTPsec

Dell-2018

Report generated: Sat Mar 21 15:47:37 2026 UTC
Start Time: Wed Mar 12 15:46:26 2025 UTC
End Time: Sat Mar 21 15:46:26 2026 UTC
Report Period: 374.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 -126.620 -8.242 -6.377 -0.190 0.632 1.126 121.205 7.009 9.368 2.606 -1.455 ms 0.1579 185
Local Clock Frequency Offset -135.511 10.466 10.679 11.252 22.076 25.283 135.754 11.397 14.816 4.103 13.582 ppm 1.186 13.38

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.135 0.168 0.382 0.899 1.397 83.702 0.731 1.262 0.926 0.444 ms 44.15 2510

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.0032 0.0039 0.0131 0.299 0.496 73.177 0.295 0.493 0.609 0.082 ppm 71.16 6158

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 -126.620 -8.242 -6.377 -0.190 0.632 1.126 121.205 7.009 9.368 2.606 -1.455 ms 0.1579 185

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 10.466 10.679 11.252 22.076 25.283 135.754 11.397 14.816 4.103 13.582 ppm 1.186 13.38
Temp /dev/sda 17.000 18.000 20.000 25.000 26.000 28.000 39.000 6.000 10.000 2.245 24.146 °C
Temp LM0 26.000 31.000 32.000 34.000 40.000 45.000 54.000 8.000 14.000 2.521 34.260 °C
Temp LM1 27.000 28.000 30.000 38.000 39.000 40.000 46.000 9.000 12.000 2.850 36.876 °C
Temp LM2 0.000 0.000 0.000 19.000 34.000 34.000 45.000 34.000 34.000 6.856 19.680 °C
Temp LM3 26.000 27.000 28.000 30.000 38.000 39.000 44.000 10.000 12.000 2.803 30.999 °C
Temp LM4 0.000 0.000 0.000 32.000 42.000 46.000 56.000 42.000 46.000 11.918 29.839 °C
Temp LM5 25.000 27.000 28.000 30.000 32.000 33.000 44.000 4.000 6.000 1.193 29.980 °C
Temp LM6 27.000 30.000 30.000 32.000 34.000 36.000 50.000 4.000 6.000 1.358 32.383 °C
Temp LM7 29.000 31.000 32.000 34.000 36.000 37.000 51.000 4.000 6.000 1.340 34.204 °C
Temp LM8 26.800 31.000 33.000 35.000 37.000 37.000 51.000 4.000 6.000 1.357 34.548 °C
Temp LM9 26.800 31.000 33.000 35.000 37.000 37.000 51.000 4.000 6.000 1.357 34.548 °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 26.800 31.000 32.000 34.000 36.000 37.000 51.000 4.000 6.000 1.351 33.656 °C
Temp ZONE2 25.000 27.000 28.000 30.000 32.000 33.000 44.000 4.000 6.000 1.193 29.980 °C
Temp ZONE3 29.000 31.000 32.000 34.000 36.000 37.000 51.000 4.000 6.000 1.351 33.661 °C
Temp ZONE4 26.800 31.000 32.000 34.000 36.000 37.000 51.000 4.000 6.000 1.351 33.656 °C
Temp ZONE5 27.000 29.000 30.000 32.000 43.000 47.000 56.000 13.000 18.000 4.431 34.598 °C
Temp ZONE6 26.000 27.000 28.000 30.000 32.000 33.000 44.000 4.000 6.000 1.184 29.996 °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 6.000 8.000 9.000 10.000 13.000 14.000 16.000 4.000 6.000 1.278 10.618 nSat 0.3197 3.496
TDOP 0.490 0.560 0.630 0.920 11.810 11.810 11.810 11.180 11.250 3.148 1.999 2.733 8.646

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 -1.209 5.368 12.615 16.334 16.334 13.824 18.859 4.610 5.570 ms 0.3612 2.585

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 104.167.215.195

peer offset 104.167.215.195 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.167.215.195 -99.469 -99.469 -99.469 -96.402 -95.938 -95.938 -95.938 3.532 3.532 1.166 -97.068 ms -1.222 3.199

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

peer offset 104.167.241.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.167.241.253 -1.130 -1.130 -1.130 3.827 174.956 174.956 174.956 176.087 176.087 77.809 54.544 ms 0.8304 1.696

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

peer offset 104.234.61.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.234.61.117 -19.828 -4.247 2.476 5.088 7.186 8.098 10.357 4.710 12.345 2.148 4.871 ms -4.632 41.14

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 108.61.73.243

peer offset 108.61.73.243 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 108.61.73.243 -4.642 0.171 2.587 5.083 7.301 8.231 12.202 4.714 8.059 1.563 5.056 ms -0.9729 8.127

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 12.71.198.242

peer offset 12.71.198.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 12.71.198.242 -567.986 -567.986 -567.986 -8.926 5.527 5.527 5.527 573.513 573.513 281.819 -249.816 ms -0.223 1.051

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 129.146.193.200

peer offset 129.146.193.200 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 129.146.193.200 -0.800 0.856 1.480 4.811 6.531 7.695 8.742 5.051 6.839 1.487 4.576 ms -0.7309 4.259

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 131.239.5.43

peer offset 131.239.5.43 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 131.239.5.43 0.782 0.782 0.782 4.026 4.797 4.797 4.797 4.014 4.014 1.405 3.356 ms -1.032 2.322

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 135.148.100.14

peer offset 135.148.100.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 135.148.100.14 -31.469 -1.302 3.035 6.034 8.883 103.460 109.098 5.848 104.763 17.769 8.674 ms 4.727 26.05

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

peer offset 137.110.222.27 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 137.110.222.27 2.083 2.083 3.615 5.797 9.449 10.485 10.485 5.834 8.402 1.558 5.893 ms 0.5532 4.579

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 139.177.202.26

peer offset 139.177.202.26 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 139.177.202.26 2.369 2.369 2.369 5.594 13.217 13.217 13.217 10.848 10.848 3.941 6.958 ms 0.6 1.806

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 139.84.137.244

peer offset 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 139.84.137.244 -88.151 -18.896 -1.976 8.174 12.866 16.588 23.798 14.843 35.484 6.651 6.780 ms -4.531 43.03

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 139.94.144.123

peer offset 139.94.144.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 139.94.144.123 7.327 7.327 7.327 7.569 8.239 8.239 8.239 0.913 0.913 0.357 7.696 ms 0.4162 1.533

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 141.11.234.198

peer offset 141.11.234.198 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 141.11.234.198 -23.184 -23.184 -23.184 3.651 11.780 11.780 11.780 34.964 34.964 8.939 0.688 ms -1.28 4.6

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

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

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

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



Server Offset 141.11.89.193

peer offset 141.11.89.193 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 141.11.89.193 2.147 2.147 2.147 3.363 5.337 5.337 5.337 3.190 3.190 1.124 3.580 ms 0.1122 1.688

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 142.202.190.19

peer offset 142.202.190.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 142.202.190.19 -170.488 -170.488 -169.889 6.947 228.113 229.915 229.915 398.002 400.403 122.650 52.253 ms 0.2226 2.25

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 144.202.0.197

peer offset 144.202.0.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.202.0.197 2.542 2.542 2.542 5.206 10.116 10.116 10.116 7.574 7.574 1.946 5.495 ms 0.6649 3.455

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 144.202.62.209

peer offset 144.202.62.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.202.62.209 -2.931 -2.931 -1.517 0.876 6.180 36.327 36.327 7.696 39.258 5.627 1.903 ms 5.12 30.38

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 144.202.66.214

peer offset 144.202.66.214 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.202.66.214 -94.866 -94.866 -94.866 -89.704 -88.958 -88.958 -88.958 5.908 5.908 2.060 -91.017 ms -0.812 2.336

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 149.248.12.167

peer offset 149.248.12.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.248.12.167 6.974 6.974 6.974 12.448 13.486 13.486 13.486 6.511 6.511 2.871 10.594 ms -0.3694 1.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 149.28.200.179

peer offset 149.28.200.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.28.200.179 1.712 1.712 3.167 5.584 10.014 25.332 25.332 6.847 23.620 3.335 5.924 ms 4.121 23.91

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 149.28.61.105

peer offset 149.28.61.105 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.28.61.105 2.916 2.916 2.916 5.252 8.017 8.017 8.017 5.100 5.100 1.667 5.088 ms 0.4936 2.163

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 15.204.198.96

peer offset 15.204.198.96 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 15.204.198.96 -806.440 -806.440 -15.115 0.763 4.729 8.189 8.189 19.845 814.629 169.536 -36.913 ms -4.304 19.54

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

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

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

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



Server Offset 15.204.87.223

peer offset 15.204.87.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 15.204.87.223 -10.681 -10.681 -8.344 2.175 164.825 164.832 164.832 173.170 175.513 65.332 29.557 ms 1.56 3.461

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 158.51.99.19

peer offset 158.51.99.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 158.51.99.19 -157.868 -3.714 0.315 3.544 6.019 8.972 238.853 5.704 12.686 14.413 4.009 ms 11.84 228.2

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

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

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

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



Server Offset 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -4.289 -1.565 3.446 6.207 8.276 9.113 9.909 4.830 10.678 1.742 6.046 ms -1.815 10.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 162.159.200.123

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 -6.062 -6.062 -5.886 -0.049 7.264 9.110 9.110 13.149 15.172 4.421 0.662 ms 0.1749 1.786

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 163.123.152.14

peer offset 163.123.152.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 163.123.152.14 8.299 8.299 8.299 9.300 12.567 12.567 12.567 4.268 4.268 1.664 9.751 ms 0.9993 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 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 170.187.147.56

peer offset 170.187.147.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 170.187.147.56 -0.641 -0.241 1.518 4.094 6.492 7.541 8.261 4.974 7.782 1.471 4.099 ms -0.1755 3.293

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 171.66.97.126

peer offset 171.66.97.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 171.66.97.126 -5.352 -3.209 -1.979 0.739 2.487 3.087 4.376 4.466 6.297 1.429 0.549 ms -0.8383 4.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 172.232.15.202

peer offset 172.232.15.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.232.15.202 0.710 0.710 0.710 4.702 38.555 38.555 38.555 37.846 37.846 15.838 13.311 ms 0.9197 1.889

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

peer offset 172.233.153.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.153.85 -9.447 -9.196 -7.932 -3.852 1.978 2.524 2.830 9.910 11.720 3.072 -3.587 ms 0.398 2.315

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

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

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

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



Server Offset 172.233.157.223

peer offset 172.233.157.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.157.223 -4.047 -4.047 -4.047 3.553 5.955 5.955 5.955 10.002 10.002 3.165 2.404 ms -1.04 2.663

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 3.459 5.884 5.884 5.884 6.372 6.372 2.046 2.970 ms -0.3216 1.683

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 4.151 11.157 11.157 11.157 20.745 20.745 4.913 3.204 ms -0.9547 3.843

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

peer offset 172.234.44.141 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.44.141 -1.177 -1.177 -1.177 4.942 9.373 9.373 9.373 10.549 10.549 3.559 3.891 ms -0.2618 1.724

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

peer offset 172.235.60.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.235.60.8 0.376 0.376 0.376 3.004 16.005 16.005 16.005 15.630 15.630 4.175 4.760 ms 1.627 4.998

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 173.249.203.227

peer offset 173.249.203.227 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.249.203.227 2.418 2.418 2.418 7.578 11.331 11.331 11.331 8.912 8.912 2.607 6.865 ms -0.2799 2.399

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 173.255.192.10

peer offset 173.255.192.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.255.192.10 -0.501 -0.501 -0.501 8.854 11.145 11.145 11.145 11.646 11.646 3.481 7.479 ms -1.158 3.37

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 173.255.255.133

peer offset 173.255.255.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.255.255.133 -1.715 -1.715 -1.715 -0.964 1.511 1.511 1.511 3.226 3.226 1.274 -0.647 ms 1.007 2.214

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 178.156.185.92

peer offset 178.156.185.92 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.156.185.92 -26.222 -8.831 -4.147 -0.703 5.776 8.694 15.799 9.923 17.525 3.089 -0.428 ms -0.01771 10.84

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 192.48.105.15

peer offset 192.48.105.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.48.105.15 0.449 0.449 0.449 3.200 7.335 7.335 7.335 6.885 6.885 1.829 3.297 ms 0.5249 2.601

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 193.29.63.226

peer offset 193.29.63.226 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 193.29.63.226 -97.166 -97.166 -95.281 0.589 7.015 9.170 9.170 102.297 106.336 42.310 -21.757 ms -1.137 2.322

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 -26.524 -5.524 -3.127 0.453 3.676 5.839 37.622 6.802 11.362 2.403 0.436 ms 0.8841 23.44

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 198.137.202.32

peer offset 198.137.202.32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.137.202.32 -1.462 -1.396 1.619 5.827 7.932 11.548 12.433 6.313 12.944 1.882 5.599 ms -0.7187 6.807

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 198.199.14.19

peer offset 198.199.14.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.199.14.19 -4.168 -4.168 -4.168 3.527 9.207 9.207 9.207 13.374 13.374 3.647 3.201 ms -0.3311 2.34

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

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

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

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



Server Offset 198.211.103.209

peer offset 198.211.103.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.211.103.209 -15.435 -15.435 -7.248 1.023 11.374 11.645 11.645 18.622 27.080 5.487 1.111 ms -0.25 4.025

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 198.46.254.130

peer offset 198.46.254.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.46.254.130 -2.287 0.292 2.403 4.430 9.560 11.525 16.197 7.157 11.234 2.139 4.805 ms 1.192 5.984

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 198.60.22.240

peer offset 198.60.22.240 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.60.22.240 -144.129 -144.129 -144.129 9.541 18.010 18.010 18.010 162.140 162.140 65.641 -23.178 ms -1.269 2.625

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 199.68.201.235

peer offset 199.68.201.235 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 199.68.201.235 2.195 2.195 2.320 4.878 7.295 9.614 9.614 4.975 7.419 1.530 4.830 ms 1.056 5.383

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:1600:13:101::16b7 (ov-eaae4e.infomaniak.ch)

peer offset 2001:1600:13:101::16b7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:1600:13:101::16b7 (ov-eaae4e.infomaniak.ch) -48.803 -25.492 -13.939 -1.873 9.982 15.177 36.277 23.921 40.669 7.350 -1.722 ms -1.042 9.167

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:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net)

peer offset 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) 0.214 2.406 3.442 5.288 7.200 7.864 9.487 3.758 5.458 1.200 5.303 ms -0.1227 3.446

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:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com)

peer offset 2001:19f0:1590:5123:1057:a11:da7a:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) 0.989 0.989 0.989 6.668 7.419 7.419 7.419 6.430 6.430 2.339 5.470 ms -1.22 2.835

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:19f0:6401:400:5400:4ff:fec3:522a

peer offset 2001:19f0:6401:400:5400:4ff:fec3:522a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:19f0:6401:400:5400:4ff:fec3:522a 2.311 2.311 2.311 4.048 6.282 6.282 6.282 3.971 3.971 1.514 3.891 ms 0.635 1.891

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:418:3ff::53 (x.ns.gin.ntt.net)

peer offset 2001:418:3ff::53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:418:3ff::53 (x.ns.gin.ntt.net) 4.247 4.247 4.247 7.231 8.571 8.571 8.571 4.324 4.324 1.678 6.539 ms -0.2545 1.376

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:418:8405:4002::12

peer offset 2001:418:8405:4002::12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:418:8405:4002::12 -281.832 -281.832 -281.832 6.130 43.679 43.679 43.679 325.511 325.511 75.678 -13.076 ms -3.151 11.39

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:41d0:303:65e9::1 (matthaeus.julia0815.de)

peer offset 2001:41d0:303:65e9::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:41d0:303:65e9::1 (matthaeus.julia0815.de) -150.721 -116.304 -14.598 3.013 11.624 159.827 305.196 26.222 276.131 26.191 2.233 ms 3.209 53

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

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

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

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



Server Offset 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de)

peer offset 2001:470:1f07:198::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) -43.336 -25.868 -0.459 3.003 5.329 102.804 104.408 5.787 128.672 14.038 4.377 ms 5.842 42.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 2001:470:1f07:24f::123

peer offset 2001:470:1f07:24f::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:1f07:24f::123 5.692 5.692 5.692 8.660 52.245 52.245 52.245 46.552 46.552 15.577 16.463 ms 1.347 3.154

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

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

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

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



Server Offset 2001:470:1f2c:60:123:123:123:123

peer offset 2001:470:1f2c:60:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:1f2c:60:123:123:123:123 -34.941 -34.941 -34.941 5.417 179.029 179.029 179.029 213.970 213.970 83.019 55.085 ms 0.6389 1.528

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

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

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

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



Server Offset 2001:470:a:b4::2 (dell-2018.jamesb912.com.)

peer offset 2001:470:a:b4::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:a:b4::2 (dell-2018.jamesb912.com.) -4.391 -4.391 -4.391 -4.391 -4.391 -4.391 -4.391 0.000 0.000 0.000 -4.391 ms nan nan

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

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

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

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



Server Offset 2001:470:e8dc:10::123

peer offset 2001:470:e8dc:10::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e8dc:10::123 -0.028 0.001 0.004 0.006 0.009 0.012 589.091 0.005 0.011 29.528 1.490 s 19.85 395

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:4998:58:183a::1000 (t2.time.bf1.yahoo.com)

peer offset 2001:4998:58:183a::1000 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) -809.971 -4.133 0.925 5.173 7.699 8.851 11.403 6.774 12.984 41.024 2.773 ms -19.54 384.4

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:4998:c:1028::1001 (t2.time.gq1.yahoo.com)

peer offset 2001:4998:c:1028::1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) -157.180 0.965 3.243 5.473 7.719 9.995 23.242 4.475 9.030 5.538 5.305 ms -26.07 749.2

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

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

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

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



Server Offset 2001:558:6014:17:8dc5:5575:5560:2cb6

peer offset 2001:558:6014:17:8dc5:5575:5560:2cb6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:558:6014:17:8dc5:5575:5560:2cb6 -281.200 -281.200 -126.154 4.670 171.115 172.773 172.773 297.269 453.972 76.160 7.959 ms -0.5863 8.15

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 -175.433 -175.433 -170.364 5.851 9.897 9.897 9.897 180.261 185.330 63.479 -23.583 ms -1.838 4.527

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) -421.375 -23.078 -11.859 -6.573 -3.217 0.122 589.234 8.642 23.200 9.862 -7.007 ms 19.14 1842

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

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

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

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



Server Offset 204.197.163.71

peer offset 204.197.163.71 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.197.163.71 -173.244 -1.861 0.406 2.637 4.342 5.127 14.383 3.936 6.988 8.636 2.114 ms -19.71 398.6

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

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

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

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



Server Offset 205.233.73.201

peer offset 205.233.73.201 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 205.233.73.201 -18.156 -18.156 -18.156 216.632 221.908 221.908 221.908 240.064 240.064 91.085 175.240 ms -1.648 3.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 208.113.130.146

peer offset 208.113.130.146 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 208.113.130.146 -807.971 -2.044 0.597 5.657 8.325 10.241 17.688 7.728 12.286 41.108 3.295 ms -19.54 384.2

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

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

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

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



Server Offset 208.67.72.43

peer offset 208.67.72.43 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 208.67.72.43 -45.246 -45.246 -45.246 -2.385 1.915 1.915 1.915 47.161 47.161 14.659 -6.938 ms -2.157 5.869

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 208.67.75.242

peer offset 208.67.75.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 208.67.75.242 -0.073 -0.073 -0.073 236.434 240.553 240.553 240.553 240.627 240.627 102.360 178.355 ms -1.154 2.333

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 216.229.4.66

peer offset 216.229.4.66 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.229.4.66 4.248 4.248 4.248 5.386 9.274 9.274 9.274 5.026 5.026 2.013 5.863 ms 1.013 2.211

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 216.229.4.69

peer offset 216.229.4.69 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.229.4.69 -565.822 -565.822 -561.261 0.035 3.427 7.531 7.531 564.688 573.353 217.192 -101.392 ms -1.65 3.722

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 216.250.115.174

peer offset 216.250.115.174 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.250.115.174 -11.971 -11.971 -11.971 -5.891 28.323 28.323 28.323 40.294 40.294 16.772 2.897 ms 0.6802 1.539

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

peer offset 23.131.160.7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.131.160.7 -4.498 1.315 2.765 5.400 7.474 8.521 12.984 4.710 7.206 1.459 5.342 ms -0.3744 5.119

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

peer offset 23.141.40.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.141.40.123 27.455 27.455 27.455 33.456 37.132 37.132 37.132 9.678 9.678 2.992 32.642 ms -0.3048 2.39

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

peer offset 23.142.248.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.142.248.8 8.594 8.594 8.594 10.977 11.802 11.802 11.802 3.207 3.207 1.009 10.550 ms -0.8827 2.771

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

peer offset 23.142.248.9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.142.248.9 -2.218 -2.218 -2.218 5.858 8.228 8.228 8.228 10.447 10.447 3.416 4.133 ms -0.3834 1.785

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

peer offset 23.143.196.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.143.196.199 2.248 2.248 2.248 3.906 5.387 5.387 5.387 3.139 3.139 1.032 4.058 ms -0.2914 2.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 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 -288.208 -156.059 -4.815 1.534 4.285 10.104 18.366 9.100 166.163 22.289 -1.539 ms -9.379 102

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

peer offset 23.186.168.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.123 -3.755 -1.507 0.222 2.615 4.450 5.651 13.437 4.228 7.158 1.430 2.525 ms -0.02099 7.779

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

peer offset 23.186.168.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.126 -5.345 -3.200 -1.287 1.767 4.438 5.722 166.185 5.726 8.922 10.343 2.300 ms 15.19 239

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

peer offset 23.186.168.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.127 2.017 2.017 2.017 5.113 8.863 8.863 8.863 6.846 6.846 2.456 5.105 ms 0.3935 1.998

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

peer offset 23.186.168.128 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.128 -571.345 -2.646 0.616 3.786 5.861 6.834 11.189 5.245 9.479 32.846 1.503 ms -16.49 282.6

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

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

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

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



Server Offset 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 -1.996 -0.428 2.998 5.842 7.926 423.814 6.270 9.922 13.136 3.517 ms 27.32 851.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 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.284 0.164 5.449 7.796 7.796 9.733 12.257 3.707 0.733 ms 0.06193 1.677

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 -4.751 -0.429 1.142 3.700 5.655 6.700 10.070 4.513 7.129 1.408 3.624 ms -0.5634 5.686

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

peer offset 23.186.168.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.132 -9.048 -5.203 -2.855 3.480 5.818 6.967 9.350 8.673 12.170 2.449 3.014 ms -1.598 6.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 23.95.49.216

peer offset 23.95.49.216 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.95.49.216 -5.139 -2.109 0.660 3.522 5.991 7.369 10.716 5.332 9.478 1.730 3.430 ms -0.7082 6.455

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) -78.463 -36.395 -20.979 -11.546 -3.410 27.956 685.845 17.569 64.351 13.179 -11.475 ms 30.75 1614

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 2402:1f00:8101:d6::1

peer offset 2402:1f00:8101:d6::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2402:1f00:8101:d6::1 -36.205 -6.436 12.070 35.428 47.477 49.168 69.786 35.407 55.604 12.669 33.985 ms -1.139 5.04

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:4002:100:9f00:5bd1:9512:8a8b:25e

peer offset 240b:4002:100:9f00:5bd1:9512:8a8b:25e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 240b:4002:100:9f00:5bd1:9512:8a8b:25e 1.797 1.797 1.797 4.344 8.047 8.047 8.047 6.249 6.249 2.182 4.694 ms 0.2446 1.809

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:26d6

peer offset 240b:4004:108:200:8314:1a08:4cee:26d6 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:26d6 -53.252 -30.228 -3.522 4.633 7.430 9.190 16.676 10.952 39.418 6.135 3.553 ms -4.789 30.29

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:26d9

peer offset 240b:4004:108:200:8314:1a08:4cee:26d9 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:26d9 3.332 3.332 3.332 5.399 14.354 14.354 14.354 11.022 11.022 4.410 6.823 ms 1.061 2.259

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:1700:5455:a70::7b:1

peer offset 2600:1700:5455:a70::7b:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1700:5455:a70::7b:1 -809.818 -809.818 -802.944 -1.720 6.474 21.994 21.994 809.418 831.812 176.723 -42.075 ms -4.096 17.79

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:1702:7400:9ac0::314:5a

peer offset 2600:1702:7400:9ac0::314:5a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1702:7400:9ac0::314:5a 0.498 0.498 0.498 13.966 17.731 17.731 17.731 17.233 17.233 5.163 12.245 ms -1.274 3.293

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:1702:7400:9ac0::5b

peer offset 2600:1702:7400:9ac0::5b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1702:7400:9ac0::5b 0.162 0.162 0.162 8.450 11.368 11.368 11.368 11.206 11.206 3.725 6.660 ms -0.2939 1.735

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:1702:80c0:9a80:1ee4:b0a2:44bc:c606

peer offset 2600:1702:80c0:9a80:1ee4:b0a2:44bc:c606 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1702:80c0:9a80:1ee4:b0a2:44bc:c606 7.543 7.543 7.543 43.369 48.456 48.456 48.456 40.913 40.913 18.767 27.247 ms 0.02285 1.042

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) -90.591 -30.497 -16.610 2.198 7.128 11.479 312.713 23.738 41.976 8.531 0.406 ms 1.915 169.9

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

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

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

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



Server Offset 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 -282.490 -1.401 3.361 6.350 9.277 21.057 75.600 5.916 22.458 11.306 6.295 ms -17.94 473.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 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) -155.691 -7.425 -5.731 3.067 6.244 8.116 110.743 11.974 15.541 4.932 1.630 ms -2.613 232.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 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) -159.116 -7.028 -3.909 3.387 6.614 8.454 422.200 10.523 15.482 6.360 2.442 ms 19.34 1705

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) -158.177 -23.587 -5.987 3.740 7.368 9.926 415.823 13.355 33.513 7.678 2.179 ms 9.969 765.7

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

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

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

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



Server Offset 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:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net)

peer offset 2600:3c00:e000:256::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) -3.406 -0.600 0.655 2.836 5.300 6.968 12.235 4.645 7.567 1.502 2.902 ms 0.4361 5.418

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:3c00:e000:318::1 (jane.qotw.net)

peer offset 2600:3c00:e000:318::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c00:e000:318::1 (jane.qotw.net) -28.246 -0.004 1.379 3.315 5.169 6.398 10.314 3.789 6.402 1.515 3.268 ms -6.661 141.7

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

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

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

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



Server Offset 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw)

peer offset 2600:3c01::f03c:93ff:fe5b:8a7d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) 2.725 2.725 2.725 5.114 14.625 14.625 14.625 11.900 11.900 4.070 5.808 ms 1.545 3.777

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) -170.467 0.056 3.237 5.672 7.881 8.850 11.725 4.644 8.794 9.635 5.092 ms -17.71 322.2

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

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

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

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



Server Offset 2600:3c02::f03c:94ff:fe59:f411

peer offset 2600:3c02::f03c:94ff:fe59:f411 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c02::f03c:94ff:fe59:f411 3.748 3.748 3.748 6.064 12.748 12.748 12.748 9.000 9.000 3.879 7.163 ms 0.6006 1.484

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:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net)

peer offset 2600:3c02:e000:bc::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) 0.867 0.867 1.114 3.790 6.386 7.915 7.915 5.272 7.048 1.512 3.637 ms 0.418 3.502

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:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net)

peer offset 2600:3c02:e001:1d00::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) -572.795 -572.795 -572.795 -9.263 4.262 4.262 4.262 577.057 577.057 280.556 -253.542 ms -0.2234 1.051

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 2600:3c03::f03c:94ff:fe59:d3de

peer offset 2600:3c03::f03c:94ff:fe59:d3de plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c03::f03c:94ff:fe59:d3de 2.854 2.854 2.854 2.958 4.537 4.537 4.537 1.683 1.683 0.770 3.449 ms 0.6976 1.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 2600:3c03:e002:1300::10 (ntp.electronmill.com)

peer offset 2600:3c03:e002:1300::10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c03:e002:1300::10 (ntp.electronmill.com) -3.742 -3.742 -3.742 3.270 6.177 6.177 6.177 9.919 9.919 3.310 1.757 ms -0.3528 1.728

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:3c06::f03c:94ff:fee2:9c28

peer offset 2600:3c06::f03c:94ff:fee2:9c28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c06::f03c:94ff:fee2:9c28 5.742 5.742 5.742 7.946 15.389 15.389 15.389 9.646 9.646 3.904 8.785 ms 1.004 2.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 2600:3c06::f03c:94ff:fee2:c53a

peer offset 2600:3c06::f03c:94ff:fee2:c53a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c06::f03c:94ff:fee2:c53a 7.934 7.934 7.934 10.652 34.769 34.769 34.769 26.835 26.835 12.061 17.785 ms 0.6803 1.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 2600:4040:e0da:f000::cbb9:201a

peer offset 2600:4040:e0da:f000::cbb9:201a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:4040:e0da:f000::cbb9:201a -99.353 -99.353 -97.880 3.306 8.180 46.292 46.292 106.060 145.645 34.906 -8.837 ms -1.974 5.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 2602:291:69::8 (time2.trtnw.net)

peer offset 2602:291:69::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:291:69::8 (time2.trtnw.net) -87.855 -87.855 -87.855 -86.413 -85.482 -85.482 -85.482 2.373 2.373 0.712 -86.511 ms -0.5905 2.861

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:291:69::9 (time.trtnw.net)

peer offset 2602:291:69::9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:291:69::9 (time.trtnw.net) -570.253 -570.253 -566.922 3.932 8.481 11.063 11.063 575.403 581.315 212.747 -91.121 ms -1.788 4.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 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net)

peer offset 2602:2b7:d11:f4::122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) -158.684 -3.456 -0.083 2.041 4.145 5.512 10.845 4.229 8.968 7.379 1.675 ms -20.33 432.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 2602:2eb:2:95:1234:5678:9abc:def0

peer offset 2602:2eb:2:95:1234:5678:9abc:def0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:2eb:2:95:1234:5678:9abc:def0 -177.116 -4.635 -1.237 2.194 5.223 7.388 240.974 6.460 12.023 12.582 2.396 ms 11.48 295.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 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) -26.339 -9.392 1.266 5.868 9.817 23.455 24.890 8.551 32.847 4.663 5.601 ms -1.967 22.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 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.748 11.083 11.083 11.083 13.479 13.479 3.735 2.173 ms 1.096 3.17

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.mci.trtnw.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.mci.trtnw.net) -12.175 -1.360 4.707 9.530 16.745 20.179 20.349 12.038 21.539 4.125 9.733 ms -0.5412 8.171

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:fb95:16::123 (time5.sigi.net)

peer offset 2602:fb95:16::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fb95:16::123 (time5.sigi.net) -3.415 -3.415 -3.415 2.197 8.657 8.657 8.657 12.072 12.072 3.322 1.725 ms 0.2884 2.931

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:fc2f:100:9800::dead:beef

peer offset 2602:fc2f:100:9800::dead:beef plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fc2f:100:9800::dead:beef -17.617 0.601 3.135 6.681 10.772 15.339 240.110 7.637 14.738 16.349 7.873 ms 13.34 186.6

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

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

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

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



Server Offset 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 2602:fe2e:3:d:f9:c7ff:fef5:379c

peer offset 2602:fe2e:3:d:f9:c7ff:fef5:379c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fe2e:3:d:f9:c7ff:fef5:379c 3.035 3.035 3.035 6.211 8.657 8.657 8.657 5.622 5.622 1.762 5.927 ms -0.1747 2.107

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 2603:c020:0:8369:0:ba11:ba11:ba11

peer offset 2603:c020:0:8369:0:ba11:ba11:ba11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369:0:ba11:ba11:ba11 -7.577 -7.577 -7.577 -4.734 -3.175 -3.175 -3.175 4.402 4.402 1.726 -5.565 ms 0.2097 1.456

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 2603:c020:0:8369:1111:1111:1111:1112

peer offset 2603:c020:0:8369:1111:1111:1111:1112 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369:1111:1111:1111:1112 -55.331 -55.331 -46.563 -7.286 94.091 94.407 94.407 140.654 149.738 44.312 13.646 ms 0.9336 2.506

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 2603:c020:0:8369::bad:beef

peer offset 2603:c020:0:8369::bad:beef plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369::bad:beef -6.830 -6.830 -6.830 -3.090 -2.867 -2.867 -2.867 3.963 3.963 1.885 -4.862 ms 0.002145 1.011

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 2603:c020:0:8369::f00d:feed

peer offset 2603:c020:0:8369::f00d:feed plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369::f00d:feed -11.789 -11.789 -11.789 -5.006 -2.327 -2.327 -2.327 9.462 9.462 3.286 -5.616 ms -0.9394 2.42

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 2603:c020:0:8369:feed:feed:feed:feed

peer offset 2603:c020:0:8369:feed:feed:feed:feed plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369:feed:feed:feed:feed -18.686 -18.686 -18.686 -5.363 -1.212 -1.212 -1.212 17.474 17.474 4.007 -6.304 ms -1.91 6.79

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 2603:c024:c005:a600:efb6:d213:cad8:251d

peer offset 2603:c024:c005:a600:efb6:d213:cad8:251d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c024:c005:a600:efb6:d213:cad8:251d 1.713 1.713 1.713 11.865 68.213 68.213 68.213 66.499 66.499 21.793 19.547 ms 1.448 3.682

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

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

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

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



Server Offset 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 (us1-ipv6.cracky-chan.com)

peer offset 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 (us1-ipv6.cracky-chan.com) 4.360 4.360 7.868 9.469 13.253 17.815 17.815 5.385 13.455 2.164 9.765 ms 1.273 7.496

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

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

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

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



Server Offset 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us)

peer offset 2604:2dc0:101:200::151 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) 2.819 2.819 2.819 10.472 14.418 14.418 14.418 11.599 11.599 3.534 9.984 ms -0.574 2.357

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

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

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

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



Server Offset 2604:2dc0:202:300::140d (vps-8f06187a.vps.ovh.us)

peer offset 2604:2dc0:202:300::140d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:2dc0:202:300::140d (vps-8f06187a.vps.ovh.us) -10.884 -6.103 -4.364 -1.787 0.663 2.038 13.335 5.027 8.141 1.665 -1.837 ms 0.09333 10.2

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

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

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

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



Server Offset 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com)

peer offset 2604:2dc0:202:300::2459 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) -49.930 -36.749 -6.555 2.041 5.114 6.502 22.290 11.670 43.251 5.807 0.770 ms -4.61 31.25

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

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

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

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



Server Offset 2604:4300:a:299::164

peer offset 2604:4300:a:299::164 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:4300:a:299::164 -9.675 -9.675 -6.261 -0.158 3.067 3.865 3.865 9.328 13.539 3.536 -1.195 ms -0.6405 2.55

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

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

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

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



Server Offset 2604:4500:6:7c9::186 (us-east-2.clearnet.pw)

peer offset 2604:4500:6:7c9::186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) -802.674 -802.674 -802.674 2.272 9.840 9.840 9.840 812.514 812.514 371.058 -243.393 ms -0.8332 1.694

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

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

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

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



Server Offset 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com)

peer offset 2604:8800:52:81:38:229:52:9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) 4.759 4.759 4.759 5.795 36.164 36.164 36.164 31.405 31.405 14.567 15.573 ms 0.7044 1.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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -97.614 -97.614 -97.614 -96.252 -95.198 -95.198 -95.198 2.416 2.416 0.727 -96.393 ms -0.05135 2.552

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

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

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

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



Server Offset 2604:a880:1:20::1fd:1001 (jitter.tickadj.net)

peer offset 2604:a880:1:20::1fd:1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) -40.303 -1.773 0.146 2.726 5.501 103.648 104.341 5.355 105.421 14.429 4.427 ms 6.057 42.23

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

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

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

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



Server Offset 2604:a880:400:d0::4ed:f001 (unifi.versadns.com)

peer offset 2604:a880:400:d0::4ed:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) -6.372 -6.372 -3.109 11.458 218.960 218.960 218.960 222.069 225.332 83.767 47.473 ms 1.451 3.181

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

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

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

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



Server Offset 2604:a880:800:10::70f:b001 (ellone.fdisk.io)

peer offset 2604:a880:800:10::70f:b001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:800:10::70f:b001 (ellone.fdisk.io) 3.373 3.373 3.373 8.241 9.581 9.581 9.581 6.208 6.208 1.791 7.376 ms -0.8255 2.41

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

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

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

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



Server Offset 2604:a880:800:a1::ec9:5001

peer offset 2604:a880:800:a1::ec9:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:800:a1::ec9:5001 -127.479 -127.479 -5.442 6.028 37.389 41.342 41.342 42.831 168.821 27.959 3.167 ms -3.748 18.56

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

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

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

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



Server Offset 2604:d200::39 (white.web-ster.com)

peer offset 2604:d200::39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:d200::39 (white.web-ster.com) -6.544 -6.544 -4.662 -2.901 28.557 30.956 30.956 33.219 37.499 9.313 0.132 ms 2.757 9.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:4840:3:fb19::1 (chi3.us.ntp.li)

peer offset 2605:4840:3:fb19::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:4840:3:fb19::1 (chi3.us.ntp.li) -278.261 -8.779 -1.247 2.712 7.022 29.833 89.152 8.269 38.612 10.586 2.900 ms -14.92 446.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 2605:6400:488d:2eda:eee9:fe8d:4543:d471

peer offset 2605:6400:488d:2eda:eee9:fe8d:4543:d471 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:6400:488d:2eda:eee9:fe8d:4543:d471 6.277 6.277 6.277 10.872 10.872 10.872 10.872 4.595 4.595 2.297 8.574 ms -5.457e-16 1

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:6400:488d:3686:546d:c03c:1689:20c

peer offset 2605:6400:488d:3686:546d:c03c:1689:20c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:6400:488d:3686:546d:c03c:1689:20c 0.063 0.063 0.063 10.815 77.942 77.942 77.942 77.879 77.879 31.733 28.904 ms 0.6938 1.564

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:6400:84e1::123

peer offset 2605:6400:84e1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:6400:84e1::123 0.114 0.114 0.114 234.240 240.273 240.273 240.273 240.159 240.159 112.476 147.282 ms -0.474 1.227

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) -170.499 -5.442 -2.472 5.308 8.514 10.151 214.236 10.986 15.593 5.341 4.854 ms 12.44 852.1

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) -810.498 -3.613 -1.258 5.106 8.514 10.408 429.230 9.772 14.021 20.517 4.561 ms -24.09 1001

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 2606:82c0:22::e (time2.lshiy.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:82c0:22::e (time2.lshiy.com) -105.777 -105.777 -105.777 -97.920 6.067 6.067 6.067 111.844 111.844 49.551 -65.517 ms 0.6996 1.504

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:23::e (time3.lshiy.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:82c0:23::e (time3.lshiy.com) 3.326 3.326 3.326 7.253 12.695 12.695 12.695 9.369 9.369 2.739 7.383 ms 0.4156 2.484

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:5600:182:500::1 (ntp-1.jonlight.com)

peer offset 2607:5600:182:500::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:5600:182:500::1 (ntp-1.jonlight.com) -568.165 -568.165 -568.165 -0.446 11.465 11.465 11.465 579.631 579.631 265.791 -190.495 ms -0.701 1.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 2607:7c80:54:3::32

peer offset 2607:7c80:54:3::32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:7c80:54:3::32 -2.394 -2.394 -2.394 3.518 11.300 11.300 11.300 13.694 13.694 4.050 4.219 ms 0.07606 1.632

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:7c80:54:3::56 (owners.kjsl.com)

peer offset 2607:7c80:54:3::56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:7c80:54:3::56 (owners.kjsl.com) -806.909 -806.909 -5.703 0.187 5.818 9.156 9.156 11.521 816.065 173.398 -38.752 ms -4.188 18.54

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

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

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

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



Server Offset 2607:9000:7000:23:216:3cff:fe25:38d7

peer offset 2607:9000:7000:23:216:3cff:fe25:38d7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:9000:7000:23:216:3cff:fe25:38d7 -7.438 -7.438 -7.438 1.350 6.995 6.995 6.995 14.433 14.433 4.427 0.540 ms -0.1739 2.018

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:9d00:2000:16::9269:208a

peer offset 2607:9d00:2000:16::9269:208a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:9d00:2000:16::9269:208a 0.027 0.027 0.549 5.418 11.274 17.615 17.615 10.726 17.588 3.719 5.554 ms 1.403 5.818

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:b500:410:7700::1

peer offset 2607:b500:410:7700::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:b500:410:7700::1 -559.793 -559.793 -558.023 15.880 247.118 247.131 247.131 805.140 806.924 235.950 5.184 ms -1.393 4.315

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

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

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

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



Server Offset 2607:f1c0:f014:9e00::2

peer offset 2607:f1c0:f014:9e00::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f014:9e00::2 1.897 1.897 1.897 14.187 176.141 176.141 176.141 174.244 174.244 77.791 64.515 ms 0.6746 1.495

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:: (ntp11.kernfusion.at)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) -64.809 -64.809 -64.809 -61.044 -58.237 -58.237 -58.237 6.572 6.572 2.268 -61.730 ms -0.02717 1.823

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::1 (ntp11.kernfusion.at)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) 2.778 2.778 2.778 7.554 7.962 7.962 7.962 5.184 5.184 1.862 6.389 ms -1.034 2.559

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::3 (ntp11.kernfusion.at)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) 3.424 3.424 3.424 9.764 40.761 40.761 40.761 37.337 37.337 12.353 15.555 ms 1.138 2.774

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) -2.373 -2.373 -1.407 3.297 10.246 11.084 11.084 11.653 13.458 3.531 3.807 ms 0.3808 2.37

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 -8.290 9.893 429.232 429.472 429.472 437.522 440.836 115.991 54.692 ms 2.751 9.098

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 -174.467 -174.467 -172.715 3.910 20.484 20.484 20.484 193.199 194.951 64.078 -20.926 ms -1.945 4.813

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:f3c8:3803:1::6

peer offset 2607:f3c8:3803:1::6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f3c8:3803:1::6 -6.026 -6.026 -6.026 2.471 214.987 214.987 214.987 221.013 221.013 95.937 61.079 ms 0.9476 1.902

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:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net)

peer offset 2607:f5b7:1:44::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) -23.263 -23.263 -23.263 -10.419 26.993 26.993 26.993 50.256 50.256 13.527 -6.124 ms 0.7442 2.94

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:f710:35::29c:0:1 (ntp6.kernfusion.at)

peer offset 2607:f710:35::29c:0:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) 6.293 6.293 6.293 9.644 16.365 16.365 16.365 10.072 10.072 2.800 10.002 ms 0.8431 3.217

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:f710:35::29c:0:5

peer offset 2607:f710:35::29c:0:5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f710:35::29c:0:5 1.230 1.230 1.230 6.637 13.998 13.998 13.998 12.768 12.768 3.502 7.121 ms 0.34 2.688

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:f710:35::29c:0:8

peer offset 2607:f710:35::29c:0:8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f710:35::29c:0:8 -3.482 -1.256 1.976 4.319 6.532 9.029 12.497 4.556 10.285 1.590 4.260 ms -0.3604 7.445

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:ff50:0:1a::10 (ntpool0.603.newcontinuum.net)

peer offset 2607:ff50:0:1a::10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) -158.123 -158.123 -158.123 3.807 12.552 12.552 12.552 170.675 170.675 66.662 -31.139 ms -1.273 2.639

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 2620:83:8000:140::b (tic.lbl.gov)

peer offset 2620:83:8000:140::b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:83:8000:140::b (tic.lbl.gov) -64.202 -16.454 -0.037 2.751 5.105 7.089 169.920 5.142 23.543 8.350 2.692 ms 14.74 314

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 2620:8d:c000::f (blotch.image1tech.net)

peer offset 2620:8d:c000::f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:8d:c000::f (blotch.image1tech.net) -12.501 -12.501 -12.501 0.670 15.127 15.127 15.127 27.628 27.628 9.564 -0.984 ms 0.2932 2

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

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

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

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



Server Offset 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com)

peer offset 2620:9a:e000:1061::2:165 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) -7.979 -7.979 -7.979 -0.845 213.035 213.035 213.035 221.015 221.015 98.515 62.052 ms 0.8326 1.697

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 2620:b0:2000:102::1:123 (time-h.den.codehof.net)

peer offset 2620:b0:2000:102::1:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:b0:2000:102::1:123 (time-h.den.codehof.net) -107.407 -107.407 -107.407 -66.747 92.475 92.475 92.475 199.883 199.883 57.820 -44.390 ms 1.21 3.478

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 2620:b0:2000:102::2:123 (time-he.den.codehof.net)

peer offset 2620:b0:2000:102::2:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:b0:2000:102::2:123 (time-he.den.codehof.net) -44.889 -44.889 -44.889 22.240 34.334 34.334 34.334 79.222 79.222 22.949 14.406 ms -2.048 5.652

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 2a00:d78:0:712:94:198:159:11 (nts1.time.nl)

peer offset 2a00:d78:0:712:94:198:159:11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) -573.994 -18.134 -6.806 2.327 5.873 12.780 70.769 12.679 30.914 9.821 1.171 ms -30.68 1529

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) -810.640 -46.911 -19.580 2.429 8.877 12.738 425.774 28.457 59.649 18.045 -0.827 ms -17.65 799.7

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

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

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

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



Server Offset 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) -178.311 -53.480 -21.082 -0.130 7.126 10.754 209.396 28.208 64.234 12.297 -2.557 ms -1.944 61.96

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:4f8:c012:1afb:123:123:123:123 (tock.telnet.li)

peer offset 2a01:4f8:c012:1afb:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:4f8:c012:1afb:123:123:123:123 (tock.telnet.li) -662.197 -43.394 -29.960 -14.733 -7.976 -0.161 153.523 21.984 43.233 17.808 -15.749 ms -19.9 818.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 2a01:4f9:c013:fa27:123:123:123:123

peer offset 2a01:4f9:c013:fa27:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:4f9:c013:fa27:123:123:123:123 -74.656 -29.575 -9.456 1.270 5.487 10.806 152.944 14.943 40.381 9.896 0.343 ms 5.416 117.1

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:4ff:f0:7300:123:123:123:123 (use1.ntspool.telnet.li)

peer offset 2a01:4ff:f0:7300:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:4ff:f0:7300:123:123:123:123 (use1.ntspool.telnet.li) -118.920 -12.890 -6.246 -2.163 1.265 5.208 288.663 7.511 18.098 9.301 -2.445 ms 12.21 561.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 2a01:4ff:f0:ebce::1

peer offset 2a01:4ff:f0:ebce::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:4ff:f0:ebce::1 8.384 8.384 8.384 34.231 34.231 34.231 34.231 25.847 25.847 12.924 21.307 ms 1.962e-16 1

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:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com)

peer offset 2a01:7e03::f03c:95ff:fef8:ac8c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) -51.215 -51.215 -51.215 6.741 19.073 19.073 19.073 70.288 70.288 23.048 -2.114 ms -1.242 3.142

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:7e04::f03c:94ff:fee2:cba5

peer offset 2a01:7e04::f03c:94ff:fee2:cba5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:7e04::f03c:94ff:fee2:cba5 -26.406 -26.406 -26.406 2.333 5.249 5.249 5.249 31.655 31.655 7.170 0.454 ms -3.228 12.34

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

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

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

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



Server Offset 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media)

peer offset 2a05:dfc1:cb1:201:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) -1.952 -1.409 0.783 3.141 6.155 10.391 13.358 5.371 11.799 1.803 3.258 ms 1.298 9.219

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 2a0a:e5c0:2:2:0:c8ff:fe68:beb7 (2a0a-e5c0-2-2-0-c8ff-fe68-beb7.loves.ipv6.at.ungleich.ch)

peer offset 2a0a:e5c0:2:2:0:c8ff:fe68:beb7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a0a:e5c0:2:2:0:c8ff:fe68:beb7 (2a0a-e5c0-2-2-0-c8ff-fe68-beb7.loves.ipv6.at.ungleich.ch) -15.575 -4.284 -0.922 1.204 3.169 4.150 7.004 4.091 8.434 1.710 1.146 ms -3.21 29.58

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 34.147.28.4

peer offset 34.147.28.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 34.147.28.4 -33.036 -14.610 -6.461 -1.698 1.628 5.064 13.648 8.089 19.674 3.238 -2.041 ms -2.728 21

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

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

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

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



Server Offset 37.27.11.4

peer offset 37.27.11.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 37.27.11.4 -51.314 -10.261 -2.384 0.947 3.098 4.523 4.544 5.482 14.784 4.805 0.292 ms -9.244 98.81

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 44.190.5.123

peer offset 44.190.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 44.190.5.123 -619.209 -1.022 1.409 5.184 7.370 8.567 28.290 5.961 9.589 8.885 4.716 ms -51.54 3298

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 -3.217 -0.103 2.951 5.735 7.668 9.707 23.365 4.717 9.811 1.722 5.639 ms 0.382 16.63

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

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

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

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



Server Offset 45.77.126.122

peer offset 45.77.126.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.77.126.122 0.280 0.280 0.280 4.312 5.554 5.554 5.554 5.273 5.273 1.572 3.685 ms -0.6575 2.314

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

peer offset 45.79.51.42 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.79.51.42 -45.604 -45.604 -45.604 8.683 108.150 108.150 108.150 153.754 153.754 57.087 39.510 ms 0.07989 1.347

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

peer offset 45.83.234.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.83.234.123 -296.062 -296.062 -36.862 5.238 11.369 12.953 12.953 48.231 309.015 50.497 -9.270 ms -4.716 25.98

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

peer offset 45.84.199.136 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.84.199.136 -110.729 -110.729 -110.729 -97.871 9.546 9.546 9.546 120.275 120.275 54.799 -52.941 ms 0.172 1.055

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 46.37.96.107

peer offset 46.37.96.107 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 46.37.96.107 -808.769 -33.538 -1.905 5.043 7.457 8.750 17.475 9.362 42.288 37.739 2.042 ms -20.74 443.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 50.117.3.52

peer offset 50.117.3.52 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.117.3.52 -8.085 -8.085 -8.085 -6.204 -5.368 -5.368 -5.368 2.717 2.717 0.914 -6.560 ms -0.319 1.928

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 50.117.3.95

peer offset 50.117.3.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.117.3.95 -146.276 -146.276 -146.276 8.636 18.465 18.465 18.465 164.741 164.741 63.106 -20.370 ms -1.48 3.224

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 50.205.57.38

peer offset 50.205.57.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.205.57.38 -18.950 -18.950 -0.288 5.249 8.633 18.417 18.417 8.921 37.367 5.890 4.328 ms -1.998 11.57

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 50.218.103.254

peer offset 50.218.103.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.218.103.254 6.935 6.935 6.935 10.777 11.835 11.835 11.835 4.899 4.899 1.768 9.997 ms -0.768 2.084

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 51.38.58.233

peer offset 51.38.58.233 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 51.38.58.233 -9.884 -9.426 -5.732 1.681 3.951 4.658 5.143 9.683 14.084 3.080 0.771 ms -1.604 5.182

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 51.81.20.76

peer offset 51.81.20.76 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 51.81.20.76 2.414 2.414 2.414 7.712 11.524 11.524 11.524 9.111 9.111 3.247 7.454 ms -0.2642 1.777

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 51.81.226.229

peer offset 51.81.226.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 51.81.226.229 -178.118 -178.118 -173.190 4.447 15.237 22.510 22.510 188.427 200.627 62.005 -17.820 ms -2.094 5.445

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 64.79.100.197

peer offset 64.79.100.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.79.100.197 -5.398 -1.308 0.115 2.437 4.257 5.695 7.196 4.142 7.002 1.439 2.356 ms -1.086 9.14

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 65.182.224.39

peer offset 65.182.224.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 65.182.224.39 1.814 1.814 1.814 2.848 5.791 5.791 5.791 3.977 3.977 1.315 3.059 ms 1.249 3.327

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 -27.328 -27.328 -11.996 4.815 12.740 46.019 46.019 24.736 73.347 10.026 2.952 ms 0.8298 9.385

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

peer offset 66.42.71.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.42.71.197 -4.404 1.597 4.014 6.528 8.619 9.544 14.523 4.605 7.947 1.519 6.426 ms -0.8517 7.915

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

peer offset 66.85.78.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.85.78.80 1.863 1.863 1.863 5.833 6.542 6.542 6.542 4.679 4.679 1.783 4.731 ms -0.7192 1.975

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

peer offset 67.217.246.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 67.217.246.127 -4.257 -3.477 -0.379 2.528 6.202 9.675 10.219 6.580 13.152 2.004 2.572 ms 0.5419 6.199

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 28.533 423.145 423.145 423.145 434.326 434.326 144.136 72.032 ms 1.949 4.963

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 68.234.48.70

peer offset 68.234.48.70 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 68.234.48.70 -2.973 -2.973 -2.973 9.512 47.817 47.817 47.817 50.790 50.790 12.262 11.128 ms 2.266 7.46

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 -35.854 -4.065 0.107 2.667 5.466 104.738 425.249 5.359 108.803 32.556 7.005 ms 10.72 133

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 -2.318 -0.017 2.894 4.643 5.551 6.408 4.661 7.869 3.416 2.593 ms -20.67 515

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 71.19.144.140

peer offset 71.19.144.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 71.19.144.140 -3.221 -3.221 -3.221 4.015 7.428 7.428 7.428 10.649 10.649 2.867 3.283 ms -0.3728 2.496

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 72.14.183.39

peer offset 72.14.183.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.14.183.39 5.676 5.676 5.676 6.591 11.748 11.748 11.748 6.071 6.071 2.174 7.473 ms 1.37 3.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 72.14.186.59

peer offset 72.14.186.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.14.186.59 2.611 2.611 2.611 5.374 7.023 7.023 7.023 4.412 4.412 1.489 5.305 ms -0.8276 2.527

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 72.46.53.234

peer offset 72.46.53.234 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.46.53.234 -35.275 -35.275 -35.275 69.197 105.228 105.228 105.228 140.503 140.503 52.722 51.699 ms -0.2012 1.301

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 72.46.61.205

peer offset 72.46.61.205 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.46.61.205 -285.110 -285.110 -285.110 6.157 16.075 16.075 16.075 301.185 301.185 76.949 -30.555 ms -2.535 8.616

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 73.185.182.209

peer offset 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 73.185.182.209 -2.743 0.925 2.341 5.411 8.588 10.253 11.822 6.247 9.328 1.947 5.428 ms -0.05719 3.857

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 73.65.80.137

peer offset 73.65.80.137 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 73.65.80.137 -809.727 -809.727 -9.135 -1.384 3.688 7.510 7.510 12.823 817.238 169.002 -38.192 ms -4.333 19.79

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 -93.402 -23.673 -4.883 8.780 13.074 17.416 35.796 17.957 41.089 8.134 7.088 ms -5.421 50.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 77.42.37.85

peer offset 77.42.37.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 77.42.37.85 -88.107 -36.089 -7.938 1.616 4.984 9.122 17.475 12.922 45.211 7.462 0.463 ms -6.436 56.55

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 79.160.225.13

peer offset 79.160.225.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 79.160.225.13 -59.926 -17.704 -5.832 -1.917 0.752 2.878 11.556 6.584 20.582 4.049 -2.367 ms -7.389 83.12

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 83.147.242.172

peer offset 83.147.242.172 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 83.147.242.172 -1.026 1.305 3.079 5.350 7.728 10.018 14.032 4.649 8.714 1.528 5.378 ms 0.287 5.704

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 94.198.159.11

peer offset 94.198.159.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 94.198.159.11 7.026 7.026 7.026 9.843 9.843 9.843 9.843 2.818 2.818 1.409 8.435 ms 0 1

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 96.19.94.82

peer offset 96.19.94.82 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 96.19.94.82 -0.647 -0.647 -0.647 1.724 5.250 5.250 5.250 5.897 5.897 1.953 2.085 ms 0.298 2.161

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 99.28.14.242

peer offset 99.28.14.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 99.28.14.242 -568.386 -2.050 0.773 4.332 6.974 9.919 171.646 6.201 11.970 46.430 1.696 ms -10.89 137.6

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

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

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

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



Server Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -865.294 -186.575 -183.021 -155.342 -124.785 -119.407 1,345.558 58.236 67.168 18.190 -157.381 ms 15.33 1133

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) -741.259 -8.626 -7.955 -4.643 -0.189 0.268 1,996.886 7.766 8.894 11.282 -4.465 ms 118.5 1.815e+04

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 -179.772 -173.150 -3.259 14.062 19.724 1,940.513 187.211 199.495 76.194 -53.845 ms -0.3284 10.87

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

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

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

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



Server Offset 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.615 -8.031 -0.731 0.651 0.970 2,061.810 8.682 9.585 11.006 -2.388 ms 169.9 3.111e+04

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) -597.294 -178.078 -174.970 -1.726 4.111 6.235 236.678 179.081 184.313 73.098 -43.269 ms -1.192 2.483

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) -52.048 -1.868 -0.986 -0.065 0.891 1.372 230.276 1.876 3.240 1.230 -0.066 ms 126 2.365e+04

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.172 -176.994 -173.059 -163.444 -157.121 -154.860 -148.505 15.938 22.134 4.800 -164.015 ms -0.5576 3.253

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) -3,009.455 -0.960 -0.610 -0.079 0.535 0.918 4.447 1.145 1.878 17.175 -0.177 ms -175.1 3.068e+04

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 17.731 18.171 18.171 17.731 18.171 4.618 5.158 ms 1.714 5.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.



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 104.167.215.195

peer jitter 104.167.215.195 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.167.215.195 0.000 0.000 0.000 1.878 2.199 2.199 2.199 2.199 2.199 0.724 1.553 ms -1.474 3.661

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

peer jitter 104.167.241.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.167.241.253 0.000 0.000 0.000 2.362 8.036 8.036 8.036 8.036 8.036 2.290 2.983 ms 0.6267 2.554

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

peer jitter 104.234.61.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.234.61.117 0.480 0.742 1.191 3.261 15.561 24.862 40.403 14.370 24.120 4.950 4.809 ms 3.219 16.66

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 108.61.73.243

peer jitter 108.61.73.243 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 108.61.73.243 0.568 0.834 1.318 9.146 40.391 56.637 69.973 39.073 55.803 12.470 12.844 ms 1.563 5.611

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 12.71.198.242

peer jitter 12.71.198.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 12.71.198.242 0.000 0.000 0.000 2.476 14.247 14.247 14.247 14.247 14.247 4.389 3.547 ms 1.44 4.115

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 129.146.193.200

peer jitter 129.146.193.200 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 129.146.193.200 0.000 0.000 0.604 2.622 17.247 17.857 18.051 16.643 17.857 3.912 3.814 ms 2.358 8.421

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 131.239.5.43

peer jitter 131.239.5.43 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 131.239.5.43 0.000 0.000 0.000 1.655 3.135 3.135 3.135 3.135 3.135 0.882 1.743 ms -0.2966 2.893

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 135.148.100.14

peer jitter 135.148.100.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 135.148.100.14 0.000 1.034 1.658 14.607 55.544 71.155 96.799 53.886 70.120 15.421 16.960 ms 1.968 8.02

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

peer jitter 137.110.222.27 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 137.110.222.27 0.000 0.000 0.341 3.330 5.202 5.372 5.372 4.861 5.372 1.250 3.135 ms -0.5711 2.996

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 139.177.202.26

peer jitter 139.177.202.26 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.177.202.26 0.000 0.000 0.000 1.560 6.528 6.528 6.528 6.528 6.528 1.992 1.908 ms 1.039 3.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 139.84.137.244

peer jitter 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.84.137.244 0.000 1.498 3.474 24.787 66.618 81.767 171.675 63.144 80.269 20.653 28.445 ms 1.093 5.724

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 139.94.144.123

peer jitter 139.94.144.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.94.144.123 0.000 0.000 0.000 1.501 2.945 2.945 2.945 2.945 2.945 1.260 1.529 ms 0.002279 1.271

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 141.11.234.198

peer jitter 141.11.234.198 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 141.11.234.198 0.000 0.000 0.000 8.942 58.361 58.361 58.361 58.361 58.361 19.957 16.134 ms 1.387 3.303

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 141.11.89.193

peer jitter 141.11.89.193 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 141.11.89.193 0.000 0.000 0.000 1.558 2.015 2.015 2.015 2.015 2.015 0.652 1.474 ms -1.441 3.889

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 142.202.190.19

peer jitter 142.202.190.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 142.202.190.19 0.000 0.000 0.000 2.175 6.985 16.409 16.409 6.985 16.409 3.192 2.973 ms 2.438 10.54

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 144.202.0.197

peer jitter 144.202.0.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.0.197 0.000 0.000 0.000 2.470 4.307 4.307 4.307 4.307 4.307 1.435 2.296 ms -0.2563 1.847

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 144.202.62.209

peer jitter 144.202.62.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.62.209 0.000 0.000 0.957 2.633 7.857 35.452 35.452 6.900 35.452 4.582 3.718 ms 5.102 32.94

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 144.202.66.214

peer jitter 144.202.66.214 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.66.214 0.000 0.000 0.000 3.268 3.564 3.564 3.564 3.564 3.564 1.326 2.411 ms -0.873 2.102

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 149.248.12.167

peer jitter 149.248.12.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.248.12.167 0.000 0.000 0.000 1.415 6.547 6.547 6.547 6.547 6.547 2.701 2.851 ms 0.3599 1.282

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 149.28.200.179

peer jitter 149.28.200.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.28.200.179 0.000 0.000 1.448 3.887 18.634 19.531 19.531 17.186 19.531 5.389 6.126 ms 1.504 3.906

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 149.28.61.105

peer jitter 149.28.61.105 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.28.61.105 0.000 0.000 0.000 2.466 4.280 4.280 4.280 4.280 4.280 1.264 2.154 ms -0.03175 2.746

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 15.204.198.96

peer jitter 15.204.198.96 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 15.204.198.96 0.000 0.000 1.528 9.635 18.188 24.740 24.740 16.661 24.740 6.496 9.205 ms 0.2143 1.632

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 15.204.87.223

peer jitter 15.204.87.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 15.204.87.223 0.000 0.000 0.000 1.610 9.826 13.655 13.655 9.826 13.655 3.554 3.131 ms 1.556 4.646

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 158.51.99.19

peer jitter 158.51.99.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 158.51.99.19 0.000 0.861 1.216 3.317 19.810 51.816 228.673 18.594 50.955 13.195 6.155 ms 10.51 149.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 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.000 0.000 1.145 2.877 10.503 23.214 42.450 9.358 23.214 4.283 3.898 ms 5.218 39.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 162.159.200.123

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.000 0.000 0.000 3.085 9.842 12.427 12.427 9.842 12.427 2.969 3.852 ms 1.147 3.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 163.123.152.14

peer jitter 163.123.152.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 163.123.152.14 0.000 0.000 0.000 3.728 4.357 4.357 4.357 4.357 4.357 1.674 2.791 ms -0.9099 2.151

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 170.187.147.56

peer jitter 170.187.147.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 170.187.147.56 0.000 0.824 1.119 3.127 15.294 35.711 154.182 14.175 34.886 9.178 5.070 ms 11.83 185.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 171.66.97.126

peer jitter 171.66.97.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 171.66.97.126 0.000 0.786 1.119 2.722 12.572 21.171 22.978 11.453 20.386 3.966 3.904 ms 3.037 12.47

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.232.15.202

peer jitter 172.232.15.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.232.15.202 0.000 0.000 0.000 3.215 33.540 33.540 33.540 33.540 33.540 13.913 13.115 ms 0.3783 1.284

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

peer jitter 172.233.153.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.153.85 0.000 0.000 1.067 4.764 14.089 23.765 302.556 13.022 23.765 29.458 8.479 ms 9.659 96.43

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

peer jitter 172.233.157.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.157.223 0.000 0.000 0.000 2.179 8.001 8.001 8.001 8.001 8.001 2.598 2.911 ms 0.8956 2.43

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.180 4.280 4.280 4.280 4.280 4.280 1.151 1.441 ms 1.042 3.453

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.761 13.618 13.618 13.618 13.618 13.618 3.635 5.254 ms 0.5438 2.723

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

peer jitter 172.234.44.141 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.44.141 0.000 0.000 0.000 2.374 7.577 7.577 7.577 7.577 7.577 2.262 3.093 ms 0.8517 2.644

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

peer jitter 172.235.60.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.235.60.8 0.000 0.000 0.000 2.985 13.407 13.407 13.407 13.407 13.407 3.264 4.071 ms 1.906 6.336

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 173.249.203.227

peer jitter 173.249.203.227 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.249.203.227 0.000 0.000 0.000 2.338 5.843 5.843 5.843 5.843 5.843 1.587 2.822 ms 0.3165 2.627

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 173.255.192.10

peer jitter 173.255.192.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.255.192.10 0.000 0.000 0.000 2.331 9.584 9.584 9.584 9.584 9.584 2.608 3.116 ms 1.465 4.472

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 173.255.255.133

peer jitter 173.255.255.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.255.255.133 0.000 0.000 0.000 4.005 4.530 4.530 4.530 4.530 4.530 1.752 2.866 ms -0.8115 2.037

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 178.156.185.92

peer jitter 178.156.185.92 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.156.185.92 0.000 0.657 1.198 6.232 36.386 60.264 69.113 35.188 59.607 11.634 10.482 ms 2.26 9.133

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 192.48.105.15

peer jitter 192.48.105.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.48.105.15 0.000 0.000 0.000 1.815 13.786 13.786 13.786 13.786 13.786 3.333 2.570 ms 2.497 8.699

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 193.29.63.226

peer jitter 193.29.63.226 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 193.29.63.226 0.000 0.000 0.000 2.362 6.790 7.768 7.768 6.790 7.768 1.752 2.617 ms 1.293 4.972

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.761 1.105 3.158 11.601 21.666 201.946 10.496 20.906 8.322 4.608 ms 15.45 309.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 198.137.202.32

peer jitter 198.137.202.32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.137.202.32 0.000 0.671 1.209 3.297 12.402 17.407 31.925 11.193 16.736 3.746 4.236 ms 3.509 20.09

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 198.199.14.19

peer jitter 198.199.14.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.199.14.19 0.000 0.000 0.000 4.868 19.360 19.360 19.360 19.360 19.360 6.619 7.607 ms 0.7297 1.985

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 198.211.103.209

peer jitter 198.211.103.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.211.103.209 0.000 0.000 0.000 3.750 13.433 21.945 21.945 13.433 21.945 4.568 5.256 ms 1.672 6.209

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 198.46.254.130

peer jitter 198.46.254.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.46.254.130 0.000 0.789 1.171 3.308 24.735 39.397 60.567 23.564 38.608 8.364 6.211 ms 3.337 16.34

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 198.60.22.240

peer jitter 198.60.22.240 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.60.22.240 0.000 0.000 0.000 1.229 8.123 8.123 8.123 8.123 8.123 2.808 2.774 ms 0.7715 2.116

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 199.68.201.235

peer jitter 199.68.201.235 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 199.68.201.235 0.000 0.000 1.107 3.083 4.994 5.795 5.795 3.886 5.795 1.244 3.083 ms -0.137 2.992

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:1600:13:101::16b7 (ov-eaae4e.infomaniak.ch)

peer jitter 2001:1600:13:101::16b7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:1600:13:101::16b7 (ov-eaae4e.infomaniak.ch) 0.000 6.381 8.865 27.341 63.554 76.237 194.366 54.689 69.856 19.414 30.805 ms 1.848 13

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:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net)

peer jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) 0.000 1.001 1.378 3.306 22.350 55.353 68.490 20.972 54.352 9.914 6.937 ms 3.502 16.46

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:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com)

peer jitter 2001:19f0:1590:5123:1057:a11:da7a:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) 0.000 0.000 0.000 6.706 10.790 10.790 10.790 10.790 10.790 3.771 6.760 ms -0.8058 2.409

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:19f0:6401:400:5400:4ff:fec3:522a

peer jitter 2001:19f0:6401:400:5400:4ff:fec3:522a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:19f0:6401:400:5400:4ff:fec3:522a 0.000 0.000 0.000 8.886 24.636 24.636 24.636 24.636 24.636 9.634 8.939 ms 0.7974 2.006

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:418:3ff::53 (x.ns.gin.ntt.net)

peer jitter 2001:418:3ff::53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:418:3ff::53 (x.ns.gin.ntt.net) 0.000 0.000 0.000 14.048 17.951 17.951 17.951 17.951 17.951 7.508 10.420 ms -0.3643 1.295

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:418:8405:4002::12

peer jitter 2001:418:8405:4002::12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:418:8405:4002::12 0.000 0.000 0.000 20.750 257.784 257.784 257.784 257.784 257.784 84.275 57.575 ms 1.804 4.559

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:41d0:303:65e9::1 (matthaeus.julia0815.de)

peer jitter 2001:41d0:303:65e9::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:41d0:303:65e9::1 (matthaeus.julia0815.de) 0.000 1.638 5.026 24.360 63.536 94.275 441.235 58.511 92.637 27.238 29.563 ms 7.074 97.1

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de)

peer jitter 2001:470:1f07:198::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) 0.000 1.136 2.036 12.122 41.039 72.944 118.845 39.003 71.808 15.175 15.560 ms 2.609 13.81

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:1f07:24f::123

peer jitter 2001:470:1f07:24f::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:1f07:24f::123 0.000 0.000 0.000 25.254 42.613 42.613 42.613 42.613 42.613 13.314 18.607 ms 0.05496 1.858

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:1f2c:60:123:123:123:123

peer jitter 2001:470:1f2c:60:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:1f2c:60:123:123:123:123 0.000 0.000 0.000 20.430 35.954 35.954 35.954 35.954 35.954 11.405 14.554 ms 0.1812 1.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 2001:470:a:b4::2 (dell-2018.jamesb912.com.)

peer jitter 2001:470:a:b4::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:a:b4::2 (dell-2018.jamesb912.com.) 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ns nan nan

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:e8dc:10::123

peer jitter 2001:470:e8dc:10::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e8dc:10::123 0.000 0.001 0.001 0.003 0.017 0.089 589.082 0.016 0.088 33.422 2.611 s 15.05 248.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com)

peer jitter 2001:4998:58:183a::1000 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) 0.000 1.102 1.686 10.928 48.225 61.432 219.778 46.539 60.331 15.215 14.564 ms 2.947 25.72

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:4998:c:1028::1001 (t2.time.gq1.yahoo.com)

peer jitter 2001:4998:c:1028::1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) 0.000 0.830 1.150 3.284 24.575 55.936 146.741 23.425 55.106 10.291 6.585 ms 4.523 32.1

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:558:6014:17:8dc5:5575:5560:2cb6

peer jitter 2001:558:6014:17:8dc5:5575:5560:2cb6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:558:6014:17:8dc5:5575:5560:2cb6 0.000 0.000 0.000 4.253 65.155 123.941 123.941 65.155 123.941 24.032 13.461 ms 3.066 13.01

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 3.333 53.390 53.390 53.390 53.390 53.390 13.672 9.507 ms 1.842 5.746

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.333 2.446 22.705 84.523 104.133 240.582 82.077 102.800 26.854 31.138 ms 0.9834 3.47

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.197.163.71

peer jitter 204.197.163.71 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.197.163.71 0.000 0.686 1.095 3.220 7.493 17.061 50.513 6.398 16.375 3.155 3.763 ms 6.631 80.71

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 205.233.73.201

peer jitter 205.233.73.201 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 205.233.73.201 0.000 0.000 0.000 2.823 5.520 5.520 5.520 5.520 5.520 1.805 2.661 ms -0.09436 1.85

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 208.113.130.146

peer jitter 208.113.130.146 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 208.113.130.146 0.000 0.861 1.394 5.061 43.913 76.684 232.036 42.519 75.823 18.789 11.721 ms 5.662 52.53

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 208.67.72.43

peer jitter 208.67.72.43 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 208.67.72.43 0.000 0.000 0.000 20.684 46.773 46.773 46.773 46.773 46.773 14.479 19.405 ms 0.3984 2.247

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 208.67.75.242

peer jitter 208.67.75.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 208.67.75.242 0.000 0.000 0.000 2.369 18.724 18.724 18.724 18.724 18.724 4.763 3.627 ms 2.559 8.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 216.229.4.66

peer jitter 216.229.4.66 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.229.4.66 0.000 0.000 0.000 4.322 5.026 5.026 5.026 5.026 5.026 2.018 2.765 ms -0.2125 1.383

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 216.229.4.69

peer jitter 216.229.4.69 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.229.4.69 0.000 0.000 0.000 2.477 5.003 5.695 5.695 5.003 5.695 1.718 2.457 ms 0.2191 2.013

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 216.250.115.174

peer jitter 216.250.115.174 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.250.115.174 0.000 0.000 0.000 22.373 24.069 24.069 24.069 24.069 24.069 10.893 12.372 ms -0.02677 1.049

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

peer jitter 23.131.160.7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.131.160.7 0.000 0.880 1.354 3.468 10.866 32.018 126.894 9.512 31.138 7.981 4.858 ms 9.335 108.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.141.40.123

peer jitter 23.141.40.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.141.40.123 0.000 0.000 0.000 3.979 5.911 5.911 5.911 5.911 5.911 1.921 3.290 ms -0.4708 2.11

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.142.248.8

peer jitter 23.142.248.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.142.248.8 0.000 0.000 0.000 1.269 2.327 2.327 2.327 2.327 2.327 0.866 1.154 ms -0.1197 1.574

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

peer jitter 23.142.248.9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.142.248.9 0.000 0.000 0.000 1.625 5.220 5.220 5.220 5.220 5.220 1.670 2.001 ms 0.7372 2.287

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

peer jitter 23.143.196.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.143.196.199 0.000 0.000 0.000 1.033 2.250 2.250 2.250 2.250 2.250 0.756 1.094 ms -0.06783 1.795

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 1.081 3.356 34.022 117.881 142.893 32.940 117.881 18.722 8.653 ms 5.033 31.38

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

peer jitter 23.186.168.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.123 0.000 0.794 1.193 3.052 8.245 20.200 30.025 7.052 19.406 3.089 3.701 ms 3.772 21.92

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

peer jitter 23.186.168.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.126 0.000 0.695 1.121 3.001 10.669 41.147 100.230 9.548 40.452 8.625 4.647 ms 7.962 75.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.127

peer jitter 23.186.168.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.127 0.000 0.000 0.000 6.846 25.786 25.786 25.786 25.786 25.786 9.961 9.050 ms 0.9537 2.186

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

peer jitter 23.186.168.128 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.128 0.000 0.814 1.329 3.310 8.610 17.200 23.748 7.281 16.386 2.792 3.875 ms 2.955 14.86

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.699 1.253 3.436 8.998 17.637 105.774 7.745 16.939 4.861 4.275 ms 11.96 214.6

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 3.466 73.799 73.994 73.994 73.799 73.994 19.691 9.038 ms 2.942 9.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 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.749 1.266 3.133 8.261 15.037 223.184 6.995 14.289 9.704 4.117 ms 21.04 473.4

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.132

peer jitter 23.186.168.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.132 0.000 0.893 1.264 3.336 9.267 18.503 72.944 8.003 17.610 3.765 4.130 ms 6.747 88.38

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

peer jitter 23.95.49.216 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.95.49.216 0.000 0.804 1.089 2.946 11.443 17.019 159.086 10.354 16.216 7.100 4.020 ms 17.62 379.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 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 1.826 4.716 29.461 72.915 89.395 159.685 68.200 87.569 21.838 33.133 ms 0.7116 3.169

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2402:1f00:8101:d6::1

peer jitter 2402:1f00:8101:d6::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2402:1f00:8101:d6::1 0.000 1.122 1.876 18.931 65.466 79.704 169.795 63.590 78.581 21.450 25.074 ms 1.025 4.123

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:4002:100:9f00:5bd1:9512:8a8b:25e

peer jitter 240b:4002:100:9f00:5bd1:9512:8a8b:25e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 240b:4002:100:9f00:5bd1:9512:8a8b:25e 0.000 0.000 0.000 4.287 5.971 5.971 5.971 5.971 5.971 2.062 3.825 ms -0.9946 2.639

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:26d6

peer jitter 240b:4004:108:200:8314:1a08:4cee:26d6 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:26d6 0.000 0.839 1.416 3.601 24.535 54.985 74.237 23.119 54.146 9.449 6.322 ms 4.13 22.24

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:26d9

peer jitter 240b:4004:108:200:8314:1a08:4cee:26d9 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:26d9 0.000 0.000 0.000 19.678 21.828 21.828 21.828 21.828 21.828 8.593 13.132 ms -0.5264 1.711

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:1700:5455:a70::7b:1

peer jitter 2600:1700:5455:a70::7b:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1700:5455:a70::7b:1 0.000 0.000 1.444 4.653 23.669 27.142 27.142 22.225 27.142 7.742 8.428 ms 1.002 2.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 2600:1702:7400:9ac0::314:5a

peer jitter 2600:1702:7400:9ac0::314:5a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1702:7400:9ac0::314:5a 0.000 0.000 0.000 2.413 15.160 15.160 15.160 15.160 15.160 4.523 4.818 ms 1.082 3.061

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:1702:7400:9ac0::5b

peer jitter 2600:1702:7400:9ac0::5b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1702:7400:9ac0::5b 0.000 0.000 0.000 2.689 7.877 7.877 7.877 7.877 7.877 2.509 3.387 ms 0.6509 2.164

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:1702:80c0:9a80:1ee4:b0a2:44bc:c606

peer jitter 2600:1702:80c0:9a80:1ee4:b0a2:44bc:c606 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1702:80c0:9a80:1ee4:b0a2:44bc:c606 0.000 0.000 0.000 5.087 22.009 22.009 22.009 22.009 22.009 8.471 7.694 ms 0.9852 2.224

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 1.432 2.735 23.981 80.125 100.086 260.324 77.390 98.655 25.098 30.934 ms 1.012 4.009

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.941 1.487 3.653 25.297 93.488 214.829 23.809 92.548 16.422 7.675 ms 6.759 62.66

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.823 1.169 3.339 21.951 49.663 185.361 20.783 48.840 9.853 6.218 ms 5.748 56.48

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.832 1.212 3.536 39.205 69.230 282.893 37.993 68.398 14.386 9.101 ms 4.117 32.69

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.835 1.266 7.203 52.230 78.393 168.874 50.964 77.558 17.372 14.338 ms 2.244 9.57

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:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net)

peer jitter 2600:3c00:e000:256::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) 0.000 0.941 1.396 3.367 16.530 40.341 125.199 15.135 39.399 7.127 5.275 ms 7.261 91.76

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:3c00:e000:318::1 (jane.qotw.net)

peer jitter 2600:3c00:e000:318::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c00:e000:318::1 (jane.qotw.net) 0.000 0.936 1.251 3.291 18.596 45.542 55.919 17.345 44.606 7.258 5.661 ms 3.76 20.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:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw)

peer jitter 2600:3c01::f03c:93ff:fe5b:8a7d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) 0.000 0.000 0.000 6.110 10.609 10.609 10.609 10.609 10.609 3.299 4.985 ms 0.1951 2.331

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.678 1.268 3.194 8.827 20.528 87.783 7.559 19.850 4.877 4.124 ms 8.554 112.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c02::f03c:94ff:fe59:f411

peer jitter 2600:3c02::f03c:94ff:fe59:f411 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02::f03c:94ff:fe59:f411 0.000 0.000 0.000 5.394 7.516 7.516 7.516 7.516 7.516 2.647 4.557 ms -0.5602 1.96

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:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net)

peer jitter 2600:3c02:e000:bc::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) 0.000 0.000 0.717 3.878 10.414 16.432 16.432 9.697 16.432 3.233 4.061 ms 1.999 7.801

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:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net)

peer jitter 2600:3c02:e001:1d00::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) 0.000 0.000 0.000 4.625 9.182 9.182 9.182 9.182 9.182 3.008 4.335 ms -0.05862 1.872

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 2600:3c03::f03c:94ff:fe59:d3de

peer jitter 2600:3c03::f03c:94ff:fe59:d3de plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c03::f03c:94ff:fe59:d3de 0.000 0.000 0.000 9.141 10.648 10.648 10.648 10.648 10.648 4.705 6.597 ms -0.6531 1.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 2600:3c03:e002:1300::10 (ntp.electronmill.com)

peer jitter 2600:3c03:e002:1300::10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c03:e002:1300::10 (ntp.electronmill.com) 0.000 0.000 0.000 3.877 7.718 7.718 7.718 7.718 7.718 2.384 3.718 ms 0.3575 1.964

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:3c06::f03c:94ff:fee2:9c28

peer jitter 2600:3c06::f03c:94ff:fee2:9c28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c06::f03c:94ff:fee2:9c28 0.000 0.000 0.000 9.325 30.736 30.736 30.736 30.736 30.736 11.553 11.593 ms 0.8589 2.149

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:3c06::f03c:94ff:fee2:c53a

peer jitter 2600:3c06::f03c:94ff:fee2:c53a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c06::f03c:94ff:fee2:c53a 0.000 0.000 0.000 15.615 24.117 24.117 24.117 24.117 24.117 9.987 13.244 ms -0.3427 1.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 2600:4040:e0da:f000::cbb9:201a

peer jitter 2600:4040:e0da:f000::cbb9:201a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:4040:e0da:f000::cbb9:201a 0.000 0.000 0.547 12.110 32.149 45.133 45.133 31.602 45.133 10.649 11.858 ms 1.048 3.818

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:291:69::8 (time2.trtnw.net)

peer jitter 2602:291:69::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:291:69::8 (time2.trtnw.net) 0.000 0.000 0.000 0.970 1.844 1.844 1.844 1.844 1.844 0.552 0.976 ms -0.2468 2.677

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:291:69::9 (time.trtnw.net)

peer jitter 2602:291:69::9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:291:69::9 (time.trtnw.net) 0.000 0.000 0.000 3.210 6.266 9.048 9.048 6.266 9.048 1.966 3.075 ms 0.8974 4.743

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:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net)

peer jitter 2602:2b7:d11:f4::122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) 0.000 0.932 1.359 3.513 14.745 35.541 139.194 13.387 34.609 7.506 5.120 ms 8.384 105.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:2eb:2:95:1234:5678:9abc:def0

peer jitter 2602:2eb:2:95:1234:5678:9abc:def0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:2eb:2:95:1234:5678:9abc:def0 0.000 0.928 1.427 3.722 27.943 60.804 262.579 26.516 59.876 14.162 7.986 ms 8.402 112.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 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 4.621 20.856 76.477 84.174 87.838 71.856 84.174 21.252 27.684 ms 0.9659 3.216

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 3.625 9.349 9.349 9.349 9.349 9.349 2.588 4.147 ms 0.2659 2.467

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.mci.trtnw.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.mci.trtnw.net) 0.000 0.000 1.448 9.790 67.645 87.579 97.607 66.198 87.579 21.576 19.008 ms 1.617 4.947

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:fb95:16::123 (time5.sigi.net)

peer jitter 2602:fb95:16::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fb95:16::123 (time5.sigi.net) 0.000 0.000 0.000 2.945 6.744 6.744 6.744 6.744 6.744 1.680 2.843 ms 0.7474 3.802

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:fc2f:100:9800::dead:beef

peer jitter 2602:fc2f:100:9800::dead:beef plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fc2f:100:9800::dead:beef 0.000 1.459 2.342 5.507 62.283 166.197 259.248 59.941 164.738 29.654 14.829 ms 4.48 25.6

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 2602:fe2e:3:d:f9:c7ff:fef5:379c

peer jitter 2602:fe2e:3:d:f9:c7ff:fef5:379c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fe2e:3:d:f9:c7ff:fef5:379c 0.000 0.000 0.000 2.011 3.424 3.424 3.424 3.424 3.424 0.929 1.786 ms -0.1796 2.962

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 2603:c020:0:8369:0:ba11:ba11:ba11

peer jitter 2603:c020:0:8369:0:ba11:ba11:ba11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369:0:ba11:ba11:ba11 0.000 0.000 0.000 2.800 5.546 5.546 5.546 5.546 5.546 2.031 2.476 ms 0.3879 1.867

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 2603:c020:0:8369:1111:1111:1111:1112

peer jitter 2603:c020:0:8369:1111:1111:1111:1112 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369:1111:1111:1111:1112 0.000 0.000 0.000 2.768 74.324 99.180 99.180 74.324 99.180 23.092 16.164 ms 2.053 7.146

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 2603:c020:0:8369::bad:beef

peer jitter 2603:c020:0:8369::bad:beef plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369::bad:beef 0.000 0.000 0.000 3.940 3.991 3.991 3.991 3.991 3.991 1.645 2.811 ms -1.067 2.256

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 2603:c020:0:8369::f00d:feed

peer jitter 2603:c020:0:8369::f00d:feed plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369::f00d:feed 0.000 0.000 0.000 2.299 8.110 8.110 8.110 8.110 8.110 2.540 2.878 ms 0.9528 2.711

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 2603:c020:0:8369:feed:feed:feed:feed

peer jitter 2603:c020:0:8369:feed:feed:feed:feed plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369:feed:feed:feed:feed 0.000 0.000 0.000 3.112 13.323 13.323 13.323 13.323 13.323 3.317 3.712 ms 1.612 5.406

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 2603:c024:c005:a600:efb6:d213:cad8:251d

peer jitter 2603:c024:c005:a600:efb6:d213:cad8:251d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c024:c005:a600:efb6:d213:cad8:251d 0.000 0.000 0.000 14.820 57.595 57.595 57.595 57.595 57.595 17.229 20.244 ms 1.209 3.457

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 (us1-ipv6.cracky-chan.com)

peer jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 (us1-ipv6.cracky-chan.com) 0.000 0.000 1.769 15.711 48.002 49.094 49.094 46.233 49.094 11.410 15.959 ms 1.156 4.594

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us)

peer jitter 2604:2dc0:101:200::151 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) 0.000 0.000 0.000 2.991 9.649 9.649 9.649 9.649 9.649 2.561 3.518 ms 1.144 3.781

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:202:300::140d (vps-8f06187a.vps.ovh.us)

peer jitter 2604:2dc0:202:300::140d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:202:300::140d (vps-8f06187a.vps.ovh.us) 0.000 0.965 1.366 3.498 9.087 21.237 71.985 7.721 20.272 3.773 4.317 ms 5.523 60.29

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com)

peer jitter 2604:2dc0:202:300::2459 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) 0.000 0.906 1.363 3.338 10.703 34.136 119.042 9.340 33.230 6.208 4.661 ms 7.131 78.29

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:4300:a:299::164

peer jitter 2604:4300:a:299::164 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:4300:a:299::164 0.000 0.000 0.000 3.582 6.183 11.304 11.304 6.183 11.304 2.417 3.650 ms 1.209 5.485

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:4500:6:7c9::186 (us-east-2.clearnet.pw)

peer jitter 2604:4500:6:7c9::186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) 0.000 0.000 0.000 3.639 13.829 13.829 13.829 13.829 13.829 3.432 4.353 ms 1.336 4.939

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com)

peer jitter 2604:8800:52:81:38:229:52:9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) 0.000 0.000 0.000 21.487 31.405 31.405 31.405 31.405 31.405 13.108 17.631 ms -0.4158 1.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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer jitter 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.000 0.000 0.869 1.657 1.657 1.657 1.657 1.657 0.479 0.845 ms -0.09905 2.996

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:1:20::1fd:1001 (jitter.tickadj.net)

peer jitter 2604:a880:1:20::1fd:1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) 0.000 0.965 1.447 3.716 18.849 29.446 120.523 17.402 28.481 10.597 5.665 ms 8.209 79.46

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:400:d0::4ed:f001 (unifi.versadns.com)

peer jitter 2604:a880:400:d0::4ed:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) 0.000 0.000 0.000 8.010 25.574 25.574 25.574 25.574 25.574 6.576 8.369 ms 0.7283 3.152

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:800:10::70f:b001 (ellone.fdisk.io)

peer jitter 2604:a880:800:10::70f:b001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:800:10::70f:b001 (ellone.fdisk.io) 0.000 0.000 0.000 1.765 3.857 3.857 3.857 3.857 3.857 1.036 1.790 ms 0.1052 2.65

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:800:a1::ec9:5001

peer jitter 2604:a880:800:a1::ec9:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:800:a1::ec9:5001 0.000 0.000 0.000 3.953 99.014 144.987 144.987 99.014 144.987 36.715 24.475 ms 1.773 5.482

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:d200::39 (white.web-ster.com)

peer jitter 2604:d200::39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:d200::39 (white.web-ster.com) 0.000 0.000 0.000 1.801 12.238 25.815 25.815 12.238 25.815 5.414 3.117 ms 3.361 13.81

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:4840:3:fb19::1 (chi3.us.ntp.li)

peer jitter 2605:4840:3:fb19::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:4840:3:fb19::1 (chi3.us.ntp.li) 0.000 2.869 6.410 21.881 58.467 76.100 242.923 52.056 73.231 18.024 25.740 ms 3.934 40.06

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:6400:488d:2eda:eee9:fe8d:4543:d471

peer jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ns nan nan

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:6400:488d:3686:546d:c03c:1689:20c

peer jitter 2605:6400:488d:3686:546d:c03c:1689:20c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:6400:488d:3686:546d:c03c:1689:20c 0.000 0.000 0.000 1.372 9.116 9.116 9.116 9.116 9.116 3.886 3.057 ms 0.6883 1.57

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:6400:84e1::123

peer jitter 2605:6400:84e1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:6400:84e1::123 0.000 0.000 0.000 3.606 8.882 8.882 8.882 8.882 8.882 2.455 3.745 ms 0.4362 2.81

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.000 0.867 1.277 3.404 17.303 42.479 226.379 16.026 41.613 8.577 5.435 ms 8.083 113.6

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

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

RMS Jitter is field 8 in the peerstats log file.



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

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.855 1.249 3.386 15.754 42.335 176.369 14.505 41.480 8.412 5.263 ms 8.396 109.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 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 2606:82c0:22::e (time2.lshiy.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:82c0:22::e (time2.lshiy.com) 0.000 0.000 0.000 4.592 24.843 24.843 24.843 24.843 24.843 9.006 8.155 ms 1.154 2.626

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:23::e (time3.lshiy.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:82c0:23::e (time3.lshiy.com) 0.000 0.000 0.000 3.337 8.248 8.248 8.248 8.248 8.248 2.270 3.415 ms 0.3181 2.67

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:5600:182:500::1 (ntp-1.jonlight.com)

peer jitter 2607:5600:182:500::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:5600:182:500::1 (ntp-1.jonlight.com) 0.000 0.000 0.000 10.156 45.021 45.021 45.021 45.021 45.021 12.499 11.485 ms 1.431 4.572

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:7c80:54:3::32

peer jitter 2607:7c80:54:3::32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:7c80:54:3::32 0.000 0.000 0.000 3.603 11.499 11.499 11.499 11.499 11.499 3.098 4.294 ms 1.035 3.383

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:7c80:54:3::56 (owners.kjsl.com)

peer jitter 2607:7c80:54:3::56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:7c80:54:3::56 (owners.kjsl.com) 0.000 0.000 1.298 3.181 22.900 24.794 24.794 21.602 24.794 5.837 5.520 ms 2.225 7.106

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:9000:7000:23:216:3cff:fe25:38d7

peer jitter 2607:9000:7000:23:216:3cff:fe25:38d7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:9000:7000:23:216:3cff:fe25:38d7 0.000 0.000 0.000 7.179 57.684 57.684 57.684 57.684 57.684 16.210 10.235 ms 2.43 7.385

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:9d00:2000:16::9269:208a

peer jitter 2607:9d00:2000:16::9269:208a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:9d00:2000:16::9269:208a 0.000 0.000 0.000 3.585 32.658 32.768 32.768 32.658 32.768 8.863 6.355 ms 2.336 7.193

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:b500:410:7700::1

peer jitter 2607:b500:410:7700::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:b500:410:7700::1 0.000 0.000 0.000 3.930 45.395 48.813 48.813 45.395 48.813 12.860 8.432 ms 2.364 7.345

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:f014:9e00::2

peer jitter 2607:f1c0:f014:9e00::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f014:9e00::2 0.000 0.000 0.000 11.460 31.195 31.195 31.195 31.195 31.195 9.231 9.169 ms 0.9354 3.131

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:: (ntp11.kernfusion.at)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) 0.000 0.000 0.000 3.311 58.981 58.981 58.981 58.981 58.981 21.215 11.609 ms 1.777 4.18

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::1 (ntp11.kernfusion.at)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) 0.000 0.000 0.000 2.585 3.939 3.939 3.939 3.939 3.939 1.251 2.204 ms -0.4741 2.288

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::3 (ntp11.kernfusion.at)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) 0.000 0.000 0.000 6.053 20.902 20.902 20.902 20.902 20.902 5.847 6.566 ms 1.063 3.708

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 3.713 17.103 17.166 17.166 17.103 17.166 4.236 4.518 ms 1.905 6.172

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 3.194 62.537 70.431 70.431 62.537 70.431 17.930 9.867 ms 2.624 8.577

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 3.238 15.794 15.794 15.794 15.794 15.794 3.672 4.170 ms 1.423 5.487

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:f3c8:3803:1::6

peer jitter 2607:f3c8:3803:1::6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f3c8:3803:1::6 0.000 0.000 0.000 3.665 9.888 9.888 9.888 9.888 9.888 3.130 3.728 ms 0.7664 2.592

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:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net)

peer jitter 2607:f5b7:1:44::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) 0.000 0.000 0.000 7.826 42.881 42.881 42.881 42.881 42.881 11.996 12.673 ms 0.9758 3.228

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:f710:35::29c:0:1 (ntp6.kernfusion.at)

peer jitter 2607:f710:35::29c:0:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) 0.000 0.000 0.000 2.953 7.543 7.543 7.543 7.543 7.543 1.917 3.128 ms 0.7412 3.627

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:f710:35::29c:0:5

peer jitter 2607:f710:35::29c:0:5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f710:35::29c:0:5 0.000 0.000 0.000 4.556 7.900 7.900 7.900 7.900 7.900 2.166 4.553 ms -0.3058 2.962

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:f710:35::29c:0:8

peer jitter 2607:f710:35::29c:0:8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f710:35::29c:0:8 0.000 0.993 1.374 7.413 35.124 57.993 80.866 33.750 57.000 11.814 11.251 ms 2.307 10.35

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:ff50:0:1a::10 (ntpool0.603.newcontinuum.net)

peer jitter 2607:ff50:0:1a::10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) 0.000 0.000 0.000 4.417 9.460 9.460 9.460 9.460 9.460 2.696 4.546 ms -0.0246 2.498

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 2620:83:8000:140::b (tic.lbl.gov)

peer jitter 2620:83:8000:140::b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:83:8000:140::b (tic.lbl.gov) 0.000 0.880 1.380 3.683 18.060 54.396 107.171 16.680 53.516 8.265 5.655 ms 5.524 41.14

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 2620:8d:c000::f (blotch.image1tech.net)

peer jitter 2620:8d:c000::f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:8d:c000::f (blotch.image1tech.net) 0.000 0.000 0.000 11.399 23.001 23.001 23.001 23.001 23.001 6.886 11.933 ms -0.1456 2.635

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 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com)

peer jitter 2620:9a:e000:1061::2:165 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) 0.000 0.000 0.000 4.268 26.331 26.331 26.331 26.331 26.331 6.810 6.258 ms 1.9 6.02

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 2620:b0:2000:102::1:123 (time-h.den.codehof.net)

peer jitter 2620:b0:2000:102::1:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:b0:2000:102::1:123 (time-h.den.codehof.net) 0.000 0.000 0.000 44.659 162.644 162.644 162.644 162.644 162.644 50.617 46.606 ms 1.096 3.207

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 2620:b0:2000:102::2:123 (time-he.den.codehof.net)

peer jitter 2620:b0:2000:102::2:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:b0:2000:102::2:123 (time-he.den.codehof.net) 0.000 0.000 0.000 5.132 67.520 67.520 67.520 67.520 67.520 21.171 12.422 ms 2.131 5.771

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 2a00:d78:0:712:94:198:159:11 (nts1.time.nl)

peer jitter 2a00:d78:0:712:94:198:159:11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.000 1.584 2.966 20.836 77.601 99.042 530.168 74.635 97.459 26.838 29.328 ms 3.305 41.99

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 2.767 10.378 53.583 100.438 114.269 271.797 90.061 111.502 27.025 54.866 ms 0.2952 3.367

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 2.403 6.787 51.353 97.946 112.264 234.358 91.159 109.862 27.496 51.683 ms 0.2183 2.833

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:4f8:c012:1afb:123:123:123:123 (tock.telnet.li)

peer jitter 2a01:4f8:c012:1afb:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:4f8:c012:1afb:123:123:123:123 (tock.telnet.li) 0.000 2.107 4.538 29.415 67.555 89.560 458.532 63.018 87.453 23.919 32.258 ms 4.77 70.42

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a01:4f9:c013:fa27:123:123:123:123

peer jitter 2a01:4f9:c013:fa27:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:4f9:c013:fa27:123:123:123:123 0.000 1.942 3.997 36.742 92.861 109.042 178.690 88.864 107.100 29.597 40.764 ms 0.5627 2.58

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:4ff:f0:7300:123:123:123:123 (use1.ntspool.telnet.li)

peer jitter 2a01:4ff:f0:7300:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:4ff:f0:7300:123:123:123:123 (use1.ntspool.telnet.li) 0.000 1.015 1.606 5.227 35.666 58.999 390.666 34.060 57.984 15.078 10.007 ms 10.55 228.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 2a01:4ff:f0:ebce::1

peer jitter 2a01:4ff:f0:ebce::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:4ff:f0:ebce::1 0.000 0.000 0.000 25.847 25.847 25.847 25.847 25.847 25.847 12.924 12.924 ms 0 1

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com)

peer jitter 2a01:7e03::f03c:95ff:fef8:ac8c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) 0.000 0.000 0.000 32.068 70.288 70.288 70.288 70.288 70.288 19.572 34.261 ms 0.1428 3.002

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:7e04::f03c:94ff:fee2:cba5

peer jitter 2a01:7e04::f03c:94ff:fee2:cba5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:7e04::f03c:94ff:fee2:cba5 0.000 0.000 0.000 1.794 29.750 29.750 29.750 29.750 29.750 9.167 5.895 ms 1.677 4.108

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 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media)

peer jitter 2a05:dfc1:cb1:201:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) 0.000 0.643 1.008 3.233 6.112 8.996 9.058 5.104 8.353 1.611 3.441 ms 0.9168 4.632

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 2a0a:e5c0:2:2:0:c8ff:fe68:beb7 (2a0a-e5c0-2-2-0-c8ff-fe68-beb7.loves.ipv6.at.ungleich.ch)

peer jitter 2a0a:e5c0:2:2:0:c8ff:fe68:beb7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a0a:e5c0:2:2:0:c8ff:fe68:beb7 (2a0a-e5c0-2-2-0-c8ff-fe68-beb7.loves.ipv6.at.ungleich.ch) 0.960 1.460 2.257 13.905 74.907 99.253 114.435 72.649 97.793 24.920 24.749 ms 1.308 3.834

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 34.147.28.4

peer jitter 34.147.28.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 34.147.28.4 0.000 0.977 1.742 13.427 70.876 98.198 166.058 69.134 97.220 23.751 22.982 ms 1.543 5.626

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 37.27.11.4

peer jitter 37.27.11.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 37.27.11.4 0.000 0.000 1.780 14.020 76.180 81.696 81.940 74.400 81.696 20.637 20.684 ms 1.598 4.786

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 44.190.5.123

peer jitter 44.190.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 44.190.5.123 0.000 0.805 1.177 3.158 12.295 25.418 625.327 11.118 24.612 9.603 4.589 ms 37.86 2266

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.775 1.270 3.495 15.701 24.323 69.818 14.431 23.547 5.100 4.768 ms 4.748 38.3

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.77.126.122

peer jitter 45.77.126.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.77.126.122 0.000 0.000 0.000 1.018 3.979 3.979 3.979 3.979 3.979 0.941 1.194 ms 1.581 5.687

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

peer jitter 45.79.51.42 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.79.51.42 0.000 0.000 0.000 11.729 96.151 96.151 96.151 96.151 96.151 29.987 22.678 ms 1.636 4.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 45.83.234.123

peer jitter 45.83.234.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.83.234.123 0.000 0.000 0.000 44.153 69.832 100.538 100.538 69.832 100.538 21.987 43.105 ms -0.3601 3.347

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

peer jitter 45.84.199.136 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.84.199.136 0.000 0.000 0.000 7.227 34.845 34.845 34.845 34.845 34.845 11.450 10.051 ms 1.254 3.184

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 46.37.96.107

peer jitter 46.37.96.107 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 46.37.96.107 0.000 0.762 1.136 3.173 17.249 45.839 76.855 16.113 45.077 7.508 5.080 ms 4.938 32.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 50.117.3.52

peer jitter 50.117.3.52 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.117.3.52 0.000 0.000 0.000 1.241 1.948 1.948 1.948 1.948 1.948 0.616 1.028 ms -0.1887 2.181

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 50.117.3.95

peer jitter 50.117.3.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.117.3.95 0.000 0.000 0.000 4.938 9.600 9.600 9.600 9.600 9.600 3.585 4.705 ms -0.06002 1.66

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 50.205.57.38

peer jitter 50.205.57.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.205.57.38 0.000 0.000 0.000 2.064 12.794 26.867 26.867 12.794 26.867 5.655 3.818 ms 2.994 11.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 50.218.103.254

peer jitter 50.218.103.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.218.103.254 0.000 0.000 0.000 1.360 15.596 15.596 15.596 15.596 15.596 4.714 2.924 ms 2.06 5.866

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 51.38.58.233

peer jitter 51.38.58.233 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 51.38.58.233 0.000 0.627 1.195 2.758 18.088 25.470 29.937 16.893 24.843 5.518 4.851 ms 2.569 9.414

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 51.81.20.76

peer jitter 51.81.20.76 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 51.81.20.76 0.000 0.000 0.000 2.794 18.439 18.439 18.439 18.439 18.439 4.702 4.747 ms 2.128 6.656

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 51.81.226.229

peer jitter 51.81.226.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 51.81.226.229 0.000 0.000 0.000 3.776 10.325 13.199 13.199 10.325 13.199 3.650 4.396 ms 0.7568 2.753

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 64.79.100.197

peer jitter 64.79.100.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.79.100.197 0.000 0.000 0.817 2.208 16.989 29.767 29.820 16.172 29.767 5.117 3.706 ms 3.407 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 65.182.224.39

peer jitter 65.182.224.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 65.182.224.39 0.000 0.000 0.000 2.070 2.943 2.943 2.943 2.943 2.943 0.933 1.809 ms -0.8566 2.777

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 27.185 55.552 77.497 77.497 55.552 77.497 20.613 27.535 ms 0.1157 1.981

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

peer jitter 66.42.71.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.42.71.197 0.544 0.805 1.162 3.040 12.958 21.732 26.941 11.796 20.927 4.027 4.327 ms 2.769 11.93

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

peer jitter 66.85.78.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.85.78.80 0.000 0.000 0.000 2.718 5.161 5.161 5.161 5.161 5.161 2.005 2.147 ms 0.4553 1.672

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

peer jitter 67.217.246.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 67.217.246.127 0.000 0.544 1.405 3.301 20.244 36.524 37.261 18.839 35.979 7.198 6.206 ms 2.642 10.4

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 17.016 16.841 ms 0.4742 1.639

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 68.234.48.70

peer jitter 68.234.48.70 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 68.234.48.70 0.000 0.000 0.000 15.255 37.426 37.426 37.426 37.426 37.426 11.694 11.915 ms 0.673 2.554

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.768 1.568 3.830 14.050 65.312 103.870 12.482 64.544 11.118 6.050 ms 7.063 57.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 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.655 1.014 2.890 14.394 29.375 217.779 13.380 28.720 10.452 4.992 ms 13.28 242.1

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 71.19.144.140

peer jitter 71.19.144.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 71.19.144.140 0.000 0.000 0.000 2.244 28.288 28.288 28.288 28.288 28.288 6.176 4.071 ms 3.331 13.18

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 72.14.183.39

peer jitter 72.14.183.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.14.183.39 0.000 0.000 0.000 2.885 5.156 5.156 5.156 5.156 5.156 1.696 2.895 ms -0.4921 2.349

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 72.14.186.59

peer jitter 72.14.186.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.14.186.59 0.000 0.000 0.000 1.353 7.812 7.812 7.812 7.812 7.812 2.791 2.333 ms 1.36 3.086

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 72.46.53.234

peer jitter 72.46.53.234 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.46.53.234 0.000 0.000 0.000 3.818 99.485 99.485 99.485 99.485 99.485 27.363 16.024 ms 2.181 6.785

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 72.46.61.205

peer jitter 72.46.61.205 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.46.61.205 0.000 0.000 0.000 41.691 79.056 79.056 79.056 79.056 79.056 22.666 38.035 ms -0.356 2.423

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 73.185.182.209

peer jitter 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.185.182.209 0.000 1.188 1.697 3.815 25.345 43.709 79.900 23.648 42.521 9.600 8.061 ms 2.934 14.97

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 73.65.80.137

peer jitter 73.65.80.137 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.65.80.137 0.000 0.000 1.979 4.758 26.082 30.271 30.271 24.103 30.271 7.745 8.134 ms 1.314 3.612

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.986 2.913 32.332 77.863 100.698 150.671 74.950 99.712 24.650 35.065 ms 0.7028 3.425

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

peer jitter 77.42.37.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.42.37.85 0.000 1.059 1.880 19.516 80.741 96.805 116.085 78.861 95.746 26.717 29.766 ms 0.8 2.531

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 79.160.225.13

peer jitter 79.160.225.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 79.160.225.13 0.000 0.887 1.362 9.775 71.031 94.447 111.150 69.669 93.560 22.353 18.781 ms 1.751 5.554

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 83.147.242.172

peer jitter 83.147.242.172 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 83.147.242.172 0.000 0.844 1.213 3.146 7.606 19.766 60.098 6.393 18.922 3.506 3.831 ms 6.515 74.75

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 94.198.159.11

peer jitter 94.198.159.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 94.198.159.11 0.000 0.000 0.000 9.727 9.727 9.727 9.727 9.727 9.727 4.863 4.863 ms 0 1

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 96.19.94.82

peer jitter 96.19.94.82 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 96.19.94.82 0.000 0.000 0.000 3.136 3.526 3.526 3.526 3.526 3.526 1.310 2.584 ms -1.401 3.116

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 99.28.14.242

peer jitter 99.28.14.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 99.28.14.242 0.000 0.841 1.296 3.369 21.031 62.332 94.505 19.735 61.491 9.798 6.251 ms 5.026 34.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 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.481 0.718 1.785 4.326 6.178 1,615.750 3.608 5.697 11.163 2.227 ms 91.21 9716

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.194 0.220 0.320 0.480 0.627 1,591.279 0.259 0.433 9.969 0.463 ms 104 1.243e+04

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

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

RMS Jitter is field 8 in the peerstats log file.



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.500 0.748 2.006 5.412 8.131 2,002.029 4.665 7.631 12.258 2.524 ms 122.9 1.627e+04

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

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

RMS Jitter is field 8 in the peerstats log file.



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.177 0.214 0.336 0.757 1.105 2,001.141 0.543 0.928 13.644 0.517 ms 112.4 1.337e+04

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

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

RMS Jitter is field 8 in the peerstats log file.



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.000 0.448 0.656 1.624 4.156 7.939 199.488 3.500 7.491 2.328 2.001 ms 32.83 1895

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) 0.000 0.201 0.227 0.343 0.704 0.971 104.304 0.477 0.770 0.576 0.390 ms 116.2 1.651e+04

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

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

RMS Jitter is field 8 in the peerstats log file.



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.000 0.600 0.948 2.374 5.637 7.241 11.212 4.689 6.641 1.481 2.715 ms 1.233 5.001

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) 0.000 0.196 0.221 0.324 0.536 0.729 3,009.547 0.315 0.533 17.171 0.461 ms 152.2 2.388e+04

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -135.511 10.466 10.679 11.252 22.076 25.283 135.754 11.397 14.816 4.103 13.582 ppm 1.186 13.38
Local Clock Time Offset -126.620 -8.242 -6.377 -0.190 0.632 1.126 121.205 7.009 9.368 2.606 -1.455 ms 0.1579 185
Local RMS Frequency Jitter 0.0000 0.0032 0.0039 0.0131 0.299 0.496 73.177 0.295 0.493 0.609 0.082 ppm 71.16 6158
Local RMS Time Jitter 0.000 0.135 0.168 0.382 0.899 1.397 83.702 0.731 1.262 0.926 0.444 ms 44.15 2510
Server Jitter 104.131.155.175 0.000 0.000 0.000 3.656 17.731 18.171 18.171 17.731 18.171 4.618 5.158 ms 1.714 5.382
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 104.167.215.195 0.000 0.000 0.000 1.878 2.199 2.199 2.199 2.199 2.199 0.724 1.553 ms -1.474 3.661
Server Jitter 104.167.241.253 0.000 0.000 0.000 2.362 8.036 8.036 8.036 8.036 8.036 2.290 2.983 ms 0.6267 2.554
Server Jitter 104.234.61.117 0.480 0.742 1.191 3.261 15.561 24.862 40.403 14.370 24.120 4.950 4.809 ms 3.219 16.66
Server Jitter 108.61.73.243 0.568 0.834 1.318 9.146 40.391 56.637 69.973 39.073 55.803 12.470 12.844 ms 1.563 5.611
Server Jitter 12.71.198.242 0.000 0.000 0.000 2.476 14.247 14.247 14.247 14.247 14.247 4.389 3.547 ms 1.44 4.115
Server Jitter 129.146.193.200 0.000 0.000 0.604 2.622 17.247 17.857 18.051 16.643 17.857 3.912 3.814 ms 2.358 8.421
Server Jitter 131.239.5.43 0.000 0.000 0.000 1.655 3.135 3.135 3.135 3.135 3.135 0.882 1.743 ms -0.2966 2.893
Server Jitter 135.148.100.14 0.000 1.034 1.658 14.607 55.544 71.155 96.799 53.886 70.120 15.421 16.960 ms 1.968 8.02
Server Jitter 137.110.222.27 0.000 0.000 0.341 3.330 5.202 5.372 5.372 4.861 5.372 1.250 3.135 ms -0.5711 2.996
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 139.177.202.26 0.000 0.000 0.000 1.560 6.528 6.528 6.528 6.528 6.528 1.992 1.908 ms 1.039 3.07
Server Jitter 139.84.137.244 0.000 1.498 3.474 24.787 66.618 81.767 171.675 63.144 80.269 20.653 28.445 ms 1.093 5.724
Server Jitter 139.94.144.123 0.000 0.000 0.000 1.501 2.945 2.945 2.945 2.945 2.945 1.260 1.529 ms 0.002279 1.271
Server Jitter 141.11.234.198 0.000 0.000 0.000 8.942 58.361 58.361 58.361 58.361 58.361 19.957 16.134 ms 1.387 3.303
Server Jitter 141.11.89.193 0.000 0.000 0.000 1.558 2.015 2.015 2.015 2.015 2.015 0.652 1.474 ms -1.441 3.889
Server Jitter 142.202.190.19 0.000 0.000 0.000 2.175 6.985 16.409 16.409 6.985 16.409 3.192 2.973 ms 2.438 10.54
Server Jitter 144.202.0.197 0.000 0.000 0.000 2.470 4.307 4.307 4.307 4.307 4.307 1.435 2.296 ms -0.2563 1.847
Server Jitter 144.202.62.209 0.000 0.000 0.957 2.633 7.857 35.452 35.452 6.900 35.452 4.582 3.718 ms 5.102 32.94
Server Jitter 144.202.66.214 0.000 0.000 0.000 3.268 3.564 3.564 3.564 3.564 3.564 1.326 2.411 ms -0.873 2.102
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 149.248.12.167 0.000 0.000 0.000 1.415 6.547 6.547 6.547 6.547 6.547 2.701 2.851 ms 0.3599 1.282
Server Jitter 149.28.200.179 0.000 0.000 1.448 3.887 18.634 19.531 19.531 17.186 19.531 5.389 6.126 ms 1.504 3.906
Server Jitter 149.28.61.105 0.000 0.000 0.000 2.466 4.280 4.280 4.280 4.280 4.280 1.264 2.154 ms -0.03175 2.746
Server Jitter 15.204.198.96 0.000 0.000 1.528 9.635 18.188 24.740 24.740 16.661 24.740 6.496 9.205 ms 0.2143 1.632
Server Jitter 15.204.87.223 0.000 0.000 0.000 1.610 9.826 13.655 13.655 9.826 13.655 3.554 3.131 ms 1.556 4.646
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 158.51.99.19 0.000 0.861 1.216 3.317 19.810 51.816 228.673 18.594 50.955 13.195 6.155 ms 10.51 149.8
Server Jitter 162.159.200.1 0.000 0.000 1.145 2.877 10.503 23.214 42.450 9.358 23.214 4.283 3.898 ms 5.218 39.2
Server Jitter 162.159.200.123 0.000 0.000 0.000 3.085 9.842 12.427 12.427 9.842 12.427 2.969 3.852 ms 1.147 3.88
Server Jitter 163.123.152.14 0.000 0.000 0.000 3.728 4.357 4.357 4.357 4.357 4.357 1.674 2.791 ms -0.9099 2.151
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 170.187.147.56 0.000 0.824 1.119 3.127 15.294 35.711 154.182 14.175 34.886 9.178 5.070 ms 11.83 185.3
Server Jitter 171.66.97.126 0.000 0.786 1.119 2.722 12.572 21.171 22.978 11.453 20.386 3.966 3.904 ms 3.037 12.47
Server Jitter 172.232.15.202 0.000 0.000 0.000 3.215 33.540 33.540 33.540 33.540 33.540 13.913 13.115 ms 0.3783 1.284
Server Jitter 172.233.153.85 0.000 0.000 1.067 4.764 14.089 23.765 302.556 13.022 23.765 29.458 8.479 ms 9.659 96.43
Server Jitter 172.233.157.223 0.000 0.000 0.000 2.179 8.001 8.001 8.001 8.001 8.001 2.598 2.911 ms 0.8956 2.43
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.180 4.280 4.280 4.280 4.280 4.280 1.151 1.441 ms 1.042 3.453
Server Jitter 172.234.37.140 0.000 0.000 0.000 5.761 13.618 13.618 13.618 13.618 13.618 3.635 5.254 ms 0.5438 2.723
Server Jitter 172.234.44.141 0.000 0.000 0.000 2.374 7.577 7.577 7.577 7.577 7.577 2.262 3.093 ms 0.8517 2.644
Server Jitter 172.235.60.8 0.000 0.000 0.000 2.985 13.407 13.407 13.407 13.407 13.407 3.264 4.071 ms 1.906 6.336
Server Jitter 173.249.203.227 0.000 0.000 0.000 2.338 5.843 5.843 5.843 5.843 5.843 1.587 2.822 ms 0.3165 2.627
Server Jitter 173.255.192.10 0.000 0.000 0.000 2.331 9.584 9.584 9.584 9.584 9.584 2.608 3.116 ms 1.465 4.472
Server Jitter 173.255.255.133 0.000 0.000 0.000 4.005 4.530 4.530 4.530 4.530 4.530 1.752 2.866 ms -0.8115 2.037
Server Jitter 178.156.185.92 0.000 0.657 1.198 6.232 36.386 60.264 69.113 35.188 59.607 11.634 10.482 ms 2.26 9.133
Server Jitter 192.48.105.15 0.000 0.000 0.000 1.815 13.786 13.786 13.786 13.786 13.786 3.333 2.570 ms 2.497 8.699
Server Jitter 193.29.63.226 0.000 0.000 0.000 2.362 6.790 7.768 7.768 6.790 7.768 1.752 2.617 ms 1.293 4.972
Server Jitter 194.0.5.123 0.000 0.761 1.105 3.158 11.601 21.666 201.946 10.496 20.906 8.322 4.608 ms 15.45 309.5
Server Jitter 198.137.202.32 0.000 0.671 1.209 3.297 12.402 17.407 31.925 11.193 16.736 3.746 4.236 ms 3.509 20.09
Server Jitter 198.199.14.19 0.000 0.000 0.000 4.868 19.360 19.360 19.360 19.360 19.360 6.619 7.607 ms 0.7297 1.985
Server Jitter 198.211.103.209 0.000 0.000 0.000 3.750 13.433 21.945 21.945 13.433 21.945 4.568 5.256 ms 1.672 6.209
Server Jitter 198.46.254.130 0.000 0.789 1.171 3.308 24.735 39.397 60.567 23.564 38.608 8.364 6.211 ms 3.337 16.34
Server Jitter 198.60.22.240 0.000 0.000 0.000 1.229 8.123 8.123 8.123 8.123 8.123 2.808 2.774 ms 0.7715 2.116
Server Jitter 199.68.201.235 0.000 0.000 1.107 3.083 4.994 5.795 5.795 3.886 5.795 1.244 3.083 ms -0.137 2.992
Server Jitter 2001:1600:13:101::16b7 (ov-eaae4e.infomaniak.ch) 0.000 6.381 8.865 27.341 63.554 76.237 194.366 54.689 69.856 19.414 30.805 ms 1.848 13
Server Jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) 0.000 1.001 1.378 3.306 22.350 55.353 68.490 20.972 54.352 9.914 6.937 ms 3.502 16.46
Server Jitter 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) 0.000 0.000 0.000 6.706 10.790 10.790 10.790 10.790 10.790 3.771 6.760 ms -0.8058 2.409
Server Jitter 2001:19f0:6401:400:5400:4ff:fec3:522a 0.000 0.000 0.000 8.886 24.636 24.636 24.636 24.636 24.636 9.634 8.939 ms 0.7974 2.006
Server Jitter 2001:418:3ff::53 (x.ns.gin.ntt.net) 0.000 0.000 0.000 14.048 17.951 17.951 17.951 17.951 17.951 7.508 10.420 ms -0.3643 1.295
Server Jitter 2001:418:8405:4002::12 0.000 0.000 0.000 20.750 257.784 257.784 257.784 257.784 257.784 84.275 57.575 ms 1.804 4.559
Server Jitter 2001:41d0:303:65e9::1 (matthaeus.julia0815.de) 0.000 1.638 5.026 24.360 63.536 94.275 441.235 58.511 92.637 27.238 29.563 ms 7.074 97.1
Server Jitter 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) 0.000 1.136 2.036 12.122 41.039 72.944 118.845 39.003 71.808 15.175 15.560 ms 2.609 13.81
Server Jitter 2001:470:1f07:24f::123 0.000 0.000 0.000 25.254 42.613 42.613 42.613 42.613 42.613 13.314 18.607 ms 0.05496 1.858
Server Jitter 2001:470:1f2c:60:123:123:123:123 0.000 0.000 0.000 20.430 35.954 35.954 35.954 35.954 35.954 11.405 14.554 ms 0.1812 1.824
Server Jitter 2001:470:a:b4::2 (dell-2018.jamesb912.com.) 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ns nan nan
Server Jitter 2001:470:e8dc:10::123 0.000 0.001 0.001 0.003 0.017 0.089 589.082 0.016 0.088 33.422 2.611 s 15.05 248.3
Server Jitter 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) 0.000 1.102 1.686 10.928 48.225 61.432 219.778 46.539 60.331 15.215 14.564 ms 2.947 25.72
Server Jitter 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) 0.000 0.830 1.150 3.284 24.575 55.936 146.741 23.425 55.106 10.291 6.585 ms 4.523 32.1
Server Jitter 2001:558:6014:17:8dc5:5575:5560:2cb6 0.000 0.000 0.000 4.253 65.155 123.941 123.941 65.155 123.941 24.032 13.461 ms 3.066 13.01
Server Jitter 2001:559:2be:3::1001 0.000 0.000 0.000 3.333 53.390 53.390 53.390 53.390 53.390 13.672 9.507 ms 1.842 5.746
Server Jitter 2001:678:8::123 (any.time.nl) 0.000 1.333 2.446 22.705 84.523 104.133 240.582 82.077 102.800 26.854 31.138 ms 0.9834 3.47
Server Jitter 204.197.163.71 0.000 0.686 1.095 3.220 7.493 17.061 50.513 6.398 16.375 3.155 3.763 ms 6.631 80.71
Server Jitter 205.233.73.201 0.000 0.000 0.000 2.823 5.520 5.520 5.520 5.520 5.520 1.805 2.661 ms -0.09436 1.85
Server Jitter 208.113.130.146 0.000 0.861 1.394 5.061 43.913 76.684 232.036 42.519 75.823 18.789 11.721 ms 5.662 52.53
Server Jitter 208.67.72.43 0.000 0.000 0.000 20.684 46.773 46.773 46.773 46.773 46.773 14.479 19.405 ms 0.3984 2.247
Server Jitter 208.67.75.242 0.000 0.000 0.000 2.369 18.724 18.724 18.724 18.724 18.724 4.763 3.627 ms 2.559 8.478
Server Jitter 216.229.4.66 0.000 0.000 0.000 4.322 5.026 5.026 5.026 5.026 5.026 2.018 2.765 ms -0.2125 1.383
Server Jitter 216.229.4.69 0.000 0.000 0.000 2.477 5.003 5.695 5.695 5.003 5.695 1.718 2.457 ms 0.2191 2.013
Server Jitter 216.250.115.174 0.000 0.000 0.000 22.373 24.069 24.069 24.069 24.069 24.069 10.893 12.372 ms -0.02677 1.049
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.131.160.7 0.000 0.880 1.354 3.468 10.866 32.018 126.894 9.512 31.138 7.981 4.858 ms 9.335 108.7
Server Jitter 23.141.40.123 0.000 0.000 0.000 3.979 5.911 5.911 5.911 5.911 5.911 1.921 3.290 ms -0.4708 2.11
Server Jitter 23.142.248.8 0.000 0.000 0.000 1.269 2.327 2.327 2.327 2.327 2.327 0.866 1.154 ms -0.1197 1.574
Server Jitter 23.142.248.9 0.000 0.000 0.000 1.625 5.220 5.220 5.220 5.220 5.220 1.670 2.001 ms 0.7372 2.287
Server Jitter 23.143.196.199 0.000 0.000 0.000 1.033 2.250 2.250 2.250 2.250 2.250 0.756 1.094 ms -0.06783 1.795
Server Jitter 23.155.40.38 0.000 0.000 1.081 3.356 34.022 117.881 142.893 32.940 117.881 18.722 8.653 ms 5.033 31.38
Server Jitter 23.186.168.123 0.000 0.794 1.193 3.052 8.245 20.200 30.025 7.052 19.406 3.089 3.701 ms 3.772 21.92
Server Jitter 23.186.168.126 0.000 0.695 1.121 3.001 10.669 41.147 100.230 9.548 40.452 8.625 4.647 ms 7.962 75.3
Server Jitter 23.186.168.127 0.000 0.000 0.000 6.846 25.786 25.786 25.786 25.786 25.786 9.961 9.050 ms 0.9537 2.186
Server Jitter 23.186.168.128 0.000 0.814 1.329 3.310 8.610 17.200 23.748 7.281 16.386 2.792 3.875 ms 2.955 14.86
Server Jitter 23.186.168.129 0.000 0.699 1.253 3.436 8.998 17.637 105.774 7.745 16.939 4.861 4.275 ms 11.96 214.6
Server Jitter 23.186.168.130 0.000 0.000 0.000 3.466 73.799 73.994 73.994 73.799 73.994 19.691 9.038 ms 2.942 9.824
Server Jitter 23.186.168.131 0.000 0.749 1.266 3.133 8.261 15.037 223.184 6.995 14.289 9.704 4.117 ms 21.04 473.4
Server Jitter 23.186.168.132 0.000 0.893 1.264 3.336 9.267 18.503 72.944 8.003 17.610 3.765 4.130 ms 6.747 88.38
Server Jitter 23.95.49.216 0.000 0.804 1.089 2.946 11.443 17.019 159.086 10.354 16.216 7.100 4.020 ms 17.62 379.9
Server Jitter 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) 0.000 1.826 4.716 29.461 72.915 89.395 159.685 68.200 87.569 21.838 33.133 ms 0.7116 3.169
Server Jitter 2402:1f00:8101:d6::1 0.000 1.122 1.876 18.931 65.466 79.704 169.795 63.590 78.581 21.450 25.074 ms 1.025 4.123
Server Jitter 240b:4002:100:9f00:5bd1:9512:8a8b:25e 0.000 0.000 0.000 4.287 5.971 5.971 5.971 5.971 5.971 2.062 3.825 ms -0.9946 2.639
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d6 0.000 0.839 1.416 3.601 24.535 54.985 74.237 23.119 54.146 9.449 6.322 ms 4.13 22.24
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:26d9 0.000 0.000 0.000 19.678 21.828 21.828 21.828 21.828 21.828 8.593 13.132 ms -0.5264 1.711
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:1700:5455:a70::7b:1 0.000 0.000 1.444 4.653 23.669 27.142 27.142 22.225 27.142 7.742 8.428 ms 1.002 2.547
Server Jitter 2600:1702:7400:9ac0::314:5a 0.000 0.000 0.000 2.413 15.160 15.160 15.160 15.160 15.160 4.523 4.818 ms 1.082 3.061
Server Jitter 2600:1702:7400:9ac0::5b 0.000 0.000 0.000 2.689 7.877 7.877 7.877 7.877 7.877 2.509 3.387 ms 0.6509 2.164
Server Jitter 2600:1702:80c0:9a80:1ee4:b0a2:44bc:c606 0.000 0.000 0.000 5.087 22.009 22.009 22.009 22.009 22.009 8.471 7.694 ms 0.9852 2.224
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 1.432 2.735 23.981 80.125 100.086 260.324 77.390 98.655 25.098 30.934 ms 1.012 4.009
Server Jitter 2600:1f13:2c1:2e00::be00:5 0.000 0.941 1.487 3.653 25.297 93.488 214.829 23.809 92.548 16.422 7.675 ms 6.759 62.66
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.000 0.823 1.169 3.339 21.951 49.663 185.361 20.783 48.840 9.853 6.218 ms 5.748 56.48
Server Jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) 0.000 0.832 1.212 3.536 39.205 69.230 282.893 37.993 68.398 14.386 9.101 ms 4.117 32.69
Server Jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) 0.000 0.835 1.266 7.203 52.230 78.393 168.874 50.964 77.558 17.372 14.338 ms 2.244 9.57
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:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) 0.000 0.941 1.396 3.367 16.530 40.341 125.199 15.135 39.399 7.127 5.275 ms 7.261 91.76
Server Jitter 2600:3c00:e000:318::1 (jane.qotw.net) 0.000 0.936 1.251 3.291 18.596 45.542 55.919 17.345 44.606 7.258 5.661 ms 3.76 20.2
Server Jitter 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) 0.000 0.000 0.000 6.110 10.609 10.609 10.609 10.609 10.609 3.299 4.985 ms 0.1951 2.331
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.678 1.268 3.194 8.827 20.528 87.783 7.559 19.850 4.877 4.124 ms 8.554 112.3
Server Jitter 2600:3c02::f03c:94ff:fe59:f411 0.000 0.000 0.000 5.394 7.516 7.516 7.516 7.516 7.516 2.647 4.557 ms -0.5602 1.96
Server Jitter 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) 0.000 0.000 0.717 3.878 10.414 16.432 16.432 9.697 16.432 3.233 4.061 ms 1.999 7.801
Server Jitter 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) 0.000 0.000 0.000 4.625 9.182 9.182 9.182 9.182 9.182 3.008 4.335 ms -0.05862 1.872
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 2600:3c03::f03c:94ff:fe59:d3de 0.000 0.000 0.000 9.141 10.648 10.648 10.648 10.648 10.648 4.705 6.597 ms -0.6531 1.5
Server Jitter 2600:3c03:e002:1300::10 (ntp.electronmill.com) 0.000 0.000 0.000 3.877 7.718 7.718 7.718 7.718 7.718 2.384 3.718 ms 0.3575 1.964
Server Jitter 2600:3c06::f03c:94ff:fee2:9c28 0.000 0.000 0.000 9.325 30.736 30.736 30.736 30.736 30.736 11.553 11.593 ms 0.8589 2.149
Server Jitter 2600:3c06::f03c:94ff:fee2:c53a 0.000 0.000 0.000 15.615 24.117 24.117 24.117 24.117 24.117 9.987 13.244 ms -0.3427 1.5
Server Jitter 2600:4040:e0da:f000::cbb9:201a 0.000 0.000 0.547 12.110 32.149 45.133 45.133 31.602 45.133 10.649 11.858 ms 1.048 3.818
Server Jitter 2602:291:69::8 (time2.trtnw.net) 0.000 0.000 0.000 0.970 1.844 1.844 1.844 1.844 1.844 0.552 0.976 ms -0.2468 2.677
Server Jitter 2602:291:69::9 (time.trtnw.net) 0.000 0.000 0.000 3.210 6.266 9.048 9.048 6.266 9.048 1.966 3.075 ms 0.8974 4.743
Server Jitter 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) 0.000 0.932 1.359 3.513 14.745 35.541 139.194 13.387 34.609 7.506 5.120 ms 8.384 105.7
Server Jitter 2602:2eb:2:95:1234:5678:9abc:def0 0.000 0.928 1.427 3.722 27.943 60.804 262.579 26.516 59.876 14.162 7.986 ms 8.402 112.8
Server Jitter 2602:80b:5000::36 (time.meme.holdings) 0.000 0.000 4.621 20.856 76.477 84.174 87.838 71.856 84.174 21.252 27.684 ms 0.9659 3.216
Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) 0.000 0.000 0.000 3.625 9.349 9.349 9.349 9.349 9.349 2.588 4.147 ms 0.2659 2.467
Server Jitter 2602:f9ba:69::210 (as393746.mci.trtnw.net) 0.000 0.000 1.448 9.790 67.645 87.579 97.607 66.198 87.579 21.576 19.008 ms 1.617 4.947
Server Jitter 2602:fb95:16::123 (time5.sigi.net) 0.000 0.000 0.000 2.945 6.744 6.744 6.744 6.744 6.744 1.680 2.843 ms 0.7474 3.802
Server Jitter 2602:fc2f:100:9800::dead:beef 0.000 1.459 2.342 5.507 62.283 166.197 259.248 59.941 164.738 29.654 14.829 ms 4.48 25.6
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 2602:fe2e:3:d:f9:c7ff:fef5:379c 0.000 0.000 0.000 2.011 3.424 3.424 3.424 3.424 3.424 0.929 1.786 ms -0.1796 2.962
Server Jitter 2603:c020:0:8369:0:ba11:ba11:ba11 0.000 0.000 0.000 2.800 5.546 5.546 5.546 5.546 5.546 2.031 2.476 ms 0.3879 1.867
Server Jitter 2603:c020:0:8369:1111:1111:1111:1112 0.000 0.000 0.000 2.768 74.324 99.180 99.180 74.324 99.180 23.092 16.164 ms 2.053 7.146
Server Jitter 2603:c020:0:8369::bad:beef 0.000 0.000 0.000 3.940 3.991 3.991 3.991 3.991 3.991 1.645 2.811 ms -1.067 2.256
Server Jitter 2603:c020:0:8369::f00d:feed 0.000 0.000 0.000 2.299 8.110 8.110 8.110 8.110 8.110 2.540 2.878 ms 0.9528 2.711
Server Jitter 2603:c020:0:8369:feed:feed:feed:feed 0.000 0.000 0.000 3.112 13.323 13.323 13.323 13.323 13.323 3.317 3.712 ms 1.612 5.406
Server Jitter 2603:c024:c005:a600:efb6:d213:cad8:251d 0.000 0.000 0.000 14.820 57.595 57.595 57.595 57.595 57.595 17.229 20.244 ms 1.209 3.457
Server Jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 (us1-ipv6.cracky-chan.com) 0.000 0.000 1.769 15.711 48.002 49.094 49.094 46.233 49.094 11.410 15.959 ms 1.156 4.594
Server Jitter 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) 0.000 0.000 0.000 2.991 9.649 9.649 9.649 9.649 9.649 2.561 3.518 ms 1.144 3.781
Server Jitter 2604:2dc0:202:300::140d (vps-8f06187a.vps.ovh.us) 0.000 0.965 1.366 3.498 9.087 21.237 71.985 7.721 20.272 3.773 4.317 ms 5.523 60.29
Server Jitter 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) 0.000 0.906 1.363 3.338 10.703 34.136 119.042 9.340 33.230 6.208 4.661 ms 7.131 78.29
Server Jitter 2604:4300:a:299::164 0.000 0.000 0.000 3.582 6.183 11.304 11.304 6.183 11.304 2.417 3.650 ms 1.209 5.485
Server Jitter 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) 0.000 0.000 0.000 3.639 13.829 13.829 13.829 13.829 13.829 3.432 4.353 ms 1.336 4.939
Server Jitter 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) 0.000 0.000 0.000 21.487 31.405 31.405 31.405 31.405 31.405 13.108 17.631 ms -0.4158 1.5
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.000 0.000 0.869 1.657 1.657 1.657 1.657 1.657 0.479 0.845 ms -0.09905 2.996
Server Jitter 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) 0.000 0.965 1.447 3.716 18.849 29.446 120.523 17.402 28.481 10.597 5.665 ms 8.209 79.46
Server Jitter 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) 0.000 0.000 0.000 8.010 25.574 25.574 25.574 25.574 25.574 6.576 8.369 ms 0.7283 3.152
Server Jitter 2604:a880:800:10::70f:b001 (ellone.fdisk.io) 0.000 0.000 0.000 1.765 3.857 3.857 3.857 3.857 3.857 1.036 1.790 ms 0.1052 2.65
Server Jitter 2604:a880:800:a1::ec9:5001 0.000 0.000 0.000 3.953 99.014 144.987 144.987 99.014 144.987 36.715 24.475 ms 1.773 5.482
Server Jitter 2604:d200::39 (white.web-ster.com) 0.000 0.000 0.000 1.801 12.238 25.815 25.815 12.238 25.815 5.414 3.117 ms 3.361 13.81
Server Jitter 2605:4840:3:fb19::1 (chi3.us.ntp.li) 0.000 2.869 6.410 21.881 58.467 76.100 242.923 52.056 73.231 18.024 25.740 ms 3.934 40.06
Server Jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ns nan nan
Server Jitter 2605:6400:488d:3686:546d:c03c:1689:20c 0.000 0.000 0.000 1.372 9.116 9.116 9.116 9.116 9.116 3.886 3.057 ms 0.6883 1.57
Server Jitter 2605:6400:84e1::123 0.000 0.000 0.000 3.606 8.882 8.882 8.882 8.882 8.882 2.455 3.745 ms 0.4362 2.81
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.000 0.867 1.277 3.404 17.303 42.479 226.379 16.026 41.613 8.577 5.435 ms 8.083 113.6
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.855 1.249 3.386 15.754 42.335 176.369 14.505 41.480 8.412 5.263 ms 8.396 109.8
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 2606:82c0:22::e (time2.lshiy.com) 0.000 0.000 0.000 4.592 24.843 24.843 24.843 24.843 24.843 9.006 8.155 ms 1.154 2.626
Server Jitter 2606:82c0:23::e (time3.lshiy.com) 0.000 0.000 0.000 3.337 8.248 8.248 8.248 8.248 8.248 2.270 3.415 ms 0.3181 2.67
Server Jitter 2607:5600:182:500::1 (ntp-1.jonlight.com) 0.000 0.000 0.000 10.156 45.021 45.021 45.021 45.021 45.021 12.499 11.485 ms 1.431 4.572
Server Jitter 2607:7c80:54:3::32 0.000 0.000 0.000 3.603 11.499 11.499 11.499 11.499 11.499 3.098 4.294 ms 1.035 3.383
Server Jitter 2607:7c80:54:3::56 (owners.kjsl.com) 0.000 0.000 1.298 3.181 22.900 24.794 24.794 21.602 24.794 5.837 5.520 ms 2.225 7.106
Server Jitter 2607:9000:7000:23:216:3cff:fe25:38d7 0.000 0.000 0.000 7.179 57.684 57.684 57.684 57.684 57.684 16.210 10.235 ms 2.43 7.385
Server Jitter 2607:9d00:2000:16::9269:208a 0.000 0.000 0.000 3.585 32.658 32.768 32.768 32.658 32.768 8.863 6.355 ms 2.336 7.193
Server Jitter 2607:b500:410:7700::1 0.000 0.000 0.000 3.930 45.395 48.813 48.813 45.395 48.813 12.860 8.432 ms 2.364 7.345
Server Jitter 2607:f1c0:f014:9e00::2 0.000 0.000 0.000 11.460 31.195 31.195 31.195 31.195 31.195 9.231 9.169 ms 0.9354 3.131
Server Jitter 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) 0.000 0.000 0.000 3.311 58.981 58.981 58.981 58.981 58.981 21.215 11.609 ms 1.777 4.18
Server Jitter 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) 0.000 0.000 0.000 2.585 3.939 3.939 3.939 3.939 3.939 1.251 2.204 ms -0.4741 2.288
Server Jitter 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) 0.000 0.000 0.000 6.053 20.902 20.902 20.902 20.902 20.902 5.847 6.566 ms 1.063 3.708
Server Jitter 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) 0.000 0.000 0.000 3.713 17.103 17.166 17.166 17.103 17.166 4.236 4.518 ms 1.905 6.172
Server Jitter 2607:f1c0:f075:9900::1 0.000 0.000 0.000 3.194 62.537 70.431 70.431 62.537 70.431 17.930 9.867 ms 2.624 8.577
Server Jitter 2607:f298:5:101d:f816:3eff:fefd:8817 0.000 0.000 0.000 3.238 15.794 15.794 15.794 15.794 15.794 3.672 4.170 ms 1.423 5.487
Server Jitter 2607:f3c8:3803:1::6 0.000 0.000 0.000 3.665 9.888 9.888 9.888 9.888 9.888 3.130 3.728 ms 0.7664 2.592
Server Jitter 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) 0.000 0.000 0.000 7.826 42.881 42.881 42.881 42.881 42.881 11.996 12.673 ms 0.9758 3.228
Server Jitter 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) 0.000 0.000 0.000 2.953 7.543 7.543 7.543 7.543 7.543 1.917 3.128 ms 0.7412 3.627
Server Jitter 2607:f710:35::29c:0:5 0.000 0.000 0.000 4.556 7.900 7.900 7.900 7.900 7.900 2.166 4.553 ms -0.3058 2.962
Server Jitter 2607:f710:35::29c:0:8 0.000 0.993 1.374 7.413 35.124 57.993 80.866 33.750 57.000 11.814 11.251 ms 2.307 10.35
Server Jitter 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) 0.000 0.000 0.000 4.417 9.460 9.460 9.460 9.460 9.460 2.696 4.546 ms -0.0246 2.498
Server Jitter 2620:83:8000:140::b (tic.lbl.gov) 0.000 0.880 1.380 3.683 18.060 54.396 107.171 16.680 53.516 8.265 5.655 ms 5.524 41.14
Server Jitter 2620:8d:c000::f (blotch.image1tech.net) 0.000 0.000 0.000 11.399 23.001 23.001 23.001 23.001 23.001 6.886 11.933 ms -0.1456 2.635
Server Jitter 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) 0.000 0.000 0.000 4.268 26.331 26.331 26.331 26.331 26.331 6.810 6.258 ms 1.9 6.02
Server Jitter 2620:b0:2000:102::1:123 (time-h.den.codehof.net) 0.000 0.000 0.000 44.659 162.644 162.644 162.644 162.644 162.644 50.617 46.606 ms 1.096 3.207
Server Jitter 2620:b0:2000:102::2:123 (time-he.den.codehof.net) 0.000 0.000 0.000 5.132 67.520 67.520 67.520 67.520 67.520 21.171 12.422 ms 2.131 5.771
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.000 1.584 2.966 20.836 77.601 99.042 530.168 74.635 97.459 26.838 29.328 ms 3.305 41.99
Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 0.000 2.767 10.378 53.583 100.438 114.269 271.797 90.061 111.502 27.025 54.866 ms 0.2952 3.367
Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) 0.000 2.403 6.787 51.353 97.946 112.264 234.358 91.159 109.862 27.496 51.683 ms 0.2183 2.833
Server Jitter 2a01:4f8:c012:1afb:123:123:123:123 (tock.telnet.li) 0.000 2.107 4.538 29.415 67.555 89.560 458.532 63.018 87.453 23.919 32.258 ms 4.77 70.42
Server Jitter 2a01:4f9:c013:fa27:123:123:123:123 0.000 1.942 3.997 36.742 92.861 109.042 178.690 88.864 107.100 29.597 40.764 ms 0.5627 2.58
Server Jitter 2a01:4ff:f0:7300:123:123:123:123 (use1.ntspool.telnet.li) 0.000 1.015 1.606 5.227 35.666 58.999 390.666 34.060 57.984 15.078 10.007 ms 10.55 228.5
Server Jitter 2a01:4ff:f0:ebce::1 0.000 0.000 0.000 25.847 25.847 25.847 25.847 25.847 25.847 12.924 12.924 ms 0 1
Server Jitter 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) 0.000 0.000 0.000 32.068 70.288 70.288 70.288 70.288 70.288 19.572 34.261 ms 0.1428 3.002
Server Jitter 2a01:7e04::f03c:94ff:fee2:cba5 0.000 0.000 0.000 1.794 29.750 29.750 29.750 29.750 29.750 9.167 5.895 ms 1.677 4.108
Server Jitter 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) 0.000 0.643 1.008 3.233 6.112 8.996 9.058 5.104 8.353 1.611 3.441 ms 0.9168 4.632
Server Jitter 2a0a:e5c0:2:2:0:c8ff:fe68:beb7 (2a0a-e5c0-2-2-0-c8ff-fe68-beb7.loves.ipv6.at.ungleich.ch) 0.960 1.460 2.257 13.905 74.907 99.253 114.435 72.649 97.793 24.920 24.749 ms 1.308 3.834
Server Jitter 34.147.28.4 0.000 0.977 1.742 13.427 70.876 98.198 166.058 69.134 97.220 23.751 22.982 ms 1.543 5.626
Server Jitter 37.27.11.4 0.000 0.000 1.780 14.020 76.180 81.696 81.940 74.400 81.696 20.637 20.684 ms 1.598 4.786
Server Jitter 44.190.5.123 0.000 0.805 1.177 3.158 12.295 25.418 625.327 11.118 24.612 9.603 4.589 ms 37.86 2266
Server Jitter 45.63.54.13 0.000 0.775 1.270 3.495 15.701 24.323 69.818 14.431 23.547 5.100 4.768 ms 4.748 38.3
Server Jitter 45.77.126.122 0.000 0.000 0.000 1.018 3.979 3.979 3.979 3.979 3.979 0.941 1.194 ms 1.581 5.687
Server Jitter 45.79.51.42 0.000 0.000 0.000 11.729 96.151 96.151 96.151 96.151 96.151 29.987 22.678 ms 1.636 4.376
Server Jitter 45.83.234.123 0.000 0.000 0.000 44.153 69.832 100.538 100.538 69.832 100.538 21.987 43.105 ms -0.3601 3.347
Server Jitter 45.84.199.136 0.000 0.000 0.000 7.227 34.845 34.845 34.845 34.845 34.845 11.450 10.051 ms 1.254 3.184
Server Jitter 46.37.96.107 0.000 0.762 1.136 3.173 17.249 45.839 76.855 16.113 45.077 7.508 5.080 ms 4.938 32.2
Server Jitter 50.117.3.52 0.000 0.000 0.000 1.241 1.948 1.948 1.948 1.948 1.948 0.616 1.028 ms -0.1887 2.181
Server Jitter 50.117.3.95 0.000 0.000 0.000 4.938 9.600 9.600 9.600 9.600 9.600 3.585 4.705 ms -0.06002 1.66
Server Jitter 50.205.57.38 0.000 0.000 0.000 2.064 12.794 26.867 26.867 12.794 26.867 5.655 3.818 ms 2.994 11.9
Server Jitter 50.218.103.254 0.000 0.000 0.000 1.360 15.596 15.596 15.596 15.596 15.596 4.714 2.924 ms 2.06 5.866
Server Jitter 51.38.58.233 0.000 0.627 1.195 2.758 18.088 25.470 29.937 16.893 24.843 5.518 4.851 ms 2.569 9.414
Server Jitter 51.81.20.76 0.000 0.000 0.000 2.794 18.439 18.439 18.439 18.439 18.439 4.702 4.747 ms 2.128 6.656
Server Jitter 51.81.226.229 0.000 0.000 0.000 3.776 10.325 13.199 13.199 10.325 13.199 3.650 4.396 ms 0.7568 2.753
Server Jitter 64.79.100.197 0.000 0.000 0.817 2.208 16.989 29.767 29.820 16.172 29.767 5.117 3.706 ms 3.407 14.88
Server Jitter 65.182.224.39 0.000 0.000 0.000 2.070 2.943 2.943 2.943 2.943 2.943 0.933 1.809 ms -0.8566 2.777
Server Jitter 66.118.231.14 0.000 0.000 0.000 27.185 55.552 77.497 77.497 55.552 77.497 20.613 27.535 ms 0.1157 1.981
Server Jitter 66.42.71.197 0.544 0.805 1.162 3.040 12.958 21.732 26.941 11.796 20.927 4.027 4.327 ms 2.769 11.93
Server Jitter 66.85.78.80 0.000 0.000 0.000 2.718 5.161 5.161 5.161 5.161 5.161 2.005 2.147 ms 0.4553 1.672
Server Jitter 67.217.246.127 0.000 0.544 1.405 3.301 20.244 36.524 37.261 18.839 35.979 7.198 6.206 ms 2.642 10.4
Server Jitter 67.217.246.204 0.000 0.000 0.000 12.593 47.481 47.481 47.481 47.481 47.481 17.016 16.841 ms 0.4742 1.639
Server Jitter 68.234.48.70 0.000 0.000 0.000 15.255 37.426 37.426 37.426 37.426 37.426 11.694 11.915 ms 0.673 2.554
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.768 1.568 3.830 14.050 65.312 103.870 12.482 64.544 11.118 6.050 ms 7.063 57.74
Server Jitter 69.89.207.99 0.000 0.655 1.014 2.890 14.394 29.375 217.779 13.380 28.720 10.452 4.992 ms 13.28 242.1
Server Jitter 71.19.144.140 0.000 0.000 0.000 2.244 28.288 28.288 28.288 28.288 28.288 6.176 4.071 ms 3.331 13.18
Server Jitter 72.14.183.39 0.000 0.000 0.000 2.885 5.156 5.156 5.156 5.156 5.156 1.696 2.895 ms -0.4921 2.349
Server Jitter 72.14.186.59 0.000 0.000 0.000 1.353 7.812 7.812 7.812 7.812 7.812 2.791 2.333 ms 1.36 3.086
Server Jitter 72.46.53.234 0.000 0.000 0.000 3.818 99.485 99.485 99.485 99.485 99.485 27.363 16.024 ms 2.181 6.785
Server Jitter 72.46.61.205 0.000 0.000 0.000 41.691 79.056 79.056 79.056 79.056 79.056 22.666 38.035 ms -0.356 2.423
Server Jitter 73.185.182.209 0.000 1.188 1.697 3.815 25.345 43.709 79.900 23.648 42.521 9.600 8.061 ms 2.934 14.97
Server Jitter 73.65.80.137 0.000 0.000 1.979 4.758 26.082 30.271 30.271 24.103 30.271 7.745 8.134 ms 1.314 3.612
Server Jitter 77.37.97.124 0.000 0.986 2.913 32.332 77.863 100.698 150.671 74.950 99.712 24.650 35.065 ms 0.7028 3.425
Server Jitter 77.42.37.85 0.000 1.059 1.880 19.516 80.741 96.805 116.085 78.861 95.746 26.717 29.766 ms 0.8 2.531
Server Jitter 79.160.225.13 0.000 0.887 1.362 9.775 71.031 94.447 111.150 69.669 93.560 22.353 18.781 ms 1.751 5.554
Server Jitter 83.147.242.172 0.000 0.844 1.213 3.146 7.606 19.766 60.098 6.393 18.922 3.506 3.831 ms 6.515 74.75
Server Jitter 94.198.159.11 0.000 0.000 0.000 9.727 9.727 9.727 9.727 9.727 9.727 4.863 4.863 ms 0 1
Server Jitter 96.19.94.82 0.000 0.000 0.000 3.136 3.526 3.526 3.526 3.526 3.526 1.310 2.584 ms -1.401 3.116
Server Jitter 99.28.14.242 0.000 0.841 1.296 3.369 21.031 62.332 94.505 19.735 61.491 9.798 6.251 ms 5.026 34.5
Server Jitter SHM(0) 0.000 0.481 0.718 1.785 4.326 6.178 1,615.750 3.608 5.697 11.163 2.227 ms 91.21 9716
Server Jitter SHM(1) 0.000 0.194 0.220 0.320 0.480 0.627 1,591.279 0.259 0.433 9.969 0.463 ms 104 1.243e+04
Server Jitter SHM(2) 0.000 0.500 0.748 2.006 5.412 8.131 2,002.029 4.665 7.631 12.258 2.524 ms 122.9 1.627e+04
Server Jitter SHM(3) 0.000 0.177 0.214 0.336 0.757 1.105 2,001.141 0.543 0.928 13.644 0.517 ms 112.4 1.337e+04
Server Jitter SOCK(0) 0.000 0.448 0.656 1.624 4.156 7.939 199.488 3.500 7.491 2.328 2.001 ms 32.83 1895
Server Jitter SOCK(1) 0.000 0.201 0.227 0.343 0.704 0.971 104.304 0.477 0.770 0.576 0.390 ms 116.2 1.651e+04
Server Jitter SOCK(2) 0.000 0.600 0.948 2.374 5.637 7.241 11.212 4.689 6.641 1.481 2.715 ms 1.233 5.001
Server Jitter SOCK(3) 0.000 0.196 0.221 0.324 0.536 0.729 3,009.547 0.315 0.533 17.171 0.461 ms 152.2 2.388e+04
Server Offset 104.131.155.175 -2.525 -2.525 -1.209 5.368 12.615 16.334 16.334 13.824 18.859 4.610 5.570 ms 0.3612 2.585
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 104.167.215.195 -99.469 -99.469 -99.469 -96.402 -95.938 -95.938 -95.938 3.532 3.532 1.166 -97.068 ms -1.222 3.199
Server Offset 104.167.241.253 -1.130 -1.130 -1.130 3.827 174.956 174.956 174.956 176.087 176.087 77.809 54.544 ms 0.8304 1.696
Server Offset 104.234.61.117 -19.828 -4.247 2.476 5.088 7.186 8.098 10.357 4.710 12.345 2.148 4.871 ms -4.632 41.14
Server Offset 108.61.73.243 -4.642 0.171 2.587 5.083 7.301 8.231 12.202 4.714 8.059 1.563 5.056 ms -0.9729 8.127
Server Offset 12.71.198.242 -567.986 -567.986 -567.986 -8.926 5.527 5.527 5.527 573.513 573.513 281.819 -249.816 ms -0.223 1.051
Server Offset 129.146.193.200 -0.800 0.856 1.480 4.811 6.531 7.695 8.742 5.051 6.839 1.487 4.576 ms -0.7309 4.259
Server Offset 131.239.5.43 0.782 0.782 0.782 4.026 4.797 4.797 4.797 4.014 4.014 1.405 3.356 ms -1.032 2.322
Server Offset 135.148.100.14 -31.469 -1.302 3.035 6.034 8.883 103.460 109.098 5.848 104.763 17.769 8.674 ms 4.727 26.05
Server Offset 137.110.222.27 2.083 2.083 3.615 5.797 9.449 10.485 10.485 5.834 8.402 1.558 5.893 ms 0.5532 4.579
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 139.177.202.26 2.369 2.369 2.369 5.594 13.217 13.217 13.217 10.848 10.848 3.941 6.958 ms 0.6 1.806
Server Offset 139.84.137.244 -88.151 -18.896 -1.976 8.174 12.866 16.588 23.798 14.843 35.484 6.651 6.780 ms -4.531 43.03
Server Offset 139.94.144.123 7.327 7.327 7.327 7.569 8.239 8.239 8.239 0.913 0.913 0.357 7.696 ms 0.4162 1.533
Server Offset 141.11.234.198 -23.184 -23.184 -23.184 3.651 11.780 11.780 11.780 34.964 34.964 8.939 0.688 ms -1.28 4.6
Server Offset 141.11.89.193 2.147 2.147 2.147 3.363 5.337 5.337 5.337 3.190 3.190 1.124 3.580 ms 0.1122 1.688
Server Offset 142.202.190.19 -170.488 -170.488 -169.889 6.947 228.113 229.915 229.915 398.002 400.403 122.650 52.253 ms 0.2226 2.25
Server Offset 144.202.0.197 2.542 2.542 2.542 5.206 10.116 10.116 10.116 7.574 7.574 1.946 5.495 ms 0.6649 3.455
Server Offset 144.202.62.209 -2.931 -2.931 -1.517 0.876 6.180 36.327 36.327 7.696 39.258 5.627 1.903 ms 5.12 30.38
Server Offset 144.202.66.214 -94.866 -94.866 -94.866 -89.704 -88.958 -88.958 -88.958 5.908 5.908 2.060 -91.017 ms -0.812 2.336
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 149.248.12.167 6.974 6.974 6.974 12.448 13.486 13.486 13.486 6.511 6.511 2.871 10.594 ms -0.3694 1.196
Server Offset 149.28.200.179 1.712 1.712 3.167 5.584 10.014 25.332 25.332 6.847 23.620 3.335 5.924 ms 4.121 23.91
Server Offset 149.28.61.105 2.916 2.916 2.916 5.252 8.017 8.017 8.017 5.100 5.100 1.667 5.088 ms 0.4936 2.163
Server Offset 15.204.198.96 -806.440 -806.440 -15.115 0.763 4.729 8.189 8.189 19.845 814.629 169.536 -36.913 ms -4.304 19.54
Server Offset 15.204.87.223 -10.681 -10.681 -8.344 2.175 164.825 164.832 164.832 173.170 175.513 65.332 29.557 ms 1.56 3.461
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 158.51.99.19 -157.868 -3.714 0.315 3.544 6.019 8.972 238.853 5.704 12.686 14.413 4.009 ms 11.84 228.2
Server Offset 162.159.200.1 -4.289 -1.565 3.446 6.207 8.276 9.113 9.909 4.830 10.678 1.742 6.046 ms -1.815 10.92
Server Offset 162.159.200.123 -6.062 -6.062 -5.886 -0.049 7.264 9.110 9.110 13.149 15.172 4.421 0.662 ms 0.1749 1.786
Server Offset 163.123.152.14 8.299 8.299 8.299 9.300 12.567 12.567 12.567 4.268 4.268 1.664 9.751 ms 0.9993 2.22
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 170.187.147.56 -0.641 -0.241 1.518 4.094 6.492 7.541 8.261 4.974 7.782 1.471 4.099 ms -0.1755 3.293
Server Offset 171.66.97.126 -5.352 -3.209 -1.979 0.739 2.487 3.087 4.376 4.466 6.297 1.429 0.549 ms -0.8383 4.339
Server Offset 172.232.15.202 0.710 0.710 0.710 4.702 38.555 38.555 38.555 37.846 37.846 15.838 13.311 ms 0.9197 1.889
Server Offset 172.233.153.85 -9.447 -9.196 -7.932 -3.852 1.978 2.524 2.830 9.910 11.720 3.072 -3.587 ms 0.398 2.315
Server Offset 172.233.157.223 -4.047 -4.047 -4.047 3.553 5.955 5.955 5.955 10.002 10.002 3.165 2.404 ms -1.04 2.663
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 3.459 5.884 5.884 5.884 6.372 6.372 2.046 2.970 ms -0.3216 1.683
Server Offset 172.234.37.140 -9.587 -9.587 -9.587 4.151 11.157 11.157 11.157 20.745 20.745 4.913 3.204 ms -0.9547 3.843
Server Offset 172.234.44.141 -1.177 -1.177 -1.177 4.942 9.373 9.373 9.373 10.549 10.549 3.559 3.891 ms -0.2618 1.724
Server Offset 172.235.60.8 0.376 0.376 0.376 3.004 16.005 16.005 16.005 15.630 15.630 4.175 4.760 ms 1.627 4.998
Server Offset 173.249.203.227 2.418 2.418 2.418 7.578 11.331 11.331 11.331 8.912 8.912 2.607 6.865 ms -0.2799 2.399
Server Offset 173.255.192.10 -0.501 -0.501 -0.501 8.854 11.145 11.145 11.145 11.646 11.646 3.481 7.479 ms -1.158 3.37
Server Offset 173.255.255.133 -1.715 -1.715 -1.715 -0.964 1.511 1.511 1.511 3.226 3.226 1.274 -0.647 ms 1.007 2.214
Server Offset 178.156.185.92 -26.222 -8.831 -4.147 -0.703 5.776 8.694 15.799 9.923 17.525 3.089 -0.428 ms -0.01771 10.84
Server Offset 192.48.105.15 0.449 0.449 0.449 3.200 7.335 7.335 7.335 6.885 6.885 1.829 3.297 ms 0.5249 2.601
Server Offset 193.29.63.226 -97.166 -97.166 -95.281 0.589 7.015 9.170 9.170 102.297 106.336 42.310 -21.757 ms -1.137 2.322
Server Offset 194.0.5.123 -26.524 -5.524 -3.127 0.453 3.676 5.839 37.622 6.802 11.362 2.403 0.436 ms 0.8841 23.44
Server Offset 198.137.202.32 -1.462 -1.396 1.619 5.827 7.932 11.548 12.433 6.313 12.944 1.882 5.599 ms -0.7187 6.807
Server Offset 198.199.14.19 -4.168 -4.168 -4.168 3.527 9.207 9.207 9.207 13.374 13.374 3.647 3.201 ms -0.3311 2.34
Server Offset 198.211.103.209 -15.435 -15.435 -7.248 1.023 11.374 11.645 11.645 18.622 27.080 5.487 1.111 ms -0.25 4.025
Server Offset 198.46.254.130 -2.287 0.292 2.403 4.430 9.560 11.525 16.197 7.157 11.234 2.139 4.805 ms 1.192 5.984
Server Offset 198.60.22.240 -144.129 -144.129 -144.129 9.541 18.010 18.010 18.010 162.140 162.140 65.641 -23.178 ms -1.269 2.625
Server Offset 199.68.201.235 2.195 2.195 2.320 4.878 7.295 9.614 9.614 4.975 7.419 1.530 4.830 ms 1.056 5.383
Server Offset 2001:1600:13:101::16b7 (ov-eaae4e.infomaniak.ch) -48.803 -25.492 -13.939 -1.873 9.982 15.177 36.277 23.921 40.669 7.350 -1.722 ms -1.042 9.167
Server Offset 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) 0.214 2.406 3.442 5.288 7.200 7.864 9.487 3.758 5.458 1.200 5.303 ms -0.1227 3.446
Server Offset 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) 0.989 0.989 0.989 6.668 7.419 7.419 7.419 6.430 6.430 2.339 5.470 ms -1.22 2.835
Server Offset 2001:19f0:6401:400:5400:4ff:fec3:522a 2.311 2.311 2.311 4.048 6.282 6.282 6.282 3.971 3.971 1.514 3.891 ms 0.635 1.891
Server Offset 2001:418:3ff::53 (x.ns.gin.ntt.net) 4.247 4.247 4.247 7.231 8.571 8.571 8.571 4.324 4.324 1.678 6.539 ms -0.2545 1.376
Server Offset 2001:418:8405:4002::12 -281.832 -281.832 -281.832 6.130 43.679 43.679 43.679 325.511 325.511 75.678 -13.076 ms -3.151 11.39
Server Offset 2001:41d0:303:65e9::1 (matthaeus.julia0815.de) -150.721 -116.304 -14.598 3.013 11.624 159.827 305.196 26.222 276.131 26.191 2.233 ms 3.209 53
Server Offset 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) -43.336 -25.868 -0.459 3.003 5.329 102.804 104.408 5.787 128.672 14.038 4.377 ms 5.842 42.8
Server Offset 2001:470:1f07:24f::123 5.692 5.692 5.692 8.660 52.245 52.245 52.245 46.552 46.552 15.577 16.463 ms 1.347 3.154
Server Offset 2001:470:1f2c:60:123:123:123:123 -34.941 -34.941 -34.941 5.417 179.029 179.029 179.029 213.970 213.970 83.019 55.085 ms 0.6389 1.528
Server Offset 2001:470:a:b4::2 (dell-2018.jamesb912.com.) -4.391 -4.391 -4.391 -4.391 -4.391 -4.391 -4.391 0.000 0.000 0.000 -4.391 ms nan nan
Server Offset 2001:470:e8dc:10::123 -0.028 0.001 0.004 0.006 0.009 0.012 589.091 0.005 0.011 29.528 1.490 s 19.85 395
Server Offset 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) -809.971 -4.133 0.925 5.173 7.699 8.851 11.403 6.774 12.984 41.024 2.773 ms -19.54 384.4
Server Offset 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) -157.180 0.965 3.243 5.473 7.719 9.995 23.242 4.475 9.030 5.538 5.305 ms -26.07 749.2
Server Offset 2001:558:6014:17:8dc5:5575:5560:2cb6 -281.200 -281.200 -126.154 4.670 171.115 172.773 172.773 297.269 453.972 76.160 7.959 ms -0.5863 8.15
Server Offset 2001:559:2be:3::1001 -175.433 -175.433 -170.364 5.851 9.897 9.897 9.897 180.261 185.330 63.479 -23.583 ms -1.838 4.527
Server Offset 2001:678:8::123 (any.time.nl) -421.375 -23.078 -11.859 -6.573 -3.217 0.122 589.234 8.642 23.200 9.862 -7.007 ms 19.14 1842
Server Offset 204.197.163.71 -173.244 -1.861 0.406 2.637 4.342 5.127 14.383 3.936 6.988 8.636 2.114 ms -19.71 398.6
Server Offset 205.233.73.201 -18.156 -18.156 -18.156 216.632 221.908 221.908 221.908 240.064 240.064 91.085 175.240 ms -1.648 3.719
Server Offset 208.113.130.146 -807.971 -2.044 0.597 5.657 8.325 10.241 17.688 7.728 12.286 41.108 3.295 ms -19.54 384.2
Server Offset 208.67.72.43 -45.246 -45.246 -45.246 -2.385 1.915 1.915 1.915 47.161 47.161 14.659 -6.938 ms -2.157 5.869
Server Offset 208.67.75.242 -0.073 -0.073 -0.073 236.434 240.553 240.553 240.553 240.627 240.627 102.360 178.355 ms -1.154 2.333
Server Offset 216.229.4.66 4.248 4.248 4.248 5.386 9.274 9.274 9.274 5.026 5.026 2.013 5.863 ms 1.013 2.211
Server Offset 216.229.4.69 -565.822 -565.822 -561.261 0.035 3.427 7.531 7.531 564.688 573.353 217.192 -101.392 ms -1.65 3.722
Server Offset 216.250.115.174 -11.971 -11.971 -11.971 -5.891 28.323 28.323 28.323 40.294 40.294 16.772 2.897 ms 0.6802 1.539
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.131.160.7 -4.498 1.315 2.765 5.400 7.474 8.521 12.984 4.710 7.206 1.459 5.342 ms -0.3744 5.119
Server Offset 23.141.40.123 27.455 27.455 27.455 33.456 37.132 37.132 37.132 9.678 9.678 2.992 32.642 ms -0.3048 2.39
Server Offset 23.142.248.8 8.594 8.594 8.594 10.977 11.802 11.802 11.802 3.207 3.207 1.009 10.550 ms -0.8827 2.771
Server Offset 23.142.248.9 -2.218 -2.218 -2.218 5.858 8.228 8.228 8.228 10.447 10.447 3.416 4.133 ms -0.3834 1.785
Server Offset 23.143.196.199 2.248 2.248 2.248 3.906 5.387 5.387 5.387 3.139 3.139 1.032 4.058 ms -0.2914 2.021
Server Offset 23.155.40.38 -288.208 -156.059 -4.815 1.534 4.285 10.104 18.366 9.100 166.163 22.289 -1.539 ms -9.379 102
Server Offset 23.186.168.123 -3.755 -1.507 0.222 2.615 4.450 5.651 13.437 4.228 7.158 1.430 2.525 ms -0.02099 7.779
Server Offset 23.186.168.126 -5.345 -3.200 -1.287 1.767 4.438 5.722 166.185 5.726 8.922 10.343 2.300 ms 15.19 239
Server Offset 23.186.168.127 2.017 2.017 2.017 5.113 8.863 8.863 8.863 6.846 6.846 2.456 5.105 ms 0.3935 1.998
Server Offset 23.186.168.128 -571.345 -2.646 0.616 3.786 5.861 6.834 11.189 5.245 9.479 32.846 1.503 ms -16.49 282.6
Server Offset 23.186.168.129 -23.022 -1.996 -0.428 2.998 5.842 7.926 423.814 6.270 9.922 13.136 3.517 ms 27.32 851.3
Server Offset 23.186.168.130 -4.461 -4.461 -4.284 0.164 5.449 7.796 7.796 9.733 12.257 3.707 0.733 ms 0.06193 1.677
Server Offset 23.186.168.131 -4.751 -0.429 1.142 3.700 5.655 6.700 10.070 4.513 7.129 1.408 3.624 ms -0.5634 5.686
Server Offset 23.186.168.132 -9.048 -5.203 -2.855 3.480 5.818 6.967 9.350 8.673 12.170 2.449 3.014 ms -1.598 6.292
Server Offset 23.95.49.216 -5.139 -2.109 0.660 3.522 5.991 7.369 10.716 5.332 9.478 1.730 3.430 ms -0.7082 6.455
Server Offset 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) -78.463 -36.395 -20.979 -11.546 -3.410 27.956 685.845 17.569 64.351 13.179 -11.475 ms 30.75 1614
Server Offset 2402:1f00:8101:d6::1 -36.205 -6.436 12.070 35.428 47.477 49.168 69.786 35.407 55.604 12.669 33.985 ms -1.139 5.04
Server Offset 240b:4002:100:9f00:5bd1:9512:8a8b:25e 1.797 1.797 1.797 4.344 8.047 8.047 8.047 6.249 6.249 2.182 4.694 ms 0.2446 1.809
Server Offset 240b:4004:108:200:8314:1a08:4cee:26d6 -53.252 -30.228 -3.522 4.633 7.430 9.190 16.676 10.952 39.418 6.135 3.553 ms -4.789 30.29
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:26d9 3.332 3.332 3.332 5.399 14.354 14.354 14.354 11.022 11.022 4.410 6.823 ms 1.061 2.259
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:1700:5455:a70::7b:1 -809.818 -809.818 -802.944 -1.720 6.474 21.994 21.994 809.418 831.812 176.723 -42.075 ms -4.096 17.79
Server Offset 2600:1702:7400:9ac0::314:5a 0.498 0.498 0.498 13.966 17.731 17.731 17.731 17.233 17.233 5.163 12.245 ms -1.274 3.293
Server Offset 2600:1702:7400:9ac0::5b 0.162 0.162 0.162 8.450 11.368 11.368 11.368 11.206 11.206 3.725 6.660 ms -0.2939 1.735
Server Offset 2600:1702:80c0:9a80:1ee4:b0a2:44bc:c606 7.543 7.543 7.543 43.369 48.456 48.456 48.456 40.913 40.913 18.767 27.247 ms 0.02285 1.042
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) -90.591 -30.497 -16.610 2.198 7.128 11.479 312.713 23.738 41.976 8.531 0.406 ms 1.915 169.9
Server Offset 2600:1f13:2c1:2e00::be00:5 -282.490 -1.401 3.361 6.350 9.277 21.057 75.600 5.916 22.458 11.306 6.295 ms -17.94 473.5
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) -155.691 -7.425 -5.731 3.067 6.244 8.116 110.743 11.974 15.541 4.932 1.630 ms -2.613 232.5
Server Offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) -159.116 -7.028 -3.909 3.387 6.614 8.454 422.200 10.523 15.482 6.360 2.442 ms 19.34 1705
Server Offset 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) -158.177 -23.587 -5.987 3.740 7.368 9.926 415.823 13.355 33.513 7.678 2.179 ms 9.969 765.7
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:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) -3.406 -0.600 0.655 2.836 5.300 6.968 12.235 4.645 7.567 1.502 2.902 ms 0.4361 5.418
Server Offset 2600:3c00:e000:318::1 (jane.qotw.net) -28.246 -0.004 1.379 3.315 5.169 6.398 10.314 3.789 6.402 1.515 3.268 ms -6.661 141.7
Server Offset 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) 2.725 2.725 2.725 5.114 14.625 14.625 14.625 11.900 11.900 4.070 5.808 ms 1.545 3.777
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) -170.467 0.056 3.237 5.672 7.881 8.850 11.725 4.644 8.794 9.635 5.092 ms -17.71 322.2
Server Offset 2600:3c02::f03c:94ff:fe59:f411 3.748 3.748 3.748 6.064 12.748 12.748 12.748 9.000 9.000 3.879 7.163 ms 0.6006 1.484
Server Offset 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) 0.867 0.867 1.114 3.790 6.386 7.915 7.915 5.272 7.048 1.512 3.637 ms 0.418 3.502
Server Offset 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) -572.795 -572.795 -572.795 -9.263 4.262 4.262 4.262 577.057 577.057 280.556 -253.542 ms -0.2234 1.051
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 2600:3c03::f03c:94ff:fe59:d3de 2.854 2.854 2.854 2.958 4.537 4.537 4.537 1.683 1.683 0.770 3.449 ms 0.6976 1.5
Server Offset 2600:3c03:e002:1300::10 (ntp.electronmill.com) -3.742 -3.742 -3.742 3.270 6.177 6.177 6.177 9.919 9.919 3.310 1.757 ms -0.3528 1.728
Server Offset 2600:3c06::f03c:94ff:fee2:9c28 5.742 5.742 5.742 7.946 15.389 15.389 15.389 9.646 9.646 3.904 8.785 ms 1.004 2.198
Server Offset 2600:3c06::f03c:94ff:fee2:c53a 7.934 7.934 7.934 10.652 34.769 34.769 34.769 26.835 26.835 12.061 17.785 ms 0.6803 1.5
Server Offset 2600:4040:e0da:f000::cbb9:201a -99.353 -99.353 -97.880 3.306 8.180 46.292 46.292 106.060 145.645 34.906 -8.837 ms -1.974 5.486
Server Offset 2602:291:69::8 (time2.trtnw.net) -87.855 -87.855 -87.855 -86.413 -85.482 -85.482 -85.482 2.373 2.373 0.712 -86.511 ms -0.5905 2.861
Server Offset 2602:291:69::9 (time.trtnw.net) -570.253 -570.253 -566.922 3.932 8.481 11.063 11.063 575.403 581.315 212.747 -91.121 ms -1.788 4.198
Server Offset 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) -158.684 -3.456 -0.083 2.041 4.145 5.512 10.845 4.229 8.968 7.379 1.675 ms -20.33 432.3
Server Offset 2602:2eb:2:95:1234:5678:9abc:def0 -177.116 -4.635 -1.237 2.194 5.223 7.388 240.974 6.460 12.023 12.582 2.396 ms 11.48 295.8
Server Offset 2602:80b:5000::36 (time.meme.holdings) -26.339 -9.392 1.266 5.868 9.817 23.455 24.890 8.551 32.847 4.663 5.601 ms -1.967 22.8
Server Offset 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) -2.396 -2.396 -2.396 0.748 11.083 11.083 11.083 13.479 13.479 3.735 2.173 ms 1.096 3.17
Server Offset 2602:f9ba:69::210 (as393746.mci.trtnw.net) -12.175 -1.360 4.707 9.530 16.745 20.179 20.349 12.038 21.539 4.125 9.733 ms -0.5412 8.171
Server Offset 2602:fb95:16::123 (time5.sigi.net) -3.415 -3.415 -3.415 2.197 8.657 8.657 8.657 12.072 12.072 3.322 1.725 ms 0.2884 2.931
Server Offset 2602:fc2f:100:9800::dead:beef -17.617 0.601 3.135 6.681 10.772 15.339 240.110 7.637 14.738 16.349 7.873 ms 13.34 186.6
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 2602:fe2e:3:d:f9:c7ff:fef5:379c 3.035 3.035 3.035 6.211 8.657 8.657 8.657 5.622 5.622 1.762 5.927 ms -0.1747 2.107
Server Offset 2603:c020:0:8369:0:ba11:ba11:ba11 -7.577 -7.577 -7.577 -4.734 -3.175 -3.175 -3.175 4.402 4.402 1.726 -5.565 ms 0.2097 1.456
Server Offset 2603:c020:0:8369:1111:1111:1111:1112 -55.331 -55.331 -46.563 -7.286 94.091 94.407 94.407 140.654 149.738 44.312 13.646 ms 0.9336 2.506
Server Offset 2603:c020:0:8369::bad:beef -6.830 -6.830 -6.830 -3.090 -2.867 -2.867 -2.867 3.963 3.963 1.885 -4.862 ms 0.002145 1.011
Server Offset 2603:c020:0:8369::f00d:feed -11.789 -11.789 -11.789 -5.006 -2.327 -2.327 -2.327 9.462 9.462 3.286 -5.616 ms -0.9394 2.42
Server Offset 2603:c020:0:8369:feed:feed:feed:feed -18.686 -18.686 -18.686 -5.363 -1.212 -1.212 -1.212 17.474 17.474 4.007 -6.304 ms -1.91 6.79
Server Offset 2603:c024:c005:a600:efb6:d213:cad8:251d 1.713 1.713 1.713 11.865 68.213 68.213 68.213 66.499 66.499 21.793 19.547 ms 1.448 3.682
Server Offset 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 (us1-ipv6.cracky-chan.com) 4.360 4.360 7.868 9.469 13.253 17.815 17.815 5.385 13.455 2.164 9.765 ms 1.273 7.496
Server Offset 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) 2.819 2.819 2.819 10.472 14.418 14.418 14.418 11.599 11.599 3.534 9.984 ms -0.574 2.357
Server Offset 2604:2dc0:202:300::140d (vps-8f06187a.vps.ovh.us) -10.884 -6.103 -4.364 -1.787 0.663 2.038 13.335 5.027 8.141 1.665 -1.837 ms 0.09333 10.2
Server Offset 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) -49.930 -36.749 -6.555 2.041 5.114 6.502 22.290 11.670 43.251 5.807 0.770 ms -4.61 31.25
Server Offset 2604:4300:a:299::164 -9.675 -9.675 -6.261 -0.158 3.067 3.865 3.865 9.328 13.539 3.536 -1.195 ms -0.6405 2.55
Server Offset 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) -802.674 -802.674 -802.674 2.272 9.840 9.840 9.840 812.514 812.514 371.058 -243.393 ms -0.8332 1.694
Server Offset 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) 4.759 4.759 4.759 5.795 36.164 36.164 36.164 31.405 31.405 14.567 15.573 ms 0.7044 1.5
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -97.614 -97.614 -97.614 -96.252 -95.198 -95.198 -95.198 2.416 2.416 0.727 -96.393 ms -0.05135 2.552
Server Offset 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) -40.303 -1.773 0.146 2.726 5.501 103.648 104.341 5.355 105.421 14.429 4.427 ms 6.057 42.23
Server Offset 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) -6.372 -6.372 -3.109 11.458 218.960 218.960 218.960 222.069 225.332 83.767 47.473 ms 1.451 3.181
Server Offset 2604:a880:800:10::70f:b001 (ellone.fdisk.io) 3.373 3.373 3.373 8.241 9.581 9.581 9.581 6.208 6.208 1.791 7.376 ms -0.8255 2.41
Server Offset 2604:a880:800:a1::ec9:5001 -127.479 -127.479 -5.442 6.028 37.389 41.342 41.342 42.831 168.821 27.959 3.167 ms -3.748 18.56
Server Offset 2604:d200::39 (white.web-ster.com) -6.544 -6.544 -4.662 -2.901 28.557 30.956 30.956 33.219 37.499 9.313 0.132 ms 2.757 9.021
Server Offset 2605:4840:3:fb19::1 (chi3.us.ntp.li) -278.261 -8.779 -1.247 2.712 7.022 29.833 89.152 8.269 38.612 10.586 2.900 ms -14.92 446.5
Server Offset 2605:6400:488d:2eda:eee9:fe8d:4543:d471 6.277 6.277 6.277 10.872 10.872 10.872 10.872 4.595 4.595 2.297 8.574 ms -5.457e-16 1
Server Offset 2605:6400:488d:3686:546d:c03c:1689:20c 0.063 0.063 0.063 10.815 77.942 77.942 77.942 77.879 77.879 31.733 28.904 ms 0.6938 1.564
Server Offset 2605:6400:84e1::123 0.114 0.114 0.114 234.240 240.273 240.273 240.273 240.159 240.159 112.476 147.282 ms -0.474 1.227
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) -170.499 -5.442 -2.472 5.308 8.514 10.151 214.236 10.986 15.593 5.341 4.854 ms 12.44 852.1
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -810.498 -3.613 -1.258 5.106 8.514 10.408 429.230 9.772 14.021 20.517 4.561 ms -24.09 1001
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 2606:82c0:22::e (time2.lshiy.com) -105.777 -105.777 -105.777 -97.920 6.067 6.067 6.067 111.844 111.844 49.551 -65.517 ms 0.6996 1.504
Server Offset 2606:82c0:23::e (time3.lshiy.com) 3.326 3.326 3.326 7.253 12.695 12.695 12.695 9.369 9.369 2.739 7.383 ms 0.4156 2.484
Server Offset 2607:5600:182:500::1 (ntp-1.jonlight.com) -568.165 -568.165 -568.165 -0.446 11.465 11.465 11.465 579.631 579.631 265.791 -190.495 ms -0.701 1.5
Server Offset 2607:7c80:54:3::32 -2.394 -2.394 -2.394 3.518 11.300 11.300 11.300 13.694 13.694 4.050 4.219 ms 0.07606 1.632
Server Offset 2607:7c80:54:3::56 (owners.kjsl.com) -806.909 -806.909 -5.703 0.187 5.818 9.156 9.156 11.521 816.065 173.398 -38.752 ms -4.188 18.54
Server Offset 2607:9000:7000:23:216:3cff:fe25:38d7 -7.438 -7.438 -7.438 1.350 6.995 6.995 6.995 14.433 14.433 4.427 0.540 ms -0.1739 2.018
Server Offset 2607:9d00:2000:16::9269:208a 0.027 0.027 0.549 5.418 11.274 17.615 17.615 10.726 17.588 3.719 5.554 ms 1.403 5.818
Server Offset 2607:b500:410:7700::1 -559.793 -559.793 -558.023 15.880 247.118 247.131 247.131 805.140 806.924 235.950 5.184 ms -1.393 4.315
Server Offset 2607:f1c0:f014:9e00::2 1.897 1.897 1.897 14.187 176.141 176.141 176.141 174.244 174.244 77.791 64.515 ms 0.6746 1.495
Server Offset 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) -64.809 -64.809 -64.809 -61.044 -58.237 -58.237 -58.237 6.572 6.572 2.268 -61.730 ms -0.02717 1.823
Server Offset 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) 2.778 2.778 2.778 7.554 7.962 7.962 7.962 5.184 5.184 1.862 6.389 ms -1.034 2.559
Server Offset 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) 3.424 3.424 3.424 9.764 40.761 40.761 40.761 37.337 37.337 12.353 15.555 ms 1.138 2.774
Server Offset 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) -2.373 -2.373 -1.407 3.297 10.246 11.084 11.084 11.653 13.458 3.531 3.807 ms 0.3808 2.37
Server Offset 2607:f1c0:f075:9900::1 -11.364 -11.364 -8.290 9.893 429.232 429.472 429.472 437.522 440.836 115.991 54.692 ms 2.751 9.098
Server Offset 2607:f298:5:101d:f816:3eff:fefd:8817 -174.467 -174.467 -172.715 3.910 20.484 20.484 20.484 193.199 194.951 64.078 -20.926 ms -1.945 4.813
Server Offset 2607:f3c8:3803:1::6 -6.026 -6.026 -6.026 2.471 214.987 214.987 214.987 221.013 221.013 95.937 61.079 ms 0.9476 1.902
Server Offset 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) -23.263 -23.263 -23.263 -10.419 26.993 26.993 26.993 50.256 50.256 13.527 -6.124 ms 0.7442 2.94
Server Offset 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) 6.293 6.293 6.293 9.644 16.365 16.365 16.365 10.072 10.072 2.800 10.002 ms 0.8431 3.217
Server Offset 2607:f710:35::29c:0:5 1.230 1.230 1.230 6.637 13.998 13.998 13.998 12.768 12.768 3.502 7.121 ms 0.34 2.688
Server Offset 2607:f710:35::29c:0:8 -3.482 -1.256 1.976 4.319 6.532 9.029 12.497 4.556 10.285 1.590 4.260 ms -0.3604 7.445
Server Offset 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) -158.123 -158.123 -158.123 3.807 12.552 12.552 12.552 170.675 170.675 66.662 -31.139 ms -1.273 2.639
Server Offset 2620:83:8000:140::b (tic.lbl.gov) -64.202 -16.454 -0.037 2.751 5.105 7.089 169.920 5.142 23.543 8.350 2.692 ms 14.74 314
Server Offset 2620:8d:c000::f (blotch.image1tech.net) -12.501 -12.501 -12.501 0.670 15.127 15.127 15.127 27.628 27.628 9.564 -0.984 ms 0.2932 2
Server Offset 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) -7.979 -7.979 -7.979 -0.845 213.035 213.035 213.035 221.015 221.015 98.515 62.052 ms 0.8326 1.697
Server Offset 2620:b0:2000:102::1:123 (time-h.den.codehof.net) -107.407 -107.407 -107.407 -66.747 92.475 92.475 92.475 199.883 199.883 57.820 -44.390 ms 1.21 3.478
Server Offset 2620:b0:2000:102::2:123 (time-he.den.codehof.net) -44.889 -44.889 -44.889 22.240 34.334 34.334 34.334 79.222 79.222 22.949 14.406 ms -2.048 5.652
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) -573.994 -18.134 -6.806 2.327 5.873 12.780 70.769 12.679 30.914 9.821 1.171 ms -30.68 1529
Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) -810.640 -46.911 -19.580 2.429 8.877 12.738 425.774 28.457 59.649 18.045 -0.827 ms -17.65 799.7
Server Offset 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) -178.311 -53.480 -21.082 -0.130 7.126 10.754 209.396 28.208 64.234 12.297 -2.557 ms -1.944 61.96
Server Offset 2a01:4f8:c012:1afb:123:123:123:123 (tock.telnet.li) -662.197 -43.394 -29.960 -14.733 -7.976 -0.161 153.523 21.984 43.233 17.808 -15.749 ms -19.9 818.3
Server Offset 2a01:4f9:c013:fa27:123:123:123:123 -74.656 -29.575 -9.456 1.270 5.487 10.806 152.944 14.943 40.381 9.896 0.343 ms 5.416 117.1
Server Offset 2a01:4ff:f0:7300:123:123:123:123 (use1.ntspool.telnet.li) -118.920 -12.890 -6.246 -2.163 1.265 5.208 288.663 7.511 18.098 9.301 -2.445 ms 12.21 561.8
Server Offset 2a01:4ff:f0:ebce::1 8.384 8.384 8.384 34.231 34.231 34.231 34.231 25.847 25.847 12.924 21.307 ms 1.962e-16 1
Server Offset 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) -51.215 -51.215 -51.215 6.741 19.073 19.073 19.073 70.288 70.288 23.048 -2.114 ms -1.242 3.142
Server Offset 2a01:7e04::f03c:94ff:fee2:cba5 -26.406 -26.406 -26.406 2.333 5.249 5.249 5.249 31.655 31.655 7.170 0.454 ms -3.228 12.34
Server Offset 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) -1.952 -1.409 0.783 3.141 6.155 10.391 13.358 5.371 11.799 1.803 3.258 ms 1.298 9.219
Server Offset 2a0a:e5c0:2:2:0:c8ff:fe68:beb7 (2a0a-e5c0-2-2-0-c8ff-fe68-beb7.loves.ipv6.at.ungleich.ch) -15.575 -4.284 -0.922 1.204 3.169 4.150 7.004 4.091 8.434 1.710 1.146 ms -3.21 29.58
Server Offset 34.147.28.4 -33.036 -14.610 -6.461 -1.698 1.628 5.064 13.648 8.089 19.674 3.238 -2.041 ms -2.728 21
Server Offset 37.27.11.4 -51.314 -10.261 -2.384 0.947 3.098 4.523 4.544 5.482 14.784 4.805 0.292 ms -9.244 98.81
Server Offset 44.190.5.123 -619.209 -1.022 1.409 5.184 7.370 8.567 28.290 5.961 9.589 8.885 4.716 ms -51.54 3298
Server Offset 45.63.54.13 -3.217 -0.103 2.951 5.735 7.668 9.707 23.365 4.717 9.811 1.722 5.639 ms 0.382 16.63
Server Offset 45.77.126.122 0.280 0.280 0.280 4.312 5.554 5.554 5.554 5.273 5.273 1.572 3.685 ms -0.6575 2.314
Server Offset 45.79.51.42 -45.604 -45.604 -45.604 8.683 108.150 108.150 108.150 153.754 153.754 57.087 39.510 ms 0.07989 1.347
Server Offset 45.83.234.123 -296.062 -296.062 -36.862 5.238 11.369 12.953 12.953 48.231 309.015 50.497 -9.270 ms -4.716 25.98
Server Offset 45.84.199.136 -110.729 -110.729 -110.729 -97.871 9.546 9.546 9.546 120.275 120.275 54.799 -52.941 ms 0.172 1.055
Server Offset 46.37.96.107 -808.769 -33.538 -1.905 5.043 7.457 8.750 17.475 9.362 42.288 37.739 2.042 ms -20.74 443.5
Server Offset 50.117.3.52 -8.085 -8.085 -8.085 -6.204 -5.368 -5.368 -5.368 2.717 2.717 0.914 -6.560 ms -0.319 1.928
Server Offset 50.117.3.95 -146.276 -146.276 -146.276 8.636 18.465 18.465 18.465 164.741 164.741 63.106 -20.370 ms -1.48 3.224
Server Offset 50.205.57.38 -18.950 -18.950 -0.288 5.249 8.633 18.417 18.417 8.921 37.367 5.890 4.328 ms -1.998 11.57
Server Offset 50.218.103.254 6.935 6.935 6.935 10.777 11.835 11.835 11.835 4.899 4.899 1.768 9.997 ms -0.768 2.084
Server Offset 51.38.58.233 -9.884 -9.426 -5.732 1.681 3.951 4.658 5.143 9.683 14.084 3.080 0.771 ms -1.604 5.182
Server Offset 51.81.20.76 2.414 2.414 2.414 7.712 11.524 11.524 11.524 9.111 9.111 3.247 7.454 ms -0.2642 1.777
Server Offset 51.81.226.229 -178.118 -178.118 -173.190 4.447 15.237 22.510 22.510 188.427 200.627 62.005 -17.820 ms -2.094 5.445
Server Offset 64.79.100.197 -5.398 -1.308 0.115 2.437 4.257 5.695 7.196 4.142 7.002 1.439 2.356 ms -1.086 9.14
Server Offset 65.182.224.39 1.814 1.814 1.814 2.848 5.791 5.791 5.791 3.977 3.977 1.315 3.059 ms 1.249 3.327
Server Offset 66.118.231.14 -27.328 -27.328 -11.996 4.815 12.740 46.019 46.019 24.736 73.347 10.026 2.952 ms 0.8298 9.385
Server Offset 66.42.71.197 -4.404 1.597 4.014 6.528 8.619 9.544 14.523 4.605 7.947 1.519 6.426 ms -0.8517 7.915
Server Offset 66.85.78.80 1.863 1.863 1.863 5.833 6.542 6.542 6.542 4.679 4.679 1.783 4.731 ms -0.7192 1.975
Server Offset 67.217.246.127 -4.257 -3.477 -0.379 2.528 6.202 9.675 10.219 6.580 13.152 2.004 2.572 ms 0.5419 6.199
Server Offset 67.217.246.204 -11.181 -11.181 -11.181 28.533 423.145 423.145 423.145 434.326 434.326 144.136 72.032 ms 1.949 4.963
Server Offset 68.234.48.70 -2.973 -2.973 -2.973 9.512 47.817 47.817 47.817 50.790 50.790 12.262 11.128 ms 2.266 7.46
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 -35.854 -4.065 0.107 2.667 5.466 104.738 425.249 5.359 108.803 32.556 7.005 ms 10.72 133
Server Offset 69.89.207.99 -82.728 -2.318 -0.017 2.894 4.643 5.551 6.408 4.661 7.869 3.416 2.593 ms -20.67 515
Server Offset 71.19.144.140 -3.221 -3.221 -3.221 4.015 7.428 7.428 7.428 10.649 10.649 2.867 3.283 ms -0.3728 2.496
Server Offset 72.14.183.39 5.676 5.676 5.676 6.591 11.748 11.748 11.748 6.071 6.071 2.174 7.473 ms 1.37 3.097
Server Offset 72.14.186.59 2.611 2.611 2.611 5.374 7.023 7.023 7.023 4.412 4.412 1.489 5.305 ms -0.8276 2.527
Server Offset 72.46.53.234 -35.275 -35.275 -35.275 69.197 105.228 105.228 105.228 140.503 140.503 52.722 51.699 ms -0.2012 1.301
Server Offset 72.46.61.205 -285.110 -285.110 -285.110 6.157 16.075 16.075 16.075 301.185 301.185 76.949 -30.555 ms -2.535 8.616
Server Offset 73.185.182.209 -2.743 0.925 2.341 5.411 8.588 10.253 11.822 6.247 9.328 1.947 5.428 ms -0.05719 3.857
Server Offset 73.65.80.137 -809.727 -809.727 -9.135 -1.384 3.688 7.510 7.510 12.823 817.238 169.002 -38.192 ms -4.333 19.79
Server Offset 77.37.97.124 -93.402 -23.673 -4.883 8.780 13.074 17.416 35.796 17.957 41.089 8.134 7.088 ms -5.421 50.68
Server Offset 77.42.37.85 -88.107 -36.089 -7.938 1.616 4.984 9.122 17.475 12.922 45.211 7.462 0.463 ms -6.436 56.55
Server Offset 79.160.225.13 -59.926 -17.704 -5.832 -1.917 0.752 2.878 11.556 6.584 20.582 4.049 -2.367 ms -7.389 83.12
Server Offset 83.147.242.172 -1.026 1.305 3.079 5.350 7.728 10.018 14.032 4.649 8.714 1.528 5.378 ms 0.287 5.704
Server Offset 94.198.159.11 7.026 7.026 7.026 9.843 9.843 9.843 9.843 2.818 2.818 1.409 8.435 ms 0 1
Server Offset 96.19.94.82 -0.647 -0.647 -0.647 1.724 5.250 5.250 5.250 5.897 5.897 1.953 2.085 ms 0.298 2.161
Server Offset 99.28.14.242 -568.386 -2.050 0.773 4.332 6.974 9.919 171.646 6.201 11.970 46.430 1.696 ms -10.89 137.6
Server Offset SHM(0) -865.294 -186.575 -183.021 -155.342 -124.785 -119.407 1,345.558 58.236 67.168 18.190 -157.381 ms 15.33 1133
Server Offset SHM(1) -741.259 -8.626 -7.955 -4.643 -0.189 0.268 1,996.886 7.766 8.894 11.282 -4.465 ms 118.5 1.815e+04
Server Offset SHM(2) -192.688 -179.772 -173.150 -3.259 14.062 19.724 1,940.513 187.211 199.495 76.194 -53.845 ms -0.3284 10.87
Server Offset SHM(3) -13.801 -8.615 -8.031 -0.731 0.651 0.970 2,061.810 8.682 9.585 11.006 -2.388 ms 169.9 3.111e+04
Server Offset SOCK(0) -597.294 -178.078 -174.970 -1.726 4.111 6.235 236.678 179.081 184.313 73.098 -43.269 ms -1.192 2.483
Server Offset SOCK(1) -52.048 -1.868 -0.986 -0.065 0.891 1.372 230.276 1.876 3.240 1.230 -0.066 ms 126 2.365e+04
Server Offset SOCK(2) -181.172 -176.994 -173.059 -163.444 -157.121 -154.860 -148.505 15.938 22.134 4.800 -164.015 ms -0.5576 3.253
Server Offset SOCK(3) -3,009.455 -0.960 -0.610 -0.079 0.535 0.918 4.447 1.145 1.878 17.175 -0.177 ms -175.1 3.068e+04
TDOP 0.490 0.560 0.630 0.920 11.810 11.810 11.810 11.180 11.250 3.148 1.999 2.733 8.646
Temp /dev/sda 17.000 18.000 20.000 25.000 26.000 28.000 39.000 6.000 10.000 2.245 24.146 °C
Temp LM0 26.000 31.000 32.000 34.000 40.000 45.000 54.000 8.000 14.000 2.521 34.260 °C
Temp LM1 27.000 28.000 30.000 38.000 39.000 40.000 46.000 9.000 12.000 2.850 36.876 °C
Temp LM2 0.000 0.000 0.000 19.000 34.000 34.000 45.000 34.000 34.000 6.856 19.680 °C
Temp LM3 26.000 27.000 28.000 30.000 38.000 39.000 44.000 10.000 12.000 2.803 30.999 °C
Temp LM4 0.000 0.000 0.000 32.000 42.000 46.000 56.000 42.000 46.000 11.918 29.839 °C
Temp LM5 25.000 27.000 28.000 30.000 32.000 33.000 44.000 4.000 6.000 1.193 29.980 °C
Temp LM6 27.000 30.000 30.000 32.000 34.000 36.000 50.000 4.000 6.000 1.358 32.383 °C
Temp LM7 29.000 31.000 32.000 34.000 36.000 37.000 51.000 4.000 6.000 1.340 34.204 °C
Temp LM8 26.800 31.000 33.000 35.000 37.000 37.000 51.000 4.000 6.000 1.357 34.548 °C
Temp LM9 26.800 31.000 33.000 35.000 37.000 37.000 51.000 4.000 6.000 1.357 34.548 °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 26.800 31.000 32.000 34.000 36.000 37.000 51.000 4.000 6.000 1.351 33.656 °C
Temp ZONE2 25.000 27.000 28.000 30.000 32.000 33.000 44.000 4.000 6.000 1.193 29.980 °C
Temp ZONE3 29.000 31.000 32.000 34.000 36.000 37.000 51.000 4.000 6.000 1.351 33.661 °C
Temp ZONE4 26.800 31.000 32.000 34.000 36.000 37.000 51.000 4.000 6.000 1.351 33.656 °C
Temp ZONE5 27.000 29.000 30.000 32.000 43.000 47.000 56.000 13.000 18.000 4.431 34.598 °C
Temp ZONE6 26.000 27.000 28.000 30.000 32.000 33.000 44.000 4.000 6.000 1.184 29.996 °C
nSats 6.000 8.000 9.000 10.000 13.000 14.000 16.000 4.000 6.000 1.278 10.618 nSat 0.3197 3.496
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!