NTPsec

Dell-2018

Report generated: Sat Jul 4 14:34:48 2026 UTC
Start Time: Wed Jun 25 14:33:52 2025 UTC
End Time: Sat Jul 4 14:33:52 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 -127.900 -8.297 -6.626 -0.231 0.363 0.834 121.205 6.989 9.131 2.878 -1.880 ms -0.595 219.3
Local Clock Frequency Offset -135.511 10.612 10.922 11.480 22.419 25.406 183.534 11.497 14.793 8.334 13.880 ppm -8.216 99.89

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.133 0.164 0.345 0.542 2.379 83.702 0.379 2.246 1.173 0.405 ms 34.73 1538

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.0031 0.0038 0.0104 0.388 0.712 73.177 0.384 0.709 0.838 0.124 ppm 44.97 2554

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 -127.900 -8.297 -6.626 -0.231 0.363 0.834 121.205 6.989 9.131 2.878 -1.880 ms -0.595 219.3

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.612 10.922 11.480 22.419 25.406 183.534 11.497 14.793 8.334 13.880 ppm -8.216 99.89
Temp /dev/sda 17.000 18.000 20.000 25.000 26.000 28.000 39.000 6.000 10.000 2.246 24.272 °C
Temp LM0 26.000 31.000 32.000 34.000 41.000 45.000 59.000 9.000 14.000 2.667 34.994 °C
Temp LM1 27.000 29.000 30.000 38.000 39.000 40.000 54.000 9.000 11.000 2.820 36.498 °C
Temp LM2 0.000 0.000 19.000 19.000 39.000 40.000 46.000 20.000 40.000 9.485 23.383 °C
Temp LM3 0.000 3.000 3.000 30.000 40.000 41.000 44.000 37.000 38.000 8.809 29.894 °C
Temp LM4 0.000 0.000 0.000 32.000 41.000 46.000 55.000 41.000 46.000 14.765 26.745 °C
Temp LM5 26.000 28.000 28.000 30.000 38.000 38.000 44.000 10.000 10.000 2.289 30.934 °C
Temp LM6 28.000 30.000 31.000 33.000 35.000 37.000 50.000 4.000 7.000 1.575 32.986 °C
Temp LM7 30.000 32.000 33.000 35.000 37.000 39.000 51.000 4.000 7.000 1.541 34.773 °C
Temp LM8 26.800 32.000 33.000 35.000 37.000 39.000 51.000 4.000 7.000 1.550 35.042 °C
Temp LM9 26.800 32.000 33.000 35.000 37.000 39.000 51.000 4.000 7.000 1.550 35.042 °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 37.000 38.000 51.000 5.000 7.000 1.591 34.210 °C
Temp ZONE2 26.000 28.000 28.000 30.000 38.000 38.000 44.000 10.000 10.000 2.763 31.345 °C
Temp ZONE3 29.000 31.000 32.000 34.000 36.000 39.000 54.000 4.000 8.000 1.635 34.208 °C
Temp ZONE4 26.800 31.000 32.000 34.000 37.000 38.000 51.000 5.000 7.000 1.591 34.210 °C
Temp ZONE5 28.000 29.000 31.000 35.000 42.000 46.000 58.000 11.000 17.000 4.233 35.222 °C
Temp ZONE6 26.000 28.000 28.000 30.000 36.000 37.000 44.000 8.000 9.000 1.907 30.788 °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 12.000 17.000 18.000 22.000 8.000 10.000 2.378 12.063 nSat 0.746 3.179
TDOP 0.450 0.520 0.590 0.860 11.810 11.810 11.810 11.220 11.290 2.634 1.593 3.536 13.8

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 -127.900 -126.109 -9.873 1.397 10.054 13.031 16.334 19.927 139.141 23.291 -3.106 ms -4.589 23.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 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.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 -11.180 -9.140 -3.447 1.426 6.606 12.091 16.244 10.053 21.231 3.430 1.519 ms -0.07377 5.449

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

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

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

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



Server Offset 107.172.222.7

peer offset 107.172.222.7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 107.172.222.7 -12.642 -11.375 -7.178 1.882 7.310 12.947 14.359 14.488 24.322 3.982 1.625 ms -0.7389 5.565

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

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

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

Clock 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.215.221

peer offset 108.61.215.221 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 108.61.215.221 -28.570 -9.305 -0.181 3.903 6.523 8.097 13.175 6.704 17.402 2.862 3.479 ms -3.533 28.36

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

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

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

Clock 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.205.28.193

peer offset 12.205.28.193 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 12.205.28.193 -126.850 -126.850 -126.850 -114.175 6.955 6.955 6.955 133.805 133.805 46.151 -91.142 ms 1.065 2.644

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

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

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

Clock 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.796 6.343 6.706 7.088 4.863 5.850 1.421 4.500 ms -1.034 4.16

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

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

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

Clock 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.250.35.250

peer offset 129.250.35.250 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 129.250.35.250 -2.943 -2.410 -1.340 1.886 5.403 7.583 8.459 6.742 9.993 2.056 1.995 ms 0.3236 3.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 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 134.215.155.177

peer offset 134.215.155.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 134.215.155.177 -6.511 -6.511 -4.780 0.657 5.183 15.538 15.538 9.962 22.050 3.593 0.567 ms 1.062 6.279

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

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

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

Clock 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 136.244.88.170

peer offset 136.244.88.170 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 136.244.88.170 -82.929 -82.929 -82.929 -12.037 -3.376 -3.376 -3.376 79.553 79.553 25.987 -27.375 ms -0.9053 2.457

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

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

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

Clock 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 -30.357 -5.499 8.690 18.170 23.381 33.775 23.669 53.738 9.115 7.606 ms -3.604 27.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 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 -5.133 -3.834 -2.747 0.216 3.825 5.337 7.287 6.572 9.171 2.098 0.486 ms 0.248 2.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 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 2.854 12.059 21.516 21.516 181.948 192.005 47.050 -9.997 ms -3.072 10.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 143.42.229.154

peer offset 143.42.229.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 143.42.229.154 -12.280 -11.918 -8.448 0.679 4.877 10.025 10.853 13.326 21.944 3.809 0.031 ms -0.9182 4.866

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

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

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

Clock 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 -112.597 -112.597 -112.597 4.642 10.116 10.116 10.116 122.713 122.713 43.496 -14.874 ms -1.777 4.18

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

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

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

Clock 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.41.38

peer offset 144.202.41.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.202.41.38 -8.294 -8.294 -8.294 4.829 12.556 12.556 12.556 20.850 20.850 6.900 3.360 ms -0.4744 2.271

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

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

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

Clock 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 -359.531 -4.209 -1.517 1.251 5.257 7.227 36.327 6.774 11.436 27.588 -0.646 ms -11.94 150

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

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

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

Clock 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 -1,991.190 -7.297 2.180 9.379 12.747 26.232 58.058 10.567 33.529 152.944 -2.874 ms -12.88 167.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 144.31.251.154

peer offset 144.31.251.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.31.251.154 -1.884 -1.884 -1.884 1.637 9.630 9.630 9.630 11.515 11.515 4.100 3.810 ms 0.1811 1.537

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

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

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

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



Server Offset 147.88.195.53

peer offset 147.88.195.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 147.88.195.53 -119.005 -102.607 -78.625 -8.685 6.545 10.280 13.559 85.170 112.887 26.779 -18.851 ms -1.354 4.238

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

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

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

Clock 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 -8.248 -8.248 -5.145 3.379 12.833 13.486 13.486 17.978 21.734 4.968 2.979 ms 0.2457 2.932

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

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

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

Clock 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 -88.226 -29.901 -7.700 1.855 7.253 12.590 25.332 14.953 42.491 9.462 0.942 ms -7.003 65.36

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

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

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

Clock 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 -1,995.498 -19.186 -4.326 3.263 6.176 17.348 44.622 10.502 36.534 163.507 -10.918 ms -12.03 145.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 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 -10.681 2.259 4.290 4.290 4.290 14.971 14.971 5.024 0.026 ms -1.3 2.977

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

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

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

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



Server Offset 151.236.20.166

peer offset 151.236.20.166 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 151.236.20.166 -7.947 -5.621 -3.416 0.364 5.984 9.517 13.621 9.399 15.138 3.092 0.765 ms 0.5972 3.916

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

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

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

Clock 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 -7.263 -4.833 -2.774 0.162 4.381 7.586 11.821 7.155 12.418 2.274 0.520 ms 0.7526 4.999

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

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

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

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



Server Offset 157.245.125.229

peer offset 157.245.125.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 157.245.125.229 1.618 1.618 1.618 2.114 3.912 3.912 3.912 2.294 2.294 0.986 2.548 ms 0.5751 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 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 -157.868 -153.883 0.302 5.849 6.583 6.583 159.732 164.451 47.726 -16.939 ms -2.469 7.308

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

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

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

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



Server Offset 161.35.230.200

peer offset 161.35.230.200 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 161.35.230.200 -2.730 -2.730 -1.127 1.511 390.595 395.667 395.667 391.722 398.397 147.881 68.930 ms 1.72 3.961

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

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

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

Clock 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 -33.205 -5.539 -1.015 5.329 8.946 11.637 16.373 9.961 17.176 3.732 4.665 ms -3.078 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 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 -1,990.740 -3.858 -1.054 5.742 8.784 12.008 41.636 9.838 15.866 54.127 3.754 ms -36.65 1351

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

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

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

Clock 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.244.81.139

peer offset 162.244.81.139 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.244.81.139 -358.787 -358.787 -358.787 2.574 8.702 8.702 8.702 367.489 367.489 116.576 -46.950 ms -2.07 5.565

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

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

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

Clock 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 168.235.89.132

peer offset 168.235.89.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 168.235.89.132 -361.703 -177.856 -1.214 2.049 6.635 8.852 9.305 7.848 186.709 37.893 -2.184 ms -8.706 79.36

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

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

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

Clock 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.705 1.980 4.722 8.587 9.921 12.448 6.607 9.216 2.044 4.934 ms 0.3738 3.245

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

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

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

Clock 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 -111.117 -109.795 -2.851 0.792 3.175 6.263 130.236 6.027 116.058 15.291 -0.217 ms -2.186 57.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 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.155.39

peer offset 172.233.155.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.155.39 -12.270 -2.993 -0.238 3.828 6.492 7.576 9.891 6.730 10.570 2.348 3.523 ms -1.715 12.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 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 -2.228 9.669 455.633 725.734 725.734 457.862 729.782 182.781 88.825 ms 2.207 6.825

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

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

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

Clock 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.233.189.68

peer offset 172.233.189.68 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.189.68 8.111 8.111 8.111 8.731 10.099 10.099 10.099 1.988 1.988 0.780 9.065 ms 0.2333 1.349

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

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

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

Clock 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 -378.349 -377.277 -0.619 7.225 13.916 16.005 16.638 14.535 393.281 67.054 -4.512 ms -5.334 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 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 -384.852 -377.114 -16.092 2.112 9.952 35.580 41.762 26.044 412.695 43.692 -2.830 ms -8.214 71.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 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 -1,994.828 -7.193 -2.951 1.688 6.668 9.261 47.412 9.618 16.455 99.943 -3.213 ms -19.77 392.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 172.238.164.57

peer offset 172.238.164.57 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.238.164.57 -20.678 -5.109 -3.388 1.693 6.481 7.573 11.018 9.869 12.682 3.241 1.724 ms -0.3793 3.926

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

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

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

Clock 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.245.210.108

peer offset 172.245.210.108 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.245.210.108 -261.506 -261.506 -251.411 0.386 170.775 173.801 173.801 422.186 435.307 82.626 -6.480 ms -0.7581 6.622

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

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

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

Clock 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.230.96

peer offset 173.255.230.96 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.255.230.96 -4.019 -1.915 0.365 4.658 8.077 9.189 28.541 7.712 11.104 2.614 4.581 ms 2.225 26.93

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

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

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

Clock 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 185.234.20.134

peer offset 185.234.20.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 185.234.20.134 -207.966 -198.229 8.539 43.765 55.709 222.317 228.892 47.170 420.546 42.923 39.520 ms -0.8843 22.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 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 -38.144 -16.120 -9.873 4.243 8.544 13.335 24.385 18.417 29.455 5.972 2.916 ms -2.066 11.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 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 -3.460 -3.460 -3.460 3.103 9.170 9.170 9.170 12.629 12.629 3.530 2.605 ms 0.006634 1.907

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

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

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

Clock 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 -1,993.360 -6.911 -3.239 1.546 6.949 9.870 390.115 10.188 16.782 46.173 0.790 ms -41.5 1789

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

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

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

Clock 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.137.202.56

peer offset 198.137.202.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.137.202.56 -206.226 -11.480 -4.652 -0.701 4.599 14.997 34.211 9.252 26.477 10.560 -0.960 ms -13.83 244.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 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 -2.909 1.625 11.374 11.645 11.645 14.282 27.080 5.917 2.710 ms -0.8834 4.822

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

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

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

Clock 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 -11.109 -8.702 -1.432 4.138 9.376 11.538 50.250 10.808 20.240 3.757 4.029 ms 2.757 44.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 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 198.71.50.75

peer offset 198.71.50.75 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.71.50.75 -21.461 -16.971 -10.397 -4.651 -1.037 1.083 5.931 9.360 18.054 3.141 -4.906 ms -1.601 9.855

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

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

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

Clock 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 199.68.201.237

peer offset 199.68.201.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 199.68.201.237 -54.221 -4.457 -2.342 2.245 5.491 7.434 14.187 7.833 11.890 3.323 1.891 ms -8.342 141.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 20.55.26.153

peer offset 20.55.26.153 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 20.55.26.153 -90.128 -90.128 -90.128 0.419 4.026 4.026 4.026 94.154 94.154 29.373 -11.273 ms -2.13 5.815

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

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

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

Clock 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

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 -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:41d0:303:65e9::1

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 -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: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: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 -0.851 -0.851 -0.851 7.144 17.145 17.145 17.145 17.997 17.997 4.502 6.891 ms 0.4579 3.325

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

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

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

Clock 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.575 -3.251 -0.150 589.234 8.607 22.927 8.794 -7.106 ms 20.66 2760

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

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

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

Clock 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 204.2.134.173

peer offset 204.2.134.173 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.2.134.173 -330.587 -1.995 0.505 4.402 7.005 7.870 8.684 6.500 9.866 24.915 2.289 ms -13.06 173.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 206.210.192.99

peer offset 206.210.192.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 206.210.192.99 3.732 3.732 3.732 10.882 12.986 12.986 12.986 9.255 9.255 2.868 9.737 ms -0.9345 2.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 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 -1.547 -1.547 -0.705 1.652 11.527 14.355 14.355 12.232 15.903 4.437 3.317 ms 1.173 3.138

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

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

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

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



Server Offset 209.177.158.85

peer offset 209.177.158.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.177.158.85 -30.375 -4.642 -3.180 0.545 5.452 6.644 15.829 8.632 11.286 3.226 0.948 ms -2.144 24.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 212.227.240.160

peer offset 212.227.240.160 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 212.227.240.160 -12.742 -12.742 -12.742 -3.409 1.156 1.156 1.156 13.898 13.898 4.103 -3.640 ms -1.253 3.789

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

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

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

Clock 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 -17.026 -11.915 -9.323 -0.696 4.542 13.045 13.185 13.865 24.960 3.827 -1.038 ms -0.2364 6.866

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

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

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

Clock 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 -50.737 -50.737 -50.737 -20.501 369.510 369.510 369.510 420.246 420.246 125.161 28.344 ms 2.264 6.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.66.48.42

peer offset 216.66.48.42 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.66.48.42 -57.714 -48.968 -41.803 -10.099 4.232 45.537 48.178 46.035 94.505 15.518 -12.901 ms 0.07764 5.238

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

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

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

Clock 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.82.35.115

peer offset 216.82.35.115 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.82.35.115 -29.297 -29.297 -9.388 -1.589 392.815 392.815 392.815 402.203 422.112 140.650 54.907 ms 1.952 4.828

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

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

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

Clock 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 -3.042 1.210 6.116 10.765 12.869 13.726 15.979 6.753 12.515 2.251 10.327 ms -1.931 8.788

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

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

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

Clock 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 -263.459 -263.459 -261.533 -1.198 167.901 168.098 168.098 429.434 431.557 92.982 -6.282 ms -0.7409 5.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 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.150.40.242

peer offset 23.150.40.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.150.40.242 -357.926 -357.926 -357.926 3.502 10.525 10.525 10.525 368.451 368.451 119.758 -47.624 ms -1.976 5.174

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

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

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

Clock 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.150.41.122

peer offset 23.150.41.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.150.41.122 -3.912 -0.906 1.567 5.532 9.044 10.304 12.219 7.477 11.210 2.174 5.373 ms -0.477 4.713

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

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

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

Clock 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.150.41.123

peer offset 23.150.41.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.150.41.123 -22.902 -6.785 -3.289 8.706 11.720 26.163 32.724 15.009 32.948 5.336 7.384 ms -0.5486 7.805

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

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

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

Clock 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 -158.747 -42.839 -3.587 1.531 3.890 6.081 8.018 7.477 48.920 15.680 -0.567 ms -9.275 91.75

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

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

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

Clock 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.72.147

peer offset 23.155.72.147 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.155.72.147 -392.987 -391.252 -12.441 -6.112 -0.837 1.703 7.397 11.604 392.955 61.955 -16.524 ms -5.782 34.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 23.159.16.194

peer offset 23.159.16.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.159.16.194 -332.773 -2.949 1.895 12.336 15.900 21.536 27.238 14.005 24.484 25.353 9.220 ms -12.89 173.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 23.161.104.133

peer offset 23.161.104.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.161.104.133 -2,049.972 -101.074 -80.281 -9.695 8.763 15.686 36.039 89.043 116.761 72.795 -20.018 ms -24.1 670.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 23.168.24.210

peer offset 23.168.24.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.168.24.210 -30.994 -9.946 -0.456 4.953 9.479 14.370 15.899 9.935 24.316 3.912 4.627 ms -3.016 28.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.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 -18.265 -7.951 -3.512 2.207 4.285 5.506 24.970 7.797 13.457 2.606 1.618 ms -1.683 11.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 23.186.168.125

peer offset 23.186.168.125 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.125 -336.573 -2.857 -1.290 2.156 4.173 5.028 21.753 5.462 7.885 12.191 1.436 ms -26.88 738.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 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 -114.793 -114.793 -114.793 -5.494 -0.844 -0.844 -0.844 113.950 113.950 54.847 -57.177 ms -0.005087 1.013

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

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

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

Clock 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 -173.852 -2.042 0.684 3.783 5.861 6.834 11.189 5.176 8.875 8.584 3.249 ms -19.66 401.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 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 -100.937 -12.969 -1.947 2.841 5.908 10.375 423.814 7.855 23.343 16.766 2.764 ms 13.97 354.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 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 -5.129 -5.129 -4.461 -1.043 5.449 7.796 7.796 9.909 12.926 3.728 -0.075 ms 0.3855 1.791

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

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

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

Clock 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.35.34

peer offset 23.95.35.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.95.35.34 -27.613 -4.807 -3.147 0.347 4.555 6.819 20.501 7.701 11.627 2.606 0.524 ms -0.5651 20.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.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 2.004 2.004 2.004 5.904 7.369 7.369 7.369 5.365 5.365 1.531 5.662 ms -0.973 3.221

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

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

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

Clock 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: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: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: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 1.672 1.672 1.672 5.591 19.969 19.969 19.969 18.297 18.297 5.131 6.284 ms 1.945 5.754

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

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

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

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



Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) -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.743 0.572 2.736 4.877 5.612 6.968 4.305 6.355 1.285 2.737 ms -0.4082 4.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 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: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: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 -30.239 -30.239 1.140 3.666 8.180 46.292 46.292 7.039 76.531 8.723 4.146 ms 1.265 19.19

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

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

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

Clock 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) -0.476 -0.476 -0.476 7.476 11.063 11.063 11.063 11.539 11.539 2.887 6.192 ms -0.5951 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: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 -3.839 -1.705 0.313 2.455 3.497 5.247 4.160 7.336 10.717 -0.295 ms -16.11 264.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: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:f590::23:161:104:133 (isere.sd.ysun.co)

peer offset 2602:f590::23:161:104:133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:f590::23:161:104:133 (isere.sd.ysun.co) -471.581 -385.176 -54.827 -11.476 0.126 5.242 28.182 54.953 390.419 61.385 -26.183 ms -5.774 37.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: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: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 (ntp.ny1.neptunenetworks.net)

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 (ntp.ny1.neptunenetworks.net) 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: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-d60fb58e.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-d60fb58e.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 -39.062 -9.506 1.053 4.764 6.043 7.109 14.270 45.105 8.589 -1.957 ms -3.022 13.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 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 -4.878 -4.878 -4.878 0.553 3.067 3.067 3.067 7.945 7.945 2.835 -0.799 ms -0.1278 1.481

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

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

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

Clock 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::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) 8.916 8.916 8.916 14.499 37.032 37.032 37.032 28.115 28.115 8.702 16.497 ms 1.735 4.537

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

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

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

Clock 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) -3.852 -3.852 -3.852 -0.420 1.987 1.987 1.987 5.839 5.839 2.396 -0.762 ms -0.2111 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 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: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.854 -3.702 5.350 8.547 9.988 51.896 12.248 15.842 4.437 4.520 ms -14.13 537

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

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

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

Clock 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) -68.168 -3.942 -2.047 5.036 8.626 10.408 429.230 10.673 14.350 8.834 4.804 ms 36.43 1691

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

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

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

Clock 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) 2.084 2.084 2.084 5.198 6.067 6.067 6.067 3.983 3.983 1.710 4.450 ms -0.5727 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 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: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: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 (vps-lax1.orleans.ddnss.de)

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 (vps-lax1.orleans.ddnss.de) 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 -26.492 -26.492 -26.492 16.912 30.534 30.534 30.534 57.026 57.026 14.105 13.122 ms -2.005 6.462

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

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

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

Clock 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: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 -26.566 0.301 2.769 4.833 6.184 9.683 4.532 32.750 4.590 2.212 ms -7.468 71.61

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

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

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

Clock 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: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) -267.863 -48.067 -22.013 0.370 7.466 11.344 425.774 29.479 59.411 12.437 -2.316 ms 2.624 203.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 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 -56.349 -20.962 -0.647 6.367 10.538 106.144 27.329 66.886 11.826 -2.978 ms -4.66 45.16

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

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

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

Clock 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

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

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 -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 (42-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 (42-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 -2,001.428 -48.644 -14.990 -1.817 1.832 5.508 13.648 16.822 54.151 42.738 -4.524 ms -44.6 2081

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

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

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

Clock 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 38.45.64.130

peer offset 38.45.64.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 38.45.64.130 -257.312 -73.003 -9.597 5.725 9.142 13.153 177.823 18.739 86.156 24.534 3.845 ms -3.142 73.78

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

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

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

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



Server Offset 40.160.28.79

peer offset 40.160.28.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 40.160.28.79 -52.835 -52.513 -34.382 -5.004 1.626 5.643 7.374 36.008 58.156 10.906 -8.229 ms -2.157 7.89

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

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

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

Clock 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.752 0.995 5.099 7.144 8.271 28.290 6.149 10.023 9.160 4.601 ms -57.22 3770

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

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

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

Clock 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.33.53.84

peer offset 45.33.53.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.33.53.84 -46.045 -1.169 1.112 4.939 7.280 7.847 8.597 6.167 9.016 2.868 4.557 ms -9.347 157.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 45.55.58.103

peer offset 45.55.58.103 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.55.58.103 -110.343 -110.343 -110.343 0.562 3.360 3.360 3.360 113.703 113.703 54.930 -52.554 ms -0.005973 1.01

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

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

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

Clock 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 -5.411 -0.490 2.322 5.646 7.622 9.009 23.365 5.301 9.499 1.820 5.474 ms -0.3691 12.49

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

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

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

Clock 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 1.370 4.514 10.132 10.132 10.132 8.762 9.852 2.436 4.532 ms 0.629 3.175

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

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

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

Clock 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 -92.017 -54.284 -39.197 0.841 29.689 32.648 37.116 68.887 86.932 19.006 -4.031 ms -1.382 7.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 47.85.203.40

peer offset 47.85.203.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 47.85.203.40 -11.482 -4.542 -0.158 5.077 10.458 14.417 15.104 10.616 18.959 3.390 5.170 ms -0.3312 5.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 49.12.103.123

peer offset 49.12.103.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 49.12.103.123 -104.453 -96.809 -69.563 -6.510 5.027 15.191 21.860 74.590 112.001 23.412 -14.909 ms -1.735 5.73

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

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

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

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



Server Offset 5.161.111.190

peer offset 5.161.111.190 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.111.190 -18.177 -13.919 -7.797 -3.175 1.189 3.412 7.582 8.985 17.330 3.150 -3.351 ms -0.7991 5.935

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

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

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

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



Server Offset 5.161.65.34

peer offset 5.161.65.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.65.34 -8.208 -8.208 -5.991 -2.626 391.162 391.162 391.162 397.153 399.370 139.388 55.456 ms 1.96 4.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 5.161.94.12

peer offset 5.161.94.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.94.12 -26.311 -6.511 -4.811 -1.264 2.953 5.663 14.347 7.764 12.174 2.580 -1.106 ms -0.4285 13.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 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.219 -10.118 -1.240 4.708 17.495 18.465 14.826 163.714 15.817 -2.959 ms -8.266 75.32

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

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

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

Clock 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 -39.877 -17.266 -8.068 0.913 10.777 46.263 49.954 18.845 63.530 7.541 1.212 ms 1.76 23.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 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 -2.368 1.056 5.159 7.878 9.310 22.510 6.821 11.678 13.703 3.961 ms -12.53 162.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 64.251.10.152

peer offset 64.251.10.152 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.251.10.152 -9.929 -6.388 -4.004 -0.535 3.189 7.131 10.599 7.193 13.520 2.557 -0.405 ms 0.497 5.923

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

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

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

Clock 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 -19.040 -5.987 -1.441 1.538 6.062 11.148 17.628 7.503 17.136 3.013 1.733 ms -0.05078 18.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 65.182.224.60

peer offset 65.182.224.60 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 65.182.224.60 -4.897 -4.897 -2.203 1.449 6.846 10.883 10.883 9.048 15.780 2.958 1.749 ms 0.4925 3.551

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

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

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

Clock 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.228.14

peer offset 66.118.228.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.118.228.14 -333.165 -10.163 -2.631 4.084 8.349 9.848 12.691 10.980 20.011 25.449 1.791 ms -12.74 167.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 66.118.229.14

peer offset 66.118.229.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.118.229.14 -46.204 -13.396 -8.297 4.542 8.438 12.813 14.060 16.735 26.209 5.776 3.279 ms -3.792 28.07

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

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

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

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



Server Offset 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 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 -33.203 -20.781 -6.815 -1.590 2.829 8.831 423.145 9.644 29.611 19.691 -1.014 ms 20.08 430.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 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.172.133.130

peer offset 69.172.133.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.172.133.130 -90.322 -90.322 -90.322 -0.456 5.333 5.333 5.333 95.655 95.655 30.376 -13.340 ms -1.942 5.071

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

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

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

Clock 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 -132.300 -129.112 -0.945 2.644 5.466 104.738 425.249 6.410 233.850 36.439 4.507 ms 6.773 86.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 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 -4.457 -2.249 1.962 4.415 5.325 6.408 6.664 9.783 3.249 1.568 ms -14.63 356.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 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.182.49

peer offset 72.14.182.49 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.14.182.49 -1.532 -0.973 0.417 4.164 7.308 8.085 8.396 6.891 9.058 1.895 4.150 ms -0.3723 3.354

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

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

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

Clock 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 -10.962 -10.962 -6.498 5.374 7.467 8.444 8.444 13.965 19.405 4.758 3.225 ms -1.263 3.404

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

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

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

Clock 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 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 -385.027 -6.151 -1.418 5.070 8.405 10.253 12.049 9.823 16.404 24.387 3.111 ms -15.45 243.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 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 -30.088 -6.553 8.715 13.063 17.416 35.796 19.617 47.504 8.901 6.769 ms -5.017 41.06

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

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

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

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



Server Offset 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 -40.517 -8.386 1.614 4.988 9.257 17.475 13.374 49.775 7.967 0.338 ms -6.267 52.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 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 -64.543 -22.125 -6.189 -1.934 0.842 3.006 11.556 7.031 25.131 4.902 -2.553 ms -7.128 70.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 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 0.735 1.927 3.184 5.282 7.898 10.686 14.032 4.714 8.759 1.554 5.393 ms 1.083 6.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 83.228.206.15

peer offset 83.228.206.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 83.228.206.15 -137.287 -103.254 -84.102 -4.454 5.321 17.569 31.867 89.423 120.823 27.221 -15.904 ms -1.832 6.201

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

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

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

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



Server Offset 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 3.866 6.473 6.473 6.473 7.120 7.120 2.149 3.382 ms -0.4244 2.121

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

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

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

Clock 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 -1,995.690 -9.227 -2.599 3.709 6.341 11.025 51.057 8.939 20.252 126.659 -4.965 ms -15.62 245.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.



Refclock Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(0) -1,142.216 -545.438 -184.677 -151.939 -128.845 -120.245 1,345.558 55.832 425.193 69.792 -164.020 ms -4.658 29.51

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(1) -1,005.833 -8.509 -7.578 -4.077 0.107 0.293 2,340.449 7.685 8.802 12.229 -3.283 ms 121.5 2.128e+04

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(2)

peer offset SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(2) -192.688 -182.186 -176.515 -149.356 -0.739 3.019 1,940.513 175.776 185.205 69.704 -113.302 ms 1.707 32.06

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(3)

peer offset SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(3) -13.801 -8.706 -8.285 -4.392 0.235 0.544 2,061.810 8.521 9.250 13.252 -3.451 ms 144.3 2.196e+04

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(4)

peer offset SHM(4) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(4) -161.294 -159.152 -156.877 -151.439 -146.907 -145.585 -142.438 9.970 13.567 3.040 -151.647 ms -0.2552 2.747

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(5)

peer offset SHM(5) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(5) -6.986 -3.330 -0.686 -0.171 0.413 0.591 0.760 1.099 3.921 0.607 -0.178 ms -4.609 34.92

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(0)

peer offset SOCK(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SOCK(0) -228.887 -179.011 -176.395 -26.716 2.712 5.057 10.783 179.108 184.068 83.058 -86.897 ms -0.05067 1.037

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(1)

peer offset SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SOCK(1) -52.048 -6.481 -5.397 -0.101 0.459 0.890 94.972 5.856 7.372 1.554 -0.446 ms -1.648 200.7

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(2)

peer offset SOCK(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock 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 local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(3)

peer offset SOCK(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock 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 local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 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.834 4.593 17.099 87.951 111.550 16.266 87.951 11.842 6.739 ms 6.605 51.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 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.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.000 0.735 1.495 3.548 13.550 26.903 29.916 12.055 26.168 4.494 4.883 ms 3.04 14.17

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 107.172.222.7

peer jitter 107.172.222.7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 107.172.222.7 0.000 0.000 1.084 4.379 25.305 36.743 37.327 24.221 36.743 8.622 8.136 ms 1.606 4.837

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

Closer to 0s 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.215.221

peer jitter 108.61.215.221 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 108.61.215.221 0.000 0.714 1.150 4.505 26.091 34.413 41.318 24.940 33.698 8.433 8.402 ms 1.357 4.032

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

Closer to 0s 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.205.28.193

peer jitter 12.205.28.193 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 12.205.28.193 0.000 0.000 0.000 11.183 108.575 108.575 108.575 108.575 108.575 37.651 31.806 ms 0.9856 2.424

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

Closer to 0s 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.809 2.667 17.247 17.857 18.051 16.439 17.857 3.953 3.880 ms 2.33 8.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 129.250.35.250

peer jitter 129.250.35.250 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 129.250.35.250 0.000 0.000 1.317 4.421 13.783 159.937 160.090 12.466 159.937 16.049 6.795 ms 9.004 85.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 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 134.215.155.177

peer jitter 134.215.155.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 134.215.155.177 0.000 0.000 0.215 3.893 9.692 11.268 11.268 9.477 11.268 2.613 4.426 ms 0.7499 2.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 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 136.244.88.170

peer jitter 136.244.88.170 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 136.244.88.170 0.000 0.000 0.000 45.687 96.956 96.956 96.956 96.956 96.956 24.598 45.912 ms -0.1894 3.157

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

Closer to 0s 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.357 3.675 23.603 63.864 79.789 171.675 60.189 78.432 18.871 27.109 ms 1.289 6.803

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

Closer to 0s 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.753 1.179 4.911 26.490 37.783 47.502 25.312 37.030 8.477 8.215 ms 1.982 7.242

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

Closer to 0s 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.277 16.409 33.553 33.553 16.409 33.553 5.930 4.248 ms 3.357 16.26

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 143.42.229.154

peer jitter 143.42.229.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 143.42.229.154 0.000 0.000 1.148 7.611 49.932 51.852 52.766 48.784 51.852 13.133 12.146 ms 1.725 5.461

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

Closer to 0s 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 111.447 111.447 111.447 111.447 111.447 36.473 18.156 ms 1.831 4.445

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

Closer to 0s 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.41.38

peer jitter 144.202.41.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.41.38 0.000 0.000 0.000 6.779 14.889 14.889 14.889 14.889 14.889 5.989 6.622 ms 0.08954 1.408

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

Closer to 0s 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 1.137 3.703 18.598 217.349 311.298 17.462 217.349 30.716 9.133 ms 7.378 59.79

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.842 1.241 3.979 17.508 43.753 123.164 16.267 42.911 9.251 6.136 ms 7.096 70.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 144.31.251.154

peer jitter 144.31.251.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.31.251.154 0.000 0.000 0.000 19.833 74.107 74.107 74.107 74.107 74.107 32.568 34.054 ms 0.1749 1.143

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 147.88.195.53

peer jitter 147.88.195.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 147.88.195.53 0.000 0.000 0.000 41.577 77.749 93.726 95.821 77.749 93.726 21.527 41.634 ms -0.03586 2.951

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

Closer to 0s 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 5.393 14.159 15.551 15.551 14.159 15.551 4.042 5.981 ms 0.6682 2.543

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

Closer to 0s 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.196 3.536 18.634 57.348 74.406 17.439 57.348 8.390 5.764 ms 5.262 36.95

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

Closer to 0s 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.594 1.159 5.081 37.680 56.441 197.074 36.521 55.847 13.477 10.313 ms 4.231 38.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 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.234 13.655 13.655 13.655 13.655 13.655 4.564 3.852 ms 1.167 2.827

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 151.236.20.166

peer jitter 151.236.20.166 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 151.236.20.166 0.000 1.259 1.527 3.486 15.315 62.462 73.702 13.788 61.203 9.812 5.895 ms 4.933 28.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 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.355 0.902 3.193 9.792 16.282 21.738 8.891 15.927 3.015 3.977 ms 2.004 8.991

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 157.245.125.229

peer jitter 157.245.125.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 157.245.125.229 0.000 0.000 0.000 1.602 1.798 1.798 1.798 1.798 1.798 0.805 1.133 ms -0.676 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 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.000 0.000 3.146 20.597 45.058 45.058 20.597 45.058 8.553 4.999 ms 3.695 17.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 161.35.230.200

peer jitter 161.35.230.200 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 161.35.230.200 0.000 0.000 0.000 1.722 4.765 5.072 5.072 4.765 5.072 1.384 2.182 ms 0.4533 2.424

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

Closer to 0s 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 0.976 3.353 15.333 89.491 91.781 14.356 89.491 12.047 5.795 ms 6.319 44.08

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

Closer to 0s 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 1.136 3.282 15.682 29.826 79.186 14.546 29.826 6.342 4.894 ms 5.842 53.45

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

Closer to 0s 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.244.81.139

peer jitter 162.244.81.139 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.244.81.139 0.000 0.000 0.000 9.802 310.114 310.114 310.114 310.114 310.114 110.370 91.381 ms 0.7029 1.807

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

Closer to 0s 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 168.235.89.132

peer jitter 168.235.89.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 168.235.89.132 0.000 0.000 1.451 6.551 24.642 241.813 312.601 23.191 241.813 41.436 15.557 ms 5.318 31.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 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.346 1.042 3.020 13.585 35.711 154.182 12.543 35.365 8.619 5.057 ms 10.79 170.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 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.000 0.934 2.691 18.421 98.115 126.152 17.487 98.115 14.936 5.909 ms 6.169 42.32

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

Closer to 0s 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.155.39

peer jitter 172.233.155.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.155.39 0.000 0.000 0.857 2.798 13.575 19.709 19.951 12.718 19.709 3.872 3.811 ms 2.816 11.19

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

Closer to 0s 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.565 304.504 477.649 477.649 304.504 477.649 119.833 64.084 ms 1.983 6.246

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.233.189.68

peer jitter 172.233.189.68 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.189.68 0.000 0.000 0.000 1.536 21.515 21.515 21.515 21.515 21.515 9.868 9.010 ms 0.4016 1.177

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

Closer to 0s 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.860 3.695 9.252 14.966 20.475 8.393 14.966 3.140 4.585 ms 1.66 7.978

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

Closer to 0s 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.358 4.258 56.738 90.303 110.008 56.380 90.303 17.894 10.624 ms 3.314 14.28

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

Closer to 0s 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.773 1.152 3.471 14.471 27.652 74.064 13.319 26.879 5.675 4.931 ms 5.262 44.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 172.238.164.57

peer jitter 172.238.164.57 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.238.164.57 0.000 0.651 1.077 3.190 12.196 22.320 98.321 11.119 21.670 6.582 4.553 ms 9.34 119.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 172.245.210.108

peer jitter 172.245.210.108 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.245.210.108 0.000 0.000 0.000 3.191 187.963 208.084 208.084 187.963 208.084 52.818 21.295 ms 2.724 8.749

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

Closer to 0s 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.230.96

peer jitter 173.255.230.96 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.255.230.96 0.000 0.000 1.050 3.510 18.774 67.403 67.650 17.724 67.403 9.020 6.895 ms 3.984 24.19

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

Closer to 0s 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 185.234.20.134

peer jitter 185.234.20.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 185.234.20.134 0.000 0.000 0.508 39.811 79.288 185.571 206.604 78.780 185.571 30.495 40.818 ms 2.363 12.83

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 7.808 30.985 62.953 81.489 85.309 55.145 81.489 17.040 34.378 ms 0.4215 2.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 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.854 7.768 7.768 7.768 7.768 7.768 1.838 2.982 ms 1.078 4.127

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

Closer to 0s 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.765 1.141 3.293 12.485 23.827 398.640 11.344 23.062 8.233 4.806 ms 17.35 504.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 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.137.202.56

peer jitter 198.137.202.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.137.202.56 0.000 0.765 1.172 3.291 13.772 31.040 170.481 12.600 30.275 8.582 5.067 ms 10.93 170.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 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.881 5.524 13.433 21.945 21.945 12.552 21.945 5.022 6.627 ms 1.269 4.587

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

Closer to 0s 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.507 1.163 3.349 21.861 39.332 60.567 20.698 38.825 8.052 6.125 ms 3.345 16.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 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 198.71.50.75

peer jitter 198.71.50.75 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.71.50.75 0.000 1.525 3.734 23.735 49.077 91.787 92.484 45.343 90.262 15.505 24.891 ms 1.557 7.619

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

Closer to 0s 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 199.68.201.237

peer jitter 199.68.201.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 199.68.201.237 0.000 1.108 1.497 4.379 13.223 24.575 59.461 11.726 23.467 4.609 5.470 ms 4.52 39.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 20.55.26.153

peer jitter 20.55.26.153 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 20.55.26.153 0.000 0.000 0.000 6.632 74.079 74.079 74.079 74.079 74.079 25.471 19.985 ms 1.005 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 2001:1600:13:101::16b7

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 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:41d0:303:65e9::1

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 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: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: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.958 20.585 20.585 20.585 20.585 20.585 4.963 6.321 ms 1.837 5.999

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

Closer to 0s 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.336 2.466 22.769 84.523 104.133 240.582 82.057 102.797 26.853 31.178 ms 0.982 3.468

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

Closer to 0s 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 204.2.134.173

peer jitter 204.2.134.173 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.2.134.173 0.000 0.737 1.155 3.937 11.016 25.193 273.013 9.861 24.456 16.748 5.825 ms 14.91 236.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 206.210.192.99

peer jitter 206.210.192.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 206.210.192.99 0.000 0.000 0.000 2.291 4.456 4.456 4.456 4.456 4.456 1.344 2.379 ms 0.04821 2.401

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

Closer to 0s 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.000 0.637 9.204 18.759 23.144 23.144 18.123 23.144 5.496 7.808 ms 0.9792 3.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 209.177.158.85

peer jitter 209.177.158.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.177.158.85 0.000 0.638 1.059 3.381 16.552 42.861 76.463 15.494 42.223 7.143 5.333 ms 5.146 38.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 212.227.240.160

peer jitter 212.227.240.160 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 212.227.240.160 0.000 0.000 0.000 5.333 13.898 13.898 13.898 13.898 13.898 4.106 5.460 ms 0.8261 3.059

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

Closer to 0s 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 1.112 3.126 13.486 18.864 19.152 12.375 18.864 3.595 4.102 ms 2.301 8.604

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

Closer to 0s 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 3.822 28.627 28.627 28.627 28.627 28.627 10.699 10.365 ms 0.418 1.362

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

Closer to 0s 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.66.48.42

peer jitter 216.66.48.42 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.66.48.42 0.000 0.000 2.641 25.978 59.408 65.378 72.744 56.767 65.378 15.554 27.857 ms 0.5488 2.961

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

Closer to 0s 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.82.35.115

peer jitter 216.82.35.115 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.82.35.115 0.000 0.000 0.000 17.805 45.013 45.013 45.013 45.013 45.013 13.064 18.801 ms 0.1825 1.945

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

Closer to 0s 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.697 1.158 4.634 17.883 23.569 194.491 16.725 22.872 8.013 6.998 ms 11.92 270.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 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 2.025 187.757 223.573 223.573 187.757 223.573 59.842 25.642 ms 2.394 7.022

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

Closer to 0s 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.150.40.242

peer jitter 23.150.40.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.150.40.242 0.000 0.000 0.000 7.670 312.076 312.076 312.076 312.076 312.076 113.085 95.475 ms 0.6106 1.686

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

Closer to 0s 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.150.41.122

peer jitter 23.150.41.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.150.41.122 0.000 0.796 1.190 3.307 13.542 32.912 36.946 12.352 32.116 4.892 4.685 ms 3.705 20.28

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

Closer to 0s 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.150.41.123

peer jitter 23.150.41.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.150.41.123 0.000 0.000 1.435 7.766 36.840 59.991 89.122 35.405 59.991 12.188 11.975 ms 2.431 11.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 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.128 3.297 25.833 117.881 142.893 24.705 117.881 18.570 8.072 ms 5.348 34.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 23.155.72.147

peer jitter 23.155.72.147 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.155.72.147 0.000 0.000 1.155 3.406 36.728 38.286 43.030 35.574 38.286 9.343 6.981 ms 2.473 8.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 23.159.16.194

peer jitter 23.159.16.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.159.16.194 0.000 1.045 2.467 16.809 27.390 32.850 58.053 24.924 31.805 7.442 16.306 ms 0.07263 4.257

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

Closer to 0s 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.161.104.133

peer jitter 23.161.104.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.161.104.133 0.000 0.000 11.339 45.335 77.663 95.911 152.099 66.323 95.911 19.814 45.793 ms 0.3031 4.716

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

Closer to 0s 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.168.24.210

peer jitter 23.168.24.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.168.24.210 0.000 0.000 1.329 6.287 36.844 40.675 48.121 35.515 40.675 10.711 11.315 ms 1.333 4.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 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.760 1.157 3.204 11.988 21.308 69.314 10.831 20.549 4.560 4.347 ms 5.553 56.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.125

peer jitter 23.186.168.125 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.125 0.000 0.760 1.194 3.478 12.503 23.541 68.977 11.309 22.781 4.874 4.687 ms 5.05 44.55

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

Closer to 0s 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.000 0.000 86.127 106.510 106.510 106.510 106.510 106.510 46.232 50.498 ms 0.03958 1.076

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

Closer to 0s 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.830 1.341 3.311 8.610 17.200 23.748 7.269 16.370 2.788 3.878 ms 2.963 14.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 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.238 1.203 3.499 10.974 82.480 281.407 9.771 82.242 14.152 5.666 ms 11.01 159.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 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 17.762 8.099 ms 3.357 12.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 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.35.34

peer jitter 23.95.35.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.95.35.34 0.000 0.829 1.232 4.064 17.053 36.772 53.916 15.821 35.942 6.495 5.868 ms 3.639 19.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 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.000 0.000 1.232 2.989 2.989 2.989 2.989 2.989 0.868 1.357 ms 0.08276 2.173

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

Closer to 0s 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: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: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: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.000 0.000 2.102 15.060 15.060 15.060 15.060 15.060 4.508 4.272 ms 1.493 3.915

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.000 0.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.602 0.861 1.214 3.106 12.458 41.666 62.069 11.244 40.805 5.911 4.465 ms 5.908 46.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 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: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: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 1.724 12.727 32.149 45.133 45.133 30.425 45.133 10.548 13.401 ms 0.9434 3.715

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

Closer to 0s 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 9.048 9.048 9.048 9.048 9.048 2.075 3.136 ms 1.443 5.582

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

Closer to 0s 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.838 1.310 3.545 24.100 56.224 193.607 22.790 55.386 15.949 8.119 ms 8.326 91.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 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:f590::23:161:104:133 (isere.sd.ysun.co)

peer jitter 2602:f590::23:161:104:133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:f590::23:161:104:133 (isere.sd.ysun.co) 0.000 0.000 7.038 40.173 63.744 78.005 83.945 56.706 78.005 17.076 39.669 ms -0.2518 2.788

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

Closer to 0s 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: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 (ntp.ny1.neptunenetworks.net)

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 (ntp.ny1.neptunenetworks.net) 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: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-d60fb58e.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-d60fb58e.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.524 0.809 1.271 3.190 11.873 49.372 76.050 10.603 48.564 7.300 4.920 ms 5.559 39.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 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.623 5.781 5.781 5.781 5.781 5.781 1.647 3.489 ms -0.4789 2.783

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

Closer to 0s 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::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 11.421 25.574 25.574 25.574 25.574 25.574 7.238 12.934 ms -0.04102 2.807

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

Closer to 0s 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 0.000 0.000 3.562 6.209 6.209 6.209 6.209 6.209 2.544 3.257 ms -0.178 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 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: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.853 1.254 3.425 16.821 38.212 196.069 15.567 37.359 7.817 5.274 ms 7.674 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 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.861 1.240 3.361 14.548 44.296 176.369 13.308 43.435 8.214 5.183 ms 8.139 104.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 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 24.326 24.843 24.843 24.843 24.843 24.843 11.591 16.390 ms -0.7061 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 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: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: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 (vps-lax1.orleans.ddnss.de)

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 (vps-lax1.orleans.ddnss.de) 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 9.776 48.813 48.813 48.813 48.813 48.813 19.531 17.265 ms 0.7692 1.734

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

Closer to 0s 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: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 1.017 1.436 3.683 18.577 53.342 107.171 17.141 52.325 8.525 5.671 ms 5.606 42.25

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

Closer to 0s 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: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.376 9.243 54.544 101.472 115.644 271.797 92.228 113.268 27.464 55.684 ms 0.2142 3.189

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

Closer to 0s 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.363 6.343 49.988 97.879 112.533 234.358 91.536 110.170 27.788 50.480 ms 0.2906 2.949

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

Closer to 0s 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

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

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 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 (42-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 (42-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.912 1.774 17.078 78.834 99.393 166.058 77.060 98.481 25.673 26.711 ms 1.192 4.091

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

Closer to 0s 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 38.45.64.130

peer jitter 38.45.64.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 38.45.64.130 0.000 0.000 7.571 29.546 64.425 166.492 263.171 56.855 166.492 23.853 34.485 ms 4.369 34.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 40.160.28.79

peer jitter 40.160.28.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 40.160.28.79 0.000 1.801 6.063 24.301 44.703 52.503 53.020 38.640 50.702 10.983 25.335 ms 0.2798 2.796

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

Closer to 0s 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.785 1.148 3.114 9.948 20.349 625.327 8.800 19.563 9.660 4.203 ms 48.43 2996

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

Closer to 0s 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.33.53.84

peer jitter 45.33.53.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.33.53.84 0.000 0.831 1.241 3.939 13.487 24.803 53.423 12.247 23.971 5.057 5.138 ms 4.216 30.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 45.55.58.103

peer jitter 45.55.58.103 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.55.58.103 0.000 0.000 0.000 85.863 108.041 108.041 108.041 108.041 108.041 46.518 50.518 ms 0.04903 1.088

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

Closer to 0s 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.675 1.205 3.429 14.379 24.347 79.311 13.174 23.672 5.764 4.732 ms 6.33 62.25

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

Closer to 0s 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.241 5.704 5.704 5.704 5.704 5.704 1.667 1.809 ms 1.009 2.758

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

Closer to 0s 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 1.495 42.711 84.854 180.211 180.284 83.360 180.211 31.061 46.707 ms 1.962 9.528

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 47.85.203.40

peer jitter 47.85.203.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 47.85.203.40 0.000 0.848 1.598 5.948 28.308 42.271 42.446 26.710 41.422 9.054 9.477 ms 1.937 6.968

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 49.12.103.123

peer jitter 49.12.103.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 49.12.103.123 0.000 0.000 7.178 50.984 95.543 105.971 112.348 88.364 105.971 24.549 51.635 ms 0.01243 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 5.161.111.190

peer jitter 5.161.111.190 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.111.190 0.000 0.887 1.554 4.668 21.349 37.015 37.112 19.795 36.128 7.669 8.606 ms 1.358 4.999

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 5.161.65.34

peer jitter 5.161.65.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.65.34 0.000 0.000 0.000 4.473 17.184 17.184 17.184 17.184 17.184 4.658 5.050 ms 0.938 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 5.161.94.12

peer jitter 5.161.94.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.94.12 0.000 0.726 1.107 5.319 32.339 56.965 81.956 31.232 56.239 10.938 9.475 ms 2.697 13.19

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

Closer to 0s 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.096 3.528 22.835 29.378 30.209 22.739 29.378 7.966 7.859 ms 1.051 2.928

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

Closer to 0s 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.163 9.296 31.573 43.704 46.371 31.410 43.704 9.986 11.553 ms 1.272 4.653

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

Closer to 0s 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.502 1.006 3.046 15.530 21.438 24.923 14.524 20.936 4.143 4.328 ms 2.606 10.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 64.251.10.152

peer jitter 64.251.10.152 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.251.10.152 0.000 0.662 1.310 2.937 14.783 23.548 24.751 13.473 22.886 4.514 4.810 ms 2.064 7.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 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.862 2.232 8.548 15.286 19.717 7.685 15.286 2.906 3.164 ms 2.538 10.82

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 65.182.224.60

peer jitter 65.182.224.60 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 65.182.224.60 0.000 0.000 2.004 3.445 7.058 10.501 10.501 5.054 10.501 1.855 3.928 ms 1.023 4.59

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

Closer to 0s 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.228.14

peer jitter 66.118.228.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.118.228.14 0.000 1.929 2.939 6.604 16.232 40.531 64.782 13.293 38.601 6.085 7.807 ms 4.869 36.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 66.118.229.14

peer jitter 66.118.229.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.118.229.14 0.000 12.905 17.541 43.034 69.623 82.562 91.203 52.082 69.657 15.534 43.735 ms 0.08592 3.136

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

Closer to 0s 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 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 3.782 16.952 25.882 32.289 50.963 22.100 32.289 6.594 16.539 ms 0.03535 4.717

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

Closer to 0s 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.172.133.130

peer jitter 69.172.133.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.172.133.130 0.000 0.000 0.000 3.230 75.376 75.376 75.376 75.376 75.376 24.828 13.852 ms 1.682 4.021

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 69.176.84.38

peer jitter 69.176.84.38 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 69.89.207.199

peer jitter 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.89.207.199 0.000 0.000 1.450 3.855 17.406 96.391 120.778 15.957 96.391 13.071 6.599 ms 6.312 45.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 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.735 1.206 3.444 11.580 28.844 217.779 10.374 28.110 8.902 5.056 ms 13.81 276.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.182.49

peer jitter 72.14.182.49 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.14.182.49 0.000 0.852 1.163 3.269 16.589 22.688 25.413 15.425 21.836 4.550 4.656 ms 2.49 9.16

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

Closer to 0s 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.232 2.515 7.822 13.480 13.480 7.590 13.480 2.909 3.730 ms 0.9794 3.718

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 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 0.530 1.606 3.864 27.203 58.725 80.745 25.597 58.195 10.849 8.290 ms 3.184 15.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 77.37.97.124

peer jitter 77.37.97.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.37.97.124 0.000 0.000 2.796 32.332 77.851 100.698 150.671 75.056 100.698 24.623 34.958 ms 0.696 3.419

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

Closer to 0s 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 0.900 1.851 19.516 80.597 96.805 116.085 78.746 95.905 26.687 29.693 ms 0.8002 2.536

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

Closer to 0s 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.793 1.333 9.929 70.698 94.447 111.150 69.365 93.654 22.373 19.069 ms 1.697 5.375

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.607 0.789 1.197 3.067 8.843 20.979 60.098 7.646 20.189 4.249 3.915 ms 6.61 69.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 83.228.206.15

peer jitter 83.228.206.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 83.228.206.15 0.000 0.000 11.060 56.909 95.536 108.530 155.978 84.476 108.530 23.568 56.450 ms 0.05599 3.839

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

Closer to 0s 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 2.890 17.347 17.347 17.347 17.347 17.347 4.961 3.776 ms 2.163 6.304

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

Closer to 0s 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.828 1.266 3.849 19.898 76.766 200.156 18.632 75.938 14.712 7.068 ms 8.068 83.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.



Refclock RMS Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(0) 0.000 0.521 0.780 2.066 249.248 295.491 1,615.750 248.468 294.970 66.477 19.767 ms 3.732 18.07

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(1) 0.000 0.158 0.201 0.311 0.485 0.649 1,591.279 0.284 0.491 9.619 0.453 ms 100 1.165e+04

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(2)

peer jitter SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(2) 0.000 0.522 0.793 2.180 5.699 8.272 2,002.029 4.906 7.750 17.422 2.801 ms 87.27 8129

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(3)

peer jitter SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(3) 0.000 0.182 0.212 0.312 0.482 0.699 2,001.141 0.270 0.517 16.599 0.526 ms 92.41 9035

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(4)

peer jitter SHM(4) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(4) 0.000 0.462 0.715 1.781 4.115 5.613 9.498 3.400 5.151 1.084 2.018 ms 1.439 6.41

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(5)

peer jitter SHM(5) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(5) 0.000 113.019 173.172 305.621 513.760 609.838 1,715.353 340.588 496.819 114.363 324.731 µs 1.861 16.26

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SOCK(0)

peer jitter SOCK(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SOCK(0) 0.000 0.439 0.641 1.587 4.205 9.159 171.548 3.565 8.719 2.205 1.994 ms 26.13 1499

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SOCK(1)

peer jitter SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SOCK(1) 0.000 0.195 0.222 0.325 0.543 0.767 104.304 0.322 0.572 0.711 0.355 ms 100.4 1.159e+04

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SOCK(2)

peer jitter SOCK(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS 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 local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SOCK(3)

peer jitter SOCK(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS 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 local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer 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.612 10.922 11.480 22.419 25.406 183.534 11.497 14.793 8.334 13.880 ppm -8.216 99.89
Local Clock Time Offset -127.900 -8.297 -6.626 -0.231 0.363 0.834 121.205 6.989 9.131 2.878 -1.880 ms -0.595 219.3
Local RMS Frequency Jitter 0.0000 0.0031 0.0038 0.0104 0.388 0.712 73.177 0.384 0.709 0.838 0.124 ppm 44.97 2554
Local RMS Time Jitter 0.000 0.133 0.164 0.345 0.542 2.379 83.702 0.379 2.246 1.173 0.405 ms 34.73 1538
Refclock Offset SHM(0) -1,142.216 -545.438 -184.677 -151.939 -128.845 -120.245 1,345.558 55.832 425.193 69.792 -164.020 ms -4.658 29.51
Refclock Offset SHM(1) -1,005.833 -8.509 -7.578 -4.077 0.107 0.293 2,340.449 7.685 8.802 12.229 -3.283 ms 121.5 2.128e+04
Refclock Offset SHM(2) -192.688 -182.186 -176.515 -149.356 -0.739 3.019 1,940.513 175.776 185.205 69.704 -113.302 ms 1.707 32.06
Refclock Offset SHM(3) -13.801 -8.706 -8.285 -4.392 0.235 0.544 2,061.810 8.521 9.250 13.252 -3.451 ms 144.3 2.196e+04
Refclock Offset SHM(4) -161.294 -159.152 -156.877 -151.439 -146.907 -145.585 -142.438 9.970 13.567 3.040 -151.647 ms -0.2552 2.747
Refclock Offset SHM(5) -6.986 -3.330 -0.686 -0.171 0.413 0.591 0.760 1.099 3.921 0.607 -0.178 ms -4.609 34.92
Refclock Offset SOCK(0) -228.887 -179.011 -176.395 -26.716 2.712 5.057 10.783 179.108 184.068 83.058 -86.897 ms -0.05067 1.037
Refclock Offset SOCK(1) -52.048 -6.481 -5.397 -0.101 0.459 0.890 94.972 5.856 7.372 1.554 -0.446 ms -1.648 200.7
Refclock 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
Refclock 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
Refclock RMS Jitter SHM(0) 0.000 0.521 0.780 2.066 249.248 295.491 1,615.750 248.468 294.970 66.477 19.767 ms 3.732 18.07
Refclock RMS Jitter SHM(1) 0.000 0.158 0.201 0.311 0.485 0.649 1,591.279 0.284 0.491 9.619 0.453 ms 100 1.165e+04
Refclock RMS Jitter SHM(2) 0.000 0.522 0.793 2.180 5.699 8.272 2,002.029 4.906 7.750 17.422 2.801 ms 87.27 8129
Refclock RMS Jitter SHM(3) 0.000 0.182 0.212 0.312 0.482 0.699 2,001.141 0.270 0.517 16.599 0.526 ms 92.41 9035
Refclock RMS Jitter SHM(4) 0.000 0.462 0.715 1.781 4.115 5.613 9.498 3.400 5.151 1.084 2.018 ms 1.439 6.41
Refclock RMS Jitter SHM(5) 0.000 113.019 173.172 305.621 513.760 609.838 1,715.353 340.588 496.819 114.363 324.731 µs 1.861 16.26
Refclock RMS Jitter SOCK(0) 0.000 0.439 0.641 1.587 4.205 9.159 171.548 3.565 8.719 2.205 1.994 ms 26.13 1499
Refclock RMS Jitter SOCK(1) 0.000 0.195 0.222 0.325 0.543 0.767 104.304 0.322 0.572 0.711 0.355 ms 100.4 1.159e+04
Refclock RMS 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
Refclock RMS 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 Jitter 104.131.155.175 0.000 0.000 0.834 4.593 17.099 87.951 111.550 16.266 87.951 11.842 6.739 ms 6.605 51.46
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.234.61.117 0.000 0.735 1.495 3.548 13.550 26.903 29.916 12.055 26.168 4.494 4.883 ms 3.04 14.17
Server Jitter 107.172.222.7 0.000 0.000 1.084 4.379 25.305 36.743 37.327 24.221 36.743 8.622 8.136 ms 1.606 4.837
Server Jitter 108.61.215.221 0.000 0.714 1.150 4.505 26.091 34.413 41.318 24.940 33.698 8.433 8.402 ms 1.357 4.032
Server Jitter 12.205.28.193 0.000 0.000 0.000 11.183 108.575 108.575 108.575 108.575 108.575 37.651 31.806 ms 0.9856 2.424
Server Jitter 129.146.193.200 0.000 0.000 0.809 2.667 17.247 17.857 18.051 16.439 17.857 3.953 3.880 ms 2.33 8.207
Server Jitter 129.250.35.250 0.000 0.000 1.317 4.421 13.783 159.937 160.090 12.466 159.937 16.049 6.795 ms 9.004 85.92
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 134.215.155.177 0.000 0.000 0.215 3.893 9.692 11.268 11.268 9.477 11.268 2.613 4.426 ms 0.7499 2.88
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 136.244.88.170 0.000 0.000 0.000 45.687 96.956 96.956 96.956 96.956 96.956 24.598 45.912 ms -0.1894 3.157
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.357 3.675 23.603 63.864 79.789 171.675 60.189 78.432 18.871 27.109 ms 1.289 6.803
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.753 1.179 4.911 26.490 37.783 47.502 25.312 37.030 8.477 8.215 ms 1.982 7.242
Server Jitter 142.202.190.19 0.000 0.000 0.000 2.277 16.409 33.553 33.553 16.409 33.553 5.930 4.248 ms 3.357 16.26
Server Jitter 143.42.229.154 0.000 0.000 1.148 7.611 49.932 51.852 52.766 48.784 51.852 13.133 12.146 ms 1.725 5.461
Server Jitter 144.202.0.197 0.000 0.000 0.000 2.470 111.447 111.447 111.447 111.447 111.447 36.473 18.156 ms 1.831 4.445
Server Jitter 144.202.41.38 0.000 0.000 0.000 6.779 14.889 14.889 14.889 14.889 14.889 5.989 6.622 ms 0.08954 1.408
Server Jitter 144.202.62.209 0.000 0.000 1.137 3.703 18.598 217.349 311.298 17.462 217.349 30.716 9.133 ms 7.378 59.79
Server Jitter 144.202.66.214 0.000 0.842 1.241 3.979 17.508 43.753 123.164 16.267 42.911 9.251 6.136 ms 7.096 70.4
Server Jitter 144.31.251.154 0.000 0.000 0.000 19.833 74.107 74.107 74.107 74.107 74.107 32.568 34.054 ms 0.1749 1.143
Server Jitter 147.88.195.53 0.000 0.000 0.000 41.577 77.749 93.726 95.821 77.749 93.726 21.527 41.634 ms -0.03586 2.951
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 5.393 14.159 15.551 15.551 14.159 15.551 4.042 5.981 ms 0.6682 2.543
Server Jitter 149.28.200.179 0.000 0.000 1.196 3.536 18.634 57.348 74.406 17.439 57.348 8.390 5.764 ms 5.262 36.95
Server Jitter 149.28.61.105 0.000 0.594 1.159 5.081 37.680 56.441 197.074 36.521 55.847 13.477 10.313 ms 4.231 38.67
Server Jitter 15.204.87.223 0.000 0.000 0.000 1.234 13.655 13.655 13.655 13.655 13.655 4.564 3.852 ms 1.167 2.827
Server Jitter 151.236.20.166 0.000 1.259 1.527 3.486 15.315 62.462 73.702 13.788 61.203 9.812 5.895 ms 4.933 28.97
Server Jitter 155.248.196.28 0.000 0.355 0.902 3.193 9.792 16.282 21.738 8.891 15.927 3.015 3.977 ms 2.004 8.991
Server Jitter 157.245.125.229 0.000 0.000 0.000 1.602 1.798 1.798 1.798 1.798 1.798 0.805 1.133 ms -0.676 1.5
Server Jitter 158.51.99.19 0.000 0.000 0.000 3.146 20.597 45.058 45.058 20.597 45.058 8.553 4.999 ms 3.695 17.01
Server Jitter 161.35.230.200 0.000 0.000 0.000 1.722 4.765 5.072 5.072 4.765 5.072 1.384 2.182 ms 0.4533 2.424
Server Jitter 162.159.200.1 0.000 0.000 0.976 3.353 15.333 89.491 91.781 14.356 89.491 12.047 5.795 ms 6.319 44.08
Server Jitter 162.159.200.123 0.000 0.000 1.136 3.282 15.682 29.826 79.186 14.546 29.826 6.342 4.894 ms 5.842 53.45
Server Jitter 162.244.81.139 0.000 0.000 0.000 9.802 310.114 310.114 310.114 310.114 310.114 110.370 91.381 ms 0.7029 1.807
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 168.235.89.132 0.000 0.000 1.451 6.551 24.642 241.813 312.601 23.191 241.813 41.436 15.557 ms 5.318 31.48
Server Jitter 170.187.147.56 0.000 0.346 1.042 3.020 13.585 35.711 154.182 12.543 35.365 8.619 5.057 ms 10.79 170.1
Server Jitter 171.66.97.126 0.000 0.000 0.934 2.691 18.421 98.115 126.152 17.487 98.115 14.936 5.909 ms 6.169 42.32
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.155.39 0.000 0.000 0.857 2.798 13.575 19.709 19.951 12.718 19.709 3.872 3.811 ms 2.816 11.19
Server Jitter 172.233.157.223 0.000 0.000 0.000 2.565 304.504 477.649 477.649 304.504 477.649 119.833 64.084 ms 1.983 6.246
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.233.189.68 0.000 0.000 0.000 1.536 21.515 21.515 21.515 21.515 21.515 9.868 9.010 ms 0.4016 1.177
Server Jitter 172.234.25.10 0.000 0.000 0.860 3.695 9.252 14.966 20.475 8.393 14.966 3.140 4.585 ms 1.66 7.978
Server Jitter 172.234.37.140 0.000 0.000 0.358 4.258 56.738 90.303 110.008 56.380 90.303 17.894 10.624 ms 3.314 14.28
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.773 1.152 3.471 14.471 27.652 74.064 13.319 26.879 5.675 4.931 ms 5.262 44.71
Server Jitter 172.238.164.57 0.000 0.651 1.077 3.190 12.196 22.320 98.321 11.119 21.670 6.582 4.553 ms 9.34 119.8
Server Jitter 172.245.210.108 0.000 0.000 0.000 3.191 187.963 208.084 208.084 187.963 208.084 52.818 21.295 ms 2.724 8.749
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.230.96 0.000 0.000 1.050 3.510 18.774 67.403 67.650 17.724 67.403 9.020 6.895 ms 3.984 24.19
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 185.234.20.134 0.000 0.000 0.508 39.811 79.288 185.571 206.604 78.780 185.571 30.495 40.818 ms 2.363 12.83
Server Jitter 192.48.105.15 0.000 0.000 7.808 30.985 62.953 81.489 85.309 55.145 81.489 17.040 34.378 ms 0.4215 2.981
Server Jitter 193.29.63.226 0.000 0.000 0.000 2.854 7.768 7.768 7.768 7.768 7.768 1.838 2.982 ms 1.078 4.127
Server Jitter 194.0.5.123 0.000 0.765 1.141 3.293 12.485 23.827 398.640 11.344 23.062 8.233 4.806 ms 17.35 504.7
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.137.202.56 0.000 0.765 1.172 3.291 13.772 31.040 170.481 12.600 30.275 8.582 5.067 ms 10.93 170.4
Server Jitter 198.211.103.209 0.000 0.000 0.881 5.524 13.433 21.945 21.945 12.552 21.945 5.022 6.627 ms 1.269 4.587
Server Jitter 198.46.254.130 0.000 0.507 1.163 3.349 21.861 39.332 60.567 20.698 38.825 8.052 6.125 ms 3.345 16.72
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 198.71.50.75 0.000 1.525 3.734 23.735 49.077 91.787 92.484 45.343 90.262 15.505 24.891 ms 1.557 7.619
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 199.68.201.237 0.000 1.108 1.497 4.379 13.223 24.575 59.461 11.726 23.467 4.609 5.470 ms 4.52 39.75
Server Jitter 20.55.26.153 0.000 0.000 0.000 6.632 74.079 74.079 74.079 74.079 74.079 25.471 19.985 ms 1.005 2.423
Server Jitter 2001:1600:13:101::16b7 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:41d0:303:65e9::1 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: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: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.958 20.585 20.585 20.585 20.585 20.585 4.963 6.321 ms 1.837 5.999
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.336 2.466 22.769 84.523 104.133 240.582 82.057 102.797 26.853 31.178 ms 0.982 3.468
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 204.2.134.173 0.000 0.737 1.155 3.937 11.016 25.193 273.013 9.861 24.456 16.748 5.825 ms 14.91 236.2
Server Jitter 206.210.192.99 0.000 0.000 0.000 2.291 4.456 4.456 4.456 4.456 4.456 1.344 2.379 ms 0.04821 2.401
Server Jitter 208.113.130.146 0.000 0.000 0.637 9.204 18.759 23.144 23.144 18.123 23.144 5.496 7.808 ms 0.9792 3.962
Server Jitter 209.177.158.85 0.000 0.638 1.059 3.381 16.552 42.861 76.463 15.494 42.223 7.143 5.333 ms 5.146 38.96
Server Jitter 212.227.240.160 0.000 0.000 0.000 5.333 13.898 13.898 13.898 13.898 13.898 4.106 5.460 ms 0.8261 3.059
Server Jitter 216.229.4.66 0.000 0.000 1.112 3.126 13.486 18.864 19.152 12.375 18.864 3.595 4.102 ms 2.301 8.604
Server Jitter 216.250.115.174 0.000 0.000 0.000 3.822 28.627 28.627 28.627 28.627 28.627 10.699 10.365 ms 0.418 1.362
Server Jitter 216.66.48.42 0.000 0.000 2.641 25.978 59.408 65.378 72.744 56.767 65.378 15.554 27.857 ms 0.5488 2.961
Server Jitter 216.82.35.115 0.000 0.000 0.000 17.805 45.013 45.013 45.013 45.013 45.013 13.064 18.801 ms 0.1825 1.945
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.697 1.158 4.634 17.883 23.569 194.491 16.725 22.872 8.013 6.998 ms 11.92 270.9
Server Jitter 23.142.248.9 0.000 0.000 0.000 2.025 187.757 223.573 223.573 187.757 223.573 59.842 25.642 ms 2.394 7.022
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.150.40.242 0.000 0.000 0.000 7.670 312.076 312.076 312.076 312.076 312.076 113.085 95.475 ms 0.6106 1.686
Server Jitter 23.150.41.122 0.000 0.796 1.190 3.307 13.542 32.912 36.946 12.352 32.116 4.892 4.685 ms 3.705 20.28
Server Jitter 23.150.41.123 0.000 0.000 1.435 7.766 36.840 59.991 89.122 35.405 59.991 12.188 11.975 ms 2.431 11.69
Server Jitter 23.155.40.38 0.000 0.000 1.128 3.297 25.833 117.881 142.893 24.705 117.881 18.570 8.072 ms 5.348 34.09
Server Jitter 23.155.72.147 0.000 0.000 1.155 3.406 36.728 38.286 43.030 35.574 38.286 9.343 6.981 ms 2.473 8.282
Server Jitter 23.159.16.194 0.000 1.045 2.467 16.809 27.390 32.850 58.053 24.924 31.805 7.442 16.306 ms 0.07263 4.257
Server Jitter 23.161.104.133 0.000 0.000 11.339 45.335 77.663 95.911 152.099 66.323 95.911 19.814 45.793 ms 0.3031 4.716
Server Jitter 23.168.24.210 0.000 0.000 1.329 6.287 36.844 40.675 48.121 35.515 40.675 10.711 11.315 ms 1.333 4.184
Server Jitter 23.186.168.123 0.000 0.760 1.157 3.204 11.988 21.308 69.314 10.831 20.549 4.560 4.347 ms 5.553 56.38
Server Jitter 23.186.168.125 0.000 0.760 1.194 3.478 12.503 23.541 68.977 11.309 22.781 4.874 4.687 ms 5.05 44.55
Server Jitter 23.186.168.126 0.000 0.000 0.000 86.127 106.510 106.510 106.510 106.510 106.510 46.232 50.498 ms 0.03958 1.076
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.830 1.341 3.311 8.610 17.200 23.748 7.269 16.370 2.788 3.878 ms 2.963 14.9
Server Jitter 23.186.168.129 0.000 0.238 1.203 3.499 10.974 82.480 281.407 9.771 82.242 14.152 5.666 ms 11.01 159.8
Server Jitter 23.186.168.130 0.000 0.000 0.000 3.466 73.799 73.994 73.994 73.799 73.994 17.762 8.099 ms 3.357 12.57
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.35.34 0.000 0.829 1.232 4.064 17.053 36.772 53.916 15.821 35.942 6.495 5.868 ms 3.639 19.9
Server Jitter 23.95.49.216 0.000 0.000 0.000 1.232 2.989 2.989 2.989 2.989 2.989 0.868 1.357 ms 0.08276 2.173
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: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: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: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.000 0.000 2.102 15.060 15.060 15.060 15.060 15.060 4.508 4.272 ms 1.493 3.915
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.000 0.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.602 0.861 1.214 3.106 12.458 41.666 62.069 11.244 40.805 5.911 4.465 ms 5.908 46.42
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: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: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 1.724 12.727 32.149 45.133 45.133 30.425 45.133 10.548 13.401 ms 0.9434 3.715
Server Jitter 2602:291:69::9 (time.trtnw.net) 0.000 0.000 0.000 3.210 9.048 9.048 9.048 9.048 9.048 2.075 3.136 ms 1.443 5.582
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.838 1.310 3.545 24.100 56.224 193.607 22.790 55.386 15.949 8.119 ms 8.326 91.43
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:f590::23:161:104:133 (isere.sd.ysun.co) 0.000 0.000 7.038 40.173 63.744 78.005 83.945 56.706 78.005 17.076 39.669 ms -0.2518 2.788
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: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 (ntp.ny1.neptunenetworks.net) 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: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-d60fb58e.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.524 0.809 1.271 3.190 11.873 49.372 76.050 10.603 48.564 7.300 4.920 ms 5.559 39.04
Server Jitter 2604:4300:a:299::164 0.000 0.000 0.000 3.623 5.781 5.781 5.781 5.781 5.781 1.647 3.489 ms -0.4789 2.783
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::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 11.421 25.574 25.574 25.574 25.574 25.574 7.238 12.934 ms -0.04102 2.807
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 0.000 0.000 3.562 6.209 6.209 6.209 6.209 6.209 2.544 3.257 ms -0.178 1.5
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: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.853 1.254 3.425 16.821 38.212 196.069 15.567 37.359 7.817 5.274 ms 7.674 106
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.861 1.240 3.361 14.548 44.296 176.369 13.308 43.435 8.214 5.183 ms 8.139 104.2
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 24.326 24.843 24.843 24.843 24.843 24.843 11.591 16.390 ms -0.7061 1.5
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: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: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 (vps-lax1.orleans.ddnss.de) 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 9.776 48.813 48.813 48.813 48.813 48.813 19.531 17.265 ms 0.7692 1.734
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: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 1.017 1.436 3.683 18.577 53.342 107.171 17.141 52.325 8.525 5.671 ms 5.606 42.25
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: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.376 9.243 54.544 101.472 115.644 271.797 92.228 113.268 27.464 55.684 ms 0.2142 3.189
Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) 0.000 2.363 6.343 49.988 97.879 112.533 234.358 91.536 110.170 27.788 50.480 ms 0.2906 2.949
Server Jitter 2a01:4f8:c012:1afb:123:123:123:123 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 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 (42-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.912 1.774 17.078 78.834 99.393 166.058 77.060 98.481 25.673 26.711 ms 1.192 4.091
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 38.45.64.130 0.000 0.000 7.571 29.546 64.425 166.492 263.171 56.855 166.492 23.853 34.485 ms 4.369 34.53
Server Jitter 40.160.28.79 0.000 1.801 6.063 24.301 44.703 52.503 53.020 38.640 50.702 10.983 25.335 ms 0.2798 2.796
Server Jitter 44.190.5.123 0.000 0.785 1.148 3.114 9.948 20.349 625.327 8.800 19.563 9.660 4.203 ms 48.43 2996
Server Jitter 45.33.53.84 0.000 0.831 1.241 3.939 13.487 24.803 53.423 12.247 23.971 5.057 5.138 ms 4.216 30.01
Server Jitter 45.55.58.103 0.000 0.000 0.000 85.863 108.041 108.041 108.041 108.041 108.041 46.518 50.518 ms 0.04903 1.088
Server Jitter 45.63.54.13 0.000 0.675 1.205 3.429 14.379 24.347 79.311 13.174 23.672 5.764 4.732 ms 6.33 62.25
Server Jitter 45.77.126.122 0.000 0.000 0.000 1.241 5.704 5.704 5.704 5.704 5.704 1.667 1.809 ms 1.009 2.758
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 1.495 42.711 84.854 180.211 180.284 83.360 180.211 31.061 46.707 ms 1.962 9.528
Server Jitter 47.85.203.40 0.000 0.848 1.598 5.948 28.308 42.271 42.446 26.710 41.422 9.054 9.477 ms 1.937 6.968
Server Jitter 49.12.103.123 0.000 0.000 7.178 50.984 95.543 105.971 112.348 88.364 105.971 24.549 51.635 ms 0.01243 2.627
Server Jitter 5.161.111.190 0.000 0.887 1.554 4.668 21.349 37.015 37.112 19.795 36.128 7.669 8.606 ms 1.358 4.999
Server Jitter 5.161.65.34 0.000 0.000 0.000 4.473 17.184 17.184 17.184 17.184 17.184 4.658 5.050 ms 0.938 3.169
Server Jitter 5.161.94.12 0.000 0.726 1.107 5.319 32.339 56.965 81.956 31.232 56.239 10.938 9.475 ms 2.697 13.19
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.096 3.528 22.835 29.378 30.209 22.739 29.378 7.966 7.859 ms 1.051 2.928
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.163 9.296 31.573 43.704 46.371 31.410 43.704 9.986 11.553 ms 1.272 4.653
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.502 1.006 3.046 15.530 21.438 24.923 14.524 20.936 4.143 4.328 ms 2.606 10.2
Server Jitter 64.251.10.152 0.000 0.662 1.310 2.937 14.783 23.548 24.751 13.473 22.886 4.514 4.810 ms 2.064 7.271
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.862 2.232 8.548 15.286 19.717 7.685 15.286 2.906 3.164 ms 2.538 10.82
Server Jitter 65.182.224.60 0.000 0.000 2.004 3.445 7.058 10.501 10.501 5.054 10.501 1.855 3.928 ms 1.023 4.59
Server Jitter 66.118.228.14 0.000 1.929 2.939 6.604 16.232 40.531 64.782 13.293 38.601 6.085 7.807 ms 4.869 36.09
Server Jitter 66.118.229.14 0.000 12.905 17.541 43.034 69.623 82.562 91.203 52.082 69.657 15.534 43.735 ms 0.08592 3.136
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 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 3.782 16.952 25.882 32.289 50.963 22.100 32.289 6.594 16.539 ms 0.03535 4.717
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.172.133.130 0.000 0.000 0.000 3.230 75.376 75.376 75.376 75.376 75.376 24.828 13.852 ms 1.682 4.021
Server Jitter 69.176.84.38 0.000 0.000 0.084 1.877 4.514 6.761 6.761 4.430 6.761 1.315 2.063 ms 1.34 5.848
Server Jitter 69.89.207.199 0.000 0.000 1.450 3.855 17.406 96.391 120.778 15.957 96.391 13.071 6.599 ms 6.312 45.92
Server Jitter 69.89.207.99 0.000 0.735 1.206 3.444 11.580 28.844 217.779 10.374 28.110 8.902 5.056 ms 13.81 276.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.182.49 0.000 0.852 1.163 3.269 16.589 22.688 25.413 15.425 21.836 4.550 4.656 ms 2.49 9.16
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.232 2.515 7.822 13.480 13.480 7.590 13.480 2.909 3.730 ms 0.9794 3.718
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 73.185.182.209 0.000 0.530 1.606 3.864 27.203 58.725 80.745 25.597 58.195 10.849 8.290 ms 3.184 15.24
Server Jitter 77.37.97.124 0.000 0.000 2.796 32.332 77.851 100.698 150.671 75.056 100.698 24.623 34.958 ms 0.696 3.419
Server Jitter 77.42.37.85 0.000 0.900 1.851 19.516 80.597 96.805 116.085 78.746 95.905 26.687 29.693 ms 0.8002 2.536
Server Jitter 79.160.225.13 0.000 0.793 1.333 9.929 70.698 94.447 111.150 69.365 93.654 22.373 19.069 ms 1.697 5.375
Server Jitter 83.147.242.172 0.607 0.789 1.197 3.067 8.843 20.979 60.098 7.646 20.189 4.249 3.915 ms 6.61 69.66
Server Jitter 83.228.206.15 0.000 0.000 11.060 56.909 95.536 108.530 155.978 84.476 108.530 23.568 56.450 ms 0.05599 3.839
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 2.890 17.347 17.347 17.347 17.347 17.347 4.961 3.776 ms 2.163 6.304
Server Jitter 99.28.14.242 0.000 0.828 1.266 3.849 19.898 76.766 200.156 18.632 75.938 14.712 7.068 ms 8.068 83.06
Server Offset 104.131.155.175 -127.900 -126.109 -9.873 1.397 10.054 13.031 16.334 19.927 139.141 23.291 -3.106 ms -4.589 23.4
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.234.61.117 -11.180 -9.140 -3.447 1.426 6.606 12.091 16.244 10.053 21.231 3.430 1.519 ms -0.07377 5.449
Server Offset 107.172.222.7 -12.642 -11.375 -7.178 1.882 7.310 12.947 14.359 14.488 24.322 3.982 1.625 ms -0.7389 5.565
Server Offset 108.61.215.221 -28.570 -9.305 -0.181 3.903 6.523 8.097 13.175 6.704 17.402 2.862 3.479 ms -3.533 28.36
Server Offset 12.205.28.193 -126.850 -126.850 -126.850 -114.175 6.955 6.955 6.955 133.805 133.805 46.151 -91.142 ms 1.065 2.644
Server Offset 129.146.193.200 -0.800 0.856 1.480 4.796 6.343 6.706 7.088 4.863 5.850 1.421 4.500 ms -1.034 4.16
Server Offset 129.250.35.250 -2.943 -2.410 -1.340 1.886 5.403 7.583 8.459 6.742 9.993 2.056 1.995 ms 0.3236 3.078
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 134.215.155.177 -6.511 -6.511 -4.780 0.657 5.183 15.538 15.538 9.962 22.050 3.593 0.567 ms 1.062 6.279
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 136.244.88.170 -82.929 -82.929 -82.929 -12.037 -3.376 -3.376 -3.376 79.553 79.553 25.987 -27.375 ms -0.9053 2.457
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 -30.357 -5.499 8.690 18.170 23.381 33.775 23.669 53.738 9.115 7.606 ms -3.604 27.41
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 -5.133 -3.834 -2.747 0.216 3.825 5.337 7.287 6.572 9.171 2.098 0.486 ms 0.248 2.697
Server Offset 142.202.190.19 -170.488 -170.488 -169.889 2.854 12.059 21.516 21.516 181.948 192.005 47.050 -9.997 ms -3.072 10.57
Server Offset 143.42.229.154 -12.280 -11.918 -8.448 0.679 4.877 10.025 10.853 13.326 21.944 3.809 0.031 ms -0.9182 4.866
Server Offset 144.202.0.197 -112.597 -112.597 -112.597 4.642 10.116 10.116 10.116 122.713 122.713 43.496 -14.874 ms -1.777 4.18
Server Offset 144.202.41.38 -8.294 -8.294 -8.294 4.829 12.556 12.556 12.556 20.850 20.850 6.900 3.360 ms -0.4744 2.271
Server Offset 144.202.62.209 -359.531 -4.209 -1.517 1.251 5.257 7.227 36.327 6.774 11.436 27.588 -0.646 ms -11.94 150
Server Offset 144.202.66.214 -1,991.190 -7.297 2.180 9.379 12.747 26.232 58.058 10.567 33.529 152.944 -2.874 ms -12.88 167.1
Server Offset 144.31.251.154 -1.884 -1.884 -1.884 1.637 9.630 9.630 9.630 11.515 11.515 4.100 3.810 ms 0.1811 1.537
Server Offset 147.88.195.53 -119.005 -102.607 -78.625 -8.685 6.545 10.280 13.559 85.170 112.887 26.779 -18.851 ms -1.354 4.238
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 -8.248 -8.248 -5.145 3.379 12.833 13.486 13.486 17.978 21.734 4.968 2.979 ms 0.2457 2.932
Server Offset 149.28.200.179 -88.226 -29.901 -7.700 1.855 7.253 12.590 25.332 14.953 42.491 9.462 0.942 ms -7.003 65.36
Server Offset 149.28.61.105 -1,995.498 -19.186 -4.326 3.263 6.176 17.348 44.622 10.502 36.534 163.507 -10.918 ms -12.03 145.8
Server Offset 15.204.87.223 -10.681 -10.681 -10.681 2.259 4.290 4.290 4.290 14.971 14.971 5.024 0.026 ms -1.3 2.977
Server Offset 151.236.20.166 -7.947 -5.621 -3.416 0.364 5.984 9.517 13.621 9.399 15.138 3.092 0.765 ms 0.5972 3.916
Server Offset 155.248.196.28 -7.263 -4.833 -2.774 0.162 4.381 7.586 11.821 7.155 12.418 2.274 0.520 ms 0.7526 4.999
Server Offset 157.245.125.229 1.618 1.618 1.618 2.114 3.912 3.912 3.912 2.294 2.294 0.986 2.548 ms 0.5751 1.5
Server Offset 158.51.99.19 -157.868 -157.868 -153.883 0.302 5.849 6.583 6.583 159.732 164.451 47.726 -16.939 ms -2.469 7.308
Server Offset 161.35.230.200 -2.730 -2.730 -1.127 1.511 390.595 395.667 395.667 391.722 398.397 147.881 68.930 ms 1.72 3.961
Server Offset 162.159.200.1 -33.205 -5.539 -1.015 5.329 8.946 11.637 16.373 9.961 17.176 3.732 4.665 ms -3.078 30.29
Server Offset 162.159.200.123 -1,990.740 -3.858 -1.054 5.742 8.784 12.008 41.636 9.838 15.866 54.127 3.754 ms -36.65 1351
Server Offset 162.244.81.139 -358.787 -358.787 -358.787 2.574 8.702 8.702 8.702 367.489 367.489 116.576 -46.950 ms -2.07 5.565
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 168.235.89.132 -361.703 -177.856 -1.214 2.049 6.635 8.852 9.305 7.848 186.709 37.893 -2.184 ms -8.706 79.36
Server Offset 170.187.147.56 -0.641 0.705 1.980 4.722 8.587 9.921 12.448 6.607 9.216 2.044 4.934 ms 0.3738 3.245
Server Offset 171.66.97.126 -111.117 -109.795 -2.851 0.792 3.175 6.263 130.236 6.027 116.058 15.291 -0.217 ms -2.186 57.79
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.155.39 -12.270 -2.993 -0.238 3.828 6.492 7.576 9.891 6.730 10.570 2.348 3.523 ms -1.715 12.15
Server Offset 172.233.157.223 -4.047 -4.047 -2.228 9.669 455.633 725.734 725.734 457.862 729.782 182.781 88.825 ms 2.207 6.825
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.233.189.68 8.111 8.111 8.111 8.731 10.099 10.099 10.099 1.988 1.988 0.780 9.065 ms 0.2333 1.349
Server Offset 172.234.25.10 -378.349 -377.277 -0.619 7.225 13.916 16.005 16.638 14.535 393.281 67.054 -4.512 ms -5.334 29.58
Server Offset 172.234.37.140 -384.852 -377.114 -16.092 2.112 9.952 35.580 41.762 26.044 412.695 43.692 -2.830 ms -8.214 71.4
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 -1,994.828 -7.193 -2.951 1.688 6.668 9.261 47.412 9.618 16.455 99.943 -3.213 ms -19.77 392.4
Server Offset 172.238.164.57 -20.678 -5.109 -3.388 1.693 6.481 7.573 11.018 9.869 12.682 3.241 1.724 ms -0.3793 3.926
Server Offset 172.245.210.108 -261.506 -261.506 -251.411 0.386 170.775 173.801 173.801 422.186 435.307 82.626 -6.480 ms -0.7581 6.622
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.230.96 -4.019 -1.915 0.365 4.658 8.077 9.189 28.541 7.712 11.104 2.614 4.581 ms 2.225 26.93
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 185.234.20.134 -207.966 -198.229 8.539 43.765 55.709 222.317 228.892 47.170 420.546 42.923 39.520 ms -0.8843 22.3
Server Offset 192.48.105.15 -38.144 -16.120 -9.873 4.243 8.544 13.335 24.385 18.417 29.455 5.972 2.916 ms -2.066 11.6
Server Offset 193.29.63.226 -3.460 -3.460 -3.460 3.103 9.170 9.170 9.170 12.629 12.629 3.530 2.605 ms 0.006634 1.907
Server Offset 194.0.5.123 -1,993.360 -6.911 -3.239 1.546 6.949 9.870 390.115 10.188 16.782 46.173 0.790 ms -41.5 1789
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.137.202.56 -206.226 -11.480 -4.652 -0.701 4.599 14.997 34.211 9.252 26.477 10.560 -0.960 ms -13.83 244.4
Server Offset 198.211.103.209 -15.435 -15.435 -2.909 1.625 11.374 11.645 11.645 14.282 27.080 5.917 2.710 ms -0.8834 4.822
Server Offset 198.46.254.130 -11.109 -8.702 -1.432 4.138 9.376 11.538 50.250 10.808 20.240 3.757 4.029 ms 2.757 44.84
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 198.71.50.75 -21.461 -16.971 -10.397 -4.651 -1.037 1.083 5.931 9.360 18.054 3.141 -4.906 ms -1.601 9.855
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 199.68.201.237 -54.221 -4.457 -2.342 2.245 5.491 7.434 14.187 7.833 11.890 3.323 1.891 ms -8.342 141.8
Server Offset 20.55.26.153 -90.128 -90.128 -90.128 0.419 4.026 4.026 4.026 94.154 94.154 29.373 -11.273 ms -2.13 5.815
Server Offset 2001:1600:13:101::16b7 -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:41d0:303:65e9::1 -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: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: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 -0.851 -0.851 -0.851 7.144 17.145 17.145 17.145 17.997 17.997 4.502 6.891 ms 0.4579 3.325
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.575 -3.251 -0.150 589.234 8.607 22.927 8.794 -7.106 ms 20.66 2760
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 204.2.134.173 -330.587 -1.995 0.505 4.402 7.005 7.870 8.684 6.500 9.866 24.915 2.289 ms -13.06 173.8
Server Offset 206.210.192.99 3.732 3.732 3.732 10.882 12.986 12.986 12.986 9.255 9.255 2.868 9.737 ms -0.9345 2.785
Server Offset 208.113.130.146 -1.547 -1.547 -0.705 1.652 11.527 14.355 14.355 12.232 15.903 4.437 3.317 ms 1.173 3.138
Server Offset 209.177.158.85 -30.375 -4.642 -3.180 0.545 5.452 6.644 15.829 8.632 11.286 3.226 0.948 ms -2.144 24.9
Server Offset 212.227.240.160 -12.742 -12.742 -12.742 -3.409 1.156 1.156 1.156 13.898 13.898 4.103 -3.640 ms -1.253 3.789
Server Offset 216.229.4.66 -17.026 -11.915 -9.323 -0.696 4.542 13.045 13.185 13.865 24.960 3.827 -1.038 ms -0.2364 6.866
Server Offset 216.250.115.174 -50.737 -50.737 -50.737 -20.501 369.510 369.510 369.510 420.246 420.246 125.161 28.344 ms 2.264 6.333
Server Offset 216.66.48.42 -57.714 -48.968 -41.803 -10.099 4.232 45.537 48.178 46.035 94.505 15.518 -12.901 ms 0.07764 5.238
Server Offset 216.82.35.115 -29.297 -29.297 -9.388 -1.589 392.815 392.815 392.815 402.203 422.112 140.650 54.907 ms 1.952 4.828
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 -3.042 1.210 6.116 10.765 12.869 13.726 15.979 6.753 12.515 2.251 10.327 ms -1.931 8.788
Server Offset 23.142.248.9 -263.459 -263.459 -261.533 -1.198 167.901 168.098 168.098 429.434 431.557 92.982 -6.282 ms -0.7409 5.495
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.150.40.242 -357.926 -357.926 -357.926 3.502 10.525 10.525 10.525 368.451 368.451 119.758 -47.624 ms -1.976 5.174
Server Offset 23.150.41.122 -3.912 -0.906 1.567 5.532 9.044 10.304 12.219 7.477 11.210 2.174 5.373 ms -0.477 4.713
Server Offset 23.150.41.123 -22.902 -6.785 -3.289 8.706 11.720 26.163 32.724 15.009 32.948 5.336 7.384 ms -0.5486 7.805
Server Offset 23.155.40.38 -158.747 -42.839 -3.587 1.531 3.890 6.081 8.018 7.477 48.920 15.680 -0.567 ms -9.275 91.75
Server Offset 23.155.72.147 -392.987 -391.252 -12.441 -6.112 -0.837 1.703 7.397 11.604 392.955 61.955 -16.524 ms -5.782 34.56
Server Offset 23.159.16.194 -332.773 -2.949 1.895 12.336 15.900 21.536 27.238 14.005 24.484 25.353 9.220 ms -12.89 173.5
Server Offset 23.161.104.133 -2,049.972 -101.074 -80.281 -9.695 8.763 15.686 36.039 89.043 116.761 72.795 -20.018 ms -24.1 670.5
Server Offset 23.168.24.210 -30.994 -9.946 -0.456 4.953 9.479 14.370 15.899 9.935 24.316 3.912 4.627 ms -3.016 28.6
Server Offset 23.186.168.123 -18.265 -7.951 -3.512 2.207 4.285 5.506 24.970 7.797 13.457 2.606 1.618 ms -1.683 11.05
Server Offset 23.186.168.125 -336.573 -2.857 -1.290 2.156 4.173 5.028 21.753 5.462 7.885 12.191 1.436 ms -26.88 738.4
Server Offset 23.186.168.126 -114.793 -114.793 -114.793 -5.494 -0.844 -0.844 -0.844 113.950 113.950 54.847 -57.177 ms -0.005087 1.013
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 -173.852 -2.042 0.684 3.783 5.861 6.834 11.189 5.176 8.875 8.584 3.249 ms -19.66 401.9
Server Offset 23.186.168.129 -100.937 -12.969 -1.947 2.841 5.908 10.375 423.814 7.855 23.343 16.766 2.764 ms 13.97 354.2
Server Offset 23.186.168.130 -5.129 -5.129 -4.461 -1.043 5.449 7.796 7.796 9.909 12.926 3.728 -0.075 ms 0.3855 1.791
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.35.34 -27.613 -4.807 -3.147 0.347 4.555 6.819 20.501 7.701 11.627 2.606 0.524 ms -0.5651 20.3
Server Offset 23.95.49.216 2.004 2.004 2.004 5.904 7.369 7.369 7.369 5.365 5.365 1.531 5.662 ms -0.973 3.221
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: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: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: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 1.672 1.672 1.672 5.591 19.969 19.969 19.969 18.297 18.297 5.131 6.284 ms 1.945 5.754
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) -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.743 0.572 2.736 4.877 5.612 6.968 4.305 6.355 1.285 2.737 ms -0.4082 4.515
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: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: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 -30.239 -30.239 1.140 3.666 8.180 46.292 46.292 7.039 76.531 8.723 4.146 ms 1.265 19.19
Server Offset 2602:291:69::9 (time.trtnw.net) -0.476 -0.476 -0.476 7.476 11.063 11.063 11.063 11.539 11.539 2.887 6.192 ms -0.5951 3.021
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 -3.839 -1.705 0.313 2.455 3.497 5.247 4.160 7.336 10.717 -0.295 ms -16.11 264.3
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:f590::23:161:104:133 (isere.sd.ysun.co) -471.581 -385.176 -54.827 -11.476 0.126 5.242 28.182 54.953 390.419 61.385 -26.183 ms -5.774 37.6
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: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 (ntp.ny1.neptunenetworks.net) 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: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-d60fb58e.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 -39.062 -9.506 1.053 4.764 6.043 7.109 14.270 45.105 8.589 -1.957 ms -3.022 13.39
Server Offset 2604:4300:a:299::164 -4.878 -4.878 -4.878 0.553 3.067 3.067 3.067 7.945 7.945 2.835 -0.799 ms -0.1278 1.481
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::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) 8.916 8.916 8.916 14.499 37.032 37.032 37.032 28.115 28.115 8.702 16.497 ms 1.735 4.537
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) -3.852 -3.852 -3.852 -0.420 1.987 1.987 1.987 5.839 5.839 2.396 -0.762 ms -0.2111 1.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: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.854 -3.702 5.350 8.547 9.988 51.896 12.248 15.842 4.437 4.520 ms -14.13 537
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -68.168 -3.942 -2.047 5.036 8.626 10.408 429.230 10.673 14.350 8.834 4.804 ms 36.43 1691
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) 2.084 2.084 2.084 5.198 6.067 6.067 6.067 3.983 3.983 1.710 4.450 ms -0.5727 1.5
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: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: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 (vps-lax1.orleans.ddnss.de) 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 -26.492 -26.492 -26.492 16.912 30.534 30.534 30.534 57.026 57.026 14.105 13.122 ms -2.005 6.462
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: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 -26.566 0.301 2.769 4.833 6.184 9.683 4.532 32.750 4.590 2.212 ms -7.468 71.61
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: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) -267.863 -48.067 -22.013 0.370 7.466 11.344 425.774 29.479 59.411 12.437 -2.316 ms 2.624 203.5
Server Offset 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) -178.311 -56.349 -20.962 -0.647 6.367 10.538 106.144 27.329 66.886 11.826 -2.978 ms -4.66 45.16
Server Offset 2a01:4f8:c012:1afb:123:123:123:123 -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 -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 (42-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 -2,001.428 -48.644 -14.990 -1.817 1.832 5.508 13.648 16.822 54.151 42.738 -4.524 ms -44.6 2081
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 38.45.64.130 -257.312 -73.003 -9.597 5.725 9.142 13.153 177.823 18.739 86.156 24.534 3.845 ms -3.142 73.78
Server Offset 40.160.28.79 -52.835 -52.513 -34.382 -5.004 1.626 5.643 7.374 36.008 58.156 10.906 -8.229 ms -2.157 7.89
Server Offset 44.190.5.123 -619.209 -1.752 0.995 5.099 7.144 8.271 28.290 6.149 10.023 9.160 4.601 ms -57.22 3770
Server Offset 45.33.53.84 -46.045 -1.169 1.112 4.939 7.280 7.847 8.597 6.167 9.016 2.868 4.557 ms -9.347 157.9
Server Offset 45.55.58.103 -110.343 -110.343 -110.343 0.562 3.360 3.360 3.360 113.703 113.703 54.930 -52.554 ms -0.005973 1.01
Server Offset 45.63.54.13 -5.411 -0.490 2.322 5.646 7.622 9.009 23.365 5.301 9.499 1.820 5.474 ms -0.3691 12.49
Server Offset 45.77.126.122 0.280 0.280 1.370 4.514 10.132 10.132 10.132 8.762 9.852 2.436 4.532 ms 0.629 3.175
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 -92.017 -54.284 -39.197 0.841 29.689 32.648 37.116 68.887 86.932 19.006 -4.031 ms -1.382 7.042
Server Offset 47.85.203.40 -11.482 -4.542 -0.158 5.077 10.458 14.417 15.104 10.616 18.959 3.390 5.170 ms -0.3312 5.456
Server Offset 49.12.103.123 -104.453 -96.809 -69.563 -6.510 5.027 15.191 21.860 74.590 112.001 23.412 -14.909 ms -1.735 5.73
Server Offset 5.161.111.190 -18.177 -13.919 -7.797 -3.175 1.189 3.412 7.582 8.985 17.330 3.150 -3.351 ms -0.7991 5.935
Server Offset 5.161.65.34 -8.208 -8.208 -5.991 -2.626 391.162 391.162 391.162 397.153 399.370 139.388 55.456 ms 1.96 4.843
Server Offset 5.161.94.12 -26.311 -6.511 -4.811 -1.264 2.953 5.663 14.347 7.764 12.174 2.580 -1.106 ms -0.4285 13.42
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.219 -10.118 -1.240 4.708 17.495 18.465 14.826 163.714 15.817 -2.959 ms -8.266 75.32
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 -39.877 -17.266 -8.068 0.913 10.777 46.263 49.954 18.845 63.530 7.541 1.212 ms 1.76 23.37
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 -2.368 1.056 5.159 7.878 9.310 22.510 6.821 11.678 13.703 3.961 ms -12.53 162.5
Server Offset 64.251.10.152 -9.929 -6.388 -4.004 -0.535 3.189 7.131 10.599 7.193 13.520 2.557 -0.405 ms 0.497 5.923
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 -19.040 -5.987 -1.441 1.538 6.062 11.148 17.628 7.503 17.136 3.013 1.733 ms -0.05078 18.55
Server Offset 65.182.224.60 -4.897 -4.897 -2.203 1.449 6.846 10.883 10.883 9.048 15.780 2.958 1.749 ms 0.4925 3.551
Server Offset 66.118.228.14 -333.165 -10.163 -2.631 4.084 8.349 9.848 12.691 10.980 20.011 25.449 1.791 ms -12.74 167.1
Server Offset 66.118.229.14 -46.204 -13.396 -8.297 4.542 8.438 12.813 14.060 16.735 26.209 5.776 3.279 ms -3.792 28.07
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 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 -33.203 -20.781 -6.815 -1.590 2.829 8.831 423.145 9.644 29.611 19.691 -1.014 ms 20.08 430.2
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.172.133.130 -90.322 -90.322 -90.322 -0.456 5.333 5.333 5.333 95.655 95.655 30.376 -13.340 ms -1.942 5.071
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 -132.300 -129.112 -0.945 2.644 5.466 104.738 425.249 6.410 233.850 36.439 4.507 ms 6.773 86.79
Server Offset 69.89.207.99 -82.728 -4.457 -2.249 1.962 4.415 5.325 6.408 6.664 9.783 3.249 1.568 ms -14.63 356.9
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.182.49 -1.532 -0.973 0.417 4.164 7.308 8.085 8.396 6.891 9.058 1.895 4.150 ms -0.3723 3.354
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 -10.962 -10.962 -6.498 5.374 7.467 8.444 8.444 13.965 19.405 4.758 3.225 ms -1.263 3.404
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 73.185.182.209 -385.027 -6.151 -1.418 5.070 8.405 10.253 12.049 9.823 16.404 24.387 3.111 ms -15.45 243.1
Server Offset 77.37.97.124 -93.402 -30.088 -6.553 8.715 13.063 17.416 35.796 19.617 47.504 8.901 6.769 ms -5.017 41.06
Server Offset 77.42.37.85 -88.107 -40.517 -8.386 1.614 4.988 9.257 17.475 13.374 49.775 7.967 0.338 ms -6.267 52.3
Server Offset 79.160.225.13 -64.543 -22.125 -6.189 -1.934 0.842 3.006 11.556 7.031 25.131 4.902 -2.553 ms -7.128 70.98
Server Offset 83.147.242.172 0.735 1.927 3.184 5.282 7.898 10.686 14.032 4.714 8.759 1.554 5.393 ms 1.083 6.68
Server Offset 83.228.206.15 -137.287 -103.254 -84.102 -4.454 5.321 17.569 31.867 89.423 120.823 27.221 -15.904 ms -1.832 6.201
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 3.866 6.473 6.473 6.473 7.120 7.120 2.149 3.382 ms -0.4244 2.121
Server Offset 99.28.14.242 -1,995.690 -9.227 -2.599 3.709 6.341 11.025 51.057 8.939 20.252 126.659 -4.965 ms -15.62 245.1
TDOP 0.450 0.520 0.590 0.860 11.810 11.810 11.810 11.220 11.290 2.634 1.593 3.536 13.8
Temp /dev/sda 17.000 18.000 20.000 25.000 26.000 28.000 39.000 6.000 10.000 2.246 24.272 °C
Temp LM0 26.000 31.000 32.000 34.000 41.000 45.000 59.000 9.000 14.000 2.667 34.994 °C
Temp LM1 27.000 29.000 30.000 38.000 39.000 40.000 54.000 9.000 11.000 2.820 36.498 °C
Temp LM2 0.000 0.000 19.000 19.000 39.000 40.000 46.000 20.000 40.000 9.485 23.383 °C
Temp LM3 0.000 3.000 3.000 30.000 40.000 41.000 44.000 37.000 38.000 8.809 29.894 °C
Temp LM4 0.000 0.000 0.000 32.000 41.000 46.000 55.000 41.000 46.000 14.765 26.745 °C
Temp LM5 26.000 28.000 28.000 30.000 38.000 38.000 44.000 10.000 10.000 2.289 30.934 °C
Temp LM6 28.000 30.000 31.000 33.000 35.000 37.000 50.000 4.000 7.000 1.575 32.986 °C
Temp LM7 30.000 32.000 33.000 35.000 37.000 39.000 51.000 4.000 7.000 1.541 34.773 °C
Temp LM8 26.800 32.000 33.000 35.000 37.000 39.000 51.000 4.000 7.000 1.550 35.042 °C
Temp LM9 26.800 32.000 33.000 35.000 37.000 39.000 51.000 4.000 7.000 1.550 35.042 °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 37.000 38.000 51.000 5.000 7.000 1.591 34.210 °C
Temp ZONE2 26.000 28.000 28.000 30.000 38.000 38.000 44.000 10.000 10.000 2.763 31.345 °C
Temp ZONE3 29.000 31.000 32.000 34.000 36.000 39.000 54.000 4.000 8.000 1.635 34.208 °C
Temp ZONE4 26.800 31.000 32.000 34.000 37.000 38.000 51.000 5.000 7.000 1.591 34.210 °C
Temp ZONE5 28.000 29.000 31.000 35.000 42.000 46.000 58.000 11.000 17.000 4.233 35.222 °C
Temp ZONE6 26.000 28.000 28.000 30.000 36.000 37.000 44.000 8.000 9.000 1.907 30.788 °C
nSats 6.000 8.000 9.000 12.000 17.000 18.000 22.000 8.000 10.000 2.378 12.063 nSat 0.746 3.179
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!