NTPsec

Dell-2018

Report generated: Sun Jan 18 23:20:55 2026 UTC
Start Time: Thu Jan 9 23:20:09 2025 UTC
End Time: Sun Jan 18 23:20:09 2026 UTC
Report Period: 374.0 days

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

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -95.988 -8.033 -4.963 -0.058 0.658 1.157 105.238 5.620 9.191 1.903 -0.585 ms -0.027 219.6
Local Clock Frequency Offset -135.511 2.905 4.604 11.075 21.876 25.051 61.826 17.272 22.146 4.617 11.846 ppm 0.8242 7.031

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.092 0.113 0.293 0.856 1.353 52.058 0.743 1.260 0.494 0.367 ms 43.07 3124

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.0033 0.0041 0.0162 2.670 3.670 73.177 2.666 3.666 0.960 0.524 ppm 8.769 418.7

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 -95.988 -8.033 -4.963 -0.058 0.658 1.157 105.238 5.620 9.191 1.903 -0.585 ms -0.027 219.6

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -135.511 2.905 4.604 11.075 21.876 25.051 61.826 17.272 22.146 4.617 11.846 ppm 0.8242 7.031
Temp /dev/sda 15.000 18.000 20.000 25.000 26.000 28.000 39.000 6.000 10.000 2.432 23.827 °C
Temp LM0 28.000 30.000 31.000 34.000 41.000 45.000 54.000 10.000 15.000 2.918 34.183 °C
Temp LM1 26.000 28.000 29.000 38.000 39.000 40.000 44.000 10.000 12.000 3.173 36.382 °C
Temp LM2 0.000 0.000 0.000 19.000 34.000 34.000 51.000 34.000 34.000 7.234 20.217 °C
Temp LM3 24.000 26.000 27.000 30.000 38.000 39.000 46.000 11.000 13.000 3.200 31.060 °C
Temp LM4 0.000 0.000 0.000 32.000 41.000 44.000 56.000 41.000 44.000 12.823 28.355 °C
Temp LM5 24.000 26.000 27.000 30.000 32.000 32.000 45.000 5.000 6.000 1.441 29.777 °C
Temp LM6 26.000 28.000 29.000 32.000 34.000 38.000 50.000 5.000 10.000 1.715 32.151 °C
Temp LM7 28.000 30.000 31.000 34.000 36.000 39.000 51.000 5.000 9.000 1.673 33.987 °C
Temp LM8 28.000 31.000 32.000 35.000 37.000 39.000 51.000 5.000 8.000 1.666 34.321 °C
Temp LM9 28.000 31.000 32.000 35.000 37.000 39.000 51.000 5.000 8.000 1.666 34.320 °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 28.000 30.000 31.000 34.000 36.000 39.000 51.000 5.000 9.000 1.703 33.436 °C
Temp ZONE2 24.000 26.000 27.000 30.000 32.000 32.000 45.000 5.000 6.000 1.440 29.777 °C
Temp ZONE3 28.000 30.000 31.000 34.000 36.000 39.000 51.000 5.000 9.000 1.705 33.442 °C
Temp ZONE4 28.000 30.000 31.000 34.000 36.000 39.000 51.000 5.000 9.000 1.703 33.436 °C
Temp ZONE5 27.000 29.000 30.000 32.000 42.000 47.000 56.000 12.000 18.000 4.177 34.415 °C
Temp ZONE6 24.000 26.000 27.000 30.000 32.000 34.000 44.000 5.000 8.000 1.493 29.784 °C

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

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



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 6.000 8.000 9.000 10.000 13.000 14.000 16.000 4.000 6.000 1.264 10.660 nSat 0.2722 3.549
TDOP 0.490 0.560 0.620 0.910 11.810 11.810 12.680 11.190 11.250 2.698 1.707 3.378 12.74

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 -2.525 -2.525 -1.209 5.368 12.615 16.334 16.334 13.824 18.859 4.610 5.570 ms 0.3612 2.585

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

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

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

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



Server Offset 104.152.220.5

peer offset 104.152.220.5 plot

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

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

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

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

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



Server Offset 104.167.215.195

peer offset 104.167.215.195 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.167.215.195 -419.941 -418.768 -10.695 1.453 14.053 18.705 19.868 24.748 437.473 64.209 -8.450 ms -5.837 36.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 104.167.241.253

peer offset 104.167.241.253 plot

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

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

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

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

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



Server Offset 104.234.61.117

peer offset 104.234.61.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.234.61.117 -21.499 -3.096 2.445 5.568 7.901 10.166 442.381 5.456 13.262 14.127 5.812 ms 29.9 919.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 108.61.56.35

peer offset 108.61.56.35 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 108.61.56.35 4.613 4.613 4.613 6.012 10.829 10.829 10.829 6.216 6.216 1.882 6.640 ms 0.9579 2.876

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

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

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

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



Server Offset 108.61.73.243

peer offset 108.61.73.243 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 108.61.73.243 -4.642 0.420 2.263 5.010 7.415 8.937 442.001 5.152 8.516 20.943 5.969 ms 20.48 423.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 12.71.198.242

peer offset 12.71.198.242 plot

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

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

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

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

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



Server Offset 129.146.193.200

peer offset 129.146.193.200 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 129.146.193.200 -0.800 0.856 1.586 4.877 7.695 10.932 11.567 6.109 10.076 1.776 4.758 ms 0.4134 5.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 131.153.171.250

peer offset 131.153.171.250 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 131.153.171.250 2.305 2.305 2.305 6.214 6.977 6.977 6.977 4.672 4.672 2.047 5.165 ms -0.6341 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 131.239.5.43

peer offset 131.239.5.43 plot

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

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

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

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

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



Server Offset 135.148.100.14

peer offset 135.148.100.14 plot

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

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

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

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

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



Server Offset 137.110.222.27

peer offset 137.110.222.27 plot

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

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

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

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

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



Server Offset 137.190.2.4

peer offset 137.190.2.4 plot

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

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

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

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

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



Server Offset 139.177.202.26

peer offset 139.177.202.26 plot

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

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

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

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

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



Server Offset 139.84.137.244

peer offset 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 139.84.137.244 -88.151 -16.767 -1.366 8.076 12.560 15.955 23.798 13.926 32.722 6.166 6.768 ms -4.604 49.76

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

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

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

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



Server Offset 139.94.144.123

peer offset 139.94.144.123 plot

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

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

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

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

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



Server Offset 141.11.234.198

peer offset 141.11.234.198 plot

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

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

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

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

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



Server Offset 141.11.89.193

peer offset 141.11.89.193 plot

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

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

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

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

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



Server Offset 142.202.190.19

peer offset 142.202.190.19 plot

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

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

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

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

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



Server Offset 144.202.0.197

peer offset 144.202.0.197 plot

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

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

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

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

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



Server Offset 144.202.66.214

peer offset 144.202.66.214 plot

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

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

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

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

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



Server Offset 148.163.226.148

peer offset 148.163.226.148 plot

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

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

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

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

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



Server Offset 149.248.12.167

peer offset 149.248.12.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.248.12.167 6.974 6.974 6.974 12.448 13.486 13.486 13.486 6.511 6.511 2.871 10.594 ms -0.3694 1.196

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

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

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

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



Server Offset 149.28.200.179

peer offset 149.28.200.179 plot

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

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

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

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

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



Server Offset 149.28.61.105

peer offset 149.28.61.105 plot

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

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

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

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

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



Server Offset 15.204.198.96

peer offset 15.204.198.96 plot

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

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

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

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

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



Server Offset 15.204.87.223

peer offset 15.204.87.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 15.204.87.223 -36.284 -8.344 -5.158 -1.169 2.341 163.102 164.832 7.498 171.447 20.085 0.950 ms 7.803 63.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 155.248.196.28

peer offset 155.248.196.28 plot

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

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

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

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

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



Server Offset 158.51.99.19

peer offset 158.51.99.19 plot

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

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

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

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

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



Server Offset 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -4.289 0.762 3.679 6.207 8.297 9.197 11.557 4.617 8.435 1.636 6.117 ms -1.454 10.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 162.159.200.123

peer offset 162.159.200.123 plot

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

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

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

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

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



Server Offset 163.123.152.14

peer offset 163.123.152.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 163.123.152.14 8.299 8.299 8.299 9.300 12.567 12.567 12.567 4.268 4.268 1.664 9.751 ms 0.9993 2.22

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

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

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

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



Server Offset 166.88.142.52

peer offset 166.88.142.52 plot

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

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

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

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

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



Server Offset 168.61.215.74

peer offset 168.61.215.74 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 168.61.215.74 -405.890 -405.890 -405.076 -2.880 13.022 14.954 14.954 418.098 420.844 173.388 -94.516 ms -1.224 2.507

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

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

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

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



Server Offset 170.187.147.56

peer offset 170.187.147.56 plot

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

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

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

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

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



Server Offset 172.233.153.85

peer offset 172.233.153.85 plot

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

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

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

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

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



Server Offset 172.233.157.223

peer offset 172.233.157.223 plot

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

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

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

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

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



Server Offset 172.233.177.198

peer offset 172.233.177.198 plot

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

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

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

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

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



Server Offset 172.234.25.10

peer offset 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.25.10 -0.488 -0.488 -0.488 3.459 5.884 5.884 5.884 6.372 6.372 2.046 2.970 ms -0.3216 1.683

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

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

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

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



Server Offset 172.234.37.140

peer offset 172.234.37.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.37.140 -9.587 -9.587 -9.587 4.151 11.157 11.157 11.157 20.745 20.745 4.913 3.204 ms -0.9547 3.843

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

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

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

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



Server Offset 172.234.44.141

peer offset 172.234.44.141 plot

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

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

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

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

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



Server Offset 172.235.60.8

peer offset 172.235.60.8 plot

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

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

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

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

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



Server Offset 172.98.15.13

peer offset 172.98.15.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.98.15.13 11.306 11.306 11.306 16.540 17.265 17.265 17.265 5.959 5.959 2.760 14.156 ms 0.02368 1.037

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

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

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

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



Server Offset 173.230.154.254

peer offset 173.230.154.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.230.154.254 -28.157 -28.157 -28.157 4.886 11.041 11.041 11.041 39.197 39.197 13.119 -0.101 ms -1.268 3.17

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

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

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

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



Server Offset 173.249.203.227

peer offset 173.249.203.227 plot

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

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

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

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

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



Server Offset 173.255.192.10

peer offset 173.255.192.10 plot

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

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

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

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

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



Server Offset 173.255.255.133

peer offset 173.255.255.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.255.255.133 -3.792 -2.842 -0.056 3.924 6.553 465.031 470.949 6.609 467.873 54.595 10.371 ms 8.207 68.45

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

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

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

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



Server Offset 173.71.68.71

peer offset 173.71.68.71 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.71.68.71 -11.013 -4.530 -1.040 3.562 6.711 464.728 470.128 7.750 469.258 52.893 9.423 ms 8.484 73.13

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

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

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

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



Server Offset 192.48.105.15

peer offset 192.48.105.15 plot

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

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

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

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

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



Server Offset 193.29.63.226

peer offset 193.29.63.226 plot

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

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

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

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

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



Server Offset 194.0.5.123

peer offset 194.0.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.0.5.123 -15.181 -4.944 -3.230 -0.145 2.272 3.945 14.812 5.502 8.890 1.763 -0.247 ms -0.2048 7.576

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

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

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

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



Server Offset 198.137.202.32

peer offset 198.137.202.32 plot

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

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

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

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

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



Server Offset 198.199.14.19

peer offset 198.199.14.19 plot

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

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

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

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

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



Server Offset 198.211.103.209

peer offset 198.211.103.209 plot

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

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

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

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

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



Server Offset 198.46.254.130

peer offset 198.46.254.130 plot

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

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

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

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

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



Server Offset 198.60.22.240

peer offset 198.60.22.240 plot

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

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

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

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

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



Server Offset 199.68.201.235

peer offset 199.68.201.235 plot

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

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

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

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

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



Server Offset 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net)

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

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

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

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

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

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



Server Offset 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com)

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

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

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

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

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

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



Server Offset 2001:19f0:6401:400:5400:4ff:fec3:522a

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:19f0:6401:400:5400:4ff:fec3:522a -7.451 -7.451 -7.451 2.889 10.062 10.062 10.062 17.513 17.513 3.931 2.476 ms -0.6439 4.347

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

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

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

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



Server Offset 2001:418:3ff::53 (x.ns.gin.ntt.net)

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

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

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

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

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

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



Server Offset 2001:418:8405:4002::12

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

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

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

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

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

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



Server Offset 2001:418:8405:4002::3

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:418:8405:4002::3 1.964 1.964 1.964 5.204 7.396 7.396 7.396 5.432 5.432 1.953 4.693 ms -0.01811 1.874

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

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

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

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



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

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

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

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

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

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

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



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

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

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

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

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

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

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



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

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

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

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

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

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

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



Server Offset 2001:470:e114::d6:12 (1.md.ntp.md)

peer offset 2001:470:e114::d6:12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e114::d6:12 (1.md.ntp.md) -10.323 -5.218 -0.737 4.529 7.577 464.586 465.594 8.315 469.804 60.950 12.283 ms 7.263 53.84

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

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

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

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



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

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e8dc:10::123 -0.028 0.001 0.004 0.006 0.009 0.011 589.091 0.005 0.010 20.006 0.687 s 29.38 864

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

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

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

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



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

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

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

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

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

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

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



Server Offset 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com) -0.195 -0.167 1.359 3.625 5.714 8.822 8.875 4.355 8.989 1.443 3.675 ms 0.4961 4.819

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

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

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

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



Server Offset 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com)

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

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

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

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

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

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



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

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

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

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

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

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

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



Server Offset 2001:559:2be:3::1001

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:559:2be:3::1001 -175.433 -175.433 -170.364 5.851 9.897 9.897 9.897 180.261 185.330 63.479 -23.583 ms -1.838 4.527

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

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

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

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



Server Offset 2001:678:8::123 (any.time.nl)

peer offset 2001:678:8::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:678:8::123 (any.time.nl) -77.912 -18.791 -10.478 -6.084 -2.852 0.862 214.705 7.626 19.654 7.324 -6.170 ms 22.59 690.6

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

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

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

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



Server Offset 204.197.163.71

peer offset 204.197.163.71 plot

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

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

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

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

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



Server Offset 204.2.134.162

peer offset 204.2.134.162 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.2.134.162 3.726 3.726 3.726 9.487 10.513 10.513 10.513 6.787 6.787 2.284 8.433 ms -0.8439 2.293

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

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

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

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



Server Offset 205.233.73.201

peer offset 205.233.73.201 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 205.233.73.201 -29.812 -29.812 -18.984 -11.710 221.908 221.908 221.908 240.892 251.721 117.212 88.651 ms 0.199 1.044

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

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

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

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



Server Offset 208.113.130.146

peer offset 208.113.130.146 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 208.113.130.146 -807.971 -2.044 0.597 5.657 8.325 10.241 17.688 7.728 12.286 41.081 3.296 ms -19.56 384.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 208.67.72.43

peer offset 208.67.72.43 plot

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

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

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

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

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



Server Offset 208.67.72.50

peer offset 208.67.72.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 208.67.72.50 -411.370 -407.370 -12.259 -1.276 14.804 461.290 467.446 27.063 868.660 105.580 8.636 ms 1.618 16.62

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

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

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

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



Server Offset 208.67.75.242

peer offset 208.67.75.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 208.67.75.242 -4.622 -0.573 1.079 4.378 7.071 10.826 240.553 5.992 11.398 17.431 5.561 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 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 0.447 1.002 2.373 4.942 6.721 7.313 9.204 4.348 6.310 1.337 4.781 ms -0.4751 3.423

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

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

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

Clock 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 -5.209 -5.209 -5.209 3.423 9.274 9.274 9.274 14.482 14.482 3.953 2.588 ms -0.1056 2.272

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

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

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

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



Server Offset 216.229.4.69

peer offset 216.229.4.69 plot

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

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

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

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

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



Server Offset 216.240.36.24

peer offset 216.240.36.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.240.36.24 -5.803 -5.803 -5.803 -0.195 2.710 2.710 2.710 8.513 8.513 2.260 -0.531 ms -0.9327 3.549

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

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

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

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

peer offset 216.31.17.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.31.17.12 -13.524 -13.524 -13.524 1.518 6.326 6.326 6.326 19.850 19.850 5.541 -1.109 ms -0.9513 3.269

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

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

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

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



Server Offset 23.111.186.186

peer offset 23.111.186.186 plot

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

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

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

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

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



Server Offset 23.131.160.7

peer offset 23.131.160.7 plot

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

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

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

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

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



Server Offset 23.141.40.123

peer offset 23.141.40.123 plot

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

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

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

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

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



Server Offset 23.142.248.8

peer offset 23.142.248.8 plot

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

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

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

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

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



Server Offset 23.142.248.9

peer offset 23.142.248.9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.142.248.9 -2.218 -2.218 -2.218 5.433 8.498 8.498 8.498 10.716 10.716 3.219 4.239 ms -0.3035 1.852

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

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

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

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



Server Offset 23.143.196.199

peer offset 23.143.196.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.143.196.199 2.248 2.248 2.248 3.906 5.387 5.387 5.387 3.139 3.139 1.032 4.058 ms -0.2914 2.021

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

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

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

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



Server Offset 23.150.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 -0.725 2.698 5.818 9.930 15.470 18.805 23.764 9.652 16.107 2.921 10.414 ms 0.547 5.963

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

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

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

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



Server Offset 23.155.40.38

peer offset 23.155.40.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.155.40.38 -288.208 -156.059 -4.815 1.534 4.285 10.104 18.366 9.100 166.163 22.289 -1.539 ms -9.379 102

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

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

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

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



Server Offset 23.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 7.914 7.914 7.914 12.589 13.467 13.467 13.467 5.553 5.553 2.207 10.952 ms -0.2124 1.412

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

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

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

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



Server Offset 23.186.168.123

peer offset 23.186.168.123 plot

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

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

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

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

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



Server Offset 23.186.168.126

peer offset 23.186.168.126 plot

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

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

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

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

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



Server Offset 23.186.168.127

peer offset 23.186.168.127 plot

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

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

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

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

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



Server Offset 23.186.168.128

peer offset 23.186.168.128 plot

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

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

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

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

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



Server Offset 23.186.168.129

peer offset 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.129 -23.022 -1.996 -0.428 2.998 5.842 7.926 423.814 6.270 9.922 13.136 3.517 ms 27.32 851.3

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

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

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

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



Server Offset 23.186.168.130

peer offset 23.186.168.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.130 -4.461 -4.461 -4.284 0.164 5.449 7.796 7.796 9.733 12.257 3.707 0.733 ms 0.06193 1.677

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

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

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

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



Server Offset 23.186.168.131

peer offset 23.186.168.131 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.131 -4.751 -0.429 1.142 3.700 5.655 6.700 10.070 4.513 7.129 1.408 3.624 ms -0.5634 5.686

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

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

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

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



Server Offset 23.186.168.132

peer offset 23.186.168.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.132 -6.108 -0.734 0.944 3.623 5.856 7.065 9.350 4.912 7.799 1.547 3.559 ms -0.388 4.285

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

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

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

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

peer offset 23.94.221.138 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.94.221.138 8.003 8.003 8.003 11.978 13.637 13.637 13.637 5.634 5.634 1.789 11.308 ms -0.8786 2.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.95.49.216

peer offset 23.95.49.216 plot

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

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

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

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

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



Server Offset 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) -70.714 -36.132 -21.035 -11.710 -3.560 28.115 38.393 17.475 64.247 8.624 -11.735 ms 1.342 14.51

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

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

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

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



Server Offset 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 41.837 41.837 41.837 43.198 43.659 43.659 43.659 1.822 1.822 0.640 42.851 ms -0.3048 1.688

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

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

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

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



Server Offset 240b:4002:100:9f00:5bd1:9512:8a8b:25e

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

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

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

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

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

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



Server Offset 240b:4004:108:200:8314:1a08:4cee:26d6

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 240b:4004:108:200:8314:1a08:4cee:26d6 -53.252 -30.228 -3.522 4.633 7.430 9.190 16.676 10.952 39.418 6.135 3.553 ms -4.789 30.29

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

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

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

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



Server Offset 240b:4004:108:200:8314:1a08:4cee:26d8

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

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

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

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

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

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



Server Offset 240b:4004:108:200:8314:1a08:4cee:26d9

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 240b:4004:108:200:8314:1a08:4cee:26d9 3.332 3.332 3.332 5.399 14.354 14.354 14.354 11.022 11.022 4.410 6.823 ms 1.061 2.259

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

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

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

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



Server Offset 240b:4004:108:200:8314:1a08:4cee:2acf

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

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

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

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

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

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



Server Offset 2600:1700:3d24:740f:9524:529a:6489:d48f

peer offset 2600:1700:3d24:740f:9524:529a:6489:d48f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1700:3d24:740f:9524:529a:6489:d48f 8.238 8.238 9.877 14.429 17.946 17.946 17.946 8.069 9.708 2.359 13.755 ms -0.5972 2.747

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

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

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

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



Server Offset 2600:1700:5455:a70::7b:1

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

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

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

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

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

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



Server Offset 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3

peer offset 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 -16.983 -16.983 2.347 14.361 471.310 472.188 472.188 468.963 489.171 193.989 112.827 ms 1.297 2.69

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

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

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

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



Server Offset 2600:1700:5a0f:ee00::314:1b

peer offset 2600:1700:5a0f:ee00::314:1b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1700:5a0f:ee00::314:1b -0.511 1.698 6.788 11.589 16.910 21.438 25.234 10.122 19.741 3.117 11.826 ms 0.01519 6.247

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

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

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

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



Server Offset 2600:1700:5a0f:ee00::314:2b

peer offset 2600:1700:5a0f:ee00::314:2b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1700:5a0f:ee00::314:2b 0.372 0.372 0.372 12.636 16.769 16.769 16.769 16.398 16.398 3.764 12.100 ms -1.682 6.304

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

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

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

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



Server Offset 2600:1702:7400:9ac0::314:5a

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

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

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

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

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

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



Server Offset 2600:1702:7400:9ac0::5b

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

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

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

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

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

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



Server Offset 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com) -90.591 -13.489 -3.590 1.754 4.959 7.566 17.081 8.549 21.055 4.239 1.308 ms -8.678 153.5

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

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

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

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



Server Offset 2600:1f13:2c1:2e00::be00:5

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f13:2c1:2e00::be00:5 -282.490 -1.401 3.361 6.350 9.277 21.057 75.600 5.916 22.458 11.306 6.295 ms -17.94 473.5

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

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

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

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



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

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) -155.691 -7.425 -5.731 3.067 6.244 8.116 110.743 11.974 15.541 4.932 1.630 ms -2.613 232.5

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

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

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

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



Server Offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) -159.116 -7.028 -3.909 3.387 6.614 8.454 422.200 10.523 15.482 6.360 2.442 ms 19.34 1705

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

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

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

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



Server Offset 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) -158.177 -23.587 -5.987 3.740 7.368 9.926 415.823 13.355 33.513 7.678 2.179 ms 9.969 765.7

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

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

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

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



Server Offset 2600:1f18:7927:8b00:123::

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

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

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

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

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

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



Server Offset 2600:2600::99 (ntp1.wiktel.com)

peer offset 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:2600::99 (ntp1.wiktel.com) 10.504 10.504 10.504 11.340 11.340 11.340 11.340 0.836 0.836 0.418 10.922 ms -6.279e-15 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 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) -3.406 -0.525 0.747 3.156 7.026 10.573 17.498 6.279 11.098 2.062 3.438 ms 1.184 6.539

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

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

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

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



Server Offset 2600:3c00:e000:318::1 (jane.qotw.net)

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

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

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

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

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

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



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

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

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

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

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

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

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



Server Offset 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com)

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

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

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

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

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

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



Server Offset 2600:3c01:e000:7e6::123 (time1.sigi.net)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c01:e000:7e6::123 (time1.sigi.net) -170.467 0.056 3.237 5.672 7.881 8.850 11.725 4.644 8.794 9.635 5.092 ms -17.71 322.2

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

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

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

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



Server Offset 2600:3c02::f03c:92ff:fe96:dc0

peer offset 2600:3c02::f03c:92ff:fe96:dc0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c02::f03c:92ff:fe96:dc0 -21.719 -4.622 -0.261 6.280 12.408 13.569 18.625 12.669 18.191 3.801 6.313 ms -1.28 11.52

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

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

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

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



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

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

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

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

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

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

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



Server Offset 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net) -1.758 0.272 2.422 5.275 7.286 8.980 9.933 4.864 8.708 1.546 5.181 ms -0.6519 4.856

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

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

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

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



Server Offset 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net)

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

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

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

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

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

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



Server Offset 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net)

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

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

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

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

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

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



Server Offset 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) -24.915 -11.563 -0.995 6.413 26.413 418.227 423.497 27.408 429.790 45.378 12.854 ms 8.158 72.77

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

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

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

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



Server Offset 2600:3c03::f03c:94ff:fe59:d3de

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c03::f03c:94ff:fe59:d3de 2.854 2.854 2.854 2.958 4.537 4.537 4.537 1.683 1.683 0.770 3.449 ms 0.6976 1.5

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

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

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

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



Server Offset 2600:3c03:e002:1300::10 (ntp.electronmill.com)

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

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

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

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

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

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



Server Offset 2600:3c06::f03c:94ff:fee2:9c28

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c06::f03c:94ff:fee2:9c28 5.742 5.742 5.742 7.946 15.389 15.389 15.389 9.646 9.646 3.904 8.785 ms 1.004 2.198

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

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

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

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



Server Offset 2600:3c06::f03c:94ff:fee2:c53a

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c06::f03c:94ff:fee2:c53a 7.934 7.934 7.934 10.652 34.769 34.769 34.769 26.835 26.835 12.061 17.785 ms 0.6803 1.5

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

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

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

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



Server Offset 2600:4040:3037:e600::1

peer offset 2600:4040:3037:e600::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:4040:3037:e600::1 2.842 2.842 2.842 6.051 6.051 6.051 6.051 3.209 3.209 1.605 4.447 ms -8.009e-16 1

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

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

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

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



Server Offset 2600:4040:e0da:f000::cbb9:201a

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:4040:e0da:f000::cbb9:201a -99.353 -99.353 -97.880 3.306 8.180 46.292 46.292 106.060 145.645 34.906 -8.837 ms -1.974 5.486

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

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

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

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



Server Offset 2602:291:69::8 (time2.tritan-bb.net)

peer offset 2602:291:69::8 plot

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

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

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

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

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



Server Offset 2602:291:69::9 (time.tritan-bb.net)

peer offset 2602:291:69::9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:291:69::9 (time.tritan-bb.net) -570.253 -570.253 -566.922 5.391 21.445 21.495 21.495 588.367 591.748 190.371 -63.466 ms -2.261 6.126

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

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

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

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



Server Offset 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) -158.684 -3.456 -0.080 2.050 4.212 6.155 10.845 4.293 9.610 7.377 1.718 ms -20.23 430.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 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net) 7.226 7.226 7.226 8.619 9.227 9.227 9.227 2.002 2.002 0.838 8.357 ms -0.4377 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 2602:2eb:2:95:1234:5678:9abc:def0

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:2eb:2:95:1234:5678:9abc:def0 -177.116 -4.361 -1.059 2.594 6.566 8.773 240.974 7.624 13.133 11.661 2.870 ms 12.1 337.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:80b:5000::36 (time.meme.holdings)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:80b:5000::36 (time.meme.holdings) -26.339 -9.392 1.266 5.868 9.817 23.455 24.890 8.551 32.847 4.663 5.601 ms -1.967 22.8

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

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

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

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



Server Offset 2602:81b:9000::c10c (time.sea.ordinaladvisors.com)

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

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

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

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

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

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



Server Offset 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net)

peer offset 2602:f9ba:69::210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) -412.469 -410.991 -9.243 1.817 13.963 25.256 77.682 23.206 436.248 60.595 -5.754 ms -6.348 42.52

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

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

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

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



Server Offset 2602:fb95:16::123 (time5.sigi.net)

peer offset 2602:fb95:16::123 plot

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

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

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

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

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



Server Offset 2602:fc2f:100:9800::dead:beef

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

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

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

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

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

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



Server Offset 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com)

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

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

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

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

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

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



Server Offset 2602:fe2e:3:d:f9:c7ff:fef5:379c

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

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

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

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

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

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



Server Offset 2602:ff06:725:100::123 (oldtime2.sigi.net)

peer offset 2602:ff06:725:100::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:ff06:725:100::123 (oldtime2.sigi.net) 3.097 3.097 3.097 9.383 10.512 10.512 10.512 7.414 7.414 2.231 8.621 ms -1.753 4.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 2602:ff23:50:3c2::1 (dns-e.ns4v.icu)

peer offset 2602:ff23:50:3c2::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:ff23:50:3c2::1 (dns-e.ns4v.icu) -414.428 -412.103 -5.498 2.874 14.322 38.967 85.012 19.820 451.069 59.635 -4.424 ms -6.489 44.25

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

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

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

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



Server Offset 2603:c020:0:8369:0:ba11:ba11:ba11

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369:0:ba11:ba11:ba11 -422.469 -422.469 -419.944 -7.467 4.024 4.850 4.850 423.968 427.319 153.878 -75.499 ms -1.784 4.191

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

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

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

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



Server Offset 2603:c020:0:8369:1111:1111:1111:1112

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369:1111:1111:1111:1112 -55.331 -55.331 -46.563 -5.926 94.091 94.407 94.407 140.654 149.738 40.627 10.132 ms 1.219 3.267

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

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

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

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



Server Offset 2603:c020:0:8369::bad:beef

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

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

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

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

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

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



Server Offset 2603:c020:0:8369::f00d:feed

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369::f00d:feed -17.667 -17.667 -15.791 -5.100 453.988 458.206 458.206 469.779 475.874 188.222 87.341 ms 1.435 3.061

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

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

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

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



Server Offset 2603:c020:0:8369::feeb:dab

peer offset 2603:c020:0:8369::feeb:dab plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:0:8369::feeb:dab -19.462 -19.462 -18.508 -9.177 453.345 453.880 453.880 471.853 473.342 182.625 78.325 ms 1.56 3.436

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

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

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

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



Server Offset 2603:c020:0:8369:feed:feed:feed:feed

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

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

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

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

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

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



Server Offset 2603:c020:6:b900:6b54:1390:4afd:814a

peer offset 2603:c020:6:b900:6b54:1390:4afd:814a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:6:b900:6b54:1390:4afd:814a -420.366 -420.366 -420.366 -15.121 2.174 2.174 2.174 422.540 422.540 183.604 -122.964 ms -0.9887 1.983

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

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

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

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



Server Offset 2603:c020:6:b900:ed2f:b442:fee7:d9b9

peer offset 2603:c020:6:b900:ed2f:b442:fee7:d9b9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2603:c020:6:b900:ed2f:b442:fee7:d9b9 -9.081 -9.081 -9.081 -3.889 -1.558 -1.558 -1.558 7.523 7.523 2.325 -4.454 ms -0.9557 3.036

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

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

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

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



Server Offset 2603:c024:c005:a600:efb6:d213:cad8:251d

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

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

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

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

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

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



Server Offset 2604:2dc0:100:25e2:2ab9:2b59:40e7:1

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

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

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

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

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

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



Server Offset 2604:2dc0:100:4d6::

peer offset 2604:2dc0:100:4d6:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:2dc0:100:4d6:: 6.451 6.451 6.451 7.846 12.197 12.197 12.197 5.746 5.746 2.175 8.548 ms 0.9328 2.204

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

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

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

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



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

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

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

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

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

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

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



Server Offset 2604:2dc0:202:300::140d (ovh.maxhost.io)

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

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

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

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

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

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



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

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

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

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

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

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

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



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

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

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

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

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

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

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



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

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) -802.674 -802.674 -802.674 2.272 9.840 9.840 9.840 812.514 812.514 371.058 -243.393 ms -0.8332 1.694

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com)

peer offset 2604:8800:52:81:38:229:52:9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) 4.759 4.759 4.759 5.795 36.164 36.164 36.164 31.405 31.405 14.567 15.573 ms 0.7044 1.5

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -97.614 -97.614 -97.614 -96.252 -95.198 -95.198 -95.198 2.416 2.416 0.727 -96.393 ms -0.05135 2.552

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2604:a880:1:20::1fd:1001 (jitter.tickadj.net)

peer offset 2604:a880:1:20::1fd:1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) -40.303 -1.773 0.146 2.726 5.501 103.648 104.341 5.355 105.421 14.429 4.427 ms 6.057 42.23

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2604:a880:400:d0::4ed:f001 (unifi.versadns.com)

peer offset 2604:a880:400:d0::4ed:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) -6.372 -6.372 -3.109 11.458 218.960 218.960 218.960 222.069 225.332 83.767 47.473 ms 1.451 3.181

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2604:a880:800:10::70f:b001 (ellone.fdisk.io)

peer offset 2604:a880:800:10::70f:b001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:800:10::70f:b001 (ellone.fdisk.io) 3.373 3.373 3.373 8.241 9.581 9.581 9.581 6.208 6.208 1.791 7.376 ms -0.8255 2.41

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2604:a880:800:a1::ec9:5001

peer offset 2604:a880:800:a1::ec9:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:800:a1::ec9:5001 -127.479 -127.479 -5.442 6.181 17.508 17.508 17.508 22.949 144.987 29.551 -0.176 ms -3.971 17.23

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2604:d200::39 (white.web-ster.com)

peer offset 2604:d200::39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:d200::39 (white.web-ster.com) -4.662 -4.662 -4.662 -2.055 0.687 0.687 0.687 5.349 5.349 1.751 -2.305 ms 0.2579 1.689

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2605:4840:3:fb19::1 (chi3.us.ntp.li)

peer offset 2605:4840:3:fb19::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:4840:3:fb19::1 (chi3.us.ntp.li) -278.261 -8.779 -1.179 2.716 7.022 29.833 89.152 8.201 38.612 10.597 2.909 ms -14.92 445.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 2605:6400:488d:2eda:eee9:fe8d:4543:d471

peer offset 2605:6400:488d:2eda:eee9:fe8d:4543:d471 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:6400:488d:2eda:eee9:fe8d:4543:d471 6.277 6.277 6.277 10.872 10.872 10.872 10.872 4.595 4.595 2.297 8.574 ms -5.457e-16 1

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2605:6400:488d:3686:546d:c03c:1689:20c

peer offset 2605:6400:488d:3686:546d:c03c:1689:20c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:6400:488d:3686:546d:c03c:1689:20c 0.063 0.063 0.063 10.815 77.942 77.942 77.942 77.879 77.879 31.733 28.904 ms 0.6938 1.564

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2605:6400:84e1::123 (oldtime3.sigi.net)

peer offset 2605:6400:84e1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:6400:84e1::123 (oldtime3.sigi.net) 0.114 0.114 0.114 234.240 240.273 240.273 240.273 240.159 240.159 112.476 147.282 ms -0.474 1.227

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de)

peer offset 2605:6f01:2000:18::94ee:fcbe plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) -1.370 -1.370 -1.370 3.697 9.921 9.921 9.921 11.292 11.292 2.854 4.172 ms 0.1428 3.178

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:4700:f1::1 (time.cloudflare.com)

peer offset 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -170.499 -5.254 -1.615 5.567 8.603 10.602 214.236 10.218 15.856 5.510 5.177 ms 13.09 708.9

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:4700:f1::123 (time.cloudflare.com)

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -810.498 -3.457 -0.858 5.411 8.658 11.643 468.641 9.516 15.099 20.712 5.095 ms -16.6 892.9

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:82c0:21::e (time1.lshiy.com)

peer offset 2606:82c0:21::e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:82c0:21::e (time1.lshiy.com) -0.347 -0.347 -0.347 2.470 5.026 5.026 5.026 5.373 5.373 1.632 2.157 ms 0.07044 2.391

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:82c0:22::e (time2.lshiy.com)

peer offset 2606:82c0:22::e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:82c0:22::e (time2.lshiy.com) -105.777 -105.777 -105.777 5.039 20.159 20.159 20.159 125.937 125.937 53.616 -35.047 ms -0.3967 1.186

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2606:82c0:23::e (time3.lshiy.com)

peer offset 2606:82c0:23::e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:82c0:23::e (time3.lshiy.com) 3.326 3.326 3.326 7.253 12.695 12.695 12.695 9.369 9.369 2.739 7.383 ms 0.4156 2.484

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:5600:182:500::1 (ntp-1.jonlight.com)

peer offset 2607:5600:182:500::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:5600:182:500::1 (ntp-1.jonlight.com) -568.165 -568.165 -568.165 -0.446 11.465 11.465 11.465 579.631 579.631 265.791 -190.495 ms -0.701 1.5

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:7c80:54:3::32

peer offset 2607:7c80:54:3::32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:7c80:54:3::32 -2.394 0.513 2.688 5.205 8.247 11.037 88.040 5.560 10.524 3.400 5.362 ms 16.18 369.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 2607:7c80:54:3::56 (owners.kjsl.com)

peer offset 2607:7c80:54:3::56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:7c80:54:3::56 (owners.kjsl.com) -806.909 -806.909 -5.703 0.187 5.818 9.156 9.156 11.521 816.065 173.398 -38.752 ms -4.188 18.54

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:9000:7000:23:216:3cff:fe25:38d7

peer offset 2607:9000:7000:23:216:3cff:fe25:38d7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:9000:7000:23:216:3cff:fe25:38d7 -3.352 -0.375 0.741 4.354 8.207 9.388 11.040 7.466 9.763 2.317 4.364 ms -0.006342 2.996

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:9d00:2000:16::9269:208a

peer offset 2607:9d00:2000:16::9269:208a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:9d00:2000:16::9269:208a 0.027 0.027 0.549 5.418 11.274 17.615 17.615 10.726 17.588 3.719 5.554 ms 1.403 5.818

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:b500:410:7700::1

peer offset 2607:b500:410:7700::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:b500:410:7700::1 -559.793 -559.793 -558.023 15.880 247.118 247.131 247.131 805.140 806.924 235.950 5.184 ms -1.393 4.315

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f1c0:f014:9e00::1

peer offset 2607:f1c0:f014:9e00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f014:9e00::1 -0.782 -0.782 -0.782 3.789 12.363 12.363 12.363 13.145 13.145 4.161 4.437 ms 0.4965 2.056

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f1c0:f014:9e00::2

peer offset 2607:f1c0:f014:9e00::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f014:9e00::2 -2.137 -2.137 0.533 8.769 175.012 176.141 176.141 174.479 178.278 60.511 32.888 ms 1.871 4.578

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f1c0:f04e:fd00::1

peer offset 2607:f1c0:f04e:fd00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f04e:fd00::1 -0.324 -0.324 -0.324 4.901 12.270 12.270 12.270 12.594 12.594 3.373 4.498 ms 0.7124 3.491

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at)

peer offset 2607:f1c0:f06b:5000:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) -64.809 -64.809 -64.809 -61.044 -58.237 -58.237 -58.237 6.572 6.572 2.268 -61.730 ms -0.02717 1.823

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at)

peer offset 2607:f1c0:f06b:5000::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) 2.778 2.778 2.778 7.554 7.962 7.962 7.962 5.184 5.184 1.862 6.389 ms -1.034 2.559

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at)

peer offset 2607:f1c0:f06b:5000::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at) 10.032 10.032 10.032 11.425 11.425 11.425 11.425 1.393 1.393 0.696 10.729 ms 3.751e-15 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 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at)

peer offset 2607:f1c0:f06b:5000::3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) 6.196 6.196 6.196 9.764 23.462 23.462 23.462 17.266 17.266 5.350 11.804 ms 1.241 3.45

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at)

peer offset 2607:f1c0:f06b:5000::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) -2.373 -2.373 -1.407 3.297 10.246 11.084 11.084 11.653 13.458 3.531 3.807 ms 0.3808 2.37

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f1c0:f075:9900::1

peer offset 2607:f1c0:f075:9900::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f1c0:f075:9900::1 -11.364 -11.364 -8.290 9.893 429.232 429.472 429.472 437.522 440.836 115.991 54.692 ms 2.751 9.098

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f298:5:101d:f816:3eff:fefd:8817

peer offset 2607:f298:5:101d:f816:3eff:fefd:8817 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f298:5:101d:f816:3eff:fefd:8817 -174.467 -174.467 -172.715 3.910 20.484 20.484 20.484 193.199 194.951 64.078 -20.926 ms -1.945 4.813

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f3c8:3803:1::6

peer offset 2607:f3c8:3803:1::6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f3c8:3803:1::6 -6.026 -6.026 -6.026 2.471 214.987 214.987 214.987 221.013 221.013 95.937 61.079 ms 0.9476 1.902

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net)

peer offset 2607:f5b7:1:44::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) -23.263 -23.263 -23.263 -10.419 26.993 26.993 26.993 50.256 50.256 13.527 -6.124 ms 0.7442 2.94

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f710:35::29c:0:1 (ntp6.kernfusion.at)

peer offset 2607:f710:35::29c:0:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) 6.293 6.293 6.293 9.644 16.365 16.365 16.365 10.072 10.072 2.800 10.002 ms 0.8431 3.217

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f710:35::29c:0:5

peer offset 2607:f710:35::29c:0:5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f710:35::29c:0:5 1.230 1.230 1.230 6.637 13.998 13.998 13.998 12.768 12.768 3.502 7.121 ms 0.34 2.688

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:f710:35::29c:0:8

peer offset 2607:f710:35::29c:0:8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f710:35::29c:0:8 -3.482 -1.256 1.976 4.319 6.532 9.029 12.497 4.556 10.285 1.590 4.260 ms -0.3604 7.445

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net)

peer offset 2607:ff50:0:1a::10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) -158.123 -158.123 -158.123 3.807 12.552 12.552 12.552 170.675 170.675 66.662 -31.139 ms -1.273 2.639

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com)

peer offset 2607:ff50:0:20::5ca1:ab1e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com) 4.183 4.183 4.183 8.895 11.415 11.415 11.415 7.232 7.232 2.452 8.699 ms -0.9315 2.629

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com)

peer offset 2620:138:5000:0:5054:ff:fe89:6673 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com) -1.149 2.106 3.500 5.817 7.713 8.724 10.233 4.212 6.619 1.327 5.750 ms -0.4876 4.269

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com)

peer offset 2620:149:a23:4000::1e2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com) -0.204 1.005 2.637 5.063 7.033 8.021 9.117 4.396 7.016 1.373 4.978 ms -0.4552 3.887

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2620:83:8000:140::b (tic.lbl.gov)

peer offset 2620:83:8000:140::b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:83:8000:140::b (tic.lbl.gov) -64.202 -16.454 -0.037 2.751 5.105 7.089 169.920 5.142 23.543 8.350 2.692 ms 14.74 314

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2620:83:8000:140::c (toc.lbl.gov)

peer offset 2620:83:8000:140::c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:83:8000:140::c (toc.lbl.gov) -8.902 -3.197 0.915 6.115 12.932 16.845 18.523 12.018 20.042 3.819 6.351 ms 0.131 4.597

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2620:8d:c000::f (blotch.image1tech.net)

peer offset 2620:8d:c000::f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:8d:c000::f (blotch.image1tech.net) -12.501 -12.501 -12.501 0.670 15.127 15.127 15.127 27.628 27.628 9.564 -0.984 ms 0.2932 2

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com)

peer offset 2620:9a:e000:1061::2:165 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) -7.979 -7.979 -7.979 -0.845 213.035 213.035 213.035 221.015 221.015 98.515 62.052 ms 0.8326 1.697

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2620:b0:2000:102::1:123 (time-h.den.codehof.net)

peer offset 2620:b0:2000:102::1:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:b0:2000:102::1:123 (time-h.den.codehof.net) -107.407 -107.407 -107.407 -66.747 92.475 92.475 92.475 199.883 199.883 57.820 -44.390 ms 1.21 3.478

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2620:b0:2000:102::2:123 (time-he.den.codehof.net)

peer offset 2620:b0:2000:102::2:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:b0:2000:102::2:123 (time-he.den.codehof.net) -44.889 -44.889 -44.889 22.240 34.334 34.334 34.334 79.222 79.222 22.949 14.406 ms -2.048 5.652

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl)

peer offset 2a00:d78:0:712:94:198:159:11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) -96.622 -6.929 -0.552 2.316 5.247 8.796 15.564 5.799 15.724 3.642 2.209 ms -13.78 330.8

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se)

peer offset 2a01:3f7:2:44::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) -810.640 -44.134 -17.627 3.292 9.170 14.212 465.738 26.797 58.346 17.909 0.307 ms -12.94 750.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 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se)

peer offset 2a01:3f7:2:44::9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) -178.311 -47.855 -19.285 1.281 8.153 11.195 209.396 27.439 59.050 11.840 -1.369 ms -2.138 61.16

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a01:4ff:f0:e33b::1

peer offset 2a01:4ff:f0:e33b::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:4ff:f0:e33b::1 -0.405 1.341 2.845 5.084 7.763 10.129 12.458 4.918 8.789 1.688 5.148 ms 0.5654 5.665

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a01:4ff:f0:ebce::1

peer offset 2a01:4ff:f0:ebce::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:4ff:f0:ebce::1 8.384 8.384 8.384 34.231 34.231 34.231 34.231 25.847 25.847 12.924 21.307 ms 1.962e-16 1

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com)

peer offset 2a01:7e03::f03c:95ff:fef8:ac8c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) -51.215 -51.215 -51.215 6.741 19.073 19.073 19.073 70.288 70.288 23.048 -2.114 ms -1.242 3.142

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a01:7e04::f03c:94ff:fee2:cba5

peer offset 2a01:7e04::f03c:94ff:fee2:cba5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:7e04::f03c:94ff:fee2:cba5 -26.406 -26.406 -26.406 2.333 5.249 5.249 5.249 31.655 31.655 7.170 0.454 ms -3.228 12.34

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media)

peer offset 2a05:dfc1:cb1:201:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) -1.952 -1.380 -0.052 3.121 7.600 10.298 13.358 7.652 11.679 2.033 3.294 ms 1.115 6.929

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 34.147.28.4

peer offset 34.147.28.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 34.147.28.4 -33.036 -17.922 -5.992 -1.956 1.805 4.539 9.658 7.797 22.461 3.509 -2.228 ms -3.24 25.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 37.27.11.4

peer offset 37.27.11.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 37.27.11.4 -51.314 -10.261 -2.384 0.947 3.098 4.523 4.544 5.482 14.784 4.805 0.292 ms -9.244 98.81

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 44.190.5.123

peer offset 44.190.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 44.190.5.123 -619.209 0.510 2.373 5.247 7.388 8.599 28.290 5.014 8.089 9.005 4.880 ms -51.42 3247

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock 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.126.202

peer offset 45.55.126.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.55.126.202 -4.945 0.220 1.800 4.365 6.846 8.437 10.649 5.046 8.216 1.549 4.364 ms -0.4012 6.047

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock 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.61.187.39

peer offset 45.61.187.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.61.187.39 -3.631 -3.631 -3.631 4.490 13.757 13.757 13.757 17.388 17.388 4.830 3.741 ms 0.536 3.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 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 -14.116 -0.809 2.451 5.749 9.193 15.128 27.310 6.742 15.937 2.596 5.789 ms 0.6719 17.26

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 45.77.126.122

peer offset 45.77.126.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.77.126.122 0.280 0.280 0.280 4.312 5.554 5.554 5.554 5.273 5.273 1.572 3.685 ms -0.6575 2.314

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 45.79.35.159

peer offset 45.79.35.159 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.79.35.159 3.746 3.746 3.746 7.855 8.568 8.568 8.568 4.821 4.821 2.112 6.125 ms 0.01386 1.093

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 45.79.51.42

peer offset 45.79.51.42 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.79.51.42 -45.604 -45.604 -45.604 8.683 108.150 108.150 108.150 153.754 153.754 57.087 39.510 ms 0.07989 1.347

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 45.83.234.123

peer offset 45.83.234.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.83.234.123 -296.062 -296.062 -36.862 5.462 11.429 15.325 15.325 48.291 311.387 44.156 -5.332 ms -5.514 35.05

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 45.84.199.136

peer offset 45.84.199.136 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.84.199.136 -110.729 -110.729 -110.729 -97.871 9.546 9.546 9.546 120.275 120.275 54.799 -52.941 ms 0.172 1.055

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 46.37.96.107

peer offset 46.37.96.107 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 46.37.96.107 -808.769 -33.538 -1.905 5.043 7.457 8.750 17.475 9.362 42.288 37.739 2.042 ms -20.74 443.5

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 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 -0.126 1.188 2.722 5.546 7.480 8.196 9.034 4.758 7.008 1.412 5.394 ms -0.7297 4.131

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock 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.78.62.36

peer offset 5.78.62.36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.78.62.36 -8.523 -2.092 0.307 5.929 11.849 15.869 16.396 11.542 17.960 3.566 6.030 ms 0.08899 3.94

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 50.117.3.52

peer offset 50.117.3.52 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.117.3.52 -8.085 -8.085 -8.085 -6.204 -5.368 -5.368 -5.368 2.717 2.717 0.914 -6.560 ms -0.319 1.928

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 50.117.3.95

peer offset 50.117.3.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.117.3.95 -146.276 -146.276 -146.276 8.636 18.465 18.465 18.465 164.741 164.741 63.106 -20.370 ms -1.48 3.224

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 50.205.57.38

peer offset 50.205.57.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.205.57.38 -18.950 0.701 2.860 5.414 7.496 10.285 20.357 4.636 9.585 1.767 5.407 ms -1.488 39.77

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 50.218.103.254

peer offset 50.218.103.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.218.103.254 6.935 6.935 6.935 10.777 11.835 11.835 11.835 4.899 4.899 1.768 9.997 ms -0.768 2.084

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 51.81.20.76

peer offset 51.81.20.76 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 51.81.20.76 2.414 2.414 2.414 7.712 11.524 11.524 11.524 9.111 9.111 3.247 7.454 ms -0.2642 1.777

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 51.81.226.229

peer offset 51.81.226.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 51.81.226.229 -178.118 -178.118 -173.190 4.447 15.237 22.510 22.510 188.427 200.627 62.005 -17.820 ms -2.094 5.445

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 64.142.54.12

peer offset 64.142.54.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.142.54.12 9.100 9.100 9.100 11.576 22.059 22.059 22.059 12.959 12.959 3.920 12.706 ms 1.335 3.639

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 64.6.144.6

peer offset 64.6.144.6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.6.144.6 -8.057 -8.057 -8.057 -4.073 467.377 467.377 467.377 475.434 475.434 226.098 164.803 ms 0.5668 1.322

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 64.79.100.197

peer offset 64.79.100.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.79.100.197 -5.398 -1.308 0.115 2.437 4.257 5.695 7.196 4.142 7.002 1.439 2.356 ms -1.086 9.14

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 65.100.46.164

peer offset 65.100.46.164 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 65.100.46.164 -12.522 -2.725 -0.387 4.920 11.409 15.307 17.739 11.796 18.032 3.731 5.348 ms 0.01927 4.589

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock 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.100.46.166

peer offset 65.100.46.166 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 65.100.46.166 0.249 1.083 2.398 5.335 7.816 11.010 13.272 5.418 9.928 1.740 5.341 ms 0.2817 4.931

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 65.182.224.39

peer offset 65.182.224.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 65.182.224.39 1.814 1.814 1.814 2.848 5.791 5.791 5.791 3.977 3.977 1.315 3.059 ms 1.249 3.327

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 66.118.231.14

peer offset 66.118.231.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.118.231.14 -27.328 -27.328 -11.996 4.815 12.740 46.019 46.019 24.736 73.347 10.026 2.952 ms 0.8298 9.385

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 66.42.71.197

peer offset 66.42.71.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.42.71.197 -4.404 1.164 3.246 6.075 8.417 9.829 440.870 5.171 8.665 20.411 6.942 ms 20.87 439.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 66.59.198.94

peer offset 66.59.198.94 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.59.198.94 -3.193 -3.193 -3.193 1.753 7.991 7.991 7.991 11.183 11.183 3.576 2.287 ms 0.3048 1.825

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 66.85.78.80

peer offset 66.85.78.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.85.78.80 1.863 1.863 1.863 5.833 6.542 6.542 6.542 4.679 4.679 1.783 4.731 ms -0.7192 1.975

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 67.217.246.127

peer offset 67.217.246.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 67.217.246.127 -4.257 -3.477 -0.379 2.528 6.202 9.675 10.219 6.580 13.152 2.004 2.572 ms 0.5419 6.199

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 67.217.246.204

peer offset 67.217.246.204 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 67.217.246.204 -407.881 -405.967 -8.655 0.545 14.549 52.682 423.145 23.204 458.649 74.575 -3.927 ms -1.928 29.64

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 68.234.48.70

peer offset 68.234.48.70 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 68.234.48.70 -2.973 -2.973 -2.973 9.512 47.817 47.817 47.817 50.790 50.790 12.262 11.128 ms 2.266 7.46

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 69.176.84.38

peer offset 69.176.84.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.176.84.38 -4.887 -4.887 -3.512 1.450 3.073 4.499 4.499 6.585 9.386 2.266 0.622 ms -0.718 2.493

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 69.48.203.16

peer offset 69.48.203.16 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.48.203.16 2.540 2.540 2.540 7.439 10.588 10.588 10.588 8.048 8.048 2.329 7.070 ms -0.4418 2.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 69.89.207.199

peer offset 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.89.207.199 -35.854 -5.484 0.115 2.952 8.851 103.597 425.249 8.736 109.081 27.435 6.199 ms 12.72 187.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 69.89.207.99

peer offset 69.89.207.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.89.207.99 -82.728 -2.318 -0.017 2.894 4.643 5.551 6.408 4.661 7.869 3.416 2.593 ms -20.67 515

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 71.123.46.186

peer offset 71.123.46.186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 71.123.46.186 -0.765 -0.089 1.160 4.514 7.163 9.760 10.300 6.003 9.849 1.893 4.465 ms 0.0854 3.856

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 71.19.144.140

peer offset 71.19.144.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 71.19.144.140 -3.221 -3.221 -3.221 4.015 7.428 7.428 7.428 10.649 10.649 2.867 3.283 ms -0.3728 2.496

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 72.14.183.39

peer offset 72.14.183.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.14.183.39 5.676 5.676 5.676 6.591 11.748 11.748 11.748 6.071 6.071 2.174 7.473 ms 1.37 3.097

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 72.14.186.59

peer offset 72.14.186.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.14.186.59 2.611 2.611 2.611 5.374 7.023 7.023 7.023 4.412 4.412 1.489 5.305 ms -0.8276 2.527

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 72.30.35.89

peer offset 72.30.35.89 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.30.35.89 8.994 8.994 8.994 12.518 13.297 13.297 13.297 4.303 4.303 1.872 11.603 ms -0.6164 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 72.46.53.234

peer offset 72.46.53.234 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.46.53.234 -35.275 -35.275 -35.275 69.197 105.228 105.228 105.228 140.503 140.503 52.722 51.699 ms -0.2012 1.301

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 72.46.61.205

peer offset 72.46.61.205 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.46.61.205 -285.110 -285.110 -285.110 6.157 16.075 16.075 16.075 301.185 301.185 73.049 -25.856 ms -2.768 9.979

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 73.185.182.209

peer offset 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 73.185.182.209 -2.743 0.925 2.341 5.411 8.588 10.253 11.822 6.247 9.328 1.947 5.428 ms -0.05719 3.857

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 73.65.80.137

peer offset 73.65.80.137 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 73.65.80.137 -809.727 -809.727 -9.135 -1.384 3.688 7.510 7.510 12.823 817.238 169.002 -38.192 ms -4.333 19.79

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 74.119.243.5

peer offset 74.119.243.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 74.119.243.5 1.643 1.643 1.643 7.015 7.452 7.452 7.452 5.809 5.809 2.661 4.585 ms -0.008075 1.037

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 74.208.117.38

peer offset 74.208.117.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 74.208.117.38 -8.056 -8.056 -8.056 -3.727 11.177 11.177 11.177 19.233 19.233 5.901 -2.284 ms 1.09 3.094

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 74.208.14.149

peer offset 74.208.14.149 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 74.208.14.149 -5.945 -5.945 -5.945 8.847 11.709 11.709 11.709 17.654 17.654 5.690 5.541 ms -1.091 3.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 74.208.25.46

peer offset 74.208.25.46 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 74.208.25.46 -7.530 -3.640 -0.753 4.698 12.042 18.695 486.710 12.795 22.336 25.751 6.862 ms 13.8 210.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 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 -67.897 -19.625 -4.883 7.206 12.622 16.428 24.791 17.505 36.053 6.393 6.396 ms -3.658 29.94

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 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 -9.917 -9.917 -3.792 0.856 4.298 12.641 12.641 8.090 22.559 2.826 0.867 ms -0.03694 8.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 83.147.242.172

peer offset 83.147.242.172 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 83.147.242.172 -1.026 1.305 3.079 5.350 7.728 10.018 14.032 4.649 8.714 1.528 5.378 ms 0.287 5.704

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 94.198.159.11

peer offset 94.198.159.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 94.198.159.11 9.843 9.843 9.843 9.843 9.843 9.843 9.843 0.000 0.000 0.000 9.843 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 99.28.14.242

peer offset 99.28.14.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 99.28.14.242 -568.386 -2.050 0.773 4.332 6.974 9.919 171.646 6.201 11.970 46.430 1.696 ms -10.89 137.6

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



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) -865.294 -187.488 -184.773 -160.162 -121.774 -118.285 -66.245 63.000 69.203 20.226 -162.204 ms -0.4126 42.68

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) -43.998 -8.669 -8.296 -4.893 0.084 0.281 52.678 8.380 8.951 2.280 -4.795 ms 0.9182 15.25

The offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(2)

peer offset SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(2) -485.911 -173.937 -154.140 -0.113 8.457 17.453 1,940.513 162.597 191.390 47.916 -19.386 ms -1.858 19.48

The offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(3)

peer offset SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(3) -13.801 -8.355 -5.705 -0.426 0.409 0.866 2,061.810 6.113 9.222 6.664 -1.098 ms 273.7 8.273e+04

The offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(0)

peer offset SOCK(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SOCK(0) -597.294 -177.834 -174.616 -0.939 7.355 181.993 236.678 181.971 359.827 80.136 -30.176 ms -0.5305 3.565

The offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(1)

peer offset SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SOCK(1) -52.048 -1.787 -0.992 -0.087 0.869 1.335 230.276 1.862 3.123 1.166 -0.087 ms 129.6 2.566e+04

The offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(2)

peer offset SOCK(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SOCK(2) -181.172 -176.994 -173.059 -163.444 -157.121 -154.860 -148.505 15.938 22.134 4.800 -164.015 ms -0.5576 3.253

The offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(3)

peer offset SOCK(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SOCK(3) -3,009.455 -0.960 -0.610 -0.079 0.535 0.918 4.447 1.145 1.878 17.175 -0.177 ms -175.1 3.068e+04

The offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 in the peerstats log file.



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.000 0.000 0.000 3.656 17.731 18.171 18.171 17.731 18.171 4.618 5.158 ms 1.714 5.382

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.152.220.5

peer jitter 104.152.220.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.152.220.5 0.000 0.000 0.000 0.888 2.438 2.438 2.438 2.438 2.438 0.710 1.068 ms 0.5336 2.756

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.167.215.195

peer jitter 104.167.215.195 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.167.215.195 0.000 0.000 1.736 5.117 35.856 66.707 67.627 34.119 66.707 12.331 8.977 ms 3.401 14.81

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.167.241.253

peer jitter 104.167.241.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.167.241.253 0.000 0.000 0.000 2.362 8.036 8.036 8.036 8.036 8.036 2.290 2.983 ms 0.6267 2.554

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.234.61.117

peer jitter 104.234.61.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.234.61.117 0.000 0.842 1.258 3.320 13.812 22.021 62.066 12.553 21.179 4.667 4.606 ms 4.224 29.96

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 108.61.56.35

peer jitter 108.61.56.35 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 108.61.56.35 0.000 0.000 0.000 2.555 4.944 4.944 4.944 4.944 4.944 1.407 2.414 ms -0.1572 2.553

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 108.61.73.243

peer jitter 108.61.73.243 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 108.61.73.243 0.000 0.930 1.583 10.816 44.654 63.282 117.163 43.070 62.352 14.583 14.522 ms 2.087 8.894

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 12.71.198.242

peer jitter 12.71.198.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 12.71.198.242 0.000 0.000 0.000 2.476 14.247 14.247 14.247 14.247 14.247 4.389 3.547 ms 1.44 4.115

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 129.146.193.200

peer jitter 129.146.193.200 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 129.146.193.200 0.000 0.000 0.604 2.572 17.247 17.857 18.051 16.643 17.857 3.879 3.728 ms 2.392 8.649

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 131.153.171.250

peer jitter 131.153.171.250 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 131.153.171.250 0.000 0.000 0.000 0.763 4.308 4.308 4.308 4.308 4.308 1.877 1.690 ms 0.6205 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 131.239.5.43

peer jitter 131.239.5.43 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 131.239.5.43 0.000 0.000 0.000 1.655 3.135 3.135 3.135 3.135 3.135 0.882 1.743 ms -0.2966 2.893

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 135.148.100.14

peer jitter 135.148.100.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 135.148.100.14 0.000 1.034 1.658 14.607 55.544 71.155 96.799 53.886 70.120 15.421 16.960 ms 1.968 8.02

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 137.110.222.27

peer jitter 137.110.222.27 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 137.110.222.27 0.000 0.000 0.341 3.330 5.202 5.372 5.372 4.861 5.372 1.250 3.135 ms -0.5711 2.996

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 137.190.2.4

peer jitter 137.190.2.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 137.190.2.4 0.000 0.000 0.000 8.346 83.883 83.883 83.883 83.883 83.883 25.677 16.869 ms 1.958 5.07

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 139.177.202.26

peer jitter 139.177.202.26 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.177.202.26 0.000 0.000 0.000 1.560 6.528 6.528 6.528 6.528 6.528 1.992 1.908 ms 1.039 3.07

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 139.84.137.244

peer jitter 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.84.137.244 0.000 1.502 3.514 23.662 63.458 81.645 171.675 59.944 80.143 19.796 27.106 ms 1.38 7.836

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 139.94.144.123

peer jitter 139.94.144.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.94.144.123 0.000 0.000 0.000 1.501 2.945 2.945 2.945 2.945 2.945 1.260 1.529 ms 0.002279 1.271

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 141.11.234.198

peer jitter 141.11.234.198 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 141.11.234.198 0.000 0.000 0.000 8.942 58.361 58.361 58.361 58.361 58.361 19.957 16.134 ms 1.387 3.303

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 141.11.89.193

peer jitter 141.11.89.193 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 141.11.89.193 0.000 0.000 0.000 1.558 2.015 2.015 2.015 2.015 2.015 0.652 1.474 ms -1.441 3.889

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 142.202.190.19

peer jitter 142.202.190.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 142.202.190.19 0.000 0.000 0.000 2.175 6.985 16.409 16.409 6.985 16.409 3.192 2.973 ms 2.438 10.54

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 144.202.0.197

peer jitter 144.202.0.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.0.197 0.000 0.000 0.000 2.470 4.307 4.307 4.307 4.307 4.307 1.435 2.296 ms -0.2563 1.847

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 144.202.66.214

peer jitter 144.202.66.214 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.66.214 0.000 0.000 0.000 3.268 3.564 3.564 3.564 3.564 3.564 1.326 2.411 ms -0.873 2.102

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 148.163.226.148

peer jitter 148.163.226.148 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 148.163.226.148 0.000 0.000 0.000 0.817 80.131 80.131 80.131 80.131 80.131 25.414 13.052 ms 1.993 5.456

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 149.248.12.167

peer jitter 149.248.12.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.248.12.167 0.000 0.000 0.000 1.415 6.547 6.547 6.547 6.547 6.547 2.701 2.851 ms 0.3599 1.282

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 149.28.200.179

peer jitter 149.28.200.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.28.200.179 0.000 0.000 1.448 3.887 18.634 19.531 19.531 17.186 19.531 5.389 6.126 ms 1.504 3.906

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 149.28.61.105

peer jitter 149.28.61.105 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.28.61.105 0.000 0.000 0.000 2.466 4.280 4.280 4.280 4.280 4.280 1.264 2.154 ms -0.03175 2.746

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 15.204.198.96

peer jitter 15.204.198.96 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 15.204.198.96 0.000 0.000 1.528 9.635 18.188 24.740 24.740 16.661 24.740 6.496 9.205 ms 0.2143 1.632

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 15.204.87.223

peer jitter 15.204.87.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 15.204.87.223 0.000 0.000 1.093 3.116 14.025 23.083 37.321 12.932 23.083 4.456 4.482 ms 3.12 16.52

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 155.248.196.28

peer jitter 155.248.196.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 155.248.196.28 0.000 0.000 0.000 1.667 4.694 4.694 4.694 4.694 4.694 1.616 1.873 ms 0.573 1.838

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 158.51.99.19

peer jitter 158.51.99.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 158.51.99.19 0.000 0.861 1.216 3.317 19.810 51.816 228.673 18.594 50.955 13.195 6.155 ms 10.51 149.8

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.000 0.384 1.100 2.819 8.229 21.629 42.450 7.129 21.245 4.023 3.765 ms 5.049 37.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 162.159.200.123

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.000 0.000 0.000 3.085 9.842 12.427 12.427 9.842 12.427 2.969 3.852 ms 1.147 3.88

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 163.123.152.14

peer jitter 163.123.152.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 163.123.152.14 0.000 0.000 0.000 3.728 4.357 4.357 4.357 4.357 4.357 1.674 2.791 ms -0.9099 2.151

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 166.88.142.52

peer jitter 166.88.142.52 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 166.88.142.52 0.000 0.000 0.000 1.075 3.927 3.927 3.927 3.927 3.927 1.133 1.349 ms 1.419 4.128

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 168.61.215.74

peer jitter 168.61.215.74 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 168.61.215.74 0.000 0.000 0.000 3.749 13.177 14.339 14.339 13.177 14.339 4.228 5.272 ms 0.615 2.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 170.187.147.56

peer jitter 170.187.147.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 170.187.147.56 0.000 0.824 1.119 3.127 15.294 35.711 154.182 14.175 34.886 9.178 5.070 ms 11.83 185.3

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.233.153.85

peer jitter 172.233.153.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.153.85 0.000 0.000 1.067 4.764 14.089 23.765 302.556 13.022 23.765 29.458 8.479 ms 9.659 96.43

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.233.157.223

peer jitter 172.233.157.223 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.157.223 0.000 0.000 0.000 2.179 8.001 8.001 8.001 8.001 8.001 2.598 2.911 ms 0.8956 2.43

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.233.177.198

peer jitter 172.233.177.198 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.177.198 0.000 0.000 0.000 5.156 9.581 9.581 9.581 9.581 9.581 2.646 5.415 ms -0.2803 2.993

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.234.25.10

peer jitter 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.25.10 0.000 0.000 0.000 1.180 4.280 4.280 4.280 4.280 4.280 1.151 1.441 ms 1.042 3.453

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.234.37.140

peer jitter 172.234.37.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.37.140 0.000 0.000 0.000 5.761 13.618 13.618 13.618 13.618 13.618 3.635 5.254 ms 0.5438 2.723

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.234.44.141

peer jitter 172.234.44.141 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.44.141 0.000 0.000 0.000 2.374 7.577 7.577 7.577 7.577 7.577 2.262 3.093 ms 0.8517 2.644

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.235.60.8

peer jitter 172.235.60.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.235.60.8 0.000 0.000 0.000 2.985 13.407 13.407 13.407 13.407 13.407 3.264 4.071 ms 1.906 6.336

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.98.15.13

peer jitter 172.98.15.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.98.15.13 0.000 0.000 0.000 6.095 6.104 6.104 6.104 6.104 6.104 2.880 3.231 ms -0.02367 1.032

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.230.154.254

peer jitter 173.230.154.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.230.154.254 0.000 0.000 0.000 17.669 34.968 34.968 34.968 34.968 34.968 10.793 16.118 ms 0.0947 2.297

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.249.203.227

peer jitter 173.249.203.227 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.249.203.227 0.000 0.000 0.000 2.338 5.843 5.843 5.843 5.843 5.843 1.587 2.822 ms 0.3165 2.627

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.255.192.10

peer jitter 173.255.192.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.255.192.10 0.000 0.000 0.000 2.331 9.584 9.584 9.584 9.584 9.584 2.608 3.116 ms 1.465 4.472

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.255.255.133

peer jitter 173.255.255.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.255.255.133 0.000 0.153 1.038 3.303 14.750 23.112 28.677 13.712 22.959 4.499 4.721 ms 2.482 9.648

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.71.68.71

peer jitter 173.71.68.71 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.71.68.71 0.000 0.627 1.250 6.765 34.293 47.740 57.792 33.043 47.112 10.711 11.124 ms 1.434 5.181

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 192.48.105.15

peer jitter 192.48.105.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.48.105.15 0.000 0.000 0.000 1.815 13.786 13.786 13.786 13.786 13.786 3.333 2.570 ms 2.497 8.699

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 193.29.63.226

peer jitter 193.29.63.226 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 193.29.63.226 0.000 0.000 0.000 2.362 6.790 7.768 7.768 6.790 7.768 1.752 2.617 ms 1.293 4.972

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 194.0.5.123

peer jitter 194.0.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.0.5.123 0.000 0.740 1.115 3.191 11.228 23.083 161.579 10.113 22.342 7.460 4.536 ms 14.75 290.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 198.137.202.32

peer jitter 198.137.202.32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.137.202.32 0.000 0.671 1.209 3.297 12.402 17.407 31.925 11.193 16.736 3.746 4.236 ms 3.509 20.09

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 198.199.14.19

peer jitter 198.199.14.19 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.199.14.19 0.000 0.000 0.000 4.868 19.360 19.360 19.360 19.360 19.360 6.619 7.607 ms 0.7297 1.985

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 198.211.103.209

peer jitter 198.211.103.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.211.103.209 0.000 0.000 0.000 3.750 13.433 21.945 21.945 13.433 21.945 4.568 5.256 ms 1.672 6.209

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 198.46.254.130

peer jitter 198.46.254.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.46.254.130 0.000 0.789 1.171 3.308 24.735 39.397 60.567 23.564 38.608 8.364 6.211 ms 3.337 16.34

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 198.60.22.240

peer jitter 198.60.22.240 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.60.22.240 0.000 0.000 0.000 1.229 8.123 8.123 8.123 8.123 8.123 2.808 2.774 ms 0.7715 2.116

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 199.68.201.235

peer jitter 199.68.201.235 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 199.68.201.235 0.000 0.000 1.107 3.083 4.994 5.795 5.795 3.886 5.795 1.244 3.083 ms -0.137 2.992

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net)

peer jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) 0.000 1.001 1.378 3.306 22.350 55.353 68.490 20.972 54.352 9.914 6.937 ms 3.502 16.46

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com)

peer jitter 2001:19f0:1590:5123:1057:a11:da7a:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) 0.000 0.000 0.000 6.706 10.790 10.790 10.790 10.790 10.790 3.771 6.760 ms -0.8058 2.409

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:19f0:6401:400:5400:4ff:fec3:522a

peer jitter 2001:19f0:6401:400:5400:4ff:fec3:522a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:19f0:6401:400:5400:4ff:fec3:522a 0.000 0.000 0.000 4.945 24.636 24.636 24.636 24.636 24.636 6.126 6.507 ms 1.809 6.149

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:418:3ff::53 (x.ns.gin.ntt.net)

peer jitter 2001:418:3ff::53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:418:3ff::53 (x.ns.gin.ntt.net) 0.000 0.000 0.000 14.048 17.951 17.951 17.951 17.951 17.951 7.508 10.420 ms -0.3643 1.295

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:418:8405:4002::12

peer jitter 2001:418:8405:4002::12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:418:8405:4002::12 0.000 0.000 0.000 20.750 257.784 257.784 257.784 257.784 257.784 84.275 57.575 ms 1.804 4.559

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:418:8405:4002::3

peer jitter 2001:418:8405:4002::3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:418:8405:4002::3 0.000 0.000 0.000 4.428 8.084 8.084 8.084 8.084 8.084 2.892 3.931 ms 0.1094 1.917

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de)

peer jitter 2001:470:1f07:198::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) 0.000 1.136 2.036 12.122 41.039 72.944 118.845 39.003 71.808 15.175 15.560 ms 2.609 13.81

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:1f07:24f::123

peer jitter 2001:470:1f07:24f::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:1f07:24f::123 0.000 0.000 0.000 25.254 42.613 42.613 42.613 42.613 42.613 13.314 18.607 ms 0.05496 1.858

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:1f2c:60:123:123:123:123

peer jitter 2001:470:1f2c:60:123:123:123:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:1f2c:60:123:123:123:123 0.000 0.000 0.000 20.430 35.954 35.954 35.954 35.954 35.954 11.405 14.554 ms 0.1812 1.824

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:e114::d6:12 (1.md.ntp.md)

peer jitter 2001:470:e114::d6:12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e114::d6:12 (1.md.ntp.md) 0.000 0.766 1.459 6.826 27.047 45.230 56.378 25.589 44.464 8.650 9.685 ms 2.029 9.062

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:470:e8dc:10::123

peer jitter 2001:470:e8dc:10::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e8dc:10::123 0.000 0.001 0.001 0.004 0.021 0.074 589.082 0.020 0.073 24.776 1.685 s 18.39 390.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 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com)

peer jitter 2001:4998:58:183a::1000 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) 0.000 1.102 1.686 10.928 48.225 61.432 219.778 46.539 60.331 15.215 14.564 ms 2.947 25.72

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com)

peer jitter 2001:4998:c:1028::1000 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com) 0.000 0.840 1.365 3.070 12.046 16.376 19.485 10.681 15.537 3.227 3.896 ms 2.632 10.33

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com)

peer jitter 2001:4998:c:1028::1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) 0.000 0.830 1.150 3.284 24.575 55.936 146.741 23.425 55.106 10.291 6.585 ms 4.523 32.1

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:558:6014:17:8dc5:5575:5560:2cb6

peer jitter 2001:558:6014:17:8dc5:5575:5560:2cb6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:558:6014:17:8dc5:5575:5560:2cb6 0.000 0.000 0.000 4.253 65.155 123.941 123.941 65.155 123.941 24.032 13.461 ms 3.066 13.01

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:559:2be:3::1001

peer jitter 2001:559:2be:3::1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:559:2be:3::1001 0.000 0.000 0.000 3.333 53.390 53.390 53.390 53.390 53.390 13.672 9.507 ms 1.842 5.746

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2001:678:8::123 (any.time.nl)

peer jitter 2001:678:8::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:678:8::123 (any.time.nl) 0.000 1.610 3.411 25.456 75.543 96.212 182.621 72.133 94.602 23.152 30.446 ms 0.9596 3.679

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.197.163.71

peer jitter 204.197.163.71 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.197.163.71 0.000 0.686 1.095 3.220 7.493 17.061 50.513 6.398 16.375 3.155 3.763 ms 6.631 80.71

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.2.134.162

peer jitter 204.2.134.162 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.2.134.162 0.000 0.000 0.000 1.171 6.096 6.096 6.096 6.096 6.096 1.827 2.047 ms 0.8441 2.681

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 205.233.73.201

peer jitter 205.233.73.201 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 205.233.73.201 0.000 0.000 0.000 3.474 11.938 11.938 11.938 11.938 11.938 2.573 3.409 ms 1.455 6.61

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 208.113.130.146

peer jitter 208.113.130.146 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 208.113.130.146 0.000 0.861 1.394 5.061 43.913 76.684 232.036 42.519 75.823 18.779 11.712 ms 5.666 52.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 208.67.72.43

peer jitter 208.67.72.43 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 208.67.72.43 0.000 0.000 0.000 20.684 46.773 46.773 46.773 46.773 46.773 14.479 19.405 ms 0.3984 2.247

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 208.67.72.50

peer jitter 208.67.72.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 208.67.72.50 0.000 0.000 1.610 9.928 32.633 65.428 66.592 31.023 65.428 11.583 11.986 ms 2.324 10.54

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 208.67.75.242

peer jitter 208.67.75.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 208.67.75.242 0.000 0.872 1.265 3.563 19.825 36.345 45.510 18.560 35.473 6.747 6.278 ms 2.54 10.94

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.916 0.946 1.311 3.935 18.958 38.990 46.313 17.647 38.044 6.905 6.714 ms 2.568 11.6

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.229.4.66

peer jitter 216.229.4.66 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.229.4.66 0.000 0.000 0.000 4.322 7.579 7.579 7.579 7.579 7.579 2.291 4.100 ms -0.5079 2.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 216.229.4.69

peer jitter 216.229.4.69 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.229.4.69 0.000 0.000 0.000 2.477 5.003 5.695 5.695 5.003 5.695 1.718 2.457 ms 0.2191 2.013

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.240.36.24

peer jitter 216.240.36.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.240.36.24 0.000 0.000 0.000 2.248 8.229 8.229 8.229 8.229 8.229 2.720 2.945 ms 1.272 3.013

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.31.17.12

peer jitter 216.31.17.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.31.17.12 0.000 0.000 0.000 4.094 14.330 14.330 14.330 14.330 14.330 4.001 4.883 ms 1.185 3.801

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.111.186.186

peer jitter 23.111.186.186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.111.186.186 0.000 0.000 0.000 1.132 1.974 1.974 1.974 1.974 1.974 0.537 1.129 ms -0.4905 3.028

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.131.160.7

peer jitter 23.131.160.7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.131.160.7 0.000 0.880 1.354 3.468 10.866 32.018 126.894 9.512 31.138 7.981 4.858 ms 9.335 108.7

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.141.40.123

peer jitter 23.141.40.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.141.40.123 0.000 0.000 0.000 3.979 5.911 5.911 5.911 5.911 5.911 1.921 3.290 ms -0.4708 2.11

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.142.248.8

peer jitter 23.142.248.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.142.248.8 0.000 0.000 0.000 1.269 2.327 2.327 2.327 2.327 2.327 0.866 1.154 ms -0.1197 1.574

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.142.248.9

peer jitter 23.142.248.9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.142.248.9 0.000 0.000 0.000 2.456 5.220 5.220 5.220 5.220 5.220 1.826 2.458 ms 0.2091 1.622

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.143.196.199

peer jitter 23.143.196.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.143.196.199 0.000 0.000 0.000 1.033 2.250 2.250 2.250 2.250 2.250 0.756 1.094 ms -0.06783 1.795

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.150.41.123

peer jitter 23.150.41.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.150.41.123 0.000 0.000 1.377 3.846 22.008 38.931 39.560 20.631 38.931 8.452 7.143 ms 2.301 8.099

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.155.40.38

peer jitter 23.155.40.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.155.40.38 0.000 0.000 1.081 3.356 34.022 117.881 142.893 32.940 117.881 18.722 8.653 ms 5.033 31.38

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.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 0.000 4.522 5.887 5.887 5.887 5.887 5.887 2.451 2.822 ms 0.06634 1.208

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.123

peer jitter 23.186.168.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.123 0.000 0.794 1.193 3.052 8.245 20.200 30.025 7.052 19.406 3.089 3.701 ms 3.772 21.92

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.126

peer jitter 23.186.168.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.126 0.000 0.695 1.121 3.001 10.669 41.147 100.230 9.548 40.452 8.625 4.647 ms 7.962 75.3

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.127

peer jitter 23.186.168.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.127 0.000 0.000 0.000 6.846 25.786 25.786 25.786 25.786 25.786 9.961 9.050 ms 0.9537 2.186

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.128

peer jitter 23.186.168.128 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.128 0.000 0.814 1.329 3.310 8.610 17.200 23.748 7.281 16.386 2.792 3.875 ms 2.955 14.86

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.129

peer jitter 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.129 0.000 0.699 1.253 3.436 8.998 17.637 105.774 7.745 16.939 4.861 4.275 ms 11.96 214.6

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.130

peer jitter 23.186.168.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.130 0.000 0.000 0.000 3.466 73.799 73.994 73.994 73.799 73.994 19.691 9.038 ms 2.942 9.824

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.131

peer jitter 23.186.168.131 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.131 0.000 0.749 1.266 3.133 8.261 15.037 223.184 6.995 14.289 9.704 4.117 ms 21.04 473.4

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.132

peer jitter 23.186.168.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.132 0.000 0.902 1.266 3.346 9.317 18.281 72.944 8.051 17.379 3.794 4.152 ms 6.892 91.34

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.94.221.138

peer jitter 23.94.221.138 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.94.221.138 0.000 0.000 0.000 1.546 4.125 4.125 4.125 4.125 4.125 1.215 1.733 ms 0.7763 2.642

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.95.49.216

peer jitter 23.95.49.216 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.95.49.216 0.000 0.804 1.089 2.946 11.443 17.019 159.086 10.354 16.216 7.100 4.020 ms 17.62 379.9

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl)

peer jitter 2401:c080:3000:2945:5400:4ff:fe69:f923 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) 0.000 1.856 4.955 29.235 71.283 87.807 159.685 66.328 85.951 21.157 32.582 ms 0.7387 3.363

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s 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 0.000 0.000 0.934 1.239 1.239 1.239 1.239 1.239 0.407 0.723 ms -0.5786 2.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 240b:4002:100:9f00:5bd1:9512:8a8b:25e

peer jitter 240b:4002:100:9f00:5bd1:9512:8a8b:25e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 240b:4002:100:9f00:5bd1:9512:8a8b:25e 0.000 0.000 0.000 4.287 5.971 5.971 5.971 5.971 5.971 2.062 3.825 ms -0.9946 2.639

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d6

peer jitter 240b:4004:108:200:8314:1a08:4cee:26d6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d6 0.000 0.839 1.416 3.601 24.535 54.985 74.237 23.119 54.146 9.449 6.322 ms 4.13 22.24

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d8

peer jitter 240b:4004:108:200:8314:1a08:4cee:26d8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d8 0.000 0.000 0.000 3.953 46.649 52.232 52.232 46.649 52.232 15.473 10.747 ms 1.58 4.101

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d9

peer jitter 240b:4004:108:200:8314:1a08:4cee:26d9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d9 0.000 0.000 0.000 19.678 21.828 21.828 21.828 21.828 21.828 8.593 13.132 ms -0.5264 1.711

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 240b:4004:108:200:8314:1a08:4cee:2acf

peer jitter 240b:4004:108:200:8314:1a08:4cee:2acf plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 240b:4004:108:200:8314:1a08:4cee:2acf 0.000 0.000 0.000 1.911 56.765 56.765 56.765 56.765 56.765 17.704 9.838 ms 2.016 5.544

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1700:3d24:740f:9524:529a:6489:d48f

peer jitter 2600:1700:3d24:740f:9524:529a:6489:d48f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1700:3d24:740f:9524:529a:6489:d48f 0.000 0.000 0.000 1.447 8.923 8.923 8.923 8.923 8.923 2.239 2.142 ms 1.358 4.664

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1700:5455:a70::7b:1

peer jitter 2600:1700:5455:a70::7b:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1700:5455:a70::7b:1 0.000 0.000 1.444 4.653 23.669 27.142 27.142 22.225 27.142 7.742 8.428 ms 1.002 2.547

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3

peer jitter 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 0.000 0.000 0.000 4.182 17.559 24.762 24.762 17.559 24.762 6.282 6.670 ms 1.239 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 2600:1700:5a0f:ee00::314:1b

peer jitter 2600:1700:5a0f:ee00::314:1b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1700:5a0f:ee00::314:1b 0.000 0.000 1.037 3.806 18.648 21.885 23.803 17.611 21.885 5.224 5.597 ms 1.78 5.219

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1700:5a0f:ee00::314:2b

peer jitter 2600:1700:5a0f:ee00::314:2b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1700:5a0f:ee00::314:2b 0.000 0.000 0.000 2.121 13.811 13.811 13.811 13.811 13.811 3.373 3.376 ms 1.687 5.974

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1702:7400:9ac0::314:5a

peer jitter 2600:1702:7400:9ac0::314:5a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1702:7400:9ac0::314:5a 0.000 0.000 0.000 2.413 15.160 15.160 15.160 15.160 15.160 4.523 4.818 ms 1.082 3.061

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1702:7400:9ac0::5b

peer jitter 2600:1702:7400:9ac0::5b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1702:7400:9ac0::5b 0.000 0.000 0.000 2.689 7.877 7.877 7.877 7.877 7.877 2.509 3.387 ms 0.6509 2.164

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com)

peer jitter 2600:1900:4060:2e7:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com) 0.000 1.703 3.526 24.446 74.599 96.231 173.647 71.073 94.529 22.963 30.367 ms 1.031 4.082

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1f13:2c1:2e00::be00:5

peer jitter 2600:1f13:2c1:2e00::be00:5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f13:2c1:2e00::be00:5 0.000 0.941 1.487 3.653 25.297 93.488 214.829 23.809 92.548 16.422 7.675 ms 6.759 62.66

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com)

peer jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.000 0.823 1.169 3.339 21.951 49.663 185.361 20.783 48.840 9.853 6.218 ms 5.748 56.48

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com)

peer jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) 0.000 0.832 1.212 3.536 39.205 69.230 282.893 37.993 68.398 14.386 9.101 ms 4.117 32.69

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com)

peer jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) 0.000 0.835 1.266 7.203 52.230 78.393 168.874 50.964 77.558 17.372 14.338 ms 2.244 9.57

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:1f18:7927:8b00:123::

peer jitter 2600:1f18:7927:8b00:123:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f18:7927:8b00:123:: 0.000 0.000 0.000 0.873 2.440 2.440 2.440 2.440 2.440 0.788 1.166 ms 0.2839 1.935

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:2600::99 (ntp1.wiktel.com)

peer jitter 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 0.000 0.000 0.000 1.922 1.922 1.922 1.922 1.922 1.922 0.961 0.961 ms 0 1

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net)

peer jitter 2600:3c00:e000:256::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) 0.000 0.890 1.356 3.377 17.886 36.557 125.199 16.531 35.668 7.187 5.405 ms 6.571 77.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 2600:3c00:e000:318::1 (jane.qotw.net)

peer jitter 2600:3c00:e000:318::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c00:e000:318::1 (jane.qotw.net) 0.000 0.936 1.251 3.291 18.596 45.542 55.919 17.345 44.606 7.258 5.661 ms 3.76 20.2

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw)

peer jitter 2600:3c01::f03c:93ff:fe5b:8a7d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) 0.000 0.000 0.000 6.110 10.609 10.609 10.609 10.609 10.609 3.299 4.985 ms 0.1951 2.331

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com)

peer jitter 2600:3c01::f03c:93ff:fedd:5a1f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com) 0.000 0.000 0.000 7.022 69.185 74.278 74.278 69.185 74.278 19.927 15.358 ms 1.999 5.824

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c01:e000:7e6::123 (time1.sigi.net)

peer jitter 2600:3c01:e000:7e6::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c01:e000:7e6::123 (time1.sigi.net) 0.000 0.678 1.268 3.194 8.827 20.528 87.783 7.559 19.850 4.877 4.124 ms 8.554 112.3

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c02::f03c:92ff:fe96:dc0

peer jitter 2600:3c02::f03c:92ff:fe96:dc0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02::f03c:92ff:fe96:dc0 0.000 0.719 1.293 3.642 35.596 64.763 70.185 34.303 64.043 13.117 8.439 ms 3.086 12.43

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c02::f03c:94ff:fe59:f411

peer jitter 2600:3c02::f03c:94ff:fe59:f411 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02::f03c:94ff:fe59:f411 0.000 0.000 0.000 5.394 7.516 7.516 7.516 7.516 7.516 2.647 4.557 ms -0.5602 1.96

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net)

peer jitter 2600:3c02:e000:74::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net) 0.000 0.698 1.366 3.382 13.487 24.586 25.970 12.121 23.888 4.296 4.750 ms 2.388 9.659

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net)

peer jitter 2600:3c02:e000:bc::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) 0.000 0.000 0.717 3.878 10.414 16.432 16.432 9.697 16.432 3.233 4.061 ms 1.999 7.801

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net)

peer jitter 2600:3c02:e001:1d00::123:0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) 0.000 0.000 0.000 4.625 9.182 9.182 9.182 9.182 9.182 3.008 4.335 ms -0.05862 1.872

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net)

peer jitter 2600:3c03::f03c:91ff:fedf:1e98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) 0.000 0.000 1.722 5.665 14.088 67.952 94.476 12.366 67.952 9.525 7.349 ms 6.462 52.16

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c03::f03c:94ff:fe59:d3de

peer jitter 2600:3c03::f03c:94ff:fe59:d3de plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c03::f03c:94ff:fe59:d3de 0.000 0.000 0.000 9.141 10.648 10.648 10.648 10.648 10.648 4.705 6.597 ms -0.6531 1.5

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c03:e002:1300::10 (ntp.electronmill.com)

peer jitter 2600:3c03:e002:1300::10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c03:e002:1300::10 (ntp.electronmill.com) 0.000 0.000 0.000 3.877 7.718 7.718 7.718 7.718 7.718 2.384 3.718 ms 0.3575 1.964

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c06::f03c:94ff:fee2:9c28

peer jitter 2600:3c06::f03c:94ff:fee2:9c28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c06::f03c:94ff:fee2:9c28 0.000 0.000 0.000 9.325 30.736 30.736 30.736 30.736 30.736 11.553 11.593 ms 0.8589 2.149

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:3c06::f03c:94ff:fee2:c53a

peer jitter 2600:3c06::f03c:94ff:fee2:c53a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c06::f03c:94ff:fee2:c53a 0.000 0.000 0.000 15.615 24.117 24.117 24.117 24.117 24.117 9.987 13.244 ms -0.3427 1.5

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2600:4040:3037:e600::1

peer jitter 2600:4040:3037:e600::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:4040:3037:e600::1 2.236 2.236 2.236 3.952 3.952 3.952 3.952 1.716 1.716 0.858 3.094 ms 8.189e-16 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 2600:4040:e0da:f000::cbb9:201a

peer jitter 2600:4040:e0da:f000::cbb9:201a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:4040:e0da:f000::cbb9:201a 0.000 0.000 0.547 12.110 32.149 45.133 45.133 31.602 45.133 10.649 11.858 ms 1.048 3.818

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:291:69::8 (time2.tritan-bb.net)

peer jitter 2602:291:69::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:291:69::8 (time2.tritan-bb.net) 0.000 0.000 0.000 0.970 1.844 1.844 1.844 1.844 1.844 0.552 0.976 ms -0.2468 2.677

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:291:69::9 (time.tritan-bb.net)

peer jitter 2602:291:69::9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:291:69::9 (time.tritan-bb.net) 0.000 0.000 0.000 2.935 6.266 9.048 9.048 6.266 9.048 1.880 2.793 ms 0.9925 5.049

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net)

peer jitter 2602:2b7:d11:f4::122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) 0.000 0.884 1.326 3.508 14.465 35.541 139.194 13.139 34.657 7.489 5.097 ms 8.397 106.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 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net)

peer jitter 2602:2b7:d11:f4::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net) 0.000 0.000 0.000 1.197 1.816 1.816 1.816 1.816 1.816 0.754 1.004 ms -0.3667 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 2602:2eb:2:95:1234:5678:9abc:def0

peer jitter 2602:2eb:2:95:1234:5678:9abc:def0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:2eb:2:95:1234:5678:9abc:def0 0.000 0.928 1.412 3.654 26.243 55.859 262.579 24.831 54.931 13.247 7.544 ms 8.809 126

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:80b:5000::36 (time.meme.holdings)

peer jitter 2602:80b:5000::36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:80b:5000::36 (time.meme.holdings) 0.000 0.000 4.621 20.856 76.477 84.174 87.838 71.856 84.174 21.252 27.684 ms 0.9659 3.216

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com)

peer jitter 2602:81b:9000::c10c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) 0.000 0.000 0.000 4.593 9.349 9.349 9.349 9.349 9.349 2.587 4.904 ms -0.09123 2.375

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net)

peer jitter 2602:f9ba:69::210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) 0.000 0.000 1.448 5.641 57.096 77.816 96.144 55.648 77.816 18.597 13.597 ms 2.205 7.472

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:fb95:16::123 (time5.sigi.net)

peer jitter 2602:fb95:16::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fb95:16::123 (time5.sigi.net) 0.000 0.000 0.000 2.945 6.744 6.744 6.744 6.744 6.744 1.680 2.843 ms 0.7474 3.802

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:fc2f:100:9800::dead:beef

peer jitter 2602:fc2f:100:9800::dead:beef plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fc2f:100:9800::dead:beef 0.000 1.459 2.342 5.503 62.283 166.197 259.248 59.941 164.738 29.640 14.817 ms 4.483 25.63

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com)

peer jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) 0.000 0.000 0.000 1.961 5.599 9.370 9.370 5.599 9.370 2.184 2.731 ms 1.202 4.547

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:fe2e:3:d:f9:c7ff:fef5:379c

peer jitter 2602:fe2e:3:d:f9:c7ff:fef5:379c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fe2e:3:d:f9:c7ff:fef5:379c 0.000 0.000 0.000 2.011 3.424 3.424 3.424 3.424 3.424 0.929 1.786 ms -0.1796 2.962

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:ff06:725:100::123 (oldtime2.sigi.net)

peer jitter 2602:ff06:725:100::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:ff06:725:100::123 (oldtime2.sigi.net) 0.000 0.000 0.000 1.447 6.369 6.369 6.369 6.369 6.369 1.854 1.683 ms 1.874 5.218

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s 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:ff23:50:3c2::1 (dns-e.ns4v.icu)

peer jitter 2602:ff23:50:3c2::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:ff23:50:3c2::1 (dns-e.ns4v.icu) 0.000 1.222 1.475 4.424 42.112 69.376 73.583 40.637 68.154 12.937 8.366 ms 3.413 14.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 2603:c020:0:8369:0:ba11:ba11:ba11

peer jitter 2603:c020:0:8369:0:ba11:ba11:ba11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369:0:ba11:ba11:ba11 0.000 0.000 0.000 4.189 14.814 17.914 17.914 14.814 17.914 4.131 4.795 ms 1.397 5.064

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2603:c020:0:8369:1111:1111:1111:1112

peer jitter 2603:c020:0:8369:1111:1111:1111:1112 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369:1111:1111:1111:1112 0.000 0.000 0.000 3.258 74.324 99.180 99.180 74.324 99.180 21.368 13.977 ms 2.367 8.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 2603:c020:0:8369::bad:beef

peer jitter 2603:c020:0:8369::bad:beef plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369::bad:beef 0.000 0.000 0.000 3.940 3.991 3.991 3.991 3.991 3.991 1.645 2.811 ms -1.067 2.256

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2603:c020:0:8369::f00d:feed

peer jitter 2603:c020:0:8369::f00d:feed plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369::f00d:feed 0.000 0.000 0.000 3.051 11.156 19.041 19.041 11.156 19.041 4.036 4.160 ms 2.143 8.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 2603:c020:0:8369::feeb:dab

peer jitter 2603:c020:0:8369::feeb:dab plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369::feeb:dab 0.000 0.000 0.000 3.443 11.129 12.564 12.564 11.129 12.564 3.141 3.778 ms 1.064 3.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 2603:c020:0:8369:feed:feed:feed:feed

peer jitter 2603:c020:0:8369:feed:feed:feed:feed plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:0:8369:feed:feed:feed:feed 0.000 0.000 0.000 3.112 13.323 13.323 13.323 13.323 13.323 3.317 3.712 ms 1.612 5.406

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2603:c020:6:b900:6b54:1390:4afd:814a

peer jitter 2603:c020:6:b900:6b54:1390:4afd:814a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:6:b900:6b54:1390:4afd:814a 0.000 0.000 0.000 4.457 16.191 16.191 16.191 16.191 16.191 4.707 5.327 ms 0.744 2.635

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2603:c020:6:b900:ed2f:b442:fee7:d9b9

peer jitter 2603:c020:6:b900:ed2f:b442:fee7:d9b9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c020:6:b900:ed2f:b442:fee7:d9b9 0.000 0.000 0.000 2.967 6.929 6.929 6.929 6.929 6.929 2.490 2.410 ms 0.6756 2.153

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2603:c024:c005:a600:efb6:d213:cad8:251d

peer jitter 2603:c024:c005:a600:efb6:d213:cad8:251d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2603:c024:c005:a600:efb6:d213:cad8:251d 0.000 0.000 0.000 14.820 57.595 57.595 57.595 57.595 57.595 17.229 20.244 ms 1.209 3.457

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1

peer jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 0.000 0.000 1.769 15.711 48.002 49.094 49.094 46.233 49.094 11.410 15.959 ms 1.156 4.594

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:100:4d6::

peer jitter 2604:2dc0:100:4d6:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:100:4d6:: 0.000 0.000 0.000 3.514 4.351 4.351 4.351 4.351 4.351 1.632 2.616 ms -0.6871 1.99

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us)

peer jitter 2604:2dc0:101:200::151 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) 0.000 0.000 0.000 2.991 9.649 9.649 9.649 9.649 9.649 2.561 3.518 ms 1.144 3.781

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:202:300::140d (ovh.maxhost.io)

peer jitter 2604:2dc0:202:300::140d plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:202:300::140d (ovh.maxhost.io) 0.000 0.965 1.366 3.498 9.087 21.237 71.985 7.721 20.272 3.773 4.317 ms 5.523 60.29

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com)

peer jitter 2604:2dc0:202:300::2459 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) 0.000 0.906 1.363 3.338 10.703 34.136 119.042 9.340 33.230 6.208 4.661 ms 7.131 78.29

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:4300:a:299::164

peer jitter 2604:4300:a:299::164 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:4300:a:299::164 0.000 0.000 0.000 3.582 6.183 11.304 11.304 6.183 11.304 2.417 3.650 ms 1.209 5.485

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:4500:6:7c9::186 (us-east-2.clearnet.pw)

peer jitter 2604:4500:6:7c9::186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) 0.000 0.000 0.000 3.639 13.829 13.829 13.829 13.829 13.829 3.432 4.353 ms 1.336 4.939

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com)

peer jitter 2604:8800:52:81:38:229:52:9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) 0.000 0.000 0.000 21.487 31.405 31.405 31.405 31.405 31.405 13.108 17.631 ms -0.4158 1.5

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer jitter 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.000 0.000 0.869 1.657 1.657 1.657 1.657 1.657 0.479 0.845 ms -0.09905 2.996

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:1:20::1fd:1001 (jitter.tickadj.net)

peer jitter 2604:a880:1:20::1fd:1001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) 0.000 0.965 1.447 3.716 18.849 29.446 120.523 17.402 28.481 10.597 5.665 ms 8.209 79.46

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:400:d0::4ed:f001 (unifi.versadns.com)

peer jitter 2604:a880:400:d0::4ed:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) 0.000 0.000 0.000 8.010 25.574 25.574 25.574 25.574 25.574 6.576 8.369 ms 0.7283 3.152

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:800:10::70f:b001 (ellone.fdisk.io)

peer jitter 2604:a880:800:10::70f:b001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:800:10::70f:b001 (ellone.fdisk.io) 0.000 0.000 0.000 1.765 3.857 3.857 3.857 3.857 3.857 1.036 1.790 ms 0.1052 2.65

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:a880:800:a1::ec9:5001

peer jitter 2604:a880:800:a1::ec9:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:800:a1::ec9:5001 0.000 0.000 0.000 3.038 144.987 144.987 144.987 144.987 144.987 40.690 27.266 ms 1.51 4.267

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2604:d200::39 (white.web-ster.com)

peer jitter 2604:d200::39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:d200::39 (white.web-ster.com) 0.000 0.000 0.000 1.874 3.949 3.949 3.949 3.949 3.949 1.165 1.768 ms 0.2062 2.03

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s 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 3.032 6.591 21.939 58.467 76.100 242.923 51.875 73.068 18.011 25.799 ms 3.949 40.23

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471

peer jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ns nan nan

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2605:6400:488d:3686:546d:c03c:1689:20c

peer jitter 2605:6400:488d:3686:546d:c03c:1689:20c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:6400:488d:3686:546d:c03c:1689:20c 0.000 0.000 0.000 1.372 9.116 9.116 9.116 9.116 9.116 3.886 3.057 ms 0.6883 1.57

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2605:6400:84e1::123 (oldtime3.sigi.net)

peer jitter 2605:6400:84e1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:6400:84e1::123 (oldtime3.sigi.net) 0.000 0.000 0.000 3.606 8.882 8.882 8.882 8.882 8.882 2.455 3.745 ms 0.4362 2.81

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de)

peer jitter 2605:6f01:2000:18::94ee:fcbe plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) 0.000 0.000 0.000 3.793 7.878 7.878 7.878 7.878 7.878 2.024 4.070 ms 0.0771 3.251

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2606:4700:f1::1 (time.cloudflare.com)

peer jitter 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.870 1.293 3.423 17.848 46.658 400.941 16.555 45.788 11.016 5.704 ms 13.69 329

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2606:4700:f1::123 (time.cloudflare.com)

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.856 1.266 3.382 16.072 47.481 176.369 14.806 46.625 8.785 5.361 ms 7.855 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 2606:82c0:21::e (time1.lshiy.com)

peer jitter 2606:82c0:21::e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:82c0:21::e (time1.lshiy.com) 0.000 0.000 0.000 1.883 3.565 3.565 3.565 3.565 3.565 1.027 1.940 ms -0.3172 2.792

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2606:82c0:22::e (time2.lshiy.com)

peer jitter 2606:82c0:22::e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:82c0:22::e (time2.lshiy.com) 0.000 0.000 0.000 5.461 24.843 24.843 24.843 24.843 24.843 7.408 7.371 ms 1.48 4.108

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2606:82c0:23::e (time3.lshiy.com)

peer jitter 2606:82c0:23::e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:82c0:23::e (time3.lshiy.com) 0.000 0.000 0.000 3.337 8.248 8.248 8.248 8.248 8.248 2.270 3.415 ms 0.3181 2.67

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:5600:182:500::1 (ntp-1.jonlight.com)

peer jitter 2607:5600:182:500::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:5600:182:500::1 (ntp-1.jonlight.com) 0.000 0.000 0.000 10.156 45.021 45.021 45.021 45.021 45.021 12.499 11.485 ms 1.431 4.572

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:7c80:54:3::32

peer jitter 2607:7c80:54:3::32 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:7c80:54:3::32 0.000 0.928 1.517 3.611 16.831 44.803 127.511 15.314 43.875 7.844 5.548 ms 6.416 63.26

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:7c80:54:3::56 (owners.kjsl.com)

peer jitter 2607:7c80:54:3::56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:7c80:54:3::56 (owners.kjsl.com) 0.000 0.000 1.298 3.181 22.900 24.794 24.794 21.602 24.794 5.837 5.520 ms 2.225 7.106

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:9000:7000:23:216:3cff:fe25:38d7

peer jitter 2607:9000:7000:23:216:3cff:fe25:38d7 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:9000:7000:23:216:3cff:fe25:38d7 0.000 0.598 1.211 3.188 11.275 18.776 101.037 10.064 18.178 7.917 4.641 ms 9.393 106.3

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:9d00:2000:16::9269:208a

peer jitter 2607:9d00:2000:16::9269:208a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:9d00:2000:16::9269:208a 0.000 0.000 0.000 3.585 32.658 32.768 32.768 32.658 32.768 8.863 6.355 ms 2.336 7.193

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:b500:410:7700::1

peer jitter 2607:b500:410:7700::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:b500:410:7700::1 0.000 0.000 0.000 3.930 45.395 48.813 48.813 45.395 48.813 12.860 8.432 ms 2.364 7.345

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f1c0:f014:9e00::1

peer jitter 2607:f1c0:f014:9e00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f014:9e00::1 0.000 0.000 0.000 4.356 10.370 10.370 10.370 10.370 10.370 2.391 5.036 ms 0.1939 4.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 2607:f1c0:f014:9e00::2

peer jitter 2607:f1c0:f014:9e00::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f014:9e00::2 0.000 0.000 0.000 4.033 19.038 31.195 31.195 19.038 31.195 7.047 6.391 ms 1.868 6.607

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f1c0:f04e:fd00::1

peer jitter 2607:f1c0:f04e:fd00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f04e:fd00::1 0.000 0.000 0.000 4.264 7.362 7.362 7.362 7.362 7.362 2.269 3.950 ms -0.238 2.144

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at)

peer jitter 2607:f1c0:f06b:5000:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) 0.000 0.000 0.000 3.311 58.981 58.981 58.981 58.981 58.981 21.215 11.609 ms 1.777 4.18

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at)

peer jitter 2607:f1c0:f06b:5000::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) 0.000 0.000 0.000 2.585 3.939 3.939 3.939 3.939 3.939 1.251 2.204 ms -0.4741 2.288

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at)

peer jitter 2607:f1c0:f06b:5000::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at) 0.000 0.000 0.000 1.285 1.285 1.285 1.285 1.285 1.285 0.642 0.642 ms 0 1

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at)

peer jitter 2607:f1c0:f06b:5000::3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) 0.000 0.000 0.000 7.684 11.739 11.739 11.739 11.739 11.739 3.498 6.746 ms -0.5998 2.636

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at)

peer jitter 2607:f1c0:f06b:5000::4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) 0.000 0.000 0.000 3.713 17.103 17.166 17.166 17.103 17.166 4.236 4.518 ms 1.905 6.172

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f1c0:f075:9900::1

peer jitter 2607:f1c0:f075:9900::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f1c0:f075:9900::1 0.000 0.000 0.000 3.194 62.537 70.431 70.431 62.537 70.431 17.930 9.867 ms 2.624 8.577

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f298:5:101d:f816:3eff:fefd:8817

peer jitter 2607:f298:5:101d:f816:3eff:fefd:8817 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f298:5:101d:f816:3eff:fefd:8817 0.000 0.000 0.000 3.238 15.794 15.794 15.794 15.794 15.794 3.672 4.170 ms 1.423 5.487

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f3c8:3803:1::6

peer jitter 2607:f3c8:3803:1::6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f3c8:3803:1::6 0.000 0.000 0.000 3.665 9.888 9.888 9.888 9.888 9.888 3.130 3.728 ms 0.7664 2.592

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net)

peer jitter 2607:f5b7:1:44::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) 0.000 0.000 0.000 7.826 42.881 42.881 42.881 42.881 42.881 11.996 12.673 ms 0.9758 3.228

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f710:35::29c:0:1 (ntp6.kernfusion.at)

peer jitter 2607:f710:35::29c:0:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) 0.000 0.000 0.000 2.953 7.543 7.543 7.543 7.543 7.543 1.917 3.128 ms 0.7412 3.627

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f710:35::29c:0:5

peer jitter 2607:f710:35::29c:0:5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f710:35::29c:0:5 0.000 0.000 0.000 4.556 7.900 7.900 7.900 7.900 7.900 2.166 4.553 ms -0.3058 2.962

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f710:35::29c:0:8

peer jitter 2607:f710:35::29c:0:8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f710:35::29c:0:8 0.000 0.993 1.374 7.413 35.124 57.993 80.866 33.750 57.000 11.814 11.251 ms 2.307 10.35

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net)

peer jitter 2607:ff50:0:1a::10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) 0.000 0.000 0.000 4.417 9.460 9.460 9.460 9.460 9.460 2.696 4.546 ms -0.0246 2.498

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com)

peer jitter 2607:ff50:0:20::5ca1:ab1e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com) 0.000 0.000 0.000 1.304 6.107 6.107 6.107 6.107 6.107 2.114 2.122 ms 1.095 2.75

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com)

peer jitter 2620:138:5000:0:5054:ff:fe89:6673 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com) 0.389 0.850 1.301 3.293 9.081 28.609 88.888 7.780 27.759 6.619 4.409 ms 9.184 104.7

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com)

peer jitter 2620:149:a23:4000::1e2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com) 0.763 1.018 1.571 3.635 13.134 29.896 108.020 11.564 28.878 6.313 5.059 ms 7.953 100.3

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:83:8000:140::b (tic.lbl.gov)

peer jitter 2620:83:8000:140::b plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:83:8000:140::b (tic.lbl.gov) 0.000 0.880 1.380 3.683 18.060 54.396 107.171 16.680 53.516 8.265 5.655 ms 5.524 41.14

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:83:8000:140::c (toc.lbl.gov)

peer jitter 2620:83:8000:140::c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:83:8000:140::c (toc.lbl.gov) 0.000 1.106 1.584 3.636 9.935 22.754 23.037 8.351 21.648 3.401 4.570 ms 2.971 15.07

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:8d:c000::f (blotch.image1tech.net)

peer jitter 2620:8d:c000::f plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:8d:c000::f (blotch.image1tech.net) 0.000 0.000 0.000 11.399 23.001 23.001 23.001 23.001 23.001 6.886 11.933 ms -0.1456 2.635

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com)

peer jitter 2620:9a:e000:1061::2:165 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) 0.000 0.000 0.000 4.268 26.331 26.331 26.331 26.331 26.331 6.810 6.258 ms 1.9 6.02

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:b0:2000:102::1:123 (time-h.den.codehof.net)

peer jitter 2620:b0:2000:102::1:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:b0:2000:102::1:123 (time-h.den.codehof.net) 0.000 0.000 0.000 44.659 162.644 162.644 162.644 162.644 162.644 50.617 46.606 ms 1.096 3.207

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:b0:2000:102::2:123 (time-he.den.codehof.net)

peer jitter 2620:b0:2000:102::2:123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:b0:2000:102::2:123 (time-he.den.codehof.net) 0.000 0.000 0.000 5.132 67.520 67.520 67.520 67.520 67.520 21.171 12.422 ms 2.131 5.771

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl)

peer jitter 2a00:d78:0:712:94:198:159:11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.000 1.746 3.432 19.222 65.886 87.844 263.025 62.453 86.098 21.462 25.498 ms 2.427 19.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 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se)

peer jitter 2a01:3f7:2:44::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 0.000 2.767 9.755 52.101 99.337 113.836 271.797 89.581 111.069 27.066 53.252 ms 0.365 3.471

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se)

peer jitter 2a01:3f7:2:44::9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) 0.000 2.475 6.684 48.771 96.527 110.599 234.358 89.842 108.124 27.198 49.433 ms 0.3041 2.82

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a01:4ff:f0:e33b::1

peer jitter 2a01:4ff:f0:e33b::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:4ff:f0:e33b::1 0.000 0.944 1.261 3.012 9.326 19.960 20.195 8.065 19.016 2.989 3.742 ms 3.166 15.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 2a01:4ff:f0:ebce::1

peer jitter 2a01:4ff:f0:ebce::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:4ff:f0:ebce::1 0.000 0.000 0.000 25.847 25.847 25.847 25.847 25.847 25.847 12.924 12.924 ms 0 1

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com)

peer jitter 2a01:7e03::f03c:95ff:fef8:ac8c plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) 0.000 0.000 0.000 32.068 70.288 70.288 70.288 70.288 70.288 19.572 34.261 ms 0.1428 3.002

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a01:7e04::f03c:94ff:fee2:cba5

peer jitter 2a01:7e04::f03c:94ff:fee2:cba5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:7e04::f03c:94ff:fee2:cba5 0.000 0.000 0.000 1.794 29.750 29.750 29.750 29.750 29.750 9.167 5.895 ms 1.677 4.108

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media)

peer jitter 2a05:dfc1:cb1:201:: plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) 0.000 0.000 0.838 3.220 6.015 8.943 9.058 5.177 8.943 1.630 3.368 ms 0.7999 4.534

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s 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.961 2.019 18.606 65.177 89.803 166.058 63.158 88.842 22.126 25.010 ms 1.748 8.655

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 37.27.11.4

peer jitter 37.27.11.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 37.27.11.4 0.000 0.000 1.780 14.020 76.180 81.696 81.940 74.400 81.696 20.637 20.684 ms 1.598 4.786

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 44.190.5.123

peer jitter 44.190.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 44.190.5.123 0.000 0.808 1.180 3.171 12.375 25.655 625.327 11.195 24.847 9.759 4.623 ms 37.41 2204

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s 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.126.202

peer jitter 45.55.126.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.55.126.202 0.000 0.847 1.361 4.011 21.385 56.733 76.922 20.024 55.886 9.351 7.409 ms 3.66 20.15

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.61.187.39

peer jitter 45.61.187.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.61.187.39 0.000 0.000 0.000 6.005 10.131 10.131 10.131 10.131 10.131 3.234 5.663 ms -0.1351 2.072

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s 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.750 1.267 3.451 16.818 30.433 69.818 15.550 29.683 6.186 5.088 ms 4.745 33.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 45.77.126.122

peer jitter 45.77.126.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.77.126.122 0.000 0.000 0.000 1.018 3.979 3.979 3.979 3.979 3.979 0.941 1.194 ms 1.581 5.687

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.79.35.159

peer jitter 45.79.35.159 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.79.35.159 0.000 0.000 0.000 0.712 4.702 4.702 4.702 4.702 4.702 1.855 1.527 ms 1.069 2.278

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.79.51.42

peer jitter 45.79.51.42 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.79.51.42 0.000 0.000 0.000 11.729 96.151 96.151 96.151 96.151 96.151 29.987 22.678 ms 1.636 4.376

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.83.234.123

peer jitter 45.83.234.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.83.234.123 0.000 0.000 0.000 38.377 69.832 100.538 100.538 69.832 100.538 25.273 34.042 ms 0.07115 2.108

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.84.199.136

peer jitter 45.84.199.136 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.84.199.136 0.000 0.000 0.000 7.227 34.845 34.845 34.845 34.845 34.845 11.450 10.051 ms 1.254 3.184

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 46.37.96.107

peer jitter 46.37.96.107 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 46.37.96.107 0.000 0.762 1.136 3.173 17.249 45.839 76.855 16.113 45.077 7.508 5.080 ms 4.938 32.2

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.774 1.053 1.418 3.434 16.082 36.133 46.484 14.665 35.080 5.774 5.434 ms 3.496 19.16

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 5.78.62.36

peer jitter 5.78.62.36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.78.62.36 0.000 0.814 1.189 3.214 7.458 14.625 17.905 6.268 13.811 2.404 3.674 ms 2.621 12.87

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 50.117.3.52

peer jitter 50.117.3.52 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.117.3.52 0.000 0.000 0.000 1.241 1.948 1.948 1.948 1.948 1.948 0.616 1.028 ms -0.1887 2.181

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 50.117.3.95

peer jitter 50.117.3.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.117.3.95 0.000 0.000 0.000 4.938 9.600 9.600 9.600 9.600 9.600 3.585 4.705 ms -0.06002 1.66

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 50.205.57.38

peer jitter 50.205.57.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.205.57.38 0.000 0.865 1.243 3.327 19.270 37.488 52.487 18.027 36.624 7.055 6.159 ms 2.927 14.35

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 50.218.103.254

peer jitter 50.218.103.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.218.103.254 0.000 0.000 0.000 1.360 15.596 15.596 15.596 15.596 15.596 4.714 2.924 ms 2.06 5.866

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 51.81.20.76

peer jitter 51.81.20.76 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 51.81.20.76 0.000 0.000 0.000 2.794 18.439 18.439 18.439 18.439 18.439 4.702 4.747 ms 2.128 6.656

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 51.81.226.229

peer jitter 51.81.226.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 51.81.226.229 0.000 0.000 0.000 3.776 10.325 13.199 13.199 10.325 13.199 3.650 4.396 ms 0.7568 2.753

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 64.142.54.12

peer jitter 64.142.54.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.142.54.12 0.000 0.000 0.000 4.301 11.521 11.521 11.521 11.521 11.521 2.947 4.784 ms 0.8351 3.574

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 64.6.144.6

peer jitter 64.6.144.6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.6.144.6 0.000 0.000 0.000 3.288 4.846 4.846 4.846 4.846 4.846 1.639 2.872 ms -0.6172 2.185

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 64.79.100.197

peer jitter 64.79.100.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.79.100.197 0.000 0.000 0.817 2.208 16.989 29.767 29.820 16.172 29.767 5.117 3.706 ms 3.407 14.88

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 65.100.46.164

peer jitter 65.100.46.164 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 65.100.46.164 0.000 0.902 1.495 3.180 12.652 17.404 21.093 11.158 16.502 3.401 4.380 ms 2.274 8.459

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s 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.100.46.166

peer jitter 65.100.46.166 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 65.100.46.166 0.000 0.877 1.365 3.588 16.248 25.653 30.128 14.883 24.777 4.652 4.994 ms 2.701 11.07

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 65.182.224.39

peer jitter 65.182.224.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 65.182.224.39 0.000 0.000 0.000 2.070 2.943 2.943 2.943 2.943 2.943 0.933 1.809 ms -0.8566 2.777

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.118.231.14

peer jitter 66.118.231.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.118.231.14 0.000 0.000 0.000 27.185 55.552 77.497 77.497 55.552 77.497 20.613 27.535 ms 0.1157 1.981

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.42.71.197

peer jitter 66.42.71.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.42.71.197 0.000 0.804 1.223 3.207 11.673 20.952 36.891 10.450 20.148 3.804 4.239 ms 3.293 17.16

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.59.198.94

peer jitter 66.59.198.94 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.59.198.94 0.000 0.000 0.000 4.307 12.760 12.760 12.760 12.760 12.760 3.136 4.798 ms 1.209 4.406

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.85.78.80

peer jitter 66.85.78.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.85.78.80 0.000 0.000 0.000 2.718 5.161 5.161 5.161 5.161 5.161 2.005 2.147 ms 0.4553 1.672

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 67.217.246.127

peer jitter 67.217.246.127 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 67.217.246.127 0.000 0.544 1.405 3.301 20.244 36.524 37.261 18.839 35.979 7.198 6.206 ms 2.642 10.4

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 67.217.246.204

peer jitter 67.217.246.204 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 67.217.246.204 0.000 0.000 1.289 5.632 23.748 37.970 47.481 22.460 37.970 8.234 9.205 ms 1.646 6.413

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 68.234.48.70

peer jitter 68.234.48.70 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 68.234.48.70 0.000 0.000 0.000 15.255 37.426 37.426 37.426 37.426 37.426 11.694 11.915 ms 0.673 2.554

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 69.176.84.38

peer jitter 69.176.84.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.176.84.38 0.000 0.000 0.084 1.877 4.514 6.761 6.761 4.430 6.761 1.315 2.063 ms 1.34 5.848

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 69.48.203.16

peer jitter 69.48.203.16 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.48.203.16 0.000 0.000 0.000 2.915 5.617 5.617 5.617 5.617 5.617 1.492 2.928 ms -0.1583 2.911

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 69.89.207.199

peer jitter 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.89.207.199 0.000 0.768 1.592 3.907 13.653 64.615 103.870 12.061 63.847 9.526 5.771 ms 8.019 76.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 69.89.207.99

peer jitter 69.89.207.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.89.207.99 0.000 0.655 1.014 2.890 14.394 29.375 217.779 13.380 28.720 10.452 4.992 ms 13.28 242.1

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 71.123.46.186

peer jitter 71.123.46.186 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 71.123.46.186 0.000 0.798 1.369 11.462 50.388 59.457 63.511 49.020 58.659 13.810 13.720 ms 1.912 6.345

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 71.19.144.140

peer jitter 71.19.144.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 71.19.144.140 0.000 0.000 0.000 2.244 28.288 28.288 28.288 28.288 28.288 6.176 4.071 ms 3.331 13.18

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 72.14.183.39

peer jitter 72.14.183.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.14.183.39 0.000 0.000 0.000 2.885 5.156 5.156 5.156 5.156 5.156 1.696 2.895 ms -0.4921 2.349

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 72.14.186.59

peer jitter 72.14.186.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.14.186.59 0.000 0.000 0.000 1.353 7.812 7.812 7.812 7.812 7.812 2.791 2.333 ms 1.36 3.086

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 72.30.35.89

peer jitter 72.30.35.89 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.30.35.89 0.000 0.000 0.000 0.779 4.898 4.898 4.898 4.898 4.898 2.149 1.892 ms 0.6381 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 72.46.53.234

peer jitter 72.46.53.234 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.46.53.234 0.000 0.000 0.000 3.818 99.485 99.485 99.485 99.485 99.485 27.363 16.024 ms 2.181 6.785

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 72.46.61.205

peer jitter 72.46.61.205 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.46.61.205 0.000 0.000 0.000 41.508 79.056 79.056 79.056 79.056 79.056 23.710 34.029 ms -0.07087 1.973

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 73.185.182.209

peer jitter 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.185.182.209 0.000 1.188 1.697 3.815 25.345 43.709 79.900 23.648 42.521 9.600 8.061 ms 2.934 14.97

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 73.65.80.137

peer jitter 73.65.80.137 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.65.80.137 0.000 0.000 1.979 4.758 26.082 30.271 30.271 24.103 30.271 7.745 8.134 ms 1.314 3.612

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 74.119.243.5

peer jitter 74.119.243.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 74.119.243.5 0.000 0.000 0.000 3.388 6.563 6.563 6.563 6.563 6.563 2.635 2.597 ms 0.4823 1.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 74.208.117.38

peer jitter 74.208.117.38 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 74.208.117.38 0.000 0.000 0.000 5.816 17.030 17.030 17.030 17.030 17.030 4.139 6.213 ms 1.416 5.194

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 74.208.14.149

peer jitter 74.208.14.149 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 74.208.14.149 0.000 0.000 0.000 8.875 13.149 13.149 13.149 13.149 13.149 4.272 6.919 ms -0.2182 2.001

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 74.208.25.46

peer jitter 74.208.25.46 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 74.208.25.46 0.000 1.633 2.195 4.561 14.012 52.935 406.747 11.817 51.301 15.656 6.906 ms 15.62 327.6

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 77.37.97.124

peer jitter 77.37.97.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.37.97.124 0.000 0.986 2.855 28.267 70.810 85.923 150.671 67.955 84.937 22.534 30.520 ms 0.9612 4.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 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.729 14.489 90.080 103.942 103.942 87.351 103.942 28.486 27.686 ms 1.277 3.184

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 83.147.242.172

peer jitter 83.147.242.172 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 83.147.242.172 0.000 0.844 1.213 3.146 7.606 19.766 60.098 6.393 18.922 3.506 3.831 ms 6.515 74.75

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 94.198.159.11

peer jitter 94.198.159.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 94.198.159.11 0.000 0.000 0.000 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 99.28.14.242

peer jitter 99.28.14.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 99.28.14.242 0.000 0.841 1.296 3.369 21.031 62.332 94.505 19.735 61.491 9.798 6.251 ms 5.026 34.5

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



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.467 0.692 1.688 3.971 5.329 745.507 3.279 4.862 4.110 1.971 ms 163.5 2.951e+04

The RMS Jitter of a local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(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.191 0.216 0.313 0.462 0.554 96.676 0.246 0.364 0.677 0.335 ms 96.23 1.147e+04

The RMS Jitter of a local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(2)

peer jitter SHM(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(2) 0.000 0.621 1.013 22.720 62.605 96.386 2,002.029 61.592 95.765 23.522 24.963 ms 5.25 270.9

The RMS Jitter of a local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(3)

peer jitter SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(3) 0.000 0.053 0.073 0.254 0.751 1.030 2,001.141 0.677 0.977 8.171 0.351 ms 187.6 3.727e+04

The RMS Jitter of a local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SOCK(0)

peer jitter SOCK(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SOCK(0) 0.000 0.451 0.658 1.622 4.097 7.521 199.488 3.438 7.070 2.193 1.979 ms 33.87 2074

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.202 0.228 0.344 0.696 0.956 104.304 0.469 0.754 0.542 0.389 ms 122 1.84e+04

The RMS Jitter of a local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SOCK(2)

peer jitter SOCK(2) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SOCK(2) 0.000 0.600 0.948 2.374 5.637 7.241 11.212 4.689 6.641 1.481 2.715 ms 1.233 5.001

The RMS Jitter of a local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SOCK(3)

peer jitter SOCK(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SOCK(3) 0.000 0.196 0.221 0.324 0.536 0.729 3,009.547 0.315 0.533 17.171 0.461 ms 152.2 2.388e+04

The RMS Jitter of a local refclock. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -135.511 2.905 4.604 11.075 21.876 25.051 61.826 17.272 22.146 4.617 11.846 ppm 0.8242 7.031
Local Clock Time Offset -95.988 -8.033 -4.963 -0.058 0.658 1.157 105.238 5.620 9.191 1.903 -0.585 ms -0.027 219.6
Local RMS Frequency Jitter 0.0000 0.0033 0.0041 0.0162 2.670 3.670 73.177 2.666 3.666 0.960 0.524 ppm 8.769 418.7
Local RMS Time Jitter 0.000 0.092 0.113 0.293 0.856 1.353 52.058 0.743 1.260 0.494 0.367 ms 43.07 3124
Refclock Offset SHM(0) -865.294 -187.488 -184.773 -160.162 -121.774 -118.285 -66.245 63.000 69.203 20.226 -162.204 ms -0.4126 42.68
Refclock Offset SHM(1) -43.998 -8.669 -8.296 -4.893 0.084 0.281 52.678 8.380 8.951 2.280 -4.795 ms 0.9182 15.25
Refclock Offset SHM(2) -485.911 -173.937 -154.140 -0.113 8.457 17.453 1,940.513 162.597 191.390 47.916 -19.386 ms -1.858 19.48
Refclock Offset SHM(3) -13.801 -8.355 -5.705 -0.426 0.409 0.866 2,061.810 6.113 9.222 6.664 -1.098 ms 273.7 8.273e+04
Refclock Offset SOCK(0) -597.294 -177.834 -174.616 -0.939 7.355 181.993 236.678 181.971 359.827 80.136 -30.176 ms -0.5305 3.565
Refclock Offset SOCK(1) -52.048 -1.787 -0.992 -0.087 0.869 1.335 230.276 1.862 3.123 1.166 -0.087 ms 129.6 2.566e+04
Refclock Offset SOCK(2) -181.172 -176.994 -173.059 -163.444 -157.121 -154.860 -148.505 15.938 22.134 4.800 -164.015 ms -0.5576 3.253
Refclock Offset SOCK(3) -3,009.455 -0.960 -0.610 -0.079 0.535 0.918 4.447 1.145 1.878 17.175 -0.177 ms -175.1 3.068e+04
Refclock RMS Jitter SHM(0) 0.000 0.467 0.692 1.688 3.971 5.329 745.507 3.279 4.862 4.110 1.971 ms 163.5 2.951e+04
Refclock RMS Jitter SHM(1) 0.000 0.191 0.216 0.313 0.462 0.554 96.676 0.246 0.364 0.677 0.335 ms 96.23 1.147e+04
Refclock RMS Jitter SHM(2) 0.000 0.621 1.013 22.720 62.605 96.386 2,002.029 61.592 95.765 23.522 24.963 ms 5.25 270.9
Refclock RMS Jitter SHM(3) 0.000 0.053 0.073 0.254 0.751 1.030 2,001.141 0.677 0.977 8.171 0.351 ms 187.6 3.727e+04
Refclock RMS Jitter SOCK(0) 0.000 0.451 0.658 1.622 4.097 7.521 199.488 3.438 7.070 2.193 1.979 ms 33.87 2074
Refclock RMS Jitter SOCK(1) 0.000 0.202 0.228 0.344 0.696 0.956 104.304 0.469 0.754 0.542 0.389 ms 122 1.84e+04
Refclock RMS Jitter SOCK(2) 0.000 0.600 0.948 2.374 5.637 7.241 11.212 4.689 6.641 1.481 2.715 ms 1.233 5.001
Refclock RMS Jitter SOCK(3) 0.000 0.196 0.221 0.324 0.536 0.729 3,009.547 0.315 0.533 17.171 0.461 ms 152.2 2.388e+04
Server Jitter 104.131.155.175 0.000 0.000 0.000 3.656 17.731 18.171 18.171 17.731 18.171 4.618 5.158 ms 1.714 5.382
Server Jitter 104.152.220.5 0.000 0.000 0.000 0.888 2.438 2.438 2.438 2.438 2.438 0.710 1.068 ms 0.5336 2.756
Server Jitter 104.167.215.195 0.000 0.000 1.736 5.117 35.856 66.707 67.627 34.119 66.707 12.331 8.977 ms 3.401 14.81
Server Jitter 104.167.241.253 0.000 0.000 0.000 2.362 8.036 8.036 8.036 8.036 8.036 2.290 2.983 ms 0.6267 2.554
Server Jitter 104.234.61.117 0.000 0.842 1.258 3.320 13.812 22.021 62.066 12.553 21.179 4.667 4.606 ms 4.224 29.96
Server Jitter 108.61.56.35 0.000 0.000 0.000 2.555 4.944 4.944 4.944 4.944 4.944 1.407 2.414 ms -0.1572 2.553
Server Jitter 108.61.73.243 0.000 0.930 1.583 10.816 44.654 63.282 117.163 43.070 62.352 14.583 14.522 ms 2.087 8.894
Server Jitter 12.71.198.242 0.000 0.000 0.000 2.476 14.247 14.247 14.247 14.247 14.247 4.389 3.547 ms 1.44 4.115
Server Jitter 129.146.193.200 0.000 0.000 0.604 2.572 17.247 17.857 18.051 16.643 17.857 3.879 3.728 ms 2.392 8.649
Server Jitter 131.153.171.250 0.000 0.000 0.000 0.763 4.308 4.308 4.308 4.308 4.308 1.877 1.690 ms 0.6205 1.5
Server Jitter 131.239.5.43 0.000 0.000 0.000 1.655 3.135 3.135 3.135 3.135 3.135 0.882 1.743 ms -0.2966 2.893
Server Jitter 135.148.100.14 0.000 1.034 1.658 14.607 55.544 71.155 96.799 53.886 70.120 15.421 16.960 ms 1.968 8.02
Server Jitter 137.110.222.27 0.000 0.000 0.341 3.330 5.202 5.372 5.372 4.861 5.372 1.250 3.135 ms -0.5711 2.996
Server Jitter 137.190.2.4 0.000 0.000 0.000 8.346 83.883 83.883 83.883 83.883 83.883 25.677 16.869 ms 1.958 5.07
Server Jitter 139.177.202.26 0.000 0.000 0.000 1.560 6.528 6.528 6.528 6.528 6.528 1.992 1.908 ms 1.039 3.07
Server Jitter 139.84.137.244 0.000 1.502 3.514 23.662 63.458 81.645 171.675 59.944 80.143 19.796 27.106 ms 1.38 7.836
Server Jitter 139.94.144.123 0.000 0.000 0.000 1.501 2.945 2.945 2.945 2.945 2.945 1.260 1.529 ms 0.002279 1.271
Server Jitter 141.11.234.198 0.000 0.000 0.000 8.942 58.361 58.361 58.361 58.361 58.361 19.957 16.134 ms 1.387 3.303
Server Jitter 141.11.89.193 0.000 0.000 0.000 1.558 2.015 2.015 2.015 2.015 2.015 0.652 1.474 ms -1.441 3.889
Server Jitter 142.202.190.19 0.000 0.000 0.000 2.175 6.985 16.409 16.409 6.985 16.409 3.192 2.973 ms 2.438 10.54
Server Jitter 144.202.0.197 0.000 0.000 0.000 2.470 4.307 4.307 4.307 4.307 4.307 1.435 2.296 ms -0.2563 1.847
Server Jitter 144.202.66.214 0.000 0.000 0.000 3.268 3.564 3.564 3.564 3.564 3.564 1.326 2.411 ms -0.873 2.102
Server Jitter 148.163.226.148 0.000 0.000 0.000 0.817 80.131 80.131 80.131 80.131 80.131 25.414 13.052 ms 1.993 5.456
Server Jitter 149.248.12.167 0.000 0.000 0.000 1.415 6.547 6.547 6.547 6.547 6.547 2.701 2.851 ms 0.3599 1.282
Server Jitter 149.28.200.179 0.000 0.000 1.448 3.887 18.634 19.531 19.531 17.186 19.531 5.389 6.126 ms 1.504 3.906
Server Jitter 149.28.61.105 0.000 0.000 0.000 2.466 4.280 4.280 4.280 4.280 4.280 1.264 2.154 ms -0.03175 2.746
Server Jitter 15.204.198.96 0.000 0.000 1.528 9.635 18.188 24.740 24.740 16.661 24.740 6.496 9.205 ms 0.2143 1.632
Server Jitter 15.204.87.223 0.000 0.000 1.093 3.116 14.025 23.083 37.321 12.932 23.083 4.456 4.482 ms 3.12 16.52
Server Jitter 155.248.196.28 0.000 0.000 0.000 1.667 4.694 4.694 4.694 4.694 4.694 1.616 1.873 ms 0.573 1.838
Server Jitter 158.51.99.19 0.000 0.861 1.216 3.317 19.810 51.816 228.673 18.594 50.955 13.195 6.155 ms 10.51 149.8
Server Jitter 162.159.200.1 0.000 0.384 1.100 2.819 8.229 21.629 42.450 7.129 21.245 4.023 3.765 ms 5.049 37.93
Server Jitter 162.159.200.123 0.000 0.000 0.000 3.085 9.842 12.427 12.427 9.842 12.427 2.969 3.852 ms 1.147 3.88
Server Jitter 163.123.152.14 0.000 0.000 0.000 3.728 4.357 4.357 4.357 4.357 4.357 1.674 2.791 ms -0.9099 2.151
Server Jitter 166.88.142.52 0.000 0.000 0.000 1.075 3.927 3.927 3.927 3.927 3.927 1.133 1.349 ms 1.419 4.128
Server Jitter 168.61.215.74 0.000 0.000 0.000 3.749 13.177 14.339 14.339 13.177 14.339 4.228 5.272 ms 0.615 2.272
Server Jitter 170.187.147.56 0.000 0.824 1.119 3.127 15.294 35.711 154.182 14.175 34.886 9.178 5.070 ms 11.83 185.3
Server Jitter 172.233.153.85 0.000 0.000 1.067 4.764 14.089 23.765 302.556 13.022 23.765 29.458 8.479 ms 9.659 96.43
Server Jitter 172.233.157.223 0.000 0.000 0.000 2.179 8.001 8.001 8.001 8.001 8.001 2.598 2.911 ms 0.8956 2.43
Server Jitter 172.233.177.198 0.000 0.000 0.000 5.156 9.581 9.581 9.581 9.581 9.581 2.646 5.415 ms -0.2803 2.993
Server Jitter 172.234.25.10 0.000 0.000 0.000 1.180 4.280 4.280 4.280 4.280 4.280 1.151 1.441 ms 1.042 3.453
Server Jitter 172.234.37.140 0.000 0.000 0.000 5.761 13.618 13.618 13.618 13.618 13.618 3.635 5.254 ms 0.5438 2.723
Server Jitter 172.234.44.141 0.000 0.000 0.000 2.374 7.577 7.577 7.577 7.577 7.577 2.262 3.093 ms 0.8517 2.644
Server Jitter 172.235.60.8 0.000 0.000 0.000 2.985 13.407 13.407 13.407 13.407 13.407 3.264 4.071 ms 1.906 6.336
Server Jitter 172.98.15.13 0.000 0.000 0.000 6.095 6.104 6.104 6.104 6.104 6.104 2.880 3.231 ms -0.02367 1.032
Server Jitter 173.230.154.254 0.000 0.000 0.000 17.669 34.968 34.968 34.968 34.968 34.968 10.793 16.118 ms 0.0947 2.297
Server Jitter 173.249.203.227 0.000 0.000 0.000 2.338 5.843 5.843 5.843 5.843 5.843 1.587 2.822 ms 0.3165 2.627
Server Jitter 173.255.192.10 0.000 0.000 0.000 2.331 9.584 9.584 9.584 9.584 9.584 2.608 3.116 ms 1.465 4.472
Server Jitter 173.255.255.133 0.000 0.153 1.038 3.303 14.750 23.112 28.677 13.712 22.959 4.499 4.721 ms 2.482 9.648
Server Jitter 173.71.68.71 0.000 0.627 1.250 6.765 34.293 47.740 57.792 33.043 47.112 10.711 11.124 ms 1.434 5.181
Server Jitter 192.48.105.15 0.000 0.000 0.000 1.815 13.786 13.786 13.786 13.786 13.786 3.333 2.570 ms 2.497 8.699
Server Jitter 193.29.63.226 0.000 0.000 0.000 2.362 6.790 7.768 7.768 6.790 7.768 1.752 2.617 ms 1.293 4.972
Server Jitter 194.0.5.123 0.000 0.740 1.115 3.191 11.228 23.083 161.579 10.113 22.342 7.460 4.536 ms 14.75 290.9
Server Jitter 198.137.202.32 0.000 0.671 1.209 3.297 12.402 17.407 31.925 11.193 16.736 3.746 4.236 ms 3.509 20.09
Server Jitter 198.199.14.19 0.000 0.000 0.000 4.868 19.360 19.360 19.360 19.360 19.360 6.619 7.607 ms 0.7297 1.985
Server Jitter 198.211.103.209 0.000 0.000 0.000 3.750 13.433 21.945 21.945 13.433 21.945 4.568 5.256 ms 1.672 6.209
Server Jitter 198.46.254.130 0.000 0.789 1.171 3.308 24.735 39.397 60.567 23.564 38.608 8.364 6.211 ms 3.337 16.34
Server Jitter 198.60.22.240 0.000 0.000 0.000 1.229 8.123 8.123 8.123 8.123 8.123 2.808 2.774 ms 0.7715 2.116
Server Jitter 199.68.201.235 0.000 0.000 1.107 3.083 4.994 5.795 5.795 3.886 5.795 1.244 3.083 ms -0.137 2.992
Server Jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) 0.000 1.001 1.378 3.306 22.350 55.353 68.490 20.972 54.352 9.914 6.937 ms 3.502 16.46
Server Jitter 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) 0.000 0.000 0.000 6.706 10.790 10.790 10.790 10.790 10.790 3.771 6.760 ms -0.8058 2.409
Server Jitter 2001:19f0:6401:400:5400:4ff:fec3:522a 0.000 0.000 0.000 4.945 24.636 24.636 24.636 24.636 24.636 6.126 6.507 ms 1.809 6.149
Server Jitter 2001:418:3ff::53 (x.ns.gin.ntt.net) 0.000 0.000 0.000 14.048 17.951 17.951 17.951 17.951 17.951 7.508 10.420 ms -0.3643 1.295
Server Jitter 2001:418:8405:4002::12 0.000 0.000 0.000 20.750 257.784 257.784 257.784 257.784 257.784 84.275 57.575 ms 1.804 4.559
Server Jitter 2001:418:8405:4002::3 0.000 0.000 0.000 4.428 8.084 8.084 8.084 8.084 8.084 2.892 3.931 ms 0.1094 1.917
Server Jitter 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) 0.000 1.136 2.036 12.122 41.039 72.944 118.845 39.003 71.808 15.175 15.560 ms 2.609 13.81
Server Jitter 2001:470:1f07:24f::123 0.000 0.000 0.000 25.254 42.613 42.613 42.613 42.613 42.613 13.314 18.607 ms 0.05496 1.858
Server Jitter 2001:470:1f2c:60:123:123:123:123 0.000 0.000 0.000 20.430 35.954 35.954 35.954 35.954 35.954 11.405 14.554 ms 0.1812 1.824
Server Jitter 2001:470:e114::d6:12 (1.md.ntp.md) 0.000 0.766 1.459 6.826 27.047 45.230 56.378 25.589 44.464 8.650 9.685 ms 2.029 9.062
Server Jitter 2001:470:e8dc:10::123 0.000 0.001 0.001 0.004 0.021 0.074 589.082 0.020 0.073 24.776 1.685 s 18.39 390.9
Server Jitter 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) 0.000 1.102 1.686 10.928 48.225 61.432 219.778 46.539 60.331 15.215 14.564 ms 2.947 25.72
Server Jitter 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com) 0.000 0.840 1.365 3.070 12.046 16.376 19.485 10.681 15.537 3.227 3.896 ms 2.632 10.33
Server Jitter 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) 0.000 0.830 1.150 3.284 24.575 55.936 146.741 23.425 55.106 10.291 6.585 ms 4.523 32.1
Server Jitter 2001:558:6014:17:8dc5:5575:5560:2cb6 0.000 0.000 0.000 4.253 65.155 123.941 123.941 65.155 123.941 24.032 13.461 ms 3.066 13.01
Server Jitter 2001:559:2be:3::1001 0.000 0.000 0.000 3.333 53.390 53.390 53.390 53.390 53.390 13.672 9.507 ms 1.842 5.746
Server Jitter 2001:678:8::123 (any.time.nl) 0.000 1.610 3.411 25.456 75.543 96.212 182.621 72.133 94.602 23.152 30.446 ms 0.9596 3.679
Server Jitter 204.197.163.71 0.000 0.686 1.095 3.220 7.493 17.061 50.513 6.398 16.375 3.155 3.763 ms 6.631 80.71
Server Jitter 204.2.134.162 0.000 0.000 0.000 1.171 6.096 6.096 6.096 6.096 6.096 1.827 2.047 ms 0.8441 2.681
Server Jitter 205.233.73.201 0.000 0.000 0.000 3.474 11.938 11.938 11.938 11.938 11.938 2.573 3.409 ms 1.455 6.61
Server Jitter 208.113.130.146 0.000 0.861 1.394 5.061 43.913 76.684 232.036 42.519 75.823 18.779 11.712 ms 5.666 52.59
Server Jitter 208.67.72.43 0.000 0.000 0.000 20.684 46.773 46.773 46.773 46.773 46.773 14.479 19.405 ms 0.3984 2.247
Server Jitter 208.67.72.50 0.000 0.000 1.610 9.928 32.633 65.428 66.592 31.023 65.428 11.583 11.986 ms 2.324 10.54
Server Jitter 208.67.75.242 0.000 0.872 1.265 3.563 19.825 36.345 45.510 18.560 35.473 6.747 6.278 ms 2.54 10.94
Server Jitter 212.227.240.160 0.916 0.946 1.311 3.935 18.958 38.990 46.313 17.647 38.044 6.905 6.714 ms 2.568 11.6
Server Jitter 216.229.4.66 0.000 0.000 0.000 4.322 7.579 7.579 7.579 7.579 7.579 2.291 4.100 ms -0.5079 2.271
Server Jitter 216.229.4.69 0.000 0.000 0.000 2.477 5.003 5.695 5.695 5.003 5.695 1.718 2.457 ms 0.2191 2.013
Server Jitter 216.240.36.24 0.000 0.000 0.000 2.248 8.229 8.229 8.229 8.229 8.229 2.720 2.945 ms 1.272 3.013
Server Jitter 216.31.17.12 0.000 0.000 0.000 4.094 14.330 14.330 14.330 14.330 14.330 4.001 4.883 ms 1.185 3.801
Server Jitter 23.111.186.186 0.000 0.000 0.000 1.132 1.974 1.974 1.974 1.974 1.974 0.537 1.129 ms -0.4905 3.028
Server Jitter 23.131.160.7 0.000 0.880 1.354 3.468 10.866 32.018 126.894 9.512 31.138 7.981 4.858 ms 9.335 108.7
Server Jitter 23.141.40.123 0.000 0.000 0.000 3.979 5.911 5.911 5.911 5.911 5.911 1.921 3.290 ms -0.4708 2.11
Server Jitter 23.142.248.8 0.000 0.000 0.000 1.269 2.327 2.327 2.327 2.327 2.327 0.866 1.154 ms -0.1197 1.574
Server Jitter 23.142.248.9 0.000 0.000 0.000 2.456 5.220 5.220 5.220 5.220 5.220 1.826 2.458 ms 0.2091 1.622
Server Jitter 23.143.196.199 0.000 0.000 0.000 1.033 2.250 2.250 2.250 2.250 2.250 0.756 1.094 ms -0.06783 1.795
Server Jitter 23.150.41.123 0.000 0.000 1.377 3.846 22.008 38.931 39.560 20.631 38.931 8.452 7.143 ms 2.301 8.099
Server Jitter 23.155.40.38 0.000 0.000 1.081 3.356 34.022 117.881 142.893 32.940 117.881 18.722 8.653 ms 5.033 31.38
Server Jitter 23.168.24.210 0.000 0.000 0.000 4.522 5.887 5.887 5.887 5.887 5.887 2.451 2.822 ms 0.06634 1.208
Server Jitter 23.186.168.123 0.000 0.794 1.193 3.052 8.245 20.200 30.025 7.052 19.406 3.089 3.701 ms 3.772 21.92
Server Jitter 23.186.168.126 0.000 0.695 1.121 3.001 10.669 41.147 100.230 9.548 40.452 8.625 4.647 ms 7.962 75.3
Server Jitter 23.186.168.127 0.000 0.000 0.000 6.846 25.786 25.786 25.786 25.786 25.786 9.961 9.050 ms 0.9537 2.186
Server Jitter 23.186.168.128 0.000 0.814 1.329 3.310 8.610 17.200 23.748 7.281 16.386 2.792 3.875 ms 2.955 14.86
Server Jitter 23.186.168.129 0.000 0.699 1.253 3.436 8.998 17.637 105.774 7.745 16.939 4.861 4.275 ms 11.96 214.6
Server Jitter 23.186.168.130 0.000 0.000 0.000 3.466 73.799 73.994 73.994 73.799 73.994 19.691 9.038 ms 2.942 9.824
Server Jitter 23.186.168.131 0.000 0.749 1.266 3.133 8.261 15.037 223.184 6.995 14.289 9.704 4.117 ms 21.04 473.4
Server Jitter 23.186.168.132 0.000 0.902 1.266 3.346 9.317 18.281 72.944 8.051 17.379 3.794 4.152 ms 6.892 91.34
Server Jitter 23.94.221.138 0.000 0.000 0.000 1.546 4.125 4.125 4.125 4.125 4.125 1.215 1.733 ms 0.7763 2.642
Server Jitter 23.95.49.216 0.000 0.804 1.089 2.946 11.443 17.019 159.086 10.354 16.216 7.100 4.020 ms 17.62 379.9
Server Jitter 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) 0.000 1.856 4.955 29.235 71.283 87.807 159.685 66.328 85.951 21.157 32.582 ms 0.7387 3.363
Server Jitter 2402:1f00:8101:d6::1 0.000 0.000 0.000 0.934 1.239 1.239 1.239 1.239 1.239 0.407 0.723 ms -0.5786 2.177
Server Jitter 240b:4002:100:9f00:5bd1:9512:8a8b:25e 0.000 0.000 0.000 4.287 5.971 5.971 5.971 5.971 5.971 2.062 3.825 ms -0.9946 2.639
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d6 0.000 0.839 1.416 3.601 24.535 54.985 74.237 23.119 54.146 9.449 6.322 ms 4.13 22.24
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d8 0.000 0.000 0.000 3.953 46.649 52.232 52.232 46.649 52.232 15.473 10.747 ms 1.58 4.101
Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d9 0.000 0.000 0.000 19.678 21.828 21.828 21.828 21.828 21.828 8.593 13.132 ms -0.5264 1.711
Server Jitter 240b:4004:108:200:8314:1a08:4cee:2acf 0.000 0.000 0.000 1.911 56.765 56.765 56.765 56.765 56.765 17.704 9.838 ms 2.016 5.544
Server Jitter 2600:1700:3d24:740f:9524:529a:6489:d48f 0.000 0.000 0.000 1.447 8.923 8.923 8.923 8.923 8.923 2.239 2.142 ms 1.358 4.664
Server Jitter 2600:1700:5455:a70::7b:1 0.000 0.000 1.444 4.653 23.669 27.142 27.142 22.225 27.142 7.742 8.428 ms 1.002 2.547
Server Jitter 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 0.000 0.000 0.000 4.182 17.559 24.762 24.762 17.559 24.762 6.282 6.670 ms 1.239 3.969
Server Jitter 2600:1700:5a0f:ee00::314:1b 0.000 0.000 1.037 3.806 18.648 21.885 23.803 17.611 21.885 5.224 5.597 ms 1.78 5.219
Server Jitter 2600:1700:5a0f:ee00::314:2b 0.000 0.000 0.000 2.121 13.811 13.811 13.811 13.811 13.811 3.373 3.376 ms 1.687 5.974
Server Jitter 2600:1702:7400:9ac0::314:5a 0.000 0.000 0.000 2.413 15.160 15.160 15.160 15.160 15.160 4.523 4.818 ms 1.082 3.061
Server Jitter 2600:1702:7400:9ac0::5b 0.000 0.000 0.000 2.689 7.877 7.877 7.877 7.877 7.877 2.509 3.387 ms 0.6509 2.164
Server Jitter 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com) 0.000 1.703 3.526 24.446 74.599 96.231 173.647 71.073 94.529 22.963 30.367 ms 1.031 4.082
Server Jitter 2600:1f13:2c1:2e00::be00:5 0.000 0.941 1.487 3.653 25.297 93.488 214.829 23.809 92.548 16.422 7.675 ms 6.759 62.66
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.000 0.823 1.169 3.339 21.951 49.663 185.361 20.783 48.840 9.853 6.218 ms 5.748 56.48
Server Jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) 0.000 0.832 1.212 3.536 39.205 69.230 282.893 37.993 68.398 14.386 9.101 ms 4.117 32.69
Server Jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) 0.000 0.835 1.266 7.203 52.230 78.393 168.874 50.964 77.558 17.372 14.338 ms 2.244 9.57
Server Jitter 2600:1f18:7927:8b00:123:: 0.000 0.000 0.000 0.873 2.440 2.440 2.440 2.440 2.440 0.788 1.166 ms 0.2839 1.935
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 0.000 0.000 0.000 1.922 1.922 1.922 1.922 1.922 1.922 0.961 0.961 ms 0 1
Server Jitter 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) 0.000 0.890 1.356 3.377 17.886 36.557 125.199 16.531 35.668 7.187 5.405 ms 6.571 77.93
Server Jitter 2600:3c00:e000:318::1 (jane.qotw.net) 0.000 0.936 1.251 3.291 18.596 45.542 55.919 17.345 44.606 7.258 5.661 ms 3.76 20.2
Server Jitter 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) 0.000 0.000 0.000 6.110 10.609 10.609 10.609 10.609 10.609 3.299 4.985 ms 0.1951 2.331
Server Jitter 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com) 0.000 0.000 0.000 7.022 69.185 74.278 74.278 69.185 74.278 19.927 15.358 ms 1.999 5.824
Server Jitter 2600:3c01:e000:7e6::123 (time1.sigi.net) 0.000 0.678 1.268 3.194 8.827 20.528 87.783 7.559 19.850 4.877 4.124 ms 8.554 112.3
Server Jitter 2600:3c02::f03c:92ff:fe96:dc0 0.000 0.719 1.293 3.642 35.596 64.763 70.185 34.303 64.043 13.117 8.439 ms 3.086 12.43
Server Jitter 2600:3c02::f03c:94ff:fe59:f411 0.000 0.000 0.000 5.394 7.516 7.516 7.516 7.516 7.516 2.647 4.557 ms -0.5602 1.96
Server Jitter 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net) 0.000 0.698 1.366 3.382 13.487 24.586 25.970 12.121 23.888 4.296 4.750 ms 2.388 9.659
Server Jitter 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) 0.000 0.000 0.717 3.878 10.414 16.432 16.432 9.697 16.432 3.233 4.061 ms 1.999 7.801
Server Jitter 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) 0.000 0.000 0.000 4.625 9.182 9.182 9.182 9.182 9.182 3.008 4.335 ms -0.05862 1.872
Server Jitter 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) 0.000 0.000 1.722 5.665 14.088 67.952 94.476 12.366 67.952 9.525 7.349 ms 6.462 52.16
Server Jitter 2600:3c03::f03c:94ff:fe59:d3de 0.000 0.000 0.000 9.141 10.648 10.648 10.648 10.648 10.648 4.705 6.597 ms -0.6531 1.5
Server Jitter 2600:3c03:e002:1300::10 (ntp.electronmill.com) 0.000 0.000 0.000 3.877 7.718 7.718 7.718 7.718 7.718 2.384 3.718 ms 0.3575 1.964
Server Jitter 2600:3c06::f03c:94ff:fee2:9c28 0.000 0.000 0.000 9.325 30.736 30.736 30.736 30.736 30.736 11.553 11.593 ms 0.8589 2.149
Server Jitter 2600:3c06::f03c:94ff:fee2:c53a 0.000 0.000 0.000 15.615 24.117 24.117 24.117 24.117 24.117 9.987 13.244 ms -0.3427 1.5
Server Jitter 2600:4040:3037:e600::1 2.236 2.236 2.236 3.952 3.952 3.952 3.952 1.716 1.716 0.858 3.094 ms 8.189e-16 1
Server Jitter 2600:4040:e0da:f000::cbb9:201a 0.000 0.000 0.547 12.110 32.149 45.133 45.133 31.602 45.133 10.649 11.858 ms 1.048 3.818
Server Jitter 2602:291:69::8 (time2.tritan-bb.net) 0.000 0.000 0.000 0.970 1.844 1.844 1.844 1.844 1.844 0.552 0.976 ms -0.2468 2.677
Server Jitter 2602:291:69::9 (time.tritan-bb.net) 0.000 0.000 0.000 2.935 6.266 9.048 9.048 6.266 9.048 1.880 2.793 ms 0.9925 5.049
Server Jitter 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) 0.000 0.884 1.326 3.508 14.465 35.541 139.194 13.139 34.657 7.489 5.097 ms 8.397 106.1
Server Jitter 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net) 0.000 0.000 0.000 1.197 1.816 1.816 1.816 1.816 1.816 0.754 1.004 ms -0.3667 1.5
Server Jitter 2602:2eb:2:95:1234:5678:9abc:def0 0.000 0.928 1.412 3.654 26.243 55.859 262.579 24.831 54.931 13.247 7.544 ms 8.809 126
Server Jitter 2602:80b:5000::36 (time.meme.holdings) 0.000 0.000 4.621 20.856 76.477 84.174 87.838 71.856 84.174 21.252 27.684 ms 0.9659 3.216
Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) 0.000 0.000 0.000 4.593 9.349 9.349 9.349 9.349 9.349 2.587 4.904 ms -0.09123 2.375
Server Jitter 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) 0.000 0.000 1.448 5.641 57.096 77.816 96.144 55.648 77.816 18.597 13.597 ms 2.205 7.472
Server Jitter 2602:fb95:16::123 (time5.sigi.net) 0.000 0.000 0.000 2.945 6.744 6.744 6.744 6.744 6.744 1.680 2.843 ms 0.7474 3.802
Server Jitter 2602:fc2f:100:9800::dead:beef 0.000 1.459 2.342 5.503 62.283 166.197 259.248 59.941 164.738 29.640 14.817 ms 4.483 25.63
Server Jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) 0.000 0.000 0.000 1.961 5.599 9.370 9.370 5.599 9.370 2.184 2.731 ms 1.202 4.547
Server Jitter 2602:fe2e:3:d:f9:c7ff:fef5:379c 0.000 0.000 0.000 2.011 3.424 3.424 3.424 3.424 3.424 0.929 1.786 ms -0.1796 2.962
Server Jitter 2602:ff06:725:100::123 (oldtime2.sigi.net) 0.000 0.000 0.000 1.447 6.369 6.369 6.369 6.369 6.369 1.854 1.683 ms 1.874 5.218
Server Jitter 2602:ff23:50:3c2::1 (dns-e.ns4v.icu) 0.000 1.222 1.475 4.424 42.112 69.376 73.583 40.637 68.154 12.937 8.366 ms 3.413 14.37
Server Jitter 2603:c020:0:8369:0:ba11:ba11:ba11 0.000 0.000 0.000 4.189 14.814 17.914 17.914 14.814 17.914 4.131 4.795 ms 1.397 5.064
Server Jitter 2603:c020:0:8369:1111:1111:1111:1112 0.000 0.000 0.000 3.258 74.324 99.180 99.180 74.324 99.180 21.368 13.977 ms 2.367 8.837
Server Jitter 2603:c020:0:8369::bad:beef 0.000 0.000 0.000 3.940 3.991 3.991 3.991 3.991 3.991 1.645 2.811 ms -1.067 2.256
Server Jitter 2603:c020:0:8369::f00d:feed 0.000 0.000 0.000 3.051 11.156 19.041 19.041 11.156 19.041 4.036 4.160 ms 2.143 8.32
Server Jitter 2603:c020:0:8369::feeb:dab 0.000 0.000 0.000 3.443 11.129 12.564 12.564 11.129 12.564 3.141 3.778 ms 1.064 3.951
Server Jitter 2603:c020:0:8369:feed:feed:feed:feed 0.000 0.000 0.000 3.112 13.323 13.323 13.323 13.323 13.323 3.317 3.712 ms 1.612 5.406
Server Jitter 2603:c020:6:b900:6b54:1390:4afd:814a 0.000 0.000 0.000 4.457 16.191 16.191 16.191 16.191 16.191 4.707 5.327 ms 0.744 2.635
Server Jitter 2603:c020:6:b900:ed2f:b442:fee7:d9b9 0.000 0.000 0.000 2.967 6.929 6.929 6.929 6.929 6.929 2.490 2.410 ms 0.6756 2.153
Server Jitter 2603:c024:c005:a600:efb6:d213:cad8:251d 0.000 0.000 0.000 14.820 57.595 57.595 57.595 57.595 57.595 17.229 20.244 ms 1.209 3.457
Server Jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 0.000 0.000 1.769 15.711 48.002 49.094 49.094 46.233 49.094 11.410 15.959 ms 1.156 4.594
Server Jitter 2604:2dc0:100:4d6:: 0.000 0.000 0.000 3.514 4.351 4.351 4.351 4.351 4.351 1.632 2.616 ms -0.6871 1.99
Server Jitter 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) 0.000 0.000 0.000 2.991 9.649 9.649 9.649 9.649 9.649 2.561 3.518 ms 1.144 3.781
Server Jitter 2604:2dc0:202:300::140d (ovh.maxhost.io) 0.000 0.965 1.366 3.498 9.087 21.237 71.985 7.721 20.272 3.773 4.317 ms 5.523 60.29
Server Jitter 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) 0.000 0.906 1.363 3.338 10.703 34.136 119.042 9.340 33.230 6.208 4.661 ms 7.131 78.29
Server Jitter 2604:4300:a:299::164 0.000 0.000 0.000 3.582 6.183 11.304 11.304 6.183 11.304 2.417 3.650 ms 1.209 5.485
Server Jitter 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) 0.000 0.000 0.000 3.639 13.829 13.829 13.829 13.829 13.829 3.432 4.353 ms 1.336 4.939
Server Jitter 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) 0.000 0.000 0.000 21.487 31.405 31.405 31.405 31.405 31.405 13.108 17.631 ms -0.4158 1.5
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.000 0.000 0.869 1.657 1.657 1.657 1.657 1.657 0.479 0.845 ms -0.09905 2.996
Server Jitter 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) 0.000 0.965 1.447 3.716 18.849 29.446 120.523 17.402 28.481 10.597 5.665 ms 8.209 79.46
Server Jitter 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) 0.000 0.000 0.000 8.010 25.574 25.574 25.574 25.574 25.574 6.576 8.369 ms 0.7283 3.152
Server Jitter 2604:a880:800:10::70f:b001 (ellone.fdisk.io) 0.000 0.000 0.000 1.765 3.857 3.857 3.857 3.857 3.857 1.036 1.790 ms 0.1052 2.65
Server Jitter 2604:a880:800:a1::ec9:5001 0.000 0.000 0.000 3.038 144.987 144.987 144.987 144.987 144.987 40.690 27.266 ms 1.51 4.267
Server Jitter 2604:d200::39 (white.web-ster.com) 0.000 0.000 0.000 1.874 3.949 3.949 3.949 3.949 3.949 1.165 1.768 ms 0.2062 2.03
Server Jitter 2605:4840:3:fb19::1 (chi3.us.ntp.li) 0.000 3.032 6.591 21.939 58.467 76.100 242.923 51.875 73.068 18.011 25.799 ms 3.949 40.23
Server Jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ns nan nan
Server Jitter 2605:6400:488d:3686:546d:c03c:1689:20c 0.000 0.000 0.000 1.372 9.116 9.116 9.116 9.116 9.116 3.886 3.057 ms 0.6883 1.57
Server Jitter 2605:6400:84e1::123 (oldtime3.sigi.net) 0.000 0.000 0.000 3.606 8.882 8.882 8.882 8.882 8.882 2.455 3.745 ms 0.4362 2.81
Server Jitter 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) 0.000 0.000 0.000 3.793 7.878 7.878 7.878 7.878 7.878 2.024 4.070 ms 0.0771 3.251
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.870 1.293 3.423 17.848 46.658 400.941 16.555 45.788 11.016 5.704 ms 13.69 329
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.000 0.856 1.266 3.382 16.072 47.481 176.369 14.806 46.625 8.785 5.361 ms 7.855 93
Server Jitter 2606:82c0:21::e (time1.lshiy.com) 0.000 0.000 0.000 1.883 3.565 3.565 3.565 3.565 3.565 1.027 1.940 ms -0.3172 2.792
Server Jitter 2606:82c0:22::e (time2.lshiy.com) 0.000 0.000 0.000 5.461 24.843 24.843 24.843 24.843 24.843 7.408 7.371 ms 1.48 4.108
Server Jitter 2606:82c0:23::e (time3.lshiy.com) 0.000 0.000 0.000 3.337 8.248 8.248 8.248 8.248 8.248 2.270 3.415 ms 0.3181 2.67
Server Jitter 2607:5600:182:500::1 (ntp-1.jonlight.com) 0.000 0.000 0.000 10.156 45.021 45.021 45.021 45.021 45.021 12.499 11.485 ms 1.431 4.572
Server Jitter 2607:7c80:54:3::32 0.000 0.928 1.517 3.611 16.831 44.803 127.511 15.314 43.875 7.844 5.548 ms 6.416 63.26
Server Jitter 2607:7c80:54:3::56 (owners.kjsl.com) 0.000 0.000 1.298 3.181 22.900 24.794 24.794 21.602 24.794 5.837 5.520 ms 2.225 7.106
Server Jitter 2607:9000:7000:23:216:3cff:fe25:38d7 0.000 0.598 1.211 3.188 11.275 18.776 101.037 10.064 18.178 7.917 4.641 ms 9.393 106.3
Server Jitter 2607:9d00:2000:16::9269:208a 0.000 0.000 0.000 3.585 32.658 32.768 32.768 32.658 32.768 8.863 6.355 ms 2.336 7.193
Server Jitter 2607:b500:410:7700::1 0.000 0.000 0.000 3.930 45.395 48.813 48.813 45.395 48.813 12.860 8.432 ms 2.364 7.345
Server Jitter 2607:f1c0:f014:9e00::1 0.000 0.000 0.000 4.356 10.370 10.370 10.370 10.370 10.370 2.391 5.036 ms 0.1939 4.09
Server Jitter 2607:f1c0:f014:9e00::2 0.000 0.000 0.000 4.033 19.038 31.195 31.195 19.038 31.195 7.047 6.391 ms 1.868 6.607
Server Jitter 2607:f1c0:f04e:fd00::1 0.000 0.000 0.000 4.264 7.362 7.362 7.362 7.362 7.362 2.269 3.950 ms -0.238 2.144
Server Jitter 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) 0.000 0.000 0.000 3.311 58.981 58.981 58.981 58.981 58.981 21.215 11.609 ms 1.777 4.18
Server Jitter 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) 0.000 0.000 0.000 2.585 3.939 3.939 3.939 3.939 3.939 1.251 2.204 ms -0.4741 2.288
Server Jitter 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at) 0.000 0.000 0.000 1.285 1.285 1.285 1.285 1.285 1.285 0.642 0.642 ms 0 1
Server Jitter 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) 0.000 0.000 0.000 7.684 11.739 11.739 11.739 11.739 11.739 3.498 6.746 ms -0.5998 2.636
Server Jitter 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) 0.000 0.000 0.000 3.713 17.103 17.166 17.166 17.103 17.166 4.236 4.518 ms 1.905 6.172
Server Jitter 2607:f1c0:f075:9900::1 0.000 0.000 0.000 3.194 62.537 70.431 70.431 62.537 70.431 17.930 9.867 ms 2.624 8.577
Server Jitter 2607:f298:5:101d:f816:3eff:fefd:8817 0.000 0.000 0.000 3.238 15.794 15.794 15.794 15.794 15.794 3.672 4.170 ms 1.423 5.487
Server Jitter 2607:f3c8:3803:1::6 0.000 0.000 0.000 3.665 9.888 9.888 9.888 9.888 9.888 3.130 3.728 ms 0.7664 2.592
Server Jitter 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) 0.000 0.000 0.000 7.826 42.881 42.881 42.881 42.881 42.881 11.996 12.673 ms 0.9758 3.228
Server Jitter 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) 0.000 0.000 0.000 2.953 7.543 7.543 7.543 7.543 7.543 1.917 3.128 ms 0.7412 3.627
Server Jitter 2607:f710:35::29c:0:5 0.000 0.000 0.000 4.556 7.900 7.900 7.900 7.900 7.900 2.166 4.553 ms -0.3058 2.962
Server Jitter 2607:f710:35::29c:0:8 0.000 0.993 1.374 7.413 35.124 57.993 80.866 33.750 57.000 11.814 11.251 ms 2.307 10.35
Server Jitter 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) 0.000 0.000 0.000 4.417 9.460 9.460 9.460 9.460 9.460 2.696 4.546 ms -0.0246 2.498
Server Jitter 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com) 0.000 0.000 0.000 1.304 6.107 6.107 6.107 6.107 6.107 2.114 2.122 ms 1.095 2.75
Server Jitter 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com) 0.389 0.850 1.301 3.293 9.081 28.609 88.888 7.780 27.759 6.619 4.409 ms 9.184 104.7
Server Jitter 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com) 0.763 1.018 1.571 3.635 13.134 29.896 108.020 11.564 28.878 6.313 5.059 ms 7.953 100.3
Server Jitter 2620:83:8000:140::b (tic.lbl.gov) 0.000 0.880 1.380 3.683 18.060 54.396 107.171 16.680 53.516 8.265 5.655 ms 5.524 41.14
Server Jitter 2620:83:8000:140::c (toc.lbl.gov) 0.000 1.106 1.584 3.636 9.935 22.754 23.037 8.351 21.648 3.401 4.570 ms 2.971 15.07
Server Jitter 2620:8d:c000::f (blotch.image1tech.net) 0.000 0.000 0.000 11.399 23.001 23.001 23.001 23.001 23.001 6.886 11.933 ms -0.1456 2.635
Server Jitter 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) 0.000 0.000 0.000 4.268 26.331 26.331 26.331 26.331 26.331 6.810 6.258 ms 1.9 6.02
Server Jitter 2620:b0:2000:102::1:123 (time-h.den.codehof.net) 0.000 0.000 0.000 44.659 162.644 162.644 162.644 162.644 162.644 50.617 46.606 ms 1.096 3.207
Server Jitter 2620:b0:2000:102::2:123 (time-he.den.codehof.net) 0.000 0.000 0.000 5.132 67.520 67.520 67.520 67.520 67.520 21.171 12.422 ms 2.131 5.771
Server Jitter 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) 0.000 1.746 3.432 19.222 65.886 87.844 263.025 62.453 86.098 21.462 25.498 ms 2.427 19.55
Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) 0.000 2.767 9.755 52.101 99.337 113.836 271.797 89.581 111.069 27.066 53.252 ms 0.365 3.471
Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) 0.000 2.475 6.684 48.771 96.527 110.599 234.358 89.842 108.124 27.198 49.433 ms 0.3041 2.82
Server Jitter 2a01:4ff:f0:e33b::1 0.000 0.944 1.261 3.012 9.326 19.960 20.195 8.065 19.016 2.989 3.742 ms 3.166 15.32
Server Jitter 2a01:4ff:f0:ebce::1 0.000 0.000 0.000 25.847 25.847 25.847 25.847 25.847 25.847 12.924 12.924 ms 0 1
Server Jitter 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) 0.000 0.000 0.000 32.068 70.288 70.288 70.288 70.288 70.288 19.572 34.261 ms 0.1428 3.002
Server Jitter 2a01:7e04::f03c:94ff:fee2:cba5 0.000 0.000 0.000 1.794 29.750 29.750 29.750 29.750 29.750 9.167 5.895 ms 1.677 4.108
Server Jitter 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) 0.000 0.000 0.838 3.220 6.015 8.943 9.058 5.177 8.943 1.630 3.368 ms 0.7999 4.534
Server Jitter 34.147.28.4 0.000 0.961 2.019 18.606 65.177 89.803 166.058 63.158 88.842 22.126 25.010 ms 1.748 8.655
Server Jitter 37.27.11.4 0.000 0.000 1.780 14.020 76.180 81.696 81.940 74.400 81.696 20.637 20.684 ms 1.598 4.786
Server Jitter 44.190.5.123 0.000 0.808 1.180 3.171 12.375 25.655 625.327 11.195 24.847 9.759 4.623 ms 37.41 2204
Server Jitter 45.55.126.202 0.000 0.847 1.361 4.011 21.385 56.733 76.922 20.024 55.886 9.351 7.409 ms 3.66 20.15
Server Jitter 45.61.187.39 0.000 0.000 0.000 6.005 10.131 10.131 10.131 10.131 10.131 3.234 5.663 ms -0.1351 2.072
Server Jitter 45.63.54.13 0.000 0.750 1.267 3.451 16.818 30.433 69.818 15.550 29.683 6.186 5.088 ms 4.745 33.4
Server Jitter 45.77.126.122 0.000 0.000 0.000 1.018 3.979 3.979 3.979 3.979 3.979 0.941 1.194 ms 1.581 5.687
Server Jitter 45.79.35.159 0.000 0.000 0.000 0.712 4.702 4.702 4.702 4.702 4.702 1.855 1.527 ms 1.069 2.278
Server Jitter 45.79.51.42 0.000 0.000 0.000 11.729 96.151 96.151 96.151 96.151 96.151 29.987 22.678 ms 1.636 4.376
Server Jitter 45.83.234.123 0.000 0.000 0.000 38.377 69.832 100.538 100.538 69.832 100.538 25.273 34.042 ms 0.07115 2.108
Server Jitter 45.84.199.136 0.000 0.000 0.000 7.227 34.845 34.845 34.845 34.845 34.845 11.450 10.051 ms 1.254 3.184
Server Jitter 46.37.96.107 0.000 0.762 1.136 3.173 17.249 45.839 76.855 16.113 45.077 7.508 5.080 ms 4.938 32.2
Server Jitter 5.161.111.190 0.774 1.053 1.418 3.434 16.082 36.133 46.484 14.665 35.080 5.774 5.434 ms 3.496 19.16
Server Jitter 5.78.62.36 0.000 0.814 1.189 3.214 7.458 14.625 17.905 6.268 13.811 2.404 3.674 ms 2.621 12.87
Server Jitter 50.117.3.52 0.000 0.000 0.000 1.241 1.948 1.948 1.948 1.948 1.948 0.616 1.028 ms -0.1887 2.181
Server Jitter 50.117.3.95 0.000 0.000 0.000 4.938 9.600 9.600 9.600 9.600 9.600 3.585 4.705 ms -0.06002 1.66
Server Jitter 50.205.57.38 0.000 0.865 1.243 3.327 19.270 37.488 52.487 18.027 36.624 7.055 6.159 ms 2.927 14.35
Server Jitter 50.218.103.254 0.000 0.000 0.000 1.360 15.596 15.596 15.596 15.596 15.596 4.714 2.924 ms 2.06 5.866
Server Jitter 51.81.20.76 0.000 0.000 0.000 2.794 18.439 18.439 18.439 18.439 18.439 4.702 4.747 ms 2.128 6.656
Server Jitter 51.81.226.229 0.000 0.000 0.000 3.776 10.325 13.199 13.199 10.325 13.199 3.650 4.396 ms 0.7568 2.753
Server Jitter 64.142.54.12 0.000 0.000 0.000 4.301 11.521 11.521 11.521 11.521 11.521 2.947 4.784 ms 0.8351 3.574
Server Jitter 64.6.144.6 0.000 0.000 0.000 3.288 4.846 4.846 4.846 4.846 4.846 1.639 2.872 ms -0.6172 2.185
Server Jitter 64.79.100.197 0.000 0.000 0.817 2.208 16.989 29.767 29.820 16.172 29.767 5.117 3.706 ms 3.407 14.88
Server Jitter 65.100.46.164 0.000 0.902 1.495 3.180 12.652 17.404 21.093 11.158 16.502 3.401 4.380 ms 2.274 8.459
Server Jitter 65.100.46.166 0.000 0.877 1.365 3.588 16.248 25.653 30.128 14.883 24.777 4.652 4.994 ms 2.701 11.07
Server Jitter 65.182.224.39 0.000 0.000 0.000 2.070 2.943 2.943 2.943 2.943 2.943 0.933 1.809 ms -0.8566 2.777
Server Jitter 66.118.231.14 0.000 0.000 0.000 27.185 55.552 77.497 77.497 55.552 77.497 20.613 27.535 ms 0.1157 1.981
Server Jitter 66.42.71.197 0.000 0.804 1.223 3.207 11.673 20.952 36.891 10.450 20.148 3.804 4.239 ms 3.293 17.16
Server Jitter 66.59.198.94 0.000 0.000 0.000 4.307 12.760 12.760 12.760 12.760 12.760 3.136 4.798 ms 1.209 4.406
Server Jitter 66.85.78.80 0.000 0.000 0.000 2.718 5.161 5.161 5.161 5.161 5.161 2.005 2.147 ms 0.4553 1.672
Server Jitter 67.217.246.127 0.000 0.544 1.405 3.301 20.244 36.524 37.261 18.839 35.979 7.198 6.206 ms 2.642 10.4
Server Jitter 67.217.246.204 0.000 0.000 1.289 5.632 23.748 37.970 47.481 22.460 37.970 8.234 9.205 ms 1.646 6.413
Server Jitter 68.234.48.70 0.000 0.000 0.000 15.255 37.426 37.426 37.426 37.426 37.426 11.694 11.915 ms 0.673 2.554
Server Jitter 69.176.84.38 0.000 0.000 0.084 1.877 4.514 6.761 6.761 4.430 6.761 1.315 2.063 ms 1.34 5.848
Server Jitter 69.48.203.16 0.000 0.000 0.000 2.915 5.617 5.617 5.617 5.617 5.617 1.492 2.928 ms -0.1583 2.911
Server Jitter 69.89.207.199 0.000 0.768 1.592 3.907 13.653 64.615 103.870 12.061 63.847 9.526 5.771 ms 8.019 76.57
Server Jitter 69.89.207.99 0.000 0.655 1.014 2.890 14.394 29.375 217.779 13.380 28.720 10.452 4.992 ms 13.28 242.1
Server Jitter 71.123.46.186 0.000 0.798 1.369 11.462 50.388 59.457 63.511 49.020 58.659 13.810 13.720 ms 1.912 6.345
Server Jitter 71.19.144.140 0.000 0.000 0.000 2.244 28.288 28.288 28.288 28.288 28.288 6.176 4.071 ms 3.331 13.18
Server Jitter 72.14.183.39 0.000 0.000 0.000 2.885 5.156 5.156 5.156 5.156 5.156 1.696 2.895 ms -0.4921 2.349
Server Jitter 72.14.186.59 0.000 0.000 0.000 1.353 7.812 7.812 7.812 7.812 7.812 2.791 2.333 ms 1.36 3.086
Server Jitter 72.30.35.89 0.000 0.000 0.000 0.779 4.898 4.898 4.898 4.898 4.898 2.149 1.892 ms 0.6381 1.5
Server Jitter 72.46.53.234 0.000 0.000 0.000 3.818 99.485 99.485 99.485 99.485 99.485 27.363 16.024 ms 2.181 6.785
Server Jitter 72.46.61.205 0.000 0.000 0.000 41.508 79.056 79.056 79.056 79.056 79.056 23.710 34.029 ms -0.07087 1.973
Server Jitter 73.185.182.209 0.000 1.188 1.697 3.815 25.345 43.709 79.900 23.648 42.521 9.600 8.061 ms 2.934 14.97
Server Jitter 73.65.80.137 0.000 0.000 1.979 4.758 26.082 30.271 30.271 24.103 30.271 7.745 8.134 ms 1.314 3.612
Server Jitter 74.119.243.5 0.000 0.000 0.000 3.388 6.563 6.563 6.563 6.563 6.563 2.635 2.597 ms 0.4823 1.635
Server Jitter 74.208.117.38 0.000 0.000 0.000 5.816 17.030 17.030 17.030 17.030 17.030 4.139 6.213 ms 1.416 5.194
Server Jitter 74.208.14.149 0.000 0.000 0.000 8.875 13.149 13.149 13.149 13.149 13.149 4.272 6.919 ms -0.2182 2.001
Server Jitter 74.208.25.46 0.000 1.633 2.195 4.561 14.012 52.935 406.747 11.817 51.301 15.656 6.906 ms 15.62 327.6
Server Jitter 77.37.97.124 0.000 0.986 2.855 28.267 70.810 85.923 150.671 67.955 84.937 22.534 30.520 ms 0.9612 4.788
Server Jitter 77.42.37.85 0.000 0.000 2.729 14.489 90.080 103.942 103.942 87.351 103.942 28.486 27.686 ms 1.277 3.184
Server Jitter 83.147.242.172 0.000 0.844 1.213 3.146 7.606 19.766 60.098 6.393 18.922 3.506 3.831 ms 6.515 74.75
Server Jitter 94.198.159.11 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ns nan nan
Server Jitter 99.28.14.242 0.000 0.841 1.296 3.369 21.031 62.332 94.505 19.735 61.491 9.798 6.251 ms 5.026 34.5
Server Offset 104.131.155.175 -2.525 -2.525 -1.209 5.368 12.615 16.334 16.334 13.824 18.859 4.610 5.570 ms 0.3612 2.585
Server Offset 104.152.220.5 1.461 1.461 1.461 2.919 4.887 4.887 4.887 3.425 3.425 1.020 2.874 ms 0.6553 2.767
Server Offset 104.167.215.195 -419.941 -418.768 -10.695 1.453 14.053 18.705 19.868 24.748 437.473 64.209 -8.450 ms -5.837 36.7
Server Offset 104.167.241.253 -1.130 -1.130 -1.130 3.827 174.956 174.956 174.956 176.087 176.087 77.809 54.544 ms 0.8304 1.696
Server Offset 104.234.61.117 -21.499 -3.096 2.445 5.568 7.901 10.166 442.381 5.456 13.262 14.127 5.812 ms 29.9 919.1
Server Offset 108.61.56.35 4.613 4.613 4.613 6.012 10.829 10.829 10.829 6.216 6.216 1.882 6.640 ms 0.9579 2.876
Server Offset 108.61.73.243 -4.642 0.420 2.263 5.010 7.415 8.937 442.001 5.152 8.516 20.943 5.969 ms 20.48 423.1
Server Offset 12.71.198.242 -567.986 -567.986 -567.986 -8.926 5.527 5.527 5.527 573.513 573.513 281.819 -249.816 ms -0.223 1.051
Server Offset 129.146.193.200 -0.800 0.856 1.586 4.877 7.695 10.932 11.567 6.109 10.076 1.776 4.758 ms 0.4134 5.789
Server Offset 131.153.171.250 2.305 2.305 2.305 6.214 6.977 6.977 6.977 4.672 4.672 2.047 5.165 ms -0.6341 1.5
Server Offset 131.239.5.43 0.782 0.782 0.782 4.026 4.797 4.797 4.797 4.014 4.014 1.405 3.356 ms -1.032 2.322
Server Offset 135.148.100.14 -31.469 -1.302 3.035 6.034 8.883 103.460 109.098 5.848 104.763 17.769 8.674 ms 4.727 26.05
Server Offset 137.110.222.27 2.083 2.083 3.615 5.797 9.449 10.485 10.485 5.834 8.402 1.558 5.893 ms 0.5532 4.579
Server Offset 137.190.2.4 -13.886 -13.886 -13.886 73.703 432.020 432.020 432.020 445.906 445.906 141.512 93.930 ms 1.772 4.593
Server Offset 139.177.202.26 2.369 2.369 2.369 5.594 13.217 13.217 13.217 10.848 10.848 3.941 6.958 ms 0.6 1.806
Server Offset 139.84.137.244 -88.151 -16.767 -1.366 8.076 12.560 15.955 23.798 13.926 32.722 6.166 6.768 ms -4.604 49.76
Server Offset 139.94.144.123 7.327 7.327 7.327 7.569 8.239 8.239 8.239 0.913 0.913 0.357 7.696 ms 0.4162 1.533
Server Offset 141.11.234.198 -23.184 -23.184 -23.184 3.651 11.780 11.780 11.780 34.964 34.964 8.939 0.688 ms -1.28 4.6
Server Offset 141.11.89.193 2.147 2.147 2.147 3.363 5.337 5.337 5.337 3.190 3.190 1.124 3.580 ms 0.1122 1.688
Server Offset 142.202.190.19 -170.488 -170.488 -169.889 6.947 228.113 229.915 229.915 398.002 400.403 122.650 52.253 ms 0.2226 2.25
Server Offset 144.202.0.197 2.542 2.542 2.542 5.206 10.116 10.116 10.116 7.574 7.574 1.946 5.495 ms 0.6649 3.455
Server Offset 144.202.66.214 -94.866 -94.866 -94.866 -89.704 -88.958 -88.958 -88.958 5.908 5.908 2.060 -91.017 ms -0.812 2.336
Server Offset 148.163.226.148 -76.672 -76.672 -76.672 2.891 6.433 6.433 6.433 83.105 83.105 25.184 -5.515 ms -2.465 7.097
Server Offset 149.248.12.167 6.974 6.974 6.974 12.448 13.486 13.486 13.486 6.511 6.511 2.871 10.594 ms -0.3694 1.196
Server Offset 149.28.200.179 1.712 1.712 3.167 5.584 10.014 25.332 25.332 6.847 23.620 3.335 5.924 ms 4.121 23.91
Server Offset 149.28.61.105 2.916 2.916 2.916 5.252 8.017 8.017 8.017 5.100 5.100 1.667 5.088 ms 0.4936 2.163
Server Offset 15.204.198.96 -806.440 -806.440 -15.115 0.763 4.729 8.189 8.189 19.845 814.629 169.536 -36.913 ms -4.304 19.54
Server Offset 15.204.87.223 -36.284 -8.344 -5.158 -1.169 2.341 163.102 164.832 7.498 171.447 20.085 0.950 ms 7.803 63.6
Server Offset 155.248.196.28 -1.736 -1.736 -1.736 0.032 3.369 3.369 3.369 5.105 5.105 1.769 0.391 ms 0.5292 1.767
Server Offset 158.51.99.19 -157.868 -3.714 0.315 3.544 6.019 8.972 238.853 5.704 12.686 14.413 4.009 ms 11.84 228.2
Server Offset 162.159.200.1 -4.289 0.762 3.679 6.207 8.297 9.197 11.557 4.617 8.435 1.636 6.117 ms -1.454 10.66
Server Offset 162.159.200.123 -6.062 -6.062 -5.886 -0.049 7.264 9.110 9.110 13.149 15.172 4.421 0.662 ms 0.1749 1.786
Server Offset 163.123.152.14 8.299 8.299 8.299 9.300 12.567 12.567 12.567 4.268 4.268 1.664 9.751 ms 0.9993 2.22
Server Offset 166.88.142.52 2.966 2.966 2.966 4.246 7.638 7.638 7.638 4.671 4.671 1.508 4.329 ms 1.273 3.521
Server Offset 168.61.215.74 -405.890 -405.890 -405.076 -2.880 13.022 14.954 14.954 418.098 420.844 173.388 -94.516 ms -1.224 2.507
Server Offset 170.187.147.56 -0.641 -0.241 1.518 4.094 6.492 7.541 8.261 4.974 7.782 1.471 4.099 ms -0.1755 3.293
Server Offset 172.233.153.85 -9.447 -9.196 -7.932 -3.852 1.978 2.524 2.830 9.910 11.720 3.072 -3.587 ms 0.398 2.315
Server Offset 172.233.157.223 -4.047 -4.047 -4.047 3.553 5.955 5.955 5.955 10.002 10.002 3.165 2.404 ms -1.04 2.663
Server Offset 172.233.177.198 -5.527 -5.527 -5.527 3.622 7.415 7.415 7.415 12.942 12.942 3.634 2.383 ms -0.9084 3.103
Server Offset 172.234.25.10 -0.488 -0.488 -0.488 3.459 5.884 5.884 5.884 6.372 6.372 2.046 2.970 ms -0.3216 1.683
Server Offset 172.234.37.140 -9.587 -9.587 -9.587 4.151 11.157 11.157 11.157 20.745 20.745 4.913 3.204 ms -0.9547 3.843
Server Offset 172.234.44.141 -1.177 -1.177 -1.177 4.942 9.373 9.373 9.373 10.549 10.549 3.559 3.891 ms -0.2618 1.724
Server Offset 172.235.60.8 0.376 0.376 0.376 3.004 16.005 16.005 16.005 15.630 15.630 4.175 4.760 ms 1.627 4.998
Server Offset 172.98.15.13 11.306 11.306 11.306 16.540 17.265 17.265 17.265 5.959 5.959 2.760 14.156 ms 0.02368 1.037
Server Offset 173.230.154.254 -28.157 -28.157 -28.157 4.886 11.041 11.041 11.041 39.197 39.197 13.119 -0.101 ms -1.268 3.17
Server Offset 173.249.203.227 2.418 2.418 2.418 7.578 11.331 11.331 11.331 8.912 8.912 2.607 6.865 ms -0.2799 2.399
Server Offset 173.255.192.10 -0.501 -0.501 -0.501 8.854 11.145 11.145 11.145 11.646 11.646 3.481 7.479 ms -1.158 3.37
Server Offset 173.255.255.133 -3.792 -2.842 -0.056 3.924 6.553 465.031 470.949 6.609 467.873 54.595 10.371 ms 8.207 68.45
Server Offset 173.71.68.71 -11.013 -4.530 -1.040 3.562 6.711 464.728 470.128 7.750 469.258 52.893 9.423 ms 8.484 73.13
Server Offset 192.48.105.15 0.449 0.449 0.449 3.200 7.335 7.335 7.335 6.885 6.885 1.829 3.297 ms 0.5249 2.601
Server Offset 193.29.63.226 -97.166 -97.166 -95.281 0.589 7.015 9.170 9.170 102.297 106.336 42.310 -21.757 ms -1.137 2.322
Server Offset 194.0.5.123 -15.181 -4.944 -3.230 -0.145 2.272 3.945 14.812 5.502 8.890 1.763 -0.247 ms -0.2048 7.576
Server Offset 198.137.202.32 -1.462 -1.396 1.619 5.827 7.932 11.548 12.433 6.313 12.944 1.882 5.599 ms -0.7187 6.807
Server Offset 198.199.14.19 -4.168 -4.168 -4.168 3.527 9.207 9.207 9.207 13.374 13.374 3.647 3.201 ms -0.3311 2.34
Server Offset 198.211.103.209 -15.435 -15.435 -7.248 1.023 11.374 11.645 11.645 18.622 27.080 5.487 1.111 ms -0.25 4.025
Server Offset 198.46.254.130 -2.287 0.292 2.403 4.430 9.560 11.525 16.197 7.157 11.234 2.139 4.805 ms 1.192 5.984
Server Offset 198.60.22.240 -144.129 -144.129 -144.129 9.541 18.010 18.010 18.010 162.140 162.140 65.641 -23.178 ms -1.269 2.625
Server Offset 199.68.201.235 2.195 2.195 2.320 4.878 7.295 9.614 9.614 4.975 7.419 1.530 4.830 ms 1.056 5.383
Server Offset 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) 0.214 2.406 3.442 5.288 7.200 7.864 9.487 3.758 5.458 1.200 5.303 ms -0.1227 3.446
Server Offset 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) 0.989 0.989 0.989 6.668 7.419 7.419 7.419 6.430 6.430 2.339 5.470 ms -1.22 2.835
Server Offset 2001:19f0:6401:400:5400:4ff:fec3:522a -7.451 -7.451 -7.451 2.889 10.062 10.062 10.062 17.513 17.513 3.931 2.476 ms -0.6439 4.347
Server Offset 2001:418:3ff::53 (x.ns.gin.ntt.net) 4.247 4.247 4.247 7.231 8.571 8.571 8.571 4.324 4.324 1.678 6.539 ms -0.2545 1.376
Server Offset 2001:418:8405:4002::12 -281.832 -281.832 -281.832 6.130 43.679 43.679 43.679 325.511 325.511 75.678 -13.076 ms -3.151 11.39
Server Offset 2001:418:8405:4002::3 1.964 1.964 1.964 5.204 7.396 7.396 7.396 5.432 5.432 1.953 4.693 ms -0.01811 1.874
Server Offset 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) -43.336 -25.868 -0.459 3.003 5.329 102.804 104.408 5.787 128.672 14.038 4.377 ms 5.842 42.8
Server Offset 2001:470:1f07:24f::123 5.692 5.692 5.692 8.660 52.245 52.245 52.245 46.552 46.552 15.577 16.463 ms 1.347 3.154
Server Offset 2001:470:1f2c:60:123:123:123:123 -34.941 -34.941 -34.941 5.417 179.029 179.029 179.029 213.970 213.970 83.019 55.085 ms 0.6389 1.528
Server Offset 2001:470:e114::d6:12 (1.md.ntp.md) -10.323 -5.218 -0.737 4.529 7.577 464.586 465.594 8.315 469.804 60.950 12.283 ms 7.263 53.84
Server Offset 2001:470:e8dc:10::123 -0.028 0.001 0.004 0.006 0.009 0.011 589.091 0.005 0.010 20.006 0.687 s 29.38 864
Server Offset 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) -809.971 -4.133 0.925 5.173 7.699 8.851 11.403 6.774 12.984 41.024 2.773 ms -19.54 384.4
Server Offset 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com) -0.195 -0.167 1.359 3.625 5.714 8.822 8.875 4.355 8.989 1.443 3.675 ms 0.4961 4.819
Server Offset 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) -157.180 0.965 3.243 5.473 7.719 9.995 23.242 4.475 9.030 5.538 5.305 ms -26.07 749.2
Server Offset 2001:558:6014:17:8dc5:5575:5560:2cb6 -281.200 -281.200 -126.154 4.670 171.115 172.773 172.773 297.269 453.972 76.160 7.959 ms -0.5863 8.15
Server Offset 2001:559:2be:3::1001 -175.433 -175.433 -170.364 5.851 9.897 9.897 9.897 180.261 185.330 63.479 -23.583 ms -1.838 4.527
Server Offset 2001:678:8::123 (any.time.nl) -77.912 -18.791 -10.478 -6.084 -2.852 0.862 214.705 7.626 19.654 7.324 -6.170 ms 22.59 690.6
Server Offset 204.197.163.71 -173.244 -1.861 0.406 2.637 4.342 5.127 14.383 3.936 6.988 8.636 2.114 ms -19.71 398.6
Server Offset 204.2.134.162 3.726 3.726 3.726 9.487 10.513 10.513 10.513 6.787 6.787 2.284 8.433 ms -0.8439 2.293
Server Offset 205.233.73.201 -29.812 -29.812 -18.984 -11.710 221.908 221.908 221.908 240.892 251.721 117.212 88.651 ms 0.199 1.044
Server Offset 208.113.130.146 -807.971 -2.044 0.597 5.657 8.325 10.241 17.688 7.728 12.286 41.081 3.296 ms -19.56 384.7
Server Offset 208.67.72.43 -45.246 -45.246 -45.246 -2.385 1.915 1.915 1.915 47.161 47.161 14.659 -6.938 ms -2.157 5.869
Server Offset 208.67.72.50 -411.370 -407.370 -12.259 -1.276 14.804 461.290 467.446 27.063 868.660 105.580 8.636 ms 1.618 16.62
Server Offset 208.67.75.242 -4.622 -0.573 1.079 4.378 7.071 10.826 240.553 5.992 11.398 17.431 5.561 ms 13.06 173.8
Server Offset 212.227.240.160 0.447 1.002 2.373 4.942 6.721 7.313 9.204 4.348 6.310 1.337 4.781 ms -0.4751 3.423
Server Offset 216.229.4.66 -5.209 -5.209 -5.209 3.423 9.274 9.274 9.274 14.482 14.482 3.953 2.588 ms -0.1056 2.272
Server Offset 216.229.4.69 -565.822 -565.822 -561.261 0.035 3.427 7.531 7.531 564.688 573.353 217.192 -101.392 ms -1.65 3.722
Server Offset 216.240.36.24 -5.803 -5.803 -5.803 -0.195 2.710 2.710 2.710 8.513 8.513 2.260 -0.531 ms -0.9327 3.549
Server Offset 216.31.17.12 -13.524 -13.524 -13.524 1.518 6.326 6.326 6.326 19.850 19.850 5.541 -1.109 ms -0.9513 3.269
Server Offset 23.111.186.186 0.800 0.800 0.800 2.292 3.617 3.617 3.617 2.817 2.817 0.849 2.280 ms -0.2598 2.078
Server Offset 23.131.160.7 -4.498 1.315 2.765 5.400 7.474 8.521 12.984 4.710 7.206 1.459 5.342 ms -0.3744 5.119
Server Offset 23.141.40.123 27.455 27.455 27.455 33.456 37.132 37.132 37.132 9.678 9.678 2.992 32.642 ms -0.3048 2.39
Server Offset 23.142.248.8 8.594 8.594 8.594 10.977 11.802 11.802 11.802 3.207 3.207 1.009 10.550 ms -0.8827 2.771
Server Offset 23.142.248.9 -2.218 -2.218 -2.218 5.433 8.498 8.498 8.498 10.716 10.716 3.219 4.239 ms -0.3035 1.852
Server Offset 23.143.196.199 2.248 2.248 2.248 3.906 5.387 5.387 5.387 3.139 3.139 1.032 4.058 ms -0.2914 2.021
Server Offset 23.150.41.123 -0.725 2.698 5.818 9.930 15.470 18.805 23.764 9.652 16.107 2.921 10.414 ms 0.547 5.963
Server Offset 23.155.40.38 -288.208 -156.059 -4.815 1.534 4.285 10.104 18.366 9.100 166.163 22.289 -1.539 ms -9.379 102
Server Offset 23.168.24.210 7.914 7.914 7.914 12.589 13.467 13.467 13.467 5.553 5.553 2.207 10.952 ms -0.2124 1.412
Server Offset 23.186.168.123 -3.755 -1.507 0.222 2.615 4.450 5.651 13.437 4.228 7.158 1.430 2.525 ms -0.02099 7.779
Server Offset 23.186.168.126 -5.345 -3.200 -1.287 1.767 4.438 5.722 166.185 5.726 8.922 10.343 2.300 ms 15.19 239
Server Offset 23.186.168.127 2.017 2.017 2.017 5.113 8.863 8.863 8.863 6.846 6.846 2.456 5.105 ms 0.3935 1.998
Server Offset 23.186.168.128 -571.345 -2.646 0.616 3.786 5.861 6.834 11.189 5.245 9.479 32.846 1.503 ms -16.49 282.6
Server Offset 23.186.168.129 -23.022 -1.996 -0.428 2.998 5.842 7.926 423.814 6.270 9.922 13.136 3.517 ms 27.32 851.3
Server Offset 23.186.168.130 -4.461 -4.461 -4.284 0.164 5.449 7.796 7.796 9.733 12.257 3.707 0.733 ms 0.06193 1.677
Server Offset 23.186.168.131 -4.751 -0.429 1.142 3.700 5.655 6.700 10.070 4.513 7.129 1.408 3.624 ms -0.5634 5.686
Server Offset 23.186.168.132 -6.108 -0.734 0.944 3.623 5.856 7.065 9.350 4.912 7.799 1.547 3.559 ms -0.388 4.285
Server Offset 23.94.221.138 8.003 8.003 8.003 11.978 13.637 13.637 13.637 5.634 5.634 1.789 11.308 ms -0.8786 2.486
Server Offset 23.95.49.216 -5.139 -2.109 0.660 3.522 5.991 7.369 10.716 5.332 9.478 1.730 3.430 ms -0.7082 6.455
Server Offset 2401:c080:3000:2945:5400:4ff:fe69:f923 (ntpd-rs.sidnlabs.nl) -70.714 -36.132 -21.035 -11.710 -3.560 28.115 38.393 17.475 64.247 8.624 -11.735 ms 1.342 14.51
Server Offset 2402:1f00:8101:d6::1 41.837 41.837 41.837 43.198 43.659 43.659 43.659 1.822 1.822 0.640 42.851 ms -0.3048 1.688
Server Offset 240b:4002:100:9f00:5bd1:9512:8a8b:25e 1.797 1.797 1.797 4.344 8.047 8.047 8.047 6.249 6.249 2.182 4.694 ms 0.2446 1.809
Server Offset 240b:4004:108:200:8314:1a08:4cee:26d6 -53.252 -30.228 -3.522 4.633 7.430 9.190 16.676 10.952 39.418 6.135 3.553 ms -4.789 30.29
Server Offset 240b:4004:108:200:8314:1a08:4cee:26d8 -10.660 -10.660 -1.669 2.211 424.412 425.724 425.724 426.080 436.384 113.328 48.896 ms 2.876 9.733
Server Offset 240b:4004:108:200:8314:1a08:4cee:26d9 3.332 3.332 3.332 5.399 14.354 14.354 14.354 11.022 11.022 4.410 6.823 ms 1.061 2.259
Server Offset 240b:4004:108:200:8314:1a08:4cee:2acf -55.272 -55.272 -55.272 0.474 2.640 2.640 2.640 57.912 57.912 17.808 -5.000 ms -2.456 7.073
Server Offset 2600:1700:3d24:740f:9524:529a:6489:d48f 8.238 8.238 9.877 14.429 17.946 17.946 17.946 8.069 9.708 2.359 13.755 ms -0.5972 2.747
Server Offset 2600:1700:5455:a70::7b:1 -809.818 -809.818 -802.944 -1.720 6.474 21.994 21.994 809.418 831.812 176.723 -42.075 ms -4.096 17.79
Server Offset 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 -16.983 -16.983 2.347 14.361 471.310 472.188 472.188 468.963 489.171 193.989 112.827 ms 1.297 2.69
Server Offset 2600:1700:5a0f:ee00::314:1b -0.511 1.698 6.788 11.589 16.910 21.438 25.234 10.122 19.741 3.117 11.826 ms 0.01519 6.247
Server Offset 2600:1700:5a0f:ee00::314:2b 0.372 0.372 0.372 12.636 16.769 16.769 16.769 16.398 16.398 3.764 12.100 ms -1.682 6.304
Server Offset 2600:1702:7400:9ac0::314:5a 0.498 0.498 0.498 13.966 17.731 17.731 17.731 17.233 17.233 5.163 12.245 ms -1.274 3.293
Server Offset 2600:1702:7400:9ac0::5b 0.162 0.162 0.162 8.450 11.368 11.368 11.368 11.206 11.206 3.725 6.660 ms -0.2939 1.735
Server Offset 2600:1900:4060:2e7:: (0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.e.2.0.0.6.0.4.0.0.9.1.0.0.6.2.bc.googleusercontent.com) -90.591 -13.489 -3.590 1.754 4.959 7.566 17.081 8.549 21.055 4.239 1.308 ms -8.678 153.5
Server Offset 2600:1f13:2c1:2e00::be00:5 -282.490 -1.401 3.361 6.350 9.277 21.057 75.600 5.916 22.458 11.306 6.295 ms -17.94 473.5
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) -155.691 -7.425 -5.731 3.067 6.244 8.116 110.743 11.974 15.541 4.932 1.630 ms -2.613 232.5
Server Offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) -159.116 -7.028 -3.909 3.387 6.614 8.454 422.200 10.523 15.482 6.360 2.442 ms 19.34 1705
Server Offset 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) -158.177 -23.587 -5.987 3.740 7.368 9.926 415.823 13.355 33.513 7.678 2.179 ms 9.969 765.7
Server Offset 2600:1f18:7927:8b00:123:: 4.710 4.710 4.710 6.720 8.399 8.399 8.399 3.689 3.689 1.160 6.461 ms 0.06963 2.058
Server Offset 2600:2600::99 (ntp1.wiktel.com) 10.504 10.504 10.504 11.340 11.340 11.340 11.340 0.836 0.836 0.418 10.922 ms -6.279e-15 1
Server Offset 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) -3.406 -0.525 0.747 3.156 7.026 10.573 17.498 6.279 11.098 2.062 3.438 ms 1.184 6.539
Server Offset 2600:3c00:e000:318::1 (jane.qotw.net) -28.246 -0.004 1.379 3.315 5.169 6.398 10.314 3.789 6.402 1.515 3.268 ms -6.661 141.7
Server Offset 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) 2.725 2.725 2.725 5.114 14.625 14.625 14.625 11.900 11.900 4.070 5.808 ms 1.545 3.777
Server Offset 2600:3c01::f03c:93ff:fedd:5a1f (sensei.ruselabs.com) -16.936 -16.936 -5.885 2.642 423.840 424.816 424.816 429.725 441.752 116.114 50.434 ms 2.724 8.986
Server Offset 2600:3c01:e000:7e6::123 (time1.sigi.net) -170.467 0.056 3.237 5.672 7.881 8.850 11.725 4.644 8.794 9.635 5.092 ms -17.71 322.2
Server Offset 2600:3c02::f03c:92ff:fe96:dc0 -21.719 -4.622 -0.261 6.280 12.408 13.569 18.625 12.669 18.191 3.801 6.313 ms -1.28 11.52
Server Offset 2600:3c02::f03c:94ff:fe59:f411 3.748 3.748 3.748 6.064 12.748 12.748 12.748 9.000 9.000 3.879 7.163 ms 0.6006 1.484
Server Offset 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net) -1.758 0.272 2.422 5.275 7.286 8.980 9.933 4.864 8.708 1.546 5.181 ms -0.6519 4.856
Server Offset 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) 0.867 0.867 1.114 3.790 6.386 7.915 7.915 5.272 7.048 1.512 3.637 ms 0.418 3.502
Server Offset 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) -572.795 -572.795 -572.795 -9.263 4.262 4.262 4.262 577.057 577.057 280.556 -253.542 ms -0.2234 1.051
Server Offset 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) -24.915 -11.563 -0.995 6.413 26.413 418.227 423.497 27.408 429.790 45.378 12.854 ms 8.158 72.77
Server Offset 2600:3c03::f03c:94ff:fe59:d3de 2.854 2.854 2.854 2.958 4.537 4.537 4.537 1.683 1.683 0.770 3.449 ms 0.6976 1.5
Server Offset 2600:3c03:e002:1300::10 (ntp.electronmill.com) -3.742 -3.742 -3.742 3.270 6.177 6.177 6.177 9.919 9.919 3.310 1.757 ms -0.3528 1.728
Server Offset 2600:3c06::f03c:94ff:fee2:9c28 5.742 5.742 5.742 7.946 15.389 15.389 15.389 9.646 9.646 3.904 8.785 ms 1.004 2.198
Server Offset 2600:3c06::f03c:94ff:fee2:c53a 7.934 7.934 7.934 10.652 34.769 34.769 34.769 26.835 26.835 12.061 17.785 ms 0.6803 1.5
Server Offset 2600:4040:3037:e600::1 2.842 2.842 2.842 6.051 6.051 6.051 6.051 3.209 3.209 1.605 4.447 ms -8.009e-16 1
Server Offset 2600:4040:e0da:f000::cbb9:201a -99.353 -99.353 -97.880 3.306 8.180 46.292 46.292 106.060 145.645 34.906 -8.837 ms -1.974 5.486
Server Offset 2602:291:69::8 (time2.tritan-bb.net) -87.855 -87.855 -87.855 -86.413 -85.482 -85.482 -85.482 2.373 2.373 0.712 -86.511 ms -0.5905 2.861
Server Offset 2602:291:69::9 (time.tritan-bb.net) -570.253 -570.253 -566.922 5.391 21.445 21.495 21.495 588.367 591.748 190.371 -63.466 ms -2.261 6.126
Server Offset 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) -158.684 -3.456 -0.080 2.050 4.212 6.155 10.845 4.293 9.610 7.377 1.718 ms -20.23 430.7
Server Offset 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net) 7.226 7.226 7.226 8.619 9.227 9.227 9.227 2.002 2.002 0.838 8.357 ms -0.4377 1.5
Server Offset 2602:2eb:2:95:1234:5678:9abc:def0 -177.116 -4.361 -1.059 2.594 6.566 8.773 240.974 7.624 13.133 11.661 2.870 ms 12.1 337.6
Server Offset 2602:80b:5000::36 (time.meme.holdings) -26.339 -9.392 1.266 5.868 9.817 23.455 24.890 8.551 32.847 4.663 5.601 ms -1.967 22.8
Server Offset 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) -2.396 -2.396 -2.396 0.924 11.083 11.083 11.083 13.479 13.479 4.287 2.602 ms 0.7321 2.194
Server Offset 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) -412.469 -410.991 -9.243 1.817 13.963 25.256 77.682 23.206 436.248 60.595 -5.754 ms -6.348 42.52
Server Offset 2602:fb95:16::123 (time5.sigi.net) -3.415 -3.415 -3.415 2.197 8.657 8.657 8.657 12.072 12.072 3.322 1.725 ms 0.2884 2.931
Server Offset 2602:fc2f:100:9800::dead:beef -17.617 0.601 3.135 6.681 10.772 15.339 240.110 7.637 14.738 16.340 7.872 ms 13.35 186.8
Server Offset 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) -2.937 -2.937 -1.379 2.434 7.512 9.493 9.493 8.892 12.430 2.905 2.389 ms 0.4696 3.021
Server Offset 2602:fe2e:3:d:f9:c7ff:fef5:379c 3.035 3.035 3.035 6.211 8.657 8.657 8.657 5.622 5.622 1.762 5.927 ms -0.1747 2.107
Server Offset 2602:ff06:725:100::123 (oldtime2.sigi.net) 3.097 3.097 3.097 9.383 10.512 10.512 10.512 7.414 7.414 2.231 8.621 ms -1.753 4.815
Server Offset 2602:ff23:50:3c2::1 (dns-e.ns4v.icu) -414.428 -412.103 -5.498 2.874 14.322 38.967 85.012 19.820 451.069 59.635 -4.424 ms -6.489 44.25
Server Offset 2603:c020:0:8369:0:ba11:ba11:ba11 -422.469 -422.469 -419.944 -7.467 4.024 4.850 4.850 423.968 427.319 153.878 -75.499 ms -1.784 4.191
Server Offset 2603:c020:0:8369:1111:1111:1111:1112 -55.331 -55.331 -46.563 -5.926 94.091 94.407 94.407 140.654 149.738 40.627 10.132 ms 1.219 3.267
Server Offset 2603:c020:0:8369::bad:beef -6.830 -6.830 -6.830 -3.090 -2.867 -2.867 -2.867 3.963 3.963 1.885 -4.862 ms 0.002145 1.011
Server Offset 2603:c020:0:8369::f00d:feed -17.667 -17.667 -15.791 -5.100 453.988 458.206 458.206 469.779 475.874 188.222 87.341 ms 1.435 3.061
Server Offset 2603:c020:0:8369::feeb:dab -19.462 -19.462 -18.508 -9.177 453.345 453.880 453.880 471.853 473.342 182.625 78.325 ms 1.56 3.436
Server Offset 2603:c020:0:8369:feed:feed:feed:feed -18.686 -18.686 -18.686 -5.363 -1.212 -1.212 -1.212 17.474 17.474 4.007 -6.304 ms -1.91 6.79
Server Offset 2603:c020:6:b900:6b54:1390:4afd:814a -420.366 -420.366 -420.366 -15.121 2.174 2.174 2.174 422.540 422.540 183.604 -122.964 ms -0.9887 1.983
Server Offset 2603:c020:6:b900:ed2f:b442:fee7:d9b9 -9.081 -9.081 -9.081 -3.889 -1.558 -1.558 -1.558 7.523 7.523 2.325 -4.454 ms -0.9557 3.036
Server Offset 2603:c024:c005:a600:efb6:d213:cad8:251d 1.713 1.713 1.713 11.865 68.213 68.213 68.213 66.499 66.499 21.793 19.547 ms 1.448 3.682
Server Offset 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 4.360 4.360 7.868 9.469 13.253 17.815 17.815 5.385 13.455 2.164 9.765 ms 1.273 7.496
Server Offset 2604:2dc0:100:4d6:: 6.451 6.451 6.451 7.846 12.197 12.197 12.197 5.746 5.746 2.175 8.548 ms 0.9328 2.204
Server Offset 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) 2.819 2.819 2.819 10.472 14.418 14.418 14.418 11.599 11.599 3.534 9.984 ms -0.574 2.357
Server Offset 2604:2dc0:202:300::140d (ovh.maxhost.io) -10.884 -6.103 -4.364 -1.787 0.663 2.038 13.335 5.027 8.141 1.665 -1.837 ms 0.09333 10.2
Server Offset 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) -49.930 -36.749 -6.555 2.041 5.114 6.502 22.290 11.670 43.251 5.807 0.770 ms -4.61 31.25
Server Offset 2604:4300:a:299::164 -9.675 -9.675 -6.261 -0.158 3.067 3.865 3.865 9.328 13.539 3.536 -1.195 ms -0.6405 2.55
Server Offset 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) -802.674 -802.674 -802.674 2.272 9.840 9.840 9.840 812.514 812.514 371.058 -243.393 ms -0.8332 1.694
Server Offset 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) 4.759 4.759 4.759 5.795 36.164 36.164 36.164 31.405 31.405 14.567 15.573 ms 0.7044 1.5
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -97.614 -97.614 -97.614 -96.252 -95.198 -95.198 -95.198 2.416 2.416 0.727 -96.393 ms -0.05135 2.552
Server Offset 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) -40.303 -1.773 0.146 2.726 5.501 103.648 104.341 5.355 105.421 14.429 4.427 ms 6.057 42.23
Server Offset 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) -6.372 -6.372 -3.109 11.458 218.960 218.960 218.960 222.069 225.332 83.767 47.473 ms 1.451 3.181
Server Offset 2604:a880:800:10::70f:b001 (ellone.fdisk.io) 3.373 3.373 3.373 8.241 9.581 9.581 9.581 6.208 6.208 1.791 7.376 ms -0.8255 2.41
Server Offset 2604:a880:800:a1::ec9:5001 -127.479 -127.479 -5.442 6.181 17.508 17.508 17.508 22.949 144.987 29.551 -0.176 ms -3.971 17.23
Server Offset 2604:d200::39 (white.web-ster.com) -4.662 -4.662 -4.662 -2.055 0.687 0.687 0.687 5.349 5.349 1.751 -2.305 ms 0.2579 1.689
Server Offset 2605:4840:3:fb19::1 (chi3.us.ntp.li) -278.261 -8.779 -1.179 2.716 7.022 29.833 89.152 8.201 38.612 10.597 2.909 ms -14.92 445.8
Server Offset 2605:6400:488d:2eda:eee9:fe8d:4543:d471 6.277 6.277 6.277 10.872 10.872 10.872 10.872 4.595 4.595 2.297 8.574 ms -5.457e-16 1
Server Offset 2605:6400:488d:3686:546d:c03c:1689:20c 0.063 0.063 0.063 10.815 77.942 77.942 77.942 77.879 77.879 31.733 28.904 ms 0.6938 1.564
Server Offset 2605:6400:84e1::123 (oldtime3.sigi.net) 0.114 0.114 0.114 234.240 240.273 240.273 240.273 240.159 240.159 112.476 147.282 ms -0.474 1.227
Server Offset 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) -1.370 -1.370 -1.370 3.697 9.921 9.921 9.921 11.292 11.292 2.854 4.172 ms 0.1428 3.178
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -170.499 -5.254 -1.615 5.567 8.603 10.602 214.236 10.218 15.856 5.510 5.177 ms 13.09 708.9
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -810.498 -3.457 -0.858 5.411 8.658 11.643 468.641 9.516 15.099 20.712 5.095 ms -16.6 892.9
Server Offset 2606:82c0:21::e (time1.lshiy.com) -0.347 -0.347 -0.347 2.470 5.026 5.026 5.026 5.373 5.373 1.632 2.157 ms 0.07044 2.391
Server Offset 2606:82c0:22::e (time2.lshiy.com) -105.777 -105.777 -105.777 5.039 20.159 20.159 20.159 125.937 125.937 53.616 -35.047 ms -0.3967 1.186
Server Offset 2606:82c0:23::e (time3.lshiy.com) 3.326 3.326 3.326 7.253 12.695 12.695 12.695 9.369 9.369 2.739 7.383 ms 0.4156 2.484
Server Offset 2607:5600:182:500::1 (ntp-1.jonlight.com) -568.165 -568.165 -568.165 -0.446 11.465 11.465 11.465 579.631 579.631 265.791 -190.495 ms -0.701 1.5
Server Offset 2607:7c80:54:3::32 -2.394 0.513 2.688 5.205 8.247 11.037 88.040 5.560 10.524 3.400 5.362 ms 16.18 369.6
Server Offset 2607:7c80:54:3::56 (owners.kjsl.com) -806.909 -806.909 -5.703 0.187 5.818 9.156 9.156 11.521 816.065 173.398 -38.752 ms -4.188 18.54
Server Offset 2607:9000:7000:23:216:3cff:fe25:38d7 -3.352 -0.375 0.741 4.354 8.207 9.388 11.040 7.466 9.763 2.317 4.364 ms -0.006342 2.996
Server Offset 2607:9d00:2000:16::9269:208a 0.027 0.027 0.549 5.418 11.274 17.615 17.615 10.726 17.588 3.719 5.554 ms 1.403 5.818
Server Offset 2607:b500:410:7700::1 -559.793 -559.793 -558.023 15.880 247.118 247.131 247.131 805.140 806.924 235.950 5.184 ms -1.393 4.315
Server Offset 2607:f1c0:f014:9e00::1 -0.782 -0.782 -0.782 3.789 12.363 12.363 12.363 13.145 13.145 4.161 4.437 ms 0.4965 2.056
Server Offset 2607:f1c0:f014:9e00::2 -2.137 -2.137 0.533 8.769 175.012 176.141 176.141 174.479 178.278 60.511 32.888 ms 1.871 4.578
Server Offset 2607:f1c0:f04e:fd00::1 -0.324 -0.324 -0.324 4.901 12.270 12.270 12.270 12.594 12.594 3.373 4.498 ms 0.7124 3.491
Server Offset 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) -64.809 -64.809 -64.809 -61.044 -58.237 -58.237 -58.237 6.572 6.572 2.268 -61.730 ms -0.02717 1.823
Server Offset 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) 2.778 2.778 2.778 7.554 7.962 7.962 7.962 5.184 5.184 1.862 6.389 ms -1.034 2.559
Server Offset 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at) 10.032 10.032 10.032 11.425 11.425 11.425 11.425 1.393 1.393 0.696 10.729 ms 3.751e-15 1
Server Offset 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) 6.196 6.196 6.196 9.764 23.462 23.462 23.462 17.266 17.266 5.350 11.804 ms 1.241 3.45
Server Offset 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) -2.373 -2.373 -1.407 3.297 10.246 11.084 11.084 11.653 13.458 3.531 3.807 ms 0.3808 2.37
Server Offset 2607:f1c0:f075:9900::1 -11.364 -11.364 -8.290 9.893 429.232 429.472 429.472 437.522 440.836 115.991 54.692 ms 2.751 9.098
Server Offset 2607:f298:5:101d:f816:3eff:fefd:8817 -174.467 -174.467 -172.715 3.910 20.484 20.484 20.484 193.199 194.951 64.078 -20.926 ms -1.945 4.813
Server Offset 2607:f3c8:3803:1::6 -6.026 -6.026 -6.026 2.471 214.987 214.987 214.987 221.013 221.013 95.937 61.079 ms 0.9476 1.902
Server Offset 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) -23.263 -23.263 -23.263 -10.419 26.993 26.993 26.993 50.256 50.256 13.527 -6.124 ms 0.7442 2.94
Server Offset 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) 6.293 6.293 6.293 9.644 16.365 16.365 16.365 10.072 10.072 2.800 10.002 ms 0.8431 3.217
Server Offset 2607:f710:35::29c:0:5 1.230 1.230 1.230 6.637 13.998 13.998 13.998 12.768 12.768 3.502 7.121 ms 0.34 2.688
Server Offset 2607:f710:35::29c:0:8 -3.482 -1.256 1.976 4.319 6.532 9.029 12.497 4.556 10.285 1.590 4.260 ms -0.3604 7.445
Server Offset 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) -158.123 -158.123 -158.123 3.807 12.552 12.552 12.552 170.675 170.675 66.662 -31.139 ms -1.273 2.639
Server Offset 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com) 4.183 4.183 4.183 8.895 11.415 11.415 11.415 7.232 7.232 2.452 8.699 ms -0.9315 2.629
Server Offset 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com) -1.149 2.106 3.500 5.817 7.713 8.724 10.233 4.212 6.619 1.327 5.750 ms -0.4876 4.269
Server Offset 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com) -0.204 1.005 2.637 5.063 7.033 8.021 9.117 4.396 7.016 1.373 4.978 ms -0.4552 3.887
Server Offset 2620:83:8000:140::b (tic.lbl.gov) -64.202 -16.454 -0.037 2.751 5.105 7.089 169.920 5.142 23.543 8.350 2.692 ms 14.74 314
Server Offset 2620:83:8000:140::c (toc.lbl.gov) -8.902 -3.197 0.915 6.115 12.932 16.845 18.523 12.018 20.042 3.819 6.351 ms 0.131 4.597
Server Offset 2620:8d:c000::f (blotch.image1tech.net) -12.501 -12.501 -12.501 0.670 15.127 15.127 15.127 27.628 27.628 9.564 -0.984 ms 0.2932 2
Server Offset 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) -7.979 -7.979 -7.979 -0.845 213.035 213.035 213.035 221.015 221.015 98.515 62.052 ms 0.8326 1.697
Server Offset 2620:b0:2000:102::1:123 (time-h.den.codehof.net) -107.407 -107.407 -107.407 -66.747 92.475 92.475 92.475 199.883 199.883 57.820 -44.390 ms 1.21 3.478
Server Offset 2620:b0:2000:102::2:123 (time-he.den.codehof.net) -44.889 -44.889 -44.889 22.240 34.334 34.334 34.334 79.222 79.222 22.949 14.406 ms -2.048 5.652
Server Offset 2a00:d78:0:712:94:198:159:11 (nts1.time.nl) -96.622 -6.929 -0.552 2.316 5.247 8.796 15.564 5.799 15.724 3.642 2.209 ms -13.78 330.8
Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) -810.640 -44.134 -17.627 3.292 9.170 14.212 465.738 26.797 58.346 17.909 0.307 ms -12.94 750.9
Server Offset 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) -178.311 -47.855 -19.285 1.281 8.153 11.195 209.396 27.439 59.050 11.840 -1.369 ms -2.138 61.16
Server Offset 2a01:4ff:f0:e33b::1 -0.405 1.341 2.845 5.084 7.763 10.129 12.458 4.918 8.789 1.688 5.148 ms 0.5654 5.665
Server Offset 2a01:4ff:f0:ebce::1 8.384 8.384 8.384 34.231 34.231 34.231 34.231 25.847 25.847 12.924 21.307 ms 1.962e-16 1
Server Offset 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) -51.215 -51.215 -51.215 6.741 19.073 19.073 19.073 70.288 70.288 23.048 -2.114 ms -1.242 3.142
Server Offset 2a01:7e04::f03c:94ff:fee2:cba5 -26.406 -26.406 -26.406 2.333 5.249 5.249 5.249 31.655 31.655 7.170 0.454 ms -3.228 12.34
Server Offset 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) -1.952 -1.380 -0.052 3.121 7.600 10.298 13.358 7.652 11.679 2.033 3.294 ms 1.115 6.929
Server Offset 34.147.28.4 -33.036 -17.922 -5.992 -1.956 1.805 4.539 9.658 7.797 22.461 3.509 -2.228 ms -3.24 25.1
Server Offset 37.27.11.4 -51.314 -10.261 -2.384 0.947 3.098 4.523 4.544 5.482 14.784 4.805 0.292 ms -9.244 98.81
Server Offset 44.190.5.123 -619.209 0.510 2.373 5.247 7.388 8.599 28.290 5.014 8.089 9.005 4.880 ms -51.42 3247
Server Offset 45.55.126.202 -4.945 0.220 1.800 4.365 6.846 8.437 10.649 5.046 8.216 1.549 4.364 ms -0.4012 6.047
Server Offset 45.61.187.39 -3.631 -3.631 -3.631 4.490 13.757 13.757 13.757 17.388 17.388 4.830 3.741 ms 0.536 3.14
Server Offset 45.63.54.13 -14.116 -0.809 2.451 5.749 9.193 15.128 27.310 6.742 15.937 2.596 5.789 ms 0.6719 17.26
Server Offset 45.77.126.122 0.280 0.280 0.280 4.312 5.554 5.554 5.554 5.273 5.273 1.572 3.685 ms -0.6575 2.314
Server Offset 45.79.35.159 3.746 3.746 3.746 7.855 8.568 8.568 8.568 4.821 4.821 2.112 6.125 ms 0.01386 1.093
Server Offset 45.79.51.42 -45.604 -45.604 -45.604 8.683 108.150 108.150 108.150 153.754 153.754 57.087 39.510 ms 0.07989 1.347
Server Offset 45.83.234.123 -296.062 -296.062 -36.862 5.462 11.429 15.325 15.325 48.291 311.387 44.156 -5.332 ms -5.514 35.05
Server Offset 45.84.199.136 -110.729 -110.729 -110.729 -97.871 9.546 9.546 9.546 120.275 120.275 54.799 -52.941 ms 0.172 1.055
Server Offset 46.37.96.107 -808.769 -33.538 -1.905 5.043 7.457 8.750 17.475 9.362 42.288 37.739 2.042 ms -20.74 443.5
Server Offset 5.161.111.190 -0.126 1.188 2.722 5.546 7.480 8.196 9.034 4.758 7.008 1.412 5.394 ms -0.7297 4.131
Server Offset 5.78.62.36 -8.523 -2.092 0.307 5.929 11.849 15.869 16.396 11.542 17.960 3.566 6.030 ms 0.08899 3.94
Server Offset 50.117.3.52 -8.085 -8.085 -8.085 -6.204 -5.368 -5.368 -5.368 2.717 2.717 0.914 -6.560 ms -0.319 1.928
Server Offset 50.117.3.95 -146.276 -146.276 -146.276 8.636 18.465 18.465 18.465 164.741 164.741 63.106 -20.370 ms -1.48 3.224
Server Offset 50.205.57.38 -18.950 0.701 2.860 5.414 7.496 10.285 20.357 4.636 9.585 1.767 5.407 ms -1.488 39.77
Server Offset 50.218.103.254 6.935 6.935 6.935 10.777 11.835 11.835 11.835 4.899 4.899 1.768 9.997 ms -0.768 2.084
Server Offset 51.81.20.76 2.414 2.414 2.414 7.712 11.524 11.524 11.524 9.111 9.111 3.247 7.454 ms -0.2642 1.777
Server Offset 51.81.226.229 -178.118 -178.118 -173.190 4.447 15.237 22.510 22.510 188.427 200.627 62.005 -17.820 ms -2.094 5.445
Server Offset 64.142.54.12 9.100 9.100 9.100 11.576 22.059 22.059 22.059 12.959 12.959 3.920 12.706 ms 1.335 3.639
Server Offset 64.6.144.6 -8.057 -8.057 -8.057 -4.073 467.377 467.377 467.377 475.434 475.434 226.098 164.803 ms 0.5668 1.322
Server Offset 64.79.100.197 -5.398 -1.308 0.115 2.437 4.257 5.695 7.196 4.142 7.002 1.439 2.356 ms -1.086 9.14
Server Offset 65.100.46.164 -12.522 -2.725 -0.387 4.920 11.409 15.307 17.739 11.796 18.032 3.731 5.348 ms 0.01927 4.589
Server Offset 65.100.46.166 0.249 1.083 2.398 5.335 7.816 11.010 13.272 5.418 9.928 1.740 5.341 ms 0.2817 4.931
Server Offset 65.182.224.39 1.814 1.814 1.814 2.848 5.791 5.791 5.791 3.977 3.977 1.315 3.059 ms 1.249 3.327
Server Offset 66.118.231.14 -27.328 -27.328 -11.996 4.815 12.740 46.019 46.019 24.736 73.347 10.026 2.952 ms 0.8298 9.385
Server Offset 66.42.71.197 -4.404 1.164 3.246 6.075 8.417 9.829 440.870 5.171 8.665 20.411 6.942 ms 20.87 439.3
Server Offset 66.59.198.94 -3.193 -3.193 -3.193 1.753 7.991 7.991 7.991 11.183 11.183 3.576 2.287 ms 0.3048 1.825
Server Offset 66.85.78.80 1.863 1.863 1.863 5.833 6.542 6.542 6.542 4.679 4.679 1.783 4.731 ms -0.7192 1.975
Server Offset 67.217.246.127 -4.257 -3.477 -0.379 2.528 6.202 9.675 10.219 6.580 13.152 2.004 2.572 ms 0.5419 6.199
Server Offset 67.217.246.204 -407.881 -405.967 -8.655 0.545 14.549 52.682 423.145 23.204 458.649 74.575 -3.927 ms -1.928 29.64
Server Offset 68.234.48.70 -2.973 -2.973 -2.973 9.512 47.817 47.817 47.817 50.790 50.790 12.262 11.128 ms 2.266 7.46
Server Offset 69.176.84.38 -4.887 -4.887 -3.512 1.450 3.073 4.499 4.499 6.585 9.386 2.266 0.622 ms -0.718 2.493
Server Offset 69.48.203.16 2.540 2.540 2.540 7.439 10.588 10.588 10.588 8.048 8.048 2.329 7.070 ms -0.4418 2.4
Server Offset 69.89.207.199 -35.854 -5.484 0.115 2.952 8.851 103.597 425.249 8.736 109.081 27.435 6.199 ms 12.72 187.6
Server Offset 69.89.207.99 -82.728 -2.318 -0.017 2.894 4.643 5.551 6.408 4.661 7.869 3.416 2.593 ms -20.67 515
Server Offset 71.123.46.186 -0.765 -0.089 1.160 4.514 7.163 9.760 10.300 6.003 9.849 1.893 4.465 ms 0.0854 3.856
Server Offset 71.19.144.140 -3.221 -3.221 -3.221 4.015 7.428 7.428 7.428 10.649 10.649 2.867 3.283 ms -0.3728 2.496
Server Offset 72.14.183.39 5.676 5.676 5.676 6.591 11.748 11.748 11.748 6.071 6.071 2.174 7.473 ms 1.37 3.097
Server Offset 72.14.186.59 2.611 2.611 2.611 5.374 7.023 7.023 7.023 4.412 4.412 1.489 5.305 ms -0.8276 2.527
Server Offset 72.30.35.89 8.994 8.994 8.994 12.518 13.297 13.297 13.297 4.303 4.303 1.872 11.603 ms -0.6164 1.5
Server Offset 72.46.53.234 -35.275 -35.275 -35.275 69.197 105.228 105.228 105.228 140.503 140.503 52.722 51.699 ms -0.2012 1.301
Server Offset 72.46.61.205 -285.110 -285.110 -285.110 6.157 16.075 16.075 16.075 301.185 301.185 73.049 -25.856 ms -2.768 9.979
Server Offset 73.185.182.209 -2.743 0.925 2.341 5.411 8.588 10.253 11.822 6.247 9.328 1.947 5.428 ms -0.05719 3.857
Server Offset 73.65.80.137 -809.727 -809.727 -9.135 -1.384 3.688 7.510 7.510 12.823 817.238 169.002 -38.192 ms -4.333 19.79
Server Offset 74.119.243.5 1.643 1.643 1.643 7.015 7.452 7.452 7.452 5.809 5.809 2.661 4.585 ms -0.008075 1.037
Server Offset 74.208.117.38 -8.056 -8.056 -8.056 -3.727 11.177 11.177 11.177 19.233 19.233 5.901 -2.284 ms 1.09 3.094
Server Offset 74.208.14.149 -5.945 -5.945 -5.945 8.847 11.709 11.709 11.709 17.654 17.654 5.690 5.541 ms -1.091 3.04
Server Offset 74.208.25.46 -7.530 -3.640 -0.753 4.698 12.042 18.695 486.710 12.795 22.336 25.751 6.862 ms 13.8 210.5
Server Offset 77.37.97.124 -67.897 -19.625 -4.883 7.206 12.622 16.428 24.791 17.505 36.053 6.393 6.396 ms -3.658 29.94
Server Offset 77.42.37.85 -9.917 -9.917 -3.792 0.856 4.298 12.641 12.641 8.090 22.559 2.826 0.867 ms -0.03694 8.815
Server Offset 83.147.242.172 -1.026 1.305 3.079 5.350 7.728 10.018 14.032 4.649 8.714 1.528 5.378 ms 0.287 5.704
Server Offset 94.198.159.11 9.843 9.843 9.843 9.843 9.843 9.843 9.843 0.000 0.000 0.000 9.843 ms nan nan
Server Offset 99.28.14.242 -568.386 -2.050 0.773 4.332 6.974 9.919 171.646 6.201 11.970 46.430 1.696 ms -10.89 137.6
TDOP 0.490 0.560 0.620 0.910 11.810 11.810 12.680 11.190 11.250 2.698 1.707 3.378 12.74
Temp /dev/sda 15.000 18.000 20.000 25.000 26.000 28.000 39.000 6.000 10.000 2.432 23.827 °C
Temp LM0 28.000 30.000 31.000 34.000 41.000 45.000 54.000 10.000 15.000 2.918 34.183 °C
Temp LM1 26.000 28.000 29.000 38.000 39.000 40.000 44.000 10.000 12.000 3.173 36.382 °C
Temp LM2 0.000 0.000 0.000 19.000 34.000 34.000 51.000 34.000 34.000 7.234 20.217 °C
Temp LM3 24.000 26.000 27.000 30.000 38.000 39.000 46.000 11.000 13.000 3.200 31.060 °C
Temp LM4 0.000 0.000 0.000 32.000 41.000 44.000 56.000 41.000 44.000 12.823 28.355 °C
Temp LM5 24.000 26.000 27.000 30.000 32.000 32.000 45.000 5.000 6.000 1.441 29.777 °C
Temp LM6 26.000 28.000 29.000 32.000 34.000 38.000 50.000 5.000 10.000 1.715 32.151 °C
Temp LM7 28.000 30.000 31.000 34.000 36.000 39.000 51.000 5.000 9.000 1.673 33.987 °C
Temp LM8 28.000 31.000 32.000 35.000 37.000 39.000 51.000 5.000 8.000 1.666 34.321 °C
Temp LM9 28.000 31.000 32.000 35.000 37.000 39.000 51.000 5.000 8.000 1.666 34.320 °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 28.000 30.000 31.000 34.000 36.000 39.000 51.000 5.000 9.000 1.703 33.436 °C
Temp ZONE2 24.000 26.000 27.000 30.000 32.000 32.000 45.000 5.000 6.000 1.440 29.777 °C
Temp ZONE3 28.000 30.000 31.000 34.000 36.000 39.000 51.000 5.000 9.000 1.705 33.442 °C
Temp ZONE4 28.000 30.000 31.000 34.000 36.000 39.000 51.000 5.000 9.000 1.703 33.436 °C
Temp ZONE5 27.000 29.000 30.000 32.000 42.000 47.000 56.000 12.000 18.000 4.177 34.415 °C
Temp ZONE6 24.000 26.000 27.000 30.000 32.000 34.000 44.000 5.000 8.000 1.493 29.784 °C
nSats 6.000 8.000 9.000 10.000 13.000 14.000 16.000 4.000 6.000 1.264 10.660 nSat 0.2722 3.549
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!