NTPsec

Dell-2018

Report generated: Thu May 21 23:30:05 2026 UTC
Start Time: Thu Feb 12 23:30:02 2026 UTC
End Time: Thu May 21 23:30:02 2026 UTC
Report Period: 98.0 days

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

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -126.620 -7.401 -6.560 -2.888 0.278 1.450 121.205 6.838 8.851 3.163 -3.129 ms 0.6265 299.9
Local Clock Frequency Offset -88.630 -83.152 11.136 15.704 22.341 23.478 135.754 11.206 106.629 16.089 14.137 ppm -5.38 32.99

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.245 0.289 0.386 0.614 4.010 83.702 0.326 3.765 2.124 0.587 ms 21.67 567

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.0048 0.0057 0.125 0.614 1.532 65.989 0.608 1.528 1.430 0.292 ppm 23.39 677

The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.

Lower is better. An ideal clock would be a horizontal line at 0ppm.

RMS Frequency Jitter is field 6 in the loopstats log file.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -126.620 -7.401 -6.560 -2.888 0.278 1.450 121.205 6.838 8.851 3.163 -3.129 ms 0.6265 299.9

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 -88.630 -83.152 11.136 15.704 22.341 23.478 135.754 11.206 106.629 16.089 14.137 ppm -5.38 32.99
Temp /dev/sda 18.000 20.000 20.000 25.000 26.000 28.000 29.000 6.000 8.000 2.249 24.237 °C
Temp LM0 31.000 32.000 34.000 37.000 40.000 42.000 59.000 6.000 10.000 1.976 37.060 °C
Temp LM1 29.000 30.000 31.000 34.000 37.000 38.000 42.000 6.000 8.000 1.950 34.142 °C
Temp LM2 26.000 26.000 34.000 38.000 40.000 41.000 45.000 6.000 15.000 2.500 37.587 °C
Temp LM3 0.000 0.000 3.000 3.000 40.000 41.000 42.000 37.000 41.000 17.802 16.868 °C
Temp LM4 0.000 0.000 0.000 32.000 39.000 41.000 51.000 39.000 41.000 17.144 21.536 °C
Temp LM5 29.000 29.000 30.000 33.000 38.000 38.000 38.000 8.000 9.000 2.910 33.627 °C
Temp LM6 31.000 32.000 33.000 34.000 37.000 37.000 44.000 4.000 5.000 1.209 34.391 °C
Temp LM7 32.000 34.000 34.000 36.000 38.000 39.000 45.000 4.000 5.000 1.236 36.004 °C
Temp LM8 26.800 26.800 34.000 36.000 38.000 39.000 45.000 4.000 12.200 1.855 35.948 °C
Temp LM9 26.800 26.800 34.000 36.000 38.000 39.000 45.000 4.000 12.200 1.855 35.948 °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 26.800 34.000 36.000 38.000 38.000 45.000 4.000 11.200 1.760 35.396 °C
Temp ZONE2 29.000 29.000 34.000 37.000 38.000 38.000 38.000 4.000 9.000 1.610 36.654 °C
Temp ZONE3 32.000 34.000 34.000 36.000 38.000 38.000 45.000 4.000 4.000 1.202 35.562 °C
Temp ZONE4 26.800 26.800 34.000 36.000 38.000 38.000 45.000 4.000 11.200 1.760 35.396 °C
Temp ZONE5 30.000 31.000 32.000 36.000 41.000 43.000 58.000 9.000 12.000 3.077 35.975 °C
Temp ZONE6 29.000 30.000 30.000 32.000 34.000 34.000 38.000 4.000 4.000 1.051 31.919 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 8.000 10.000 11.000 13.000 17.000 19.000 21.000 6.000 9.000 1.918 13.625 nSat 0.4589 2.864
TDOP 0.450 0.510 0.570 0.780 1.240 1.650 3.610 0.670 1.140 0.228 0.827 2.589 18.85

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 -9.978 -9.873 -7.869 1.310 6.960 13.031 14.937 14.829 22.904 4.061 1.075 ms 0.02473 4.904

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

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

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

Clock 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 -4.792 -2.272 0.549 3.917 6.211 7.860 9.035 5.662 10.132 1.761 3.664 ms -0.7761 5.096

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

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

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

Clock 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 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 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 -76.084 -67.500 -35.019 10.925 22.560 26.652 28.254 57.579 94.152 17.944 5.833 ms -2.35 9.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 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.158 3.794 5.235 7.287 6.541 9.069 2.065 0.422 ms 0.2609 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 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 -2.514 -2.514 -2.514 0.562 4.040 4.040 4.040 6.554 6.554 1.834 0.714 ms 0.1866 2.03

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

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

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

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



Server Offset 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 -0.542 1.509 1.509 1.509 114.106 114.106 56.383 -55.610 ms 0.0001555 1.001

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

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

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

Clock 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.521 1.466 5.257 7.006 9.284 6.778 11.215 30.798 -1.308 ms -10.76 120.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 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 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 2.102 8.205 12.647 12.647 13.350 20.895 4.129 1.825 ms 0.01569 3.465

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

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

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

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



Server Offset 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 -86.256 -9.082 0.956 6.594 11.091 14.392 15.676 97.347 10.098 -0.378 ms -7.006 59.74

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

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

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

Clock 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 -5.683 -5.683 -1.383 3.425 7.083 10.113 10.113 8.466 15.796 2.756 3.058 ms -0.2133 3.428

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

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

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

Clock 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.819 0.165 4.387 7.586 11.821 7.206 12.418 2.280 0.522 ms 0.7525 5.003

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

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

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

Clock 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 -41.684 -41.684 -41.684 0.979 5.849 5.849 5.849 47.534 47.534 11.216 -2.520 ms -2.785 9.976

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

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

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

Clock 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 -6.317 -5.539 -2.005 1.526 6.070 6.509 14.827 8.075 12.049 2.947 1.865 ms 0.5047 5.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 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 -5.100 -3.554 -1.544 5.409 8.497 10.316 40.107 10.040 13.870 3.641 4.692 ms 2.367 29.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 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 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 1.026 1.199 3.846 6.744 9.809 11.373 12.448 5.963 10.174 1.897 6.818 ms -0.2684 3.74

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

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

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

Clock 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.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 6.078 6.078 6.078 10.698 725.734 725.734 725.734 719.656 719.656 210.967 132.036 ms 1.564 4.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 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 -1.613 7.945 13.980 16.005 16.638 15.592 393.281 71.028 -5.439 ms -5.005 26.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 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 -382.248 -18.988 -1.211 4.187 5.631 9.952 23.175 387.879 58.312 -11.645 ms -6.113 38.82

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

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

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

Clock 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 -4.609 -2.609 -1.288 1.945 6.837 7.903 9.759 8.125 10.511 2.398 2.368 ms 0.4168 2.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 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 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 -11.713 -8.831 -4.179 -0.706 3.017 6.942 13.785 7.195 15.773 2.556 -0.678 ms -0.01569 7.164

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

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

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

Clock 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 -206.319 6.959 42.992 55.729 222.373 228.892 48.770 428.693 46.172 38.514 ms -0.7618 19.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 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 -452.715 -8.424 -3.585 3.117 7.269 10.673 38.968 10.853 19.098 12.506 2.400 ms -32.54 1181

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

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

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

Clock 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.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 -10.105 -8.900 -0.000 6.524 48.594 50.250 15.424 58.699 6.597 0.210 ms 4.556 35.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 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: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: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: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 -31.977 -15.406 -7.172 -3.482 0.045 589.234 11.924 32.022 19.880 -7.890 ms 12.14 684.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 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 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 -5.273 -3.659 -0.342 2.300 6.493 15.829 5.958 11.766 2.914 -0.447 ms -3.653 46.66

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

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

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

Clock 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.727 3.365 13.045 13.185 12.689 24.960 3.711 -1.195 ms -0.3257 7.429

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

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

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

Clock 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 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 5.217 6.311 7.730 10.986 13.253 14.647 15.979 5.523 8.336 1.615 10.885 ms -0.5224 3.944

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

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

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

Clock 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 -262.784 -2.992 167.935 168.098 168.098 430.720 431.557 109.223 -10.313 ms -0.5237 3.918

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

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

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

Clock 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 2.498 3.818 5.315 9.059 11.720 17.772 29.911 6.405 13.955 2.354 9.042 ms 2.282 20.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 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 -120.099 -96.843 -75.901 -8.718 9.325 14.069 24.574 85.226 110.912 26.011 -16.573 ms -1.394 4.486

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

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

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

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



Server Offset 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 -11.785 -6.413 1.295 4.250 5.852 24.970 10.663 17.637 3.731 0.148 ms -0.8055 6.081

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

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

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

Clock 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 -3.098 -1.585 2.037 4.140 5.172 21.753 5.725 8.270 16.559 0.943 ms -19.9 402

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

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

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

Clock 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.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 -6.268 -6.268 -6.268 -2.041 1.676 1.676 1.676 7.944 7.944 2.335 -1.348 ms -0.4703 2.407

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

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

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

Clock 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 -94.054 -94.054 -93.816 -1.602 282.002 282.002 282.002 375.818 376.056 70.236 1.009 ms 2.948 13.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 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 -5.129 -3.084 -1.667 -1.667 -1.667 3.462 3.462 1.214 -3.305 ms -0.01898 1.693

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

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

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

Clock 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 -8.170 -7.030 -3.318 -1.756 -0.801 -0.358 5.274 7.370 1.536 -3.601 ms -1.052 4.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 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 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) 685.845 685.845 685.845 685.845 685.845 685.845 685.845 0.000 0.000 0.000 685.845 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 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 -35.696 -13.455 6.013 26.982 33.757 37.961 52.890 27.744 51.416 9.367 24.013 ms -1.968 8.857

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

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

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

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



Server Offset 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) -78.408 -38.587 -25.758 2.891 8.850 15.203 312.713 34.608 53.791 13.226 -2.555 ms 3.114 94.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 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) 0.258 0.258 0.258 0.748 3.016 3.016 3.016 2.759 2.759 1.122 1.099 ms 1.068 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 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.585 16.789 20.179 20.349 12.082 21.539 4.146 9.944 ms -0.6706 8.562

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

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

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

Clock 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 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 -3.494 6.995 6.995 6.995 14.433 14.433 4.803 -1.951 ms 0.9793 2.753

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

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

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

Clock 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 -24.432 -11.353 -0.211 6.538 22.187 70.769 17.890 46.619 14.096 -0.800 ms -23.27 852.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:4f8:c012:1afb:123:123:123:123 (tock.telnet.li)

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

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

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

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

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

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



Server Offset 2a01:4f9:c013:fa27:123:123:123:123

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:4f9:c013:fa27:123:123:123:123 -74.656 -27.333 -9.959 1.200 5.509 11.828 152.944 15.468 39.161 10.688 0.396 ms 7.092 119.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 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 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 -129.797 -97.451 -53.266 -8.090 4.141 9.142 11.849 57.407 106.593 21.047 -13.839 ms -2.49 10.74

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

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

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

Clock 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 -7.144 -5.890 -3.383 0.473 2.586 3.398 3.924 5.969 9.288 1.795 0.182 ms -1.014 4.359

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

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

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

Clock 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 -1.368 -1.368 -1.281 3.720 5.707 6.732 6.732 6.988 8.101 1.980 3.475 ms -0.9176 3.305

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

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

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

Clock 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 -3.611 -3.611 -3.611 3.279 5.849 5.849 5.849 9.461 9.461 2.672 2.213 ms -0.5509 2.573

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

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

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

Clock 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.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.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 -13.393 -13.270 -8.900 -1.296 1.731 4.497 6.235 10.631 17.767 3.214 -1.929 ms -1.378 5.671

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

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

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

Clock 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.775 5.720 46.263 49.954 13.788 63.530 7.440 0.730 ms 2.027 26.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 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 -3.807 -1.522 1.150 5.163 7.606 8.830 11.602 6.456 10.352 1.992 4.926 ms -0.7831 4.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 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 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.484 1.519 6.164 11.148 17.628 7.648 17.136 3.038 1.696 ms -0.02657 18.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 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 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 -28.602 -25.457 -6.819 -1.820 0.412 2.488 4.396 7.232 27.945 4.227 -2.713 ms -3.881 21.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 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 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.272 7.467 8.444 8.444 13.965 19.405 4.884 3.065 ms -1.172 3.134

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

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

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

Clock 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 -380.946 -7.553 0.377 7.557 9.409 12.049 15.110 390.355 60.904 -9.147 ms -5.909 36.08

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

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

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

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



Server 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 -57.546 -12.749 10.012 13.457 18.384 35.796 26.206 75.930 11.475 7.299 ms -4.83 32.47

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

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

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

Clock 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 -83.037 -36.507 -11.565 2.520 5.983 10.171 17.475 17.548 46.677 8.296 0.606 ms -4.951 36.87

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

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

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

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



Server Offset 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 -64.543 -42.814 -4.024 6.089 6.346 6.346 48.903 70.890 17.573 -11.460 ms -1.667 4.99

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

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

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

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



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) -270.192 -160.598 -157.441 -146.914 -132.903 -128.984 1,345.558 24.538 31.614 15.103 -145.701 ms 54.12 4427

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) -741.259 -7.604 -6.598 -2.751 0.063 0.310 1,996.886 6.661 7.914 15.832 -2.822 ms 84.78 9257

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) -10.997 -6.973 -6.670 -5.768 -2.715 -0.986 1.134 3.955 5.986 1.216 -5.481 ms 1.834 7.08

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 1.028 4.212 12.495 17.482 17.517 11.467 17.482 3.589 5.160 ms 1.325 5.087

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

Closer to 0s 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.770 1.016 3.771 15.346 20.390 23.932 14.330 19.620 4.525 5.360 ms 1.395 4.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 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 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 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 0.000 9.662 23.578 40.347 63.043 70.631 30.685 63.043 10.333 24.153 ms 0.9429 6.608

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

Closer to 0s 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.787 1.202 4.977 26.490 37.783 47.502 25.288 36.996 8.507 8.354 ms 1.963 7.148

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

Closer to 0s 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.202 33.553 33.553 33.553 33.553 33.553 7.428 4.893 ms 2.967 11.73

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 87.784 111.447 111.447 111.447 111.447 111.447 49.774 49.877 ms 0.05641 1.077

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

Closer to 0s 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.646 1.304 4.048 20.845 217.349 311.298 19.541 216.704 34.258 10.540 ms 6.577 47.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 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 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 1.937 5.393 14.159 15.551 15.551 12.222 15.551 4.000 6.455 ms 0.6547 2.36

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

Closer to 0s 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.122 3.430 13.171 65.088 74.406 12.049 65.088 9.017 5.668 ms 5.298 35.12

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 0.000 1.415 3.990 29.831 73.702 73.702 28.416 73.702 13.521 7.418 ms 3.962 17.64

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

Closer to 0s 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.557 0.932 3.234 9.816 16.282 21.738 8.884 15.725 3.019 4.004 ms 2.005 8.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 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 2.350 45.058 45.058 45.058 45.058 45.058 11.437 6.580 ms 2.59 8.731

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

Closer to 0s 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.676 2.978 7.651 10.149 15.209 6.975 10.149 2.215 3.213 ms 2.162 10.89

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

Closer to 0s 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.195 3.534 14.139 36.292 45.935 12.944 36.292 5.374 4.797 ms 4.66 30.8

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.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 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.000 0.910 2.839 12.056 56.163 57.472 11.146 56.163 7.201 5.030 ms 4.95 33.37

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

Closer to 0s 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.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 3.309 477.649 477.649 477.649 477.649 477.649 136.857 94.670 ms 1.361 3.969

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

Closer to 0s 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 1.365 4.096 9.848 14.966 20.475 8.483 14.966 3.089 4.974 ms 1.756 8.373

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

Closer to 0s 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.355 3.807 36.038 38.858 42.878 35.683 38.858 8.769 7.004 ms 2.59 9.493

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

Closer to 0s 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.751 1.062 3.032 13.301 21.797 56.769 12.239 21.046 4.518 4.267 ms 4.171 29.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 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 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.526 1.143 4.938 36.964 58.153 64.983 35.821 57.627 11.355 9.946 ms 2.174 8.518

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

Closer to 0s 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 38.308 75.329 198.429 206.604 74.820 198.429 31.494 40.888 ms 2.51 12.98

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

Closer to 0s 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.769 1.190 3.375 13.657 28.824 201.946 12.467 28.055 7.709 5.009 ms 12.28 244.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 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.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.000 0.999 3.685 17.434 36.558 41.450 16.435 36.558 6.279 5.702 ms 2.802 13.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 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: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: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: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.436 3.838 37.772 90.348 105.714 240.582 86.510 104.278 28.059 40.799 ms 0.6487 3.886

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

Closer to 0s 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 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.823 1.081 3.604 16.507 38.097 76.463 15.426 37.274 7.026 5.533 ms 5.352 44.93

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.118 3.126 13.486 18.864 19.152 12.368 18.864 3.617 4.133 ms 2.295 8.497

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

Closer to 0s 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 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.678 1.247 4.410 17.771 23.569 38.418 16.524 22.891 5.711 6.607 ms 1.451 5.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 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 3.254 197.363 223.573 223.573 197.363 223.573 68.309 34.794 ms 1.845 4.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 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.795 1.447 9.664 37.263 50.390 61.594 35.816 49.594 10.889 12.301 ms 1.653 6.272

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

Closer to 0s 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 8.473 43.359 78.056 98.879 152.099 69.583 98.879 20.762 44.089 ms 0.5614 5.322

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

Closer to 0s 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.755 1.178 3.460 13.815 20.461 28.697 12.636 19.706 4.025 4.652 ms 2.4 9.887

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

Closer to 0s 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.896 1.257 3.701 12.303 22.188 43.613 11.046 21.293 4.414 4.844 ms 3.728 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 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.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.000 0.000 2.030 4.367 4.367 4.367 4.367 4.367 1.236 2.254 ms 0.1072 2.316

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.129

peer jitter 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.129 0.000 0.000 0.000 7.981 281.407 281.407 281.407 281.407 281.407 78.460 53.363 ms 1.575 4.529

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

Closer to 0s 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.949 8.358 8.358 8.358 8.358 8.358 3.003 4.343 ms 0.1799 1.702

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

Closer to 0s 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.768 1.232 3.180 8.166 19.139 28.348 6.934 18.371 3.378 3.859 ms 4.121 25.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 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 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 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 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 2.193 4.795 27.751 62.461 73.954 88.695 57.666 71.761 18.437 30.041 ms 0.4639 2.354

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

Closer to 0s 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 2.380 4.629 32.546 76.538 100.413 260.324 71.909 98.033 23.487 35.320 ms 0.9762 5.764

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

Closer to 0s 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.089 3.092 3.092 3.092 3.092 3.092 1.306 2.255 ms -1.134 2.316

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

Closer to 0s 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 1.432 1.745 11.133 68.106 87.579 97.607 66.361 86.148 21.760 20.073 ms 1.557 4.724

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 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 8.025 10.608 10.608 10.608 10.608 10.608 3.670 6.974 ms -1.137 2.823

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

Closer to 0s 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.898 4.724 29.347 76.342 100.140 530.168 71.618 98.242 28.079 33.847 ms 5.288 77.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:4f8:c012:1afb:123:123:123:123 (tock.telnet.li)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:4f8:c012:1afb:123:123:123:123 (tock.telnet.li) 0.000 2.107 4.538 29.415 67.555 89.560 458.532 63.018 87.453 23.919 32.258 ms 4.77 70.42

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a01:4f9:c013:fa27:123:123:123:123

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:4f9:c013:fa27:123:123:123:123 0.000 2.267 4.256 36.707 88.465 105.507 178.690 84.209 103.240 27.722 39.531 ms 0.6325 3.112

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

Closer to 0s 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 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.000 18.567 51.344 92.831 102.838 108.993 74.264 102.838 23.085 54.142 ms 0.002413 2.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 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.500 1.086 2.883 8.779 20.149 30.738 7.693 19.650 3.133 3.695 ms 3.896 25.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 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.000 0.831 2.773 8.887 22.246 22.246 8.055 22.246 3.687 3.743 ms 2.963 14.62

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

Closer to 0s 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.000 0.000 1.227 11.524 11.524 11.524 11.524 11.524 3.176 2.245 ms 1.972 6.191

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

Closer to 0s 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.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.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.710 3.258 22.835 29.378 30.209 22.125 29.378 8.114 8.046 ms 1.002 2.77

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

Closer to 0s 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 1.605 10.036 31.573 43.704 46.371 29.968 43.704 9.984 12.026 ms 1.256 4.602

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

Closer to 0s 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.713 1.057 3.022 15.578 21.479 24.923 14.521 20.766 4.163 4.325 ms 2.659 10.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 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 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.239 8.881 15.286 19.717 8.019 15.286 2.933 3.202 ms 2.506 10.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 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 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 2.269 16.515 24.928 27.666 29.296 22.659 27.666 6.224 15.665 ms -0.5925 3.057

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

Closer to 0s 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 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.605 2.607 7.822 13.480 13.480 7.218 13.480 2.890 3.838 ms 0.9825 3.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 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.000 1.076 5.134 58.522 61.483 80.745 57.446 61.483 16.461 10.395 ms 2.601 8.451

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

Closer to 0s 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.523 38.651 83.096 108.261 137.030 80.573 108.261 25.905 40.537 ms 0.3753 2.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 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.000 2.842 34.892 82.286 96.957 116.085 79.444 96.957 25.467 36.824 ms 0.4446 2.341

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

Closer to 0s 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.000 0.000 39.014 56.934 61.519 61.519 56.934 61.519 18.688 32.853 ms -0.5671 2.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 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 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.



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.586 0.872 2.207 5.424 7.439 1,615.750 4.552 6.854 15.186 2.830 ms 68.63 5469

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.156 0.199 0.313 0.519 0.808 1,591.279 0.320 0.652 14.028 0.581 ms 74.07 6290

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.137 0.185 0.339 0.739 1.218 10.303 0.554 1.081 0.280 0.394 ms 12.24 312.7

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 -88.630 -83.152 11.136 15.704 22.341 23.478 135.754 11.206 106.629 16.089 14.137 ppm -5.38 32.99
Local Clock Time Offset -126.620 -7.401 -6.560 -2.888 0.278 1.450 121.205 6.838 8.851 3.163 -3.129 ms 0.6265 299.9
Local RMS Frequency Jitter 0.0000 0.0048 0.0057 0.125 0.614 1.532 65.989 0.608 1.528 1.430 0.292 ppm 23.39 677
Local RMS Time Jitter 0.000 0.245 0.289 0.386 0.614 4.010 83.702 0.326 3.765 2.124 0.587 ms 21.67 567
Refclock Offset SHM(0) -270.192 -160.598 -157.441 -146.914 -132.903 -128.984 1,345.558 24.538 31.614 15.103 -145.701 ms 54.12 4427
Refclock Offset SHM(1) -741.259 -7.604 -6.598 -2.751 0.063 0.310 1,996.886 6.661 7.914 15.832 -2.822 ms 84.78 9257
Refclock Offset SOCK(1) -10.997 -6.973 -6.670 -5.768 -2.715 -0.986 1.134 3.955 5.986 1.216 -5.481 ms 1.834 7.08
Refclock RMS Jitter SHM(0) 0.000 0.586 0.872 2.207 5.424 7.439 1,615.750 4.552 6.854 15.186 2.830 ms 68.63 5469
Refclock RMS Jitter SHM(1) 0.000 0.156 0.199 0.313 0.519 0.808 1,591.279 0.320 0.652 14.028 0.581 ms 74.07 6290
Refclock RMS Jitter SOCK(1) 0.000 0.137 0.185 0.339 0.739 1.218 10.303 0.554 1.081 0.280 0.394 ms 12.24 312.7
Server Jitter 104.131.155.175 0.000 0.000 1.028 4.212 12.495 17.482 17.517 11.467 17.482 3.589 5.160 ms 1.325 5.087
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.770 1.016 3.771 15.346 20.390 23.932 14.330 19.620 4.525 5.360 ms 1.395 4.627
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 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 139.84.137.244 0.000 0.000 9.662 23.578 40.347 63.043 70.631 30.685 63.043 10.333 24.153 ms 0.9429 6.608
Server Jitter 141.11.89.193 0.000 0.787 1.202 4.977 26.490 37.783 47.502 25.288 36.996 8.507 8.354 ms 1.963 7.148
Server Jitter 142.202.190.19 0.000 0.000 0.000 2.202 33.553 33.553 33.553 33.553 33.553 7.428 4.893 ms 2.967 11.73
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 87.784 111.447 111.447 111.447 111.447 111.447 49.774 49.877 ms 0.05641 1.077
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.646 1.304 4.048 20.845 217.349 311.298 19.541 216.704 34.258 10.540 ms 6.577 47.59
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 149.248.12.167 0.000 0.000 1.937 5.393 14.159 15.551 15.551 12.222 15.551 4.000 6.455 ms 0.6547 2.36
Server Jitter 149.28.200.179 0.000 0.000 1.122 3.430 13.171 65.088 74.406 12.049 65.088 9.017 5.668 ms 5.298 35.12
Server Jitter 151.236.20.166 0.000 0.000 1.415 3.990 29.831 73.702 73.702 28.416 73.702 13.521 7.418 ms 3.962 17.64
Server Jitter 155.248.196.28 0.000 0.557 0.932 3.234 9.816 16.282 21.738 8.884 15.725 3.019 4.004 ms 2.005 8.97
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 2.350 45.058 45.058 45.058 45.058 45.058 11.437 6.580 ms 2.59 8.731
Server Jitter 162.159.200.1 0.000 0.000 0.676 2.978 7.651 10.149 15.209 6.975 10.149 2.215 3.213 ms 2.162 10.89
Server Jitter 162.159.200.123 0.000 0.000 1.195 3.534 14.139 36.292 45.935 12.944 36.292 5.374 4.797 ms 4.66 30.8
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 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.000 0.910 2.839 12.056 56.163 57.472 11.146 56.163 7.201 5.030 ms 4.95 33.37
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.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 3.309 477.649 477.649 477.649 477.649 477.649 136.857 94.670 ms 1.361 3.969
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 1.365 4.096 9.848 14.966 20.475 8.483 14.966 3.089 4.974 ms 1.756 8.373
Server Jitter 172.234.37.140 0.000 0.000 0.355 3.807 36.038 38.858 42.878 35.683 38.858 8.769 7.004 ms 2.59 9.493
Server Jitter 172.235.60.8 0.000 0.751 1.062 3.032 13.301 21.797 56.769 12.239 21.046 4.518 4.267 ms 4.171 29.55
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 178.156.185.92 0.000 0.526 1.143 4.938 36.964 58.153 64.983 35.821 57.627 11.355 9.946 ms 2.174 8.518
Server Jitter 185.234.20.134 0.000 0.000 0.508 38.308 75.329 198.429 206.604 74.820 198.429 31.494 40.888 ms 2.51 12.98
Server Jitter 194.0.5.123 0.000 0.769 1.190 3.375 13.657 28.824 201.946 12.467 28.055 7.709 5.009 ms 12.28 244.8
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.46.254.130 0.000 0.000 0.999 3.685 17.434 36.558 41.450 16.435 36.558 6.279 5.702 ms 2.802 13.08
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: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: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:678:8::123 (any.time.nl) 0.000 1.436 3.838 37.772 90.348 105.714 240.582 86.510 104.278 28.059 40.799 ms 0.6487 3.886
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 209.177.158.85 0.000 0.823 1.081 3.604 16.507 38.097 76.463 15.426 37.274 7.026 5.533 ms 5.352 44.93
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.118 3.126 13.486 18.864 19.152 12.368 18.864 3.617 4.133 ms 2.295 8.497
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 23.142.248.8 0.000 0.678 1.247 4.410 17.771 23.569 38.418 16.524 22.891 5.711 6.607 ms 1.451 5.734
Server Jitter 23.142.248.9 0.000 0.000 0.000 3.254 197.363 223.573 223.573 197.363 223.573 68.309 34.794 ms 1.845 4.635
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.795 1.447 9.664 37.263 50.390 61.594 35.816 49.594 10.889 12.301 ms 1.653 6.272
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 8.473 43.359 78.056 98.879 152.099 69.583 98.879 20.762 44.089 ms 0.5614 5.322
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.755 1.178 3.460 13.815 20.461 28.697 12.636 19.706 4.025 4.652 ms 2.4 9.887
Server Jitter 23.186.168.125 0.000 0.896 1.257 3.701 12.303 22.188 43.613 11.046 21.293 4.414 4.844 ms 3.728 24
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.128 0.000 0.000 0.000 2.030 4.367 4.367 4.367 4.367 4.367 1.236 2.254 ms 0.1072 2.316
Server Jitter 23.186.168.129 0.000 0.000 0.000 7.981 281.407 281.407 281.407 281.407 281.407 78.460 53.363 ms 1.575 4.529
Server Jitter 23.186.168.130 0.000 0.000 0.000 3.949 8.358 8.358 8.358 8.358 8.358 3.003 4.343 ms 0.1799 1.702
Server Jitter 23.186.168.132 0.000 0.768 1.232 3.180 8.166 19.139 28.348 6.934 18.371 3.378 3.859 ms 4.121 25.48
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 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) 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 2402:1f00:8101:d6::1 0.000 2.193 4.795 27.751 62.461 73.954 88.695 57.666 71.761 18.437 30.041 ms 0.4639 2.354
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 2.380 4.629 32.546 76.538 100.413 260.324 71.909 98.033 23.487 35.320 ms 0.9762 5.764
Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) 0.000 0.000 0.000 3.089 3.092 3.092 3.092 3.092 3.092 1.306 2.255 ms -1.134 2.316
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 1.432 1.745 11.133 68.106 87.579 97.607 66.361 86.148 21.760 20.073 ms 1.557 4.724
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 2607:9000:7000:23:216:3cff:fe25:38d7 0.000 0.000 0.000 8.025 10.608 10.608 10.608 10.608 10.608 3.670 6.974 ms -1.137 2.823
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.000 1.898 4.724 29.347 76.342 100.140 530.168 71.618 98.242 28.079 33.847 ms 5.288 77.58
Server Jitter 2a01:4f8:c012:1afb:123:123:123:123 (tock.telnet.li) 0.000 2.107 4.538 29.415 67.555 89.560 458.532 63.018 87.453 23.919 32.258 ms 4.77 70.42
Server Jitter 2a01:4f9:c013:fa27:123:123:123:123 0.000 2.267 4.256 36.707 88.465 105.507 178.690 84.209 103.240 27.722 39.531 ms 0.6325 3.112
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 34.147.28.4 0.000 0.000 18.567 51.344 92.831 102.838 108.993 74.264 102.838 23.085 54.142 ms 0.002413 2.577
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.500 1.086 2.883 8.779 20.149 30.738 7.693 19.650 3.133 3.695 ms 3.896 25.97
Server Jitter 45.33.53.84 0.000 0.000 0.831 2.773 8.887 22.246 22.246 8.055 22.246 3.687 3.743 ms 2.963 14.62
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.000 0.000 1.227 11.524 11.524 11.524 11.524 11.524 3.176 2.245 ms 1.972 6.191
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.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.95 0.000 0.000 0.710 3.258 22.835 29.378 30.209 22.125 29.378 8.114 8.046 ms 1.002 2.77
Server Jitter 50.218.103.254 0.000 0.000 1.605 10.036 31.573 43.704 46.371 29.968 43.704 9.984 12.026 ms 1.256 4.602
Server Jitter 51.81.226.229 0.000 0.713 1.057 3.022 15.578 21.479 24.923 14.521 20.766 4.163 4.325 ms 2.659 10.38
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 65.182.224.39 0.000 0.000 0.862 2.239 8.881 15.286 19.717 8.019 15.286 2.933 3.202 ms 2.506 10.58
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 67.217.246.204 0.000 0.000 2.269 16.515 24.928 27.666 29.296 22.659 27.666 6.224 15.665 ms -0.5925 3.057
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 72.14.186.59 0.000 0.000 0.605 2.607 7.822 13.480 13.480 7.218 13.480 2.890 3.838 ms 0.9825 3.827
Server Jitter 73.185.182.209 0.000 0.000 1.076 5.134 58.522 61.483 80.745 57.446 61.483 16.461 10.395 ms 2.601 8.451
Server Jitter 77.37.97.124 0.000 0.000 2.523 38.651 83.096 108.261 137.030 80.573 108.261 25.905 40.537 ms 0.3753 2.57
Server Jitter 77.42.37.85 0.000 0.000 2.842 34.892 82.286 96.957 116.085 79.444 96.957 25.467 36.824 ms 0.4446 2.341
Server Jitter 79.160.225.13 0.000 0.000 0.000 39.014 56.934 61.519 61.519 56.934 61.519 18.688 32.853 ms -0.5671 2.169
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 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 Offset 104.131.155.175 -9.978 -9.873 -7.869 1.310 6.960 13.031 14.937 14.829 22.904 4.061 1.075 ms 0.02473 4.904
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 -4.792 -2.272 0.549 3.917 6.211 7.860 9.035 5.662 10.132 1.761 3.664 ms -0.7761 5.096
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 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 139.84.137.244 -76.084 -67.500 -35.019 10.925 22.560 26.652 28.254 57.579 94.152 17.944 5.833 ms -2.35 9.18
Server Offset 141.11.89.193 -5.133 -3.834 -2.747 0.158 3.794 5.235 7.287 6.541 9.069 2.065 0.422 ms 0.2609 2.767
Server Offset 142.202.190.19 -2.514 -2.514 -2.514 0.562 4.040 4.040 4.040 6.554 6.554 1.834 0.714 ms 0.1866 2.03
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 -0.542 1.509 1.509 1.509 114.106 114.106 56.383 -55.610 ms 0.0001555 1.001
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.521 1.466 5.257 7.006 9.284 6.778 11.215 30.798 -1.308 ms -10.76 120.7
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 149.248.12.167 -8.248 -8.248 -5.145 2.102 8.205 12.647 12.647 13.350 20.895 4.129 1.825 ms 0.01569 3.465
Server Offset 149.28.200.179 -88.226 -86.256 -9.082 0.956 6.594 11.091 14.392 15.676 97.347 10.098 -0.378 ms -7.006 59.74
Server Offset 151.236.20.166 -5.683 -5.683 -1.383 3.425 7.083 10.113 10.113 8.466 15.796 2.756 3.058 ms -0.2133 3.428
Server Offset 155.248.196.28 -7.263 -4.833 -2.819 0.165 4.387 7.586 11.821 7.206 12.418 2.280 0.522 ms 0.7525 5.003
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 -41.684 -41.684 -41.684 0.979 5.849 5.849 5.849 47.534 47.534 11.216 -2.520 ms -2.785 9.976
Server Offset 162.159.200.1 -6.317 -5.539 -2.005 1.526 6.070 6.509 14.827 8.075 12.049 2.947 1.865 ms 0.5047 5.56
Server Offset 162.159.200.123 -5.100 -3.554 -1.544 5.409 8.497 10.316 40.107 10.040 13.870 3.641 4.692 ms 2.367 29.19
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 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 1.026 1.199 3.846 6.744 9.809 11.373 12.448 5.963 10.174 1.897 6.818 ms -0.2684 3.74
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.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 6.078 6.078 6.078 10.698 725.734 725.734 725.734 719.656 719.656 210.967 132.036 ms 1.564 4.219
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 -1.613 7.945 13.980 16.005 16.638 15.592 393.281 71.028 -5.439 ms -5.005 26.14
Server Offset 172.234.37.140 -384.852 -382.248 -18.988 -1.211 4.187 5.631 9.952 23.175 387.879 58.312 -11.645 ms -6.113 38.82
Server Offset 172.235.60.8 -4.609 -2.609 -1.288 1.945 6.837 7.903 9.759 8.125 10.511 2.398 2.368 ms 0.4168 2.916
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 178.156.185.92 -11.713 -8.831 -4.179 -0.706 3.017 6.942 13.785 7.195 15.773 2.556 -0.678 ms -0.01569 7.164
Server Offset 185.234.20.134 -207.966 -206.319 6.959 42.992 55.729 222.373 228.892 48.770 428.693 46.172 38.514 ms -0.7618 19.3
Server Offset 194.0.5.123 -452.715 -8.424 -3.585 3.117 7.269 10.673 38.968 10.853 19.098 12.506 2.400 ms -32.54 1181
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.46.254.130 -11.109 -10.105 -8.900 -0.000 6.524 48.594 50.250 15.424 58.699 6.597 0.210 ms 4.556 35.9
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: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: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:678:8::123 (any.time.nl) -421.375 -31.977 -15.406 -7.172 -3.482 0.045 589.234 11.924 32.022 19.880 -7.890 ms 12.14 684.3
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 209.177.158.85 -30.375 -5.273 -3.659 -0.342 2.300 6.493 15.829 5.958 11.766 2.914 -0.447 ms -3.653 46.66
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.727 3.365 13.045 13.185 12.689 24.960 3.711 -1.195 ms -0.3257 7.429
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 23.142.248.8 5.217 6.311 7.730 10.986 13.253 14.647 15.979 5.523 8.336 1.615 10.885 ms -0.5224 3.944
Server Offset 23.142.248.9 -263.459 -263.459 -262.784 -2.992 167.935 168.098 168.098 430.720 431.557 109.223 -10.313 ms -0.5237 3.918
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 2.498 3.818 5.315 9.059 11.720 17.772 29.911 6.405 13.955 2.354 9.042 ms 2.282 20.79
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 -120.099 -96.843 -75.901 -8.718 9.325 14.069 24.574 85.226 110.912 26.011 -16.573 ms -1.394 4.486
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 -11.785 -6.413 1.295 4.250 5.852 24.970 10.663 17.637 3.731 0.148 ms -0.8055 6.081
Server Offset 23.186.168.125 -336.573 -3.098 -1.585 2.037 4.140 5.172 21.753 5.725 8.270 16.559 0.943 ms -19.9 402
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.128 -6.268 -6.268 -6.268 -2.041 1.676 1.676 1.676 7.944 7.944 2.335 -1.348 ms -0.4703 2.407
Server Offset 23.186.168.129 -94.054 -94.054 -93.816 -1.602 282.002 282.002 282.002 375.818 376.056 70.236 1.009 ms 2.948 13.15
Server Offset 23.186.168.130 -5.129 -5.129 -5.129 -3.084 -1.667 -1.667 -1.667 3.462 3.462 1.214 -3.305 ms -0.01898 1.693
Server Offset 23.186.168.132 -9.048 -8.170 -7.030 -3.318 -1.756 -0.801 -0.358 5.274 7.370 1.536 -3.601 ms -1.052 4.19
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 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) 685.845 685.845 685.845 685.845 685.845 685.845 685.845 0.000 0.000 0.000 685.845 ms nan nan
Server Offset 2402:1f00:8101:d6::1 -35.696 -13.455 6.013 26.982 33.757 37.961 52.890 27.744 51.416 9.367 24.013 ms -1.968 8.857
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) -78.408 -38.587 -25.758 2.891 8.850 15.203 312.713 34.608 53.791 13.226 -2.555 ms 3.114 94.55
Server Offset 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) 0.258 0.258 0.258 0.748 3.016 3.016 3.016 2.759 2.759 1.122 1.099 ms 1.068 2.259
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.585 16.789 20.179 20.349 12.082 21.539 4.146 9.944 ms -0.6706 8.562
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 2607:9000:7000:23:216:3cff:fe25:38d7 -7.438 -7.438 -7.438 -3.494 6.995 6.995 6.995 14.433 14.433 4.803 -1.951 ms 0.9793 2.753
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) -573.994 -24.432 -11.353 -0.211 6.538 22.187 70.769 17.890 46.619 14.096 -0.800 ms -23.27 852.5
Server Offset 2a01:4f8:c012:1afb:123:123:123:123 (tock.telnet.li) -662.197 -43.394 -29.960 -14.733 -7.976 -0.161 153.523 21.984 43.233 17.808 -15.749 ms -19.9 818.3
Server Offset 2a01:4f9:c013:fa27:123:123:123:123 -74.656 -27.333 -9.959 1.200 5.509 11.828 152.944 15.468 39.161 10.688 0.396 ms 7.092 119.6
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 34.147.28.4 -129.797 -97.451 -53.266 -8.090 4.141 9.142 11.849 57.407 106.593 21.047 -13.839 ms -2.49 10.74
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 -7.144 -5.890 -3.383 0.473 2.586 3.398 3.924 5.969 9.288 1.795 0.182 ms -1.014 4.359
Server Offset 45.33.53.84 -1.368 -1.368 -1.281 3.720 5.707 6.732 6.732 6.988 8.101 1.980 3.475 ms -0.9176 3.305
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 -3.611 -3.611 -3.611 3.279 5.849 5.849 5.849 9.461 9.461 2.672 2.213 ms -0.5509 2.573
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.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.95 -13.393 -13.270 -8.900 -1.296 1.731 4.497 6.235 10.631 17.767 3.214 -1.929 ms -1.378 5.671
Server Offset 50.218.103.254 -39.877 -17.266 -8.068 0.775 5.720 46.263 49.954 13.788 63.530 7.440 0.730 ms 2.027 26.4
Server Offset 51.81.226.229 -3.807 -1.522 1.150 5.163 7.606 8.830 11.602 6.456 10.352 1.992 4.926 ms -0.7831 4.9
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 65.182.224.39 -19.040 -5.987 -1.484 1.519 6.164 11.148 17.628 7.648 17.136 3.038 1.696 ms -0.02657 18.42
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 67.217.246.204 -28.602 -25.457 -6.819 -1.820 0.412 2.488 4.396 7.232 27.945 4.227 -2.713 ms -3.881 21.04
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 72.14.186.59 -10.962 -10.962 -6.498 5.272 7.467 8.444 8.444 13.965 19.405 4.884 3.065 ms -1.172 3.134
Server Offset 73.185.182.209 -385.027 -380.946 -7.553 0.377 7.557 9.409 12.049 15.110 390.355 60.904 -9.147 ms -5.909 36.08
Server Offset 77.37.97.124 -93.402 -57.546 -12.749 10.012 13.457 18.384 35.796 26.206 75.930 11.475 7.299 ms -4.83 32.47
Server Offset 77.42.37.85 -83.037 -36.507 -11.565 2.520 5.983 10.171 17.475 17.548 46.677 8.296 0.606 ms -4.951 36.87
Server Offset 79.160.225.13 -64.543 -64.543 -42.814 -4.024 6.089 6.346 6.346 48.903 70.890 17.573 -11.460 ms -1.667 4.99
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 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
TDOP 0.450 0.510 0.570 0.780 1.240 1.650 3.610 0.670 1.140 0.228 0.827 2.589 18.85
Temp /dev/sda 18.000 20.000 20.000 25.000 26.000 28.000 29.000 6.000 8.000 2.249 24.237 °C
Temp LM0 31.000 32.000 34.000 37.000 40.000 42.000 59.000 6.000 10.000 1.976 37.060 °C
Temp LM1 29.000 30.000 31.000 34.000 37.000 38.000 42.000 6.000 8.000 1.950 34.142 °C
Temp LM2 26.000 26.000 34.000 38.000 40.000 41.000 45.000 6.000 15.000 2.500 37.587 °C
Temp LM3 0.000 0.000 3.000 3.000 40.000 41.000 42.000 37.000 41.000 17.802 16.868 °C
Temp LM4 0.000 0.000 0.000 32.000 39.000 41.000 51.000 39.000 41.000 17.144 21.536 °C
Temp LM5 29.000 29.000 30.000 33.000 38.000 38.000 38.000 8.000 9.000 2.910 33.627 °C
Temp LM6 31.000 32.000 33.000 34.000 37.000 37.000 44.000 4.000 5.000 1.209 34.391 °C
Temp LM7 32.000 34.000 34.000 36.000 38.000 39.000 45.000 4.000 5.000 1.236 36.004 °C
Temp LM8 26.800 26.800 34.000 36.000 38.000 39.000 45.000 4.000 12.200 1.855 35.948 °C
Temp LM9 26.800 26.800 34.000 36.000 38.000 39.000 45.000 4.000 12.200 1.855 35.948 °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 26.800 34.000 36.000 38.000 38.000 45.000 4.000 11.200 1.760 35.396 °C
Temp ZONE2 29.000 29.000 34.000 37.000 38.000 38.000 38.000 4.000 9.000 1.610 36.654 °C
Temp ZONE3 32.000 34.000 34.000 36.000 38.000 38.000 45.000 4.000 4.000 1.202 35.562 °C
Temp ZONE4 26.800 26.800 34.000 36.000 38.000 38.000 45.000 4.000 11.200 1.760 35.396 °C
Temp ZONE5 30.000 31.000 32.000 36.000 41.000 43.000 58.000 9.000 12.000 3.077 35.975 °C
Temp ZONE6 29.000 30.000 30.000 32.000 34.000 34.000 38.000 4.000 4.000 1.051 31.919 °C
nSats 8.000 10.000 11.000 13.000 17.000 19.000 21.000 6.000 9.000 1.918 13.625 nSat 0.4589 2.864
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!