NTPsec

Dell-2018

Report generated: Thu Sep 17 23:30:04 2026 UTC
Start Time: Thu Jun 11 23:30:02 2026 UTC
End Time: Thu Sep 17 23:30:02 2026 UTC
Report Period: 98.0 days

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

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -127.900 -3.900 -0.608 -0.030 0.436 2.086 30.877 1.044 5.985 2.069 -0.108 ms -45.16 2583
Local Clock Frequency Offset -187.984 10.708 10.936 11.447 11.825 17.678 183.534 0.889 6.971 2.286 11.543 ppm -33.4 5691

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.188 0.229 0.348 0.906 3.041 45.220 0.677 2.854 0.886 0.461 ms 28.9 1176

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.0037 0.0046 0.0068 0.069 0.231 96.849 0.065 0.227 2.299 0.106 ppm 31.43 1069

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

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

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



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -127.900 -3.900 -0.608 -0.030 0.436 2.086 30.877 1.044 5.985 2.069 -0.108 ms -45.16 2583

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 -187.984 10.708 10.936 11.447 11.825 17.678 183.534 0.889 6.971 2.286 11.543 ppm -33.4 5691
Temp /dev/sda 18.000 20.000 20.000 26.000 26.000 28.000 33.000 6.000 8.000 2.275 24.591 °C
Temp LM0 29.000 31.000 32.000 35.000 36.000 39.000 54.000 4.000 8.000 1.725 34.726 °C
Temp LM1 28.000 30.000 31.000 35.000 39.000 42.000 54.000 8.000 12.000 2.682 35.257 °C
Temp LM2 0.000 0.000 19.000 36.000 40.000 40.000 48.000 21.000 40.000 8.525 32.751 °C
Temp LM3 0.000 0.000 19.000 38.000 40.000 41.000 44.000 21.000 41.000 9.383 31.847 °C
Temp LM4 0.000 0.000 0.000 0.000 42.000 45.000 49.000 42.000 45.000 18.565 17.825 °C
Temp LM5 27.000 28.000 29.000 33.000 41.000 41.000 53.000 12.000 13.000 4.113 34.179 °C
Temp LM6 28.000 30.000 31.000 35.000 37.000 37.000 47.000 6.000 7.000 1.527 34.395 °C
Temp LM7 31.000 32.000 33.000 36.000 38.000 39.000 49.000 5.000 7.000 1.577 36.098 °C
Temp LM8 31.000 32.000 33.000 37.000 39.000 39.000 49.000 6.000 7.000 1.557 36.206 °C
Temp LM9 31.000 32.000 33.000 37.000 39.000 39.000 49.000 6.000 7.000 1.557 36.206 °C
Temp ZONE0 20.000 20.000 20.000 20.000 20.000 20.000 20.000 0.000 0.000 0.000 20.000 °C
Temp ZONE1 30.000 32.000 33.000 36.000 38.000 38.000 48.000 5.000 6.000 1.498 35.563 °C
Temp ZONE2 27.000 28.000 29.000 33.000 41.000 41.000 41.000 12.000 13.000 4.003 34.379 °C
Temp ZONE3 30.000 31.000 32.000 36.000 38.000 43.000 54.000 6.000 12.000 1.992 35.448 °C
Temp ZONE4 30.000 32.000 33.000 36.000 38.000 38.000 48.000 5.000 6.000 1.498 35.563 °C
Temp ZONE5 30.000 31.000 32.000 36.000 42.000 45.000 54.000 10.000 14.000 2.791 36.026 °C
Temp ZONE6 27.000 28.000 29.000 33.000 37.000 38.000 46.000 8.000 10.000 2.470 33.029 °C

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

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



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 8.000 11.000 12.000 15.000 18.000 19.000 22.000 6.000 8.000 2.083 14.580 nSat 0.2339 2.51
TDOP 0.460 0.500 0.550 0.740 1.110 1.380 2.720 0.560 0.880 0.184 0.775 1.807 10.59

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

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

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



Server Offsets

peer offsets plot

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

Clock Offset is field 5 in the peerstats log file.



Server Offset 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 -127.900 -127.900 -127.900 -114.808 6.202 6.202 6.202 134.103 134.103 49.326 -87.006 ms 0.873 2.083

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

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

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

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



Server Offset 108.61.215.221

peer offset 108.61.215.221 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 108.61.215.221 0.912 0.912 0.912 6.660 8.097 8.097 8.097 7.184 7.184 2.257 6.113 ms -1.574 4.16

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

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

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

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



Server Offset 12.205.28.193

peer offset 12.205.28.193 plot

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

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

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

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

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



Server Offset 134.215.155.177

peer offset 134.215.155.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 134.215.155.177 -12.535 -8.446 -5.827 -0.551 3.716 7.609 12.655 9.543 16.055 3.375 -0.730 ms 0.09781 5.026

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

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

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

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



Server Offset 136.244.88.170

peer offset 136.244.88.170 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 136.244.88.170 -82.929 -82.929 -82.929 -9.844 -2.577 -2.577 -2.577 80.352 80.352 24.937 -24.324 ms -1.039 2.814

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

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

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

Clock 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 -65.577 -65.577 -65.577 -19.778 6.380 6.380 6.380 71.957 71.957 23.754 -24.163 ms -0.5366 2.002

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

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

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

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



Server Offset 143.42.229.154

peer offset 143.42.229.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 143.42.229.154 -24.531 -8.099 -4.579 0.595 6.426 8.889 16.272 11.006 16.988 3.620 0.576 ms -0.4433 9.745

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

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

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

Clock 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 -71.402 3.068 5.506 10.153 12.572 14.364 405.866 7.065 11.296 22.123 10.883 ms 17.02 300.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 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 -58.207 -0.554 0.670 4.047 6.049 7.084 9.093 5.379 7.638 2.658 3.744 ms -14.36 332.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 157.245.125.229

peer offset 157.245.125.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 157.245.125.229 -11.025 -0.605 1.272 5.232 7.446 8.834 14.151 6.173 9.439 2.036 4.897 ms -0.973 8.112

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

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

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

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



Server Offset 161.35.230.200

peer offset 161.35.230.200 plot

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

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

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

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

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



Server Offset 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -33.205 -2.542 0.283 4.906 7.513 9.741 392.310 7.230 12.283 15.609 5.116 ms 24.01 593.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.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 -8.218 0.832 3.070 6.053 9.045 11.670 15.619 5.975 10.839 1.965 6.065 ms -0.2896 8.908

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

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

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

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

peer offset 163.123.153.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 163.123.153.14 -11.080 -9.303 -6.804 -0.971 5.743 11.448 18.438 12.547 20.750 3.919 -0.756 ms 0.6367 5.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 172.233.189.68

peer offset 172.233.189.68 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.189.68 2.792 2.792 2.792 4.599 5.335 5.335 5.335 2.543 2.543 0.787 4.392 ms -0.8344 2.648

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

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

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

Clock 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 1.249 1.249 1.762 5.217 12.873 399.088 399.088 11.112 397.839 76.494 21.086 ms 4.687 22.99

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

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

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

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



Server Offset 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 -1.005 0.370 1.565 5.905 10.300 41.102 41.762 8.735 40.732 6.573 6.900 ms 3.868 18.85

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

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

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

Clock 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 -5.581 -3.149 -1.652 1.771 6.251 7.987 11.308 7.902 11.136 2.291 1.955 ms 0.4718 3.935

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

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

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

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



Server Offset 173.255.230.96

peer offset 173.255.230.96 plot

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

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

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

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

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



Server Offset 185.214.143.237

peer offset 185.214.143.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 185.214.143.237 -1.142 -1.142 0.235 4.432 9.788 396.180 396.180 9.553 397.322 67.845 16.688 ms 5.377 29.95

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

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

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

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



Server Offset 185.234.20.134

peer offset 185.234.20.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 185.234.20.134 30.761 30.761 37.870 46.118 52.226 53.264 53.264 14.356 22.503 4.733 45.690 ms -0.8365 4.3

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

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

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

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



Server Offset 192.231.84.118

peer offset 192.231.84.118 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.231.84.118 -13.353 -6.026 -4.094 1.046 7.010 9.659 13.476 11.105 15.685 3.463 1.245 ms 0.109 4.02

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

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

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

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



Server Offset 192.48.105.15

peer offset 192.48.105.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.48.105.15 -38.144 -16.120 -11.322 4.337 8.624 13.335 24.385 19.946 29.455 6.098 2.898 ms -2.025 11.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 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 -21.766 -3.686 -0.193 5.290 8.528 12.222 898.980 8.721 15.908 31.145 6.194 ms 25.66 699.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 198.23.132.33

peer offset 198.23.132.33 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.23.132.33 -2.897 -2.897 -2.897 9.802 12.642 12.642 12.642 15.539 15.539 4.534 7.741 ms -1.402 4.019

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

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

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

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



Server Offset 198.71.50.75

peer offset 198.71.50.75 plot

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

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

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

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

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



Server Offset 199.68.201.237

peer offset 199.68.201.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 199.68.201.237 -54.221 -4.457 -2.342 2.245 5.491 7.434 14.187 7.833 11.890 3.323 1.891 ms -8.342 141.8

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

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

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

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



Server Offset 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 -3.011 -0.930 0.782 4.158 6.717 8.251 10.594 5.936 9.181 1.878 3.976 ms -0.3391 3.503

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

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

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

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



Server Offset 209.177.158.85

peer offset 209.177.158.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.177.158.85 -3.528 -0.144 0.456 3.926 5.974 6.644 7.500 5.518 6.788 1.647 3.712 ms -0.7409 3.799

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

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

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

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



Server Offset 209.253.210.112

peer offset 209.253.210.112 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.253.210.112 -43.512 -43.512 -6.797 2.630 11.767 21.137 21.137 18.564 64.649 7.034 2.131 ms -2.818 20.89

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

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

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

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



Server Offset 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 -11.500 -11.500 -3.447 0.175 6.879 8.150 8.150 10.326 19.650 3.412 0.499 ms -0.119 4.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 216.229.0.50

peer offset 216.229.0.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.229.0.50 -5.338 -5.338 -4.006 1.384 897.146 898.740 898.740 901.151 904.079 243.079 73.841 ms 3.093 10.58

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

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

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

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



Server Offset 216.250.115.174

peer offset 216.250.115.174 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.250.115.174 -50.737 -50.737 -50.737 -22.856 369.510 369.510 369.510 420.246 420.246 153.331 42.225 ms 1.636 3.702

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

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

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

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



Server Offset 216.82.35.115

peer offset 216.82.35.115 plot

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

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

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

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

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



Server Offset 217.197.83.230

peer offset 217.197.83.230 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 217.197.83.230 -120.144 -120.144 -87.085 -14.439 8.345 25.380 25.380 95.430 145.524 31.829 -26.016 ms -0.7938 2.762

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

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

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

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



Server Offset 23.150.41.123

peer offset 23.150.41.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.150.41.123 -22.902 -13.342 -6.785 -1.813 25.972 27.430 32.724 32.757 40.772 7.932 -0.313 ms 2.307 10.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 23.157.160.168

peer offset 23.157.160.168 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.157.160.168 -5.068 -1.215 0.086 3.583 6.081 7.468 9.623 5.995 8.683 1.775 3.402 ms -0.5016 4.099

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

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

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

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



Server Offset 23.161.104.133

peer offset 23.161.104.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.161.104.133 -90.864 -79.673 -46.827 -6.042 7.606 28.610 36.039 54.433 108.283 18.111 -10.956 ms -1.287 5.772

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

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

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

Clock 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 -6.743 -4.772 -2.653 1.554 3.878 4.819 10.085 6.530 9.591 2.020 1.220 ms -0.7622 4.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 23.186.168.124

peer offset 23.186.168.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.124 -7.176 -6.031 -5.380 -1.281 2.774 3.857 4.744 8.154 9.888 2.555 -1.268 ms 0.008223 2.264

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

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

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

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



Server Offset 23.186.168.125

peer offset 23.186.168.125 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.125 -21.394 -9.059 -5.950 -0.424 6.818 13.658 897.143 12.768 22.718 61.343 4.173 ms 14.4 209.2

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

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

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

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



Server Offset 23.186.168.129

peer offset 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.129 -100.937 -94.535 -6.487 -0.529 5.967 27.757 903.521 12.453 122.292 55.673 1.901 ms 15.31 248.2

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

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

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

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



Server Offset 23.186.168.133

peer offset 23.186.168.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.133 -7.844 -6.607 -5.595 -2.001 2.119 2.715 3.271 7.713 9.323 2.577 -1.805 ms 0.003423 2.023

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

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

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

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



Server Offset 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 -95.521 -95.148 -90.300 -29.066 1.535 5.918 6.374 91.835 101.066 27.729 -33.072 ms -0.5549 2.36

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

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

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

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



Server Offset 45.33.53.84

peer offset 45.33.53.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.33.53.84 -46.045 -0.594 1.252 5.059 7.317 7.897 8.597 6.064 8.490 2.909 4.640 ms -9.672 161.8

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

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

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

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



Server Offset 45.45.184.14

peer offset 45.45.184.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.45.184.14 -3.583 -3.583 -2.213 2.314 5.861 8.196 8.196 8.074 11.779 2.497 2.295 ms -0.1048 2.439

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

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

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

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



Server Offset 45.63.54.13

peer offset 45.63.54.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.63.54.13 -5.411 -1.284 1.511 5.531 7.546 8.410 9.171 6.035 9.693 1.905 5.168 ms -1.347 6.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 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 2.520 2.520 2.520 7.490 10.132 10.132 10.132 7.613 7.613 2.779 7.072 ms -0.4913 1.881

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

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

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

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

peer offset 45.79.227.165 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.79.227.165 -24.668 -5.318 -3.071 1.972 9.158 13.190 899.559 12.230 18.507 60.930 6.199 ms 14.51 212.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 45.79.82.45

peer offset 45.79.82.45 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.79.82.45 -8.160 -4.866 -1.302 5.432 7.656 8.754 15.796 8.958 13.620 2.573 4.888 ms -1.751 7.666

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

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

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

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



Server Offset 45.83.234.123

peer offset 45.83.234.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.83.234.123 -92.017 -33.072 -11.827 2.648 8.385 11.688 37.116 20.213 44.760 8.331 1.141 ms -3.437 28.02

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

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

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

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



Server Offset 5.161.65.34

peer offset 5.161.65.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.65.34 -8.208 -8.208 -5.991 -2.626 391.162 391.162 391.162 397.153 399.370 139.388 55.456 ms 1.96 4.843

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

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

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

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



Server Offset 66.118.229.14

peer offset 66.118.229.14 plot

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

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

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

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

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



Server Offset 69.89.207.199

peer offset 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 69.89.207.199 -132.300 -132.300 -132.300 -82.315 12.317 12.317 12.317 144.616 144.616 60.181 -69.022 ms 0.2283 1.231

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

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

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

Clock 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 -38.922 -5.235 -2.966 0.525 2.859 4.153 5.952 5.826 9.389 2.447 0.240 ms -7.231 113.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 72.14.182.49

peer offset 72.14.182.49 plot

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

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

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

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

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



Server Offset 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.088 -2.088 -1.038 3.170 6.372 6.756 6.756 7.410 8.843 2.232 2.989 ms -0.2874 2.334

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

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

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

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



Server Offset 91.224.149.196

peer offset 91.224.149.196 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 91.224.149.196 -98.542 -98.542 -75.284 -14.534 7.565 23.694 23.694 82.849 122.237 25.854 -20.872 ms -0.9368 3.139

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

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

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

Clock 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 -78.513 -3.972 -0.193 4.016 6.279 7.523 12.041 6.472 11.495 3.342 3.505 ms -12.09 259.6

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

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

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

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



Server Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -157.441 -152.843 -149.160 -139.494 -131.691 -128.807 -121.310 17.469 24.035 5.271 -139.860 ms -0.2242 2.915

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

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

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

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



Server Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -6.941 -0.744 -0.572 -0.215 0.215 0.334 0.728 0.787 1.078 0.449 -0.218 ms -8.454 102.6

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

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

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

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



Server Offset SHM(3)

peer offset SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(3) -8.030 -4.074 -1.143 -0.328 0.212 0.459 2.477 1.354 4.533 0.723 -0.405 ms -3.957 22.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 SHM(4)

peer offset SHM(4) plot

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

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

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

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

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



Server Offset SHM(5)

peer offset SHM(5) plot

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

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

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

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

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



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.000 0.000 0.000 11.216 111.550 111.550 111.550 111.550 111.550 39.440 34.882 ms 0.8598 2.097

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 108.61.215.221

peer jitter 108.61.215.221 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 108.61.215.221 0.000 0.000 0.000 2.778 4.463 4.463 4.463 4.463 4.463 1.521 2.406 ms -0.3996 1.809

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 12.205.28.193

peer jitter 12.205.28.193 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 134.215.155.177

peer jitter 134.215.155.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 134.215.155.177 0.000 1.171 2.135 4.415 20.214 21.390 22.367 18.079 20.219 4.544 5.754 ms 2.233 7.899

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 136.244.88.170

peer jitter 136.244.88.170 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 136.244.88.170 0.000 0.000 0.000 43.463 96.956 96.956 96.956 96.956 96.956 24.402 42.192 ms -0.08277 3.057

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 139.84.137.244

peer jitter 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.84.137.244 0.000 0.000 0.000 12.921 56.192 56.192 56.192 56.192 56.192 23.484 20.004 ms 0.756 1.798

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 143.42.229.154

peer jitter 143.42.229.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 143.42.229.154 0.000 0.914 1.472 4.651 22.494 35.197 36.006 21.022 34.283 7.610 7.729 ms 1.82 6.067

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

Closer to 0s 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.694 1.139 3.678 15.887 61.941 123.164 14.748 61.247 10.286 5.979 ms 7.07 64.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 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.617 1.108 4.307 36.641 77.462 113.778 35.532 76.846 12.764 9.103 ms 3.598 20.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 157.245.125.229

peer jitter 157.245.125.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 157.245.125.229 0.000 0.748 1.230 6.590 33.986 58.212 77.920 32.756 57.464 11.405 10.766 ms 2.199 9.138

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 161.35.230.200

peer jitter 161.35.230.200 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.000 0.743 1.104 3.557 11.732 23.622 115.178 10.628 22.880 6.997 4.976 ms 9.166 115.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.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.632 1.100 2.957 13.937 51.934 89.291 12.837 51.301 8.281 4.823 ms 7.046 62.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 163.123.153.14

peer jitter 163.123.153.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 163.123.153.14 0.000 0.899 1.452 4.247 16.420 73.823 82.597 14.967 72.924 9.309 6.365 ms 6.389 49.28

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.233.189.68

peer jitter 172.233.189.68 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.189.68 0.000 0.000 0.000 16.407 17.934 17.934 17.934 17.934 17.934 8.290 8.941 ms -0.00303 1.027

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.234.25.10

peer jitter 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.25.10 0.000 0.000 1.070 4.186 14.676 17.311 17.311 13.606 17.311 3.659 5.114 ms 1.643 5.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 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 1.982 7.559 75.492 100.950 110.008 73.510 100.950 20.949 15.577 ms 2.504 9.088

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.792 1.171 3.421 10.574 31.497 74.064 9.403 30.705 5.873 4.649 ms 6.748 63.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 173.255.230.96

peer jitter 173.255.230.96 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 185.214.143.237

peer jitter 185.214.143.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 185.214.143.237 0.000 0.000 0.849 3.509 24.075 66.532 66.532 23.226 66.532 12.782 6.885 ms 4.143 19.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 185.234.20.134

peer jitter 185.234.20.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 185.234.20.134 0.000 0.000 1.345 46.144 79.488 79.659 79.659 78.143 79.659 23.446 40.389 ms -0.2637 2.31

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

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

peer jitter 192.231.84.118 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.231.84.118 0.000 0.944 1.541 3.885 12.751 66.450 69.847 11.210 65.507 8.503 5.529 ms 6.391 46.25

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 8.231 15.837 32.614 63.290 81.489 85.309 47.453 73.258 15.919 35.883 ms 0.6456 3.005

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

Closer to 0s 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.734 1.176 3.358 11.216 23.711 398.640 10.040 22.977 9.667 4.877 ms 21.92 757.4

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 198.23.132.33

peer jitter 198.23.132.33 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.23.132.33 0.000 0.000 0.000 3.835 12.113 12.113 12.113 12.113 12.113 3.497 4.943 ms 0.7304 2.789

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 198.71.50.75

peer jitter 198.71.50.75 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 199.68.201.237

peer jitter 199.68.201.237 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 199.68.201.237 0.000 1.108 1.497 4.379 13.223 24.575 59.461 11.726 23.467 4.609 5.470 ms 4.52 39.75

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.726 1.226 4.463 28.136 54.240 78.971 26.910 53.514 10.217 8.334 ms 3.109 15.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 209.177.158.85

peer jitter 209.177.158.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.177.158.85 0.000 0.496 0.914 3.112 17.297 52.082 53.244 16.382 51.586 7.352 4.936 ms 4.827 29.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 209.253.210.112

peer jitter 209.253.210.112 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.253.210.112 0.000 0.000 2.230 18.138 47.776 56.088 56.088 45.545 56.088 14.263 19.678 ms 0.6626 2.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 212.227.240.160

peer jitter 212.227.240.160 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 212.227.240.160 0.000 0.000 1.874 4.654 37.570 39.142 39.142 35.696 39.142 13.018 11.110 ms 1.341 2.991

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.229.0.50

peer jitter 216.229.0.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.229.0.50 0.000 0.000 0.000 6.077 14.009 14.099 14.099 14.009 14.099 3.875 6.718 ms 0.1996 2.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 216.250.115.174

peer jitter 216.250.115.174 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.250.115.174 0.000 0.000 0.000 2.191 28.627 28.627 28.627 28.627 28.627 10.430 9.269 ms 0.6825 1.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 216.82.35.115

peer jitter 216.82.35.115 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 217.197.83.230

peer jitter 217.197.83.230 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 217.197.83.230 0.000 0.000 2.624 44.705 77.397 86.335 86.335 74.773 86.335 19.481 45.210 ms -0.2313 2.979

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

Closer to 0s 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 0.930 4.587 36.415 87.270 89.122 35.485 87.270 16.876 10.464 ms 3.263 13.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.157.160.168

peer jitter 23.157.160.168 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.157.160.168 0.000 0.810 1.174 3.957 23.987 41.434 53.568 22.813 40.624 8.446 7.290 ms 2.463 9.675

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.161.104.133

peer jitter 23.161.104.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.161.104.133 0.000 0.000 19.946 46.904 73.804 84.202 95.307 53.858 84.202 17.088 46.514 ms -0.2216 3.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 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.816 1.189 3.515 12.602 24.386 113.039 11.413 23.571 6.353 4.929 ms 9.63 142.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.186.168.124

peer jitter 23.186.168.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.124 0.000 0.892 1.418 4.435 8.722 18.808 19.308 7.305 17.916 3.049 4.889 ms 2.312 11.25

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.125

peer jitter 23.186.168.125 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.125 0.000 0.190 1.525 4.490 12.806 18.857 24.978 11.282 18.667 3.773 5.547 ms 1.717 7.056

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.129

peer jitter 23.186.168.129 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.129 0.000 0.000 1.508 4.125 14.345 94.456 99.122 12.837 94.456 12.095 6.517 ms 6.422 46.44

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.133

peer jitter 23.186.168.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.133 0.000 1.512 1.823 5.300 16.896 23.032 23.906 15.073 21.520 4.392 6.131 ms 2.111 8.042

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 34.147.28.4

peer jitter 34.147.28.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 34.147.28.4 0.000 0.000 16.821 40.838 63.292 68.703 75.458 46.470 68.703 15.486 40.136 ms -0.3183 3.077

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.33.53.84

peer jitter 45.33.53.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.33.53.84 0.000 0.840 1.364 3.976 13.560 25.417 53.423 12.196 24.576 5.132 5.246 ms 4.231 29.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 45.45.184.14

peer jitter 45.45.184.14 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.45.184.14 0.000 0.000 1.110 4.697 21.496 34.599 34.599 20.386 34.599 7.191 6.851 ms 2.344 8.455

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

Closer to 0s 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.703 1.053 3.308 11.454 24.347 79.311 10.401 23.644 7.089 4.708 ms 7.246 66.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 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 4.330 5.704 5.704 5.704 5.704 5.704 1.979 3.654 ms -0.9831 2.587

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.79.227.165

peer jitter 45.79.227.165 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.79.227.165 0.000 0.683 1.797 4.502 12.181 19.609 21.129 10.384 18.926 3.405 5.295 ms 2.128 8.633

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

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

peer jitter 45.79.82.45 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.79.82.45 0.000 0.754 1.102 3.321 12.050 24.480 63.897 10.948 23.726 4.900 4.561 ms 5.374 50.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 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 1.483 4.387 42.939 82.952 103.588 180.284 78.565 102.105 25.149 41.908 ms 0.5962 4.49

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 5.161.65.34

peer jitter 5.161.65.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.65.34 0.000 0.000 0.000 4.473 17.184 17.184 17.184 17.184 17.184 4.658 5.050 ms 0.938 3.169

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.118.229.14

peer jitter 66.118.229.14 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 69.89.207.199

peer jitter 69.89.207.199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 69.89.207.199 0.000 0.000 0.000 5.339 120.778 120.778 120.778 120.778 120.778 35.927 22.760 ms 1.778 4.812

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

Closer to 0s 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.952 1.441 4.280 9.976 22.131 97.381 8.535 21.179 6.351 5.140 ms 10.66 147.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 72.14.182.49

peer jitter 72.14.182.49 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 73.185.182.209

peer jitter 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.185.182.209 0.000 0.000 0.695 2.925 17.804 18.190 18.190 17.108 18.190 4.836 4.988 ms 1.507 4.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 91.224.149.196

peer jitter 91.224.149.196 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 91.224.149.196 0.000 0.000 16.047 40.823 74.227 88.191 88.191 58.180 88.191 17.022 40.608 ms 0.1145 3.495

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

Closer to 0s 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.834 1.236 3.823 17.246 87.810 200.156 16.010 86.976 15.843 7.119 ms 7.848 75.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 SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.290 0.671 0.976 2.437 5.754 7.655 12.644 4.778 6.984 1.518 2.777 ms 1.333 5.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 SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.060 0.129 0.165 0.283 0.489 0.572 7.138 0.323 0.442 0.158 0.303 ms 19.27 662

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(3)

peer jitter SHM(3) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(3) 0.000 137.803 174.745 288.587 477.101 623.166 4,258.535 302.356 485.363 139.814 309.439 µs 7.737 130.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 SHM(4)

peer jitter SHM(4) plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(5)

peer jitter SHM(5) plot

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

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

Closer 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 -187.984 10.708 10.936 11.447 11.825 17.678 183.534 0.889 6.971 2.286 11.543 ppm -33.4 5691
Local Clock Time Offset -127.900 -3.900 -0.608 -0.030 0.436 2.086 30.877 1.044 5.985 2.069 -0.108 ms -45.16 2583
Local RMS Frequency Jitter 0.0000 0.0037 0.0046 0.0068 0.069 0.231 96.849 0.065 0.227 2.299 0.106 ppm 31.43 1069
Local RMS Time Jitter 0.000 0.188 0.229 0.348 0.906 3.041 45.220 0.677 2.854 0.886 0.461 ms 28.9 1176
Server Jitter 104.131.155.175 0.000 0.000 0.000 11.216 111.550 111.550 111.550 111.550 111.550 39.440 34.882 ms 0.8598 2.097
Server Jitter 108.61.215.221 0.000 0.000 0.000 2.778 4.463 4.463 4.463 4.463 4.463 1.521 2.406 ms -0.3996 1.809
Server Jitter 12.205.28.193 0.000 0.000 0.000 11.183 108.575 108.575 108.575 108.575 108.575 37.651 31.806 ms 0.9856 2.424
Server Jitter 134.215.155.177 0.000 1.171 2.135 4.415 20.214 21.390 22.367 18.079 20.219 4.544 5.754 ms 2.233 7.899
Server Jitter 136.244.88.170 0.000 0.000 0.000 43.463 96.956 96.956 96.956 96.956 96.956 24.402 42.192 ms -0.08277 3.057
Server Jitter 139.84.137.244 0.000 0.000 0.000 12.921 56.192 56.192 56.192 56.192 56.192 23.484 20.004 ms 0.756 1.798
Server Jitter 143.42.229.154 0.000 0.914 1.472 4.651 22.494 35.197 36.006 21.022 34.283 7.610 7.729 ms 1.82 6.067
Server Jitter 144.202.66.214 0.000 0.694 1.139 3.678 15.887 61.941 123.164 14.748 61.247 10.286 5.979 ms 7.07 64.94
Server Jitter 149.28.61.105 0.000 0.617 1.108 4.307 36.641 77.462 113.778 35.532 76.846 12.764 9.103 ms 3.598 20.3
Server Jitter 157.245.125.229 0.000 0.748 1.230 6.590 33.986 58.212 77.920 32.756 57.464 11.405 10.766 ms 2.199 9.138
Server Jitter 161.35.230.200 0.000 0.000 0.000 1.722 4.765 5.072 5.072 4.765 5.072 1.384 2.182 ms 0.4533 2.424
Server Jitter 162.159.200.1 0.000 0.743 1.104 3.557 11.732 23.622 115.178 10.628 22.880 6.997 4.976 ms 9.166 115.8
Server Jitter 162.159.200.123 0.000 0.632 1.100 2.957 13.937 51.934 89.291 12.837 51.301 8.281 4.823 ms 7.046 62.81
Server Jitter 163.123.153.14 0.000 0.899 1.452 4.247 16.420 73.823 82.597 14.967 72.924 9.309 6.365 ms 6.389 49.28
Server Jitter 172.233.189.68 0.000 0.000 0.000 16.407 17.934 17.934 17.934 17.934 17.934 8.290 8.941 ms -0.00303 1.027
Server Jitter 172.234.25.10 0.000 0.000 1.070 4.186 14.676 17.311 17.311 13.606 17.311 3.659 5.114 ms 1.643 5.349
Server Jitter 172.234.37.140 0.000 0.000 1.982 7.559 75.492 100.950 110.008 73.510 100.950 20.949 15.577 ms 2.504 9.088
Server Jitter 172.235.60.8 0.000 0.792 1.171 3.421 10.574 31.497 74.064 9.403 30.705 5.873 4.649 ms 6.748 63.48
Server Jitter 173.255.230.96 0.000 0.000 1.050 3.510 18.774 67.403 67.650 17.724 67.403 9.020 6.895 ms 3.984 24.19
Server Jitter 185.214.143.237 0.000 0.000 0.849 3.509 24.075 66.532 66.532 23.226 66.532 12.782 6.885 ms 4.143 19.26
Server Jitter 185.234.20.134 0.000 0.000 1.345 46.144 79.488 79.659 79.659 78.143 79.659 23.446 40.389 ms -0.2637 2.31
Server Jitter 192.231.84.118 0.000 0.944 1.541 3.885 12.751 66.450 69.847 11.210 65.507 8.503 5.529 ms 6.391 46.25
Server Jitter 192.48.105.15 0.000 8.231 15.837 32.614 63.290 81.489 85.309 47.453 73.258 15.919 35.883 ms 0.6456 3.005
Server Jitter 194.0.5.123 0.000 0.734 1.176 3.358 11.216 23.711 398.640 10.040 22.977 9.667 4.877 ms 21.92 757.4
Server Jitter 198.23.132.33 0.000 0.000 0.000 3.835 12.113 12.113 12.113 12.113 12.113 3.497 4.943 ms 0.7304 2.789
Server Jitter 198.71.50.75 0.000 1.525 3.734 23.735 49.077 91.787 92.484 45.343 90.262 15.505 24.891 ms 1.557 7.619
Server Jitter 199.68.201.237 0.000 1.108 1.497 4.379 13.223 24.575 59.461 11.726 23.467 4.609 5.470 ms 4.52 39.75
Server Jitter 208.113.130.146 0.000 0.726 1.226 4.463 28.136 54.240 78.971 26.910 53.514 10.217 8.334 ms 3.109 15.87
Server Jitter 209.177.158.85 0.000 0.496 0.914 3.112 17.297 52.082 53.244 16.382 51.586 7.352 4.936 ms 4.827 29.24
Server Jitter 209.253.210.112 0.000 0.000 2.230 18.138 47.776 56.088 56.088 45.545 56.088 14.263 19.678 ms 0.6626 2.544
Server Jitter 212.227.240.160 0.000 0.000 1.874 4.654 37.570 39.142 39.142 35.696 39.142 13.018 11.110 ms 1.341 2.991
Server Jitter 216.229.0.50 0.000 0.000 0.000 6.077 14.009 14.099 14.099 14.009 14.099 3.875 6.718 ms 0.1996 2.38
Server Jitter 216.250.115.174 0.000 0.000 0.000 2.191 28.627 28.627 28.627 28.627 28.627 10.430 9.269 ms 0.6825 1.75
Server Jitter 216.82.35.115 0.000 0.000 0.000 17.805 45.013 45.013 45.013 45.013 45.013 13.064 18.801 ms 0.1825 1.945
Server Jitter 217.197.83.230 0.000 0.000 2.624 44.705 77.397 86.335 86.335 74.773 86.335 19.481 45.210 ms -0.2313 2.979
Server Jitter 23.150.41.123 0.000 0.000 0.930 4.587 36.415 87.270 89.122 35.485 87.270 16.876 10.464 ms 3.263 13.86
Server Jitter 23.157.160.168 0.000 0.810 1.174 3.957 23.987 41.434 53.568 22.813 40.624 8.446 7.290 ms 2.463 9.675
Server Jitter 23.161.104.133 0.000 0.000 19.946 46.904 73.804 84.202 95.307 53.858 84.202 17.088 46.514 ms -0.2216 3.459
Server Jitter 23.186.168.123 0.000 0.816 1.189 3.515 12.602 24.386 113.039 11.413 23.571 6.353 4.929 ms 9.63 142.7
Server Jitter 23.186.168.124 0.000 0.892 1.418 4.435 8.722 18.808 19.308 7.305 17.916 3.049 4.889 ms 2.312 11.25
Server Jitter 23.186.168.125 0.000 0.190 1.525 4.490 12.806 18.857 24.978 11.282 18.667 3.773 5.547 ms 1.717 7.056
Server Jitter 23.186.168.129 0.000 0.000 1.508 4.125 14.345 94.456 99.122 12.837 94.456 12.095 6.517 ms 6.422 46.44
Server Jitter 23.186.168.133 0.000 1.512 1.823 5.300 16.896 23.032 23.906 15.073 21.520 4.392 6.131 ms 2.111 8.042
Server Jitter 34.147.28.4 0.000 0.000 16.821 40.838 63.292 68.703 75.458 46.470 68.703 15.486 40.136 ms -0.3183 3.077
Server Jitter 45.33.53.84 0.000 0.840 1.364 3.976 13.560 25.417 53.423 12.196 24.576 5.132 5.246 ms 4.231 29.9
Server Jitter 45.45.184.14 0.000 0.000 1.110 4.697 21.496 34.599 34.599 20.386 34.599 7.191 6.851 ms 2.344 8.455
Server Jitter 45.63.54.13 0.000 0.703 1.053 3.308 11.454 24.347 79.311 10.401 23.644 7.089 4.708 ms 7.246 66.94
Server Jitter 45.77.126.122 0.000 0.000 0.000 4.330 5.704 5.704 5.704 5.704 5.704 1.979 3.654 ms -0.9831 2.587
Server Jitter 45.79.227.165 0.000 0.683 1.797 4.502 12.181 19.609 21.129 10.384 18.926 3.405 5.295 ms 2.128 8.633
Server Jitter 45.79.82.45 0.000 0.754 1.102 3.321 12.050 24.480 63.897 10.948 23.726 4.900 4.561 ms 5.374 50.29
Server Jitter 45.83.234.123 0.000 1.483 4.387 42.939 82.952 103.588 180.284 78.565 102.105 25.149 41.908 ms 0.5962 4.49
Server Jitter 5.161.65.34 0.000 0.000 0.000 4.473 17.184 17.184 17.184 17.184 17.184 4.658 5.050 ms 0.938 3.169
Server Jitter 66.118.229.14 0.000 12.905 17.541 43.034 69.623 82.562 91.203 52.082 69.657 15.534 43.735 ms 0.08592 3.136
Server Jitter 69.89.207.199 0.000 0.000 0.000 5.339 120.778 120.778 120.778 120.778 120.778 35.927 22.760 ms 1.778 4.812
Server Jitter 69.89.207.99 0.000 0.952 1.441 4.280 9.976 22.131 97.381 8.535 21.179 6.351 5.140 ms 10.66 147.3
Server Jitter 72.14.182.49 0.000 0.852 1.163 3.269 16.589 22.688 25.413 15.425 21.836 4.550 4.656 ms 2.49 9.16
Server Jitter 73.185.182.209 0.000 0.000 0.695 2.925 17.804 18.190 18.190 17.108 18.190 4.836 4.988 ms 1.507 4.194
Server Jitter 91.224.149.196 0.000 0.000 16.047 40.823 74.227 88.191 88.191 58.180 88.191 17.022 40.608 ms 0.1145 3.495
Server Jitter 99.28.14.242 0.000 0.834 1.236 3.823 17.246 87.810 200.156 16.010 86.976 15.843 7.119 ms 7.848 75.72
Server Jitter SHM(0) 0.290 0.671 0.976 2.437 5.754 7.655 12.644 4.778 6.984 1.518 2.777 ms 1.333 5.409
Server Jitter SHM(1) 0.060 0.129 0.165 0.283 0.489 0.572 7.138 0.323 0.442 0.158 0.303 ms 19.27 662
Server Jitter SHM(3) 0.000 137.803 174.745 288.587 477.101 623.166 4,258.535 302.356 485.363 139.814 309.439 µs 7.737 130.7
Server Jitter SHM(4) 0.000 0.462 0.715 1.781 4.115 5.613 9.498 3.400 5.151 1.084 2.018 ms 1.439 6.41
Server Jitter SHM(5) 0.000 113.019 173.172 305.621 513.760 609.838 1,715.353 340.588 496.819 114.363 324.731 µs 1.861 16.26
Server Offset 104.131.155.175 -127.900 -127.900 -127.900 -114.808 6.202 6.202 6.202 134.103 134.103 49.326 -87.006 ms 0.873 2.083
Server Offset 108.61.215.221 0.912 0.912 0.912 6.660 8.097 8.097 8.097 7.184 7.184 2.257 6.113 ms -1.574 4.16
Server Offset 12.205.28.193 -126.850 -126.850 -126.850 -114.175 6.955 6.955 6.955 133.805 133.805 46.151 -91.142 ms 1.065 2.644
Server Offset 134.215.155.177 -12.535 -8.446 -5.827 -0.551 3.716 7.609 12.655 9.543 16.055 3.375 -0.730 ms 0.09781 5.026
Server Offset 136.244.88.170 -82.929 -82.929 -82.929 -9.844 -2.577 -2.577 -2.577 80.352 80.352 24.937 -24.324 ms -1.039 2.814
Server Offset 139.84.137.244 -65.577 -65.577 -65.577 -19.778 6.380 6.380 6.380 71.957 71.957 23.754 -24.163 ms -0.5366 2.002
Server Offset 143.42.229.154 -24.531 -8.099 -4.579 0.595 6.426 8.889 16.272 11.006 16.988 3.620 0.576 ms -0.4433 9.745
Server Offset 144.202.66.214 -71.402 3.068 5.506 10.153 12.572 14.364 405.866 7.065 11.296 22.123 10.883 ms 17.02 300.1
Server Offset 149.28.61.105 -58.207 -0.554 0.670 4.047 6.049 7.084 9.093 5.379 7.638 2.658 3.744 ms -14.36 332.8
Server Offset 157.245.125.229 -11.025 -0.605 1.272 5.232 7.446 8.834 14.151 6.173 9.439 2.036 4.897 ms -0.973 8.112
Server Offset 161.35.230.200 -2.730 -2.730 -1.127 1.511 390.595 395.667 395.667 391.722 398.397 147.881 68.930 ms 1.72 3.961
Server Offset 162.159.200.1 -33.205 -2.542 0.283 4.906 7.513 9.741 392.310 7.230 12.283 15.609 5.116 ms 24.01 593.2
Server Offset 162.159.200.123 -8.218 0.832 3.070 6.053 9.045 11.670 15.619 5.975 10.839 1.965 6.065 ms -0.2896 8.908
Server Offset 163.123.153.14 -11.080 -9.303 -6.804 -0.971 5.743 11.448 18.438 12.547 20.750 3.919 -0.756 ms 0.6367 5.044
Server Offset 172.233.189.68 2.792 2.792 2.792 4.599 5.335 5.335 5.335 2.543 2.543 0.787 4.392 ms -0.8344 2.648
Server Offset 172.234.25.10 1.249 1.249 1.762 5.217 12.873 399.088 399.088 11.112 397.839 76.494 21.086 ms 4.687 22.99
Server Offset 172.234.37.140 -1.005 0.370 1.565 5.905 10.300 41.102 41.762 8.735 40.732 6.573 6.900 ms 3.868 18.85
Server Offset 172.235.60.8 -5.581 -3.149 -1.652 1.771 6.251 7.987 11.308 7.902 11.136 2.291 1.955 ms 0.4718 3.935
Server Offset 173.255.230.96 -4.019 -1.915 0.365 4.658 8.077 9.189 28.541 7.712 11.104 2.614 4.581 ms 2.225 26.93
Server Offset 185.214.143.237 -1.142 -1.142 0.235 4.432 9.788 396.180 396.180 9.553 397.322 67.845 16.688 ms 5.377 29.95
Server Offset 185.234.20.134 30.761 30.761 37.870 46.118 52.226 53.264 53.264 14.356 22.503 4.733 45.690 ms -0.8365 4.3
Server Offset 192.231.84.118 -13.353 -6.026 -4.094 1.046 7.010 9.659 13.476 11.105 15.685 3.463 1.245 ms 0.109 4.02
Server Offset 192.48.105.15 -38.144 -16.120 -11.322 4.337 8.624 13.335 24.385 19.946 29.455 6.098 2.898 ms -2.025 11.15
Server Offset 194.0.5.123 -21.766 -3.686 -0.193 5.290 8.528 12.222 898.980 8.721 15.908 31.145 6.194 ms 25.66 699.8
Server Offset 198.23.132.33 -2.897 -2.897 -2.897 9.802 12.642 12.642 12.642 15.539 15.539 4.534 7.741 ms -1.402 4.019
Server Offset 198.71.50.75 -21.461 -16.971 -10.397 -4.651 -1.037 1.083 5.931 9.360 18.054 3.141 -4.906 ms -1.601 9.855
Server Offset 199.68.201.237 -54.221 -4.457 -2.342 2.245 5.491 7.434 14.187 7.833 11.890 3.323 1.891 ms -8.342 141.8
Server Offset 208.113.130.146 -3.011 -0.930 0.782 4.158 6.717 8.251 10.594 5.936 9.181 1.878 3.976 ms -0.3391 3.503
Server Offset 209.177.158.85 -3.528 -0.144 0.456 3.926 5.974 6.644 7.500 5.518 6.788 1.647 3.712 ms -0.7409 3.799
Server Offset 209.253.210.112 -43.512 -43.512 -6.797 2.630 11.767 21.137 21.137 18.564 64.649 7.034 2.131 ms -2.818 20.89
Server Offset 212.227.240.160 -11.500 -11.500 -3.447 0.175 6.879 8.150 8.150 10.326 19.650 3.412 0.499 ms -0.119 4.267
Server Offset 216.229.0.50 -5.338 -5.338 -4.006 1.384 897.146 898.740 898.740 901.151 904.079 243.079 73.841 ms 3.093 10.58
Server Offset 216.250.115.174 -50.737 -50.737 -50.737 -22.856 369.510 369.510 369.510 420.246 420.246 153.331 42.225 ms 1.636 3.702
Server Offset 216.82.35.115 -29.297 -29.297 -9.388 -1.589 392.815 392.815 392.815 402.203 422.112 140.650 54.907 ms 1.952 4.828
Server Offset 217.197.83.230 -120.144 -120.144 -87.085 -14.439 8.345 25.380 25.380 95.430 145.524 31.829 -26.016 ms -0.7938 2.762
Server Offset 23.150.41.123 -22.902 -13.342 -6.785 -1.813 25.972 27.430 32.724 32.757 40.772 7.932 -0.313 ms 2.307 10.34
Server Offset 23.157.160.168 -5.068 -1.215 0.086 3.583 6.081 7.468 9.623 5.995 8.683 1.775 3.402 ms -0.5016 4.099
Server Offset 23.161.104.133 -90.864 -79.673 -46.827 -6.042 7.606 28.610 36.039 54.433 108.283 18.111 -10.956 ms -1.287 5.772
Server Offset 23.186.168.123 -6.743 -4.772 -2.653 1.554 3.878 4.819 10.085 6.530 9.591 2.020 1.220 ms -0.7622 4.423
Server Offset 23.186.168.124 -7.176 -6.031 -5.380 -1.281 2.774 3.857 4.744 8.154 9.888 2.555 -1.268 ms 0.008223 2.264
Server Offset 23.186.168.125 -21.394 -9.059 -5.950 -0.424 6.818 13.658 897.143 12.768 22.718 61.343 4.173 ms 14.4 209.2
Server Offset 23.186.168.129 -100.937 -94.535 -6.487 -0.529 5.967 27.757 903.521 12.453 122.292 55.673 1.901 ms 15.31 248.2
Server Offset 23.186.168.133 -7.844 -6.607 -5.595 -2.001 2.119 2.715 3.271 7.713 9.323 2.577 -1.805 ms 0.003423 2.023
Server Offset 34.147.28.4 -95.521 -95.148 -90.300 -29.066 1.535 5.918 6.374 91.835 101.066 27.729 -33.072 ms -0.5549 2.36
Server Offset 45.33.53.84 -46.045 -0.594 1.252 5.059 7.317 7.897 8.597 6.064 8.490 2.909 4.640 ms -9.672 161.8
Server Offset 45.45.184.14 -3.583 -3.583 -2.213 2.314 5.861 8.196 8.196 8.074 11.779 2.497 2.295 ms -0.1048 2.439
Server Offset 45.63.54.13 -5.411 -1.284 1.511 5.531 7.546 8.410 9.171 6.035 9.693 1.905 5.168 ms -1.347 6.272
Server Offset 45.77.126.122 2.520 2.520 2.520 7.490 10.132 10.132 10.132 7.613 7.613 2.779 7.072 ms -0.4913 1.881
Server Offset 45.79.227.165 -24.668 -5.318 -3.071 1.972 9.158 13.190 899.559 12.230 18.507 60.930 6.199 ms 14.51 212.6
Server Offset 45.79.82.45 -8.160 -4.866 -1.302 5.432 7.656 8.754 15.796 8.958 13.620 2.573 4.888 ms -1.751 7.666
Server Offset 45.83.234.123 -92.017 -33.072 -11.827 2.648 8.385 11.688 37.116 20.213 44.760 8.331 1.141 ms -3.437 28.02
Server Offset 5.161.65.34 -8.208 -8.208 -5.991 -2.626 391.162 391.162 391.162 397.153 399.370 139.388 55.456 ms 1.96 4.843
Server Offset 66.118.229.14 -46.204 -13.396 -8.297 4.542 8.438 12.813 14.060 16.735 26.209 5.776 3.279 ms -3.792 28.07
Server Offset 69.89.207.199 -132.300 -132.300 -132.300 -82.315 12.317 12.317 12.317 144.616 144.616 60.181 -69.022 ms 0.2283 1.231
Server Offset 69.89.207.99 -38.922 -5.235 -2.966 0.525 2.859 4.153 5.952 5.826 9.389 2.447 0.240 ms -7.231 113.7
Server Offset 72.14.182.49 -1.532 -0.973 0.417 4.164 7.308 8.085 8.396 6.891 9.058 1.895 4.150 ms -0.3723 3.354
Server Offset 73.185.182.209 -2.088 -2.088 -1.038 3.170 6.372 6.756 6.756 7.410 8.843 2.232 2.989 ms -0.2874 2.334
Server Offset 91.224.149.196 -98.542 -98.542 -75.284 -14.534 7.565 23.694 23.694 82.849 122.237 25.854 -20.872 ms -0.9368 3.139
Server Offset 99.28.14.242 -78.513 -3.972 -0.193 4.016 6.279 7.523 12.041 6.472 11.495 3.342 3.505 ms -12.09 259.6
Server Offset SHM(0) -157.441 -152.843 -149.160 -139.494 -131.691 -128.807 -121.310 17.469 24.035 5.271 -139.860 ms -0.2242 2.915
Server Offset SHM(1) -6.941 -0.744 -0.572 -0.215 0.215 0.334 0.728 0.787 1.078 0.449 -0.218 ms -8.454 102.6
Server Offset SHM(3) -8.030 -4.074 -1.143 -0.328 0.212 0.459 2.477 1.354 4.533 0.723 -0.405 ms -3.957 22.5
Server Offset SHM(4) -161.294 -159.152 -156.877 -151.439 -146.907 -145.585 -142.438 9.970 13.567 3.040 -151.647 ms -0.2552 2.747
Server Offset SHM(5) -6.986 -3.330 -0.686 -0.171 0.413 0.591 0.760 1.099 3.921 0.607 -0.178 ms -4.609 34.92
TDOP 0.460 0.500 0.550 0.740 1.110 1.380 2.720 0.560 0.880 0.184 0.775 1.807 10.59
Temp /dev/sda 18.000 20.000 20.000 26.000 26.000 28.000 33.000 6.000 8.000 2.275 24.591 °C
Temp LM0 29.000 31.000 32.000 35.000 36.000 39.000 54.000 4.000 8.000 1.725 34.726 °C
Temp LM1 28.000 30.000 31.000 35.000 39.000 42.000 54.000 8.000 12.000 2.682 35.257 °C
Temp LM2 0.000 0.000 19.000 36.000 40.000 40.000 48.000 21.000 40.000 8.525 32.751 °C
Temp LM3 0.000 0.000 19.000 38.000 40.000 41.000 44.000 21.000 41.000 9.383 31.847 °C
Temp LM4 0.000 0.000 0.000 0.000 42.000 45.000 49.000 42.000 45.000 18.565 17.825 °C
Temp LM5 27.000 28.000 29.000 33.000 41.000 41.000 53.000 12.000 13.000 4.113 34.179 °C
Temp LM6 28.000 30.000 31.000 35.000 37.000 37.000 47.000 6.000 7.000 1.527 34.395 °C
Temp LM7 31.000 32.000 33.000 36.000 38.000 39.000 49.000 5.000 7.000 1.577 36.098 °C
Temp LM8 31.000 32.000 33.000 37.000 39.000 39.000 49.000 6.000 7.000 1.557 36.206 °C
Temp LM9 31.000 32.000 33.000 37.000 39.000 39.000 49.000 6.000 7.000 1.557 36.206 °C
Temp ZONE0 20.000 20.000 20.000 20.000 20.000 20.000 20.000 0.000 0.000 0.000 20.000 °C
Temp ZONE1 30.000 32.000 33.000 36.000 38.000 38.000 48.000 5.000 6.000 1.498 35.563 °C
Temp ZONE2 27.000 28.000 29.000 33.000 41.000 41.000 41.000 12.000 13.000 4.003 34.379 °C
Temp ZONE3 30.000 31.000 32.000 36.000 38.000 43.000 54.000 6.000 12.000 1.992 35.448 °C
Temp ZONE4 30.000 32.000 33.000 36.000 38.000 38.000 48.000 5.000 6.000 1.498 35.563 °C
Temp ZONE5 30.000 31.000 32.000 36.000 42.000 45.000 54.000 10.000 14.000 2.791 36.026 °C
Temp ZONE6 27.000 28.000 29.000 33.000 37.000 38.000 46.000 8.000 10.000 2.470 33.029 °C
nSats 8.000 11.000 12.000 15.000 18.000 19.000 22.000 6.000 8.000 2.083 14.580 nSat 0.2339 2.51
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!