NTPsec

Dell-2018

Report generated: Tue May 5 00:40:01 2026 UTC
Start Time: Tue Mar 31 00:40:00 2026 UTC
End Time: Tue May 5 00:40:00 2026 UTC
Report Period: 35.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 -76.840 -6.890 -6.454 -2.145 1.600 4.125 116.829 8.054 11.015 3.814 -2.597 ms 1.989 182.3
Local Clock Frequency Offset -7.584 10.456 10.888 11.804 22.292 22.641 120.802 11.404 12.185 5.046 15.636 ppm 2.178 37.87

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.247 0.286 0.401 3.530 6.344 70.769 3.244 6.097 2.985 1.100 ms 13.95 247.1

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.0053 0.0061 0.242 0.877 5.705 48.231 0.871 5.700 2.129 0.473 ppm 13.76 221.4

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 -76.840 -6.890 -6.454 -2.145 1.600 4.125 116.829 8.054 11.015 3.814 -2.597 ms 1.989 182.3

The clock offsets of the local clock as a histogram.

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



Local Temperatures

local temps plot

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

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



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -7.584 10.456 10.888 11.804 22.292 22.641 120.802 11.404 12.185 5.046 15.636 ppm 2.178 37.87
Temp /dev/sda 18.000 20.000 20.000 25.000 26.000 26.000 29.000 6.000 6.000 2.166 24.247 °C
Temp LM0 31.000 31.000 32.000 37.000 37.000 37.000 50.000 5.000 6.000 1.413 36.183 °C
Temp LM1 29.000 30.000 31.000 35.000 37.000 38.000 42.000 6.000 8.000 1.834 34.501 °C
Temp LM2 26.000 26.000 34.000 38.000 40.000 41.000 45.000 6.000 15.000 2.826 37.819 °C
Temp LM3 0.000 0.000 0.000 3.000 39.000 40.000 41.000 39.000 40.000 13.985 9.457 °C
Temp LM4 0.000 0.000 0.000 34.000 39.000 42.000 46.000 39.000 42.000 13.486 27.996 °C
Temp LM5 29.000 29.000 30.000 32.000 34.000 34.000 37.000 4.000 5.000 1.354 31.878 °C
Temp LM6 31.000 32.000 33.000 34.000 36.000 37.000 44.000 3.000 5.000 1.160 33.995 °C
Temp LM7 32.000 33.000 34.000 35.000 37.000 39.000 45.000 3.000 6.000 1.129 35.567 °C
Temp LM8 26.800 26.800 34.000 35.000 37.000 39.000 45.000 3.000 12.200 2.061 35.417 °C
Temp LM9 26.800 26.800 34.000 35.000 37.000 39.000 45.000 3.000 12.200 2.061 35.417 °C
Temp ZONE0 20.000 20.000 20.000 20.000 20.000 20.000 20.000 0.000 0.000 0.000 20.000 °C
Temp ZONE1 26.800 26.800 34.000 35.000 37.000 38.000 45.000 3.000 11.200 1.960 34.886 °C
Temp ZONE2 29.000 29.000 34.000 37.000 37.000 37.000 37.000 3.000 8.000 1.733 35.963 °C
Temp ZONE3 32.000 33.000 34.000 35.000 37.000 38.000 45.000 3.000 5.000 1.149 35.165 °C
Temp ZONE4 26.800 26.800 34.000 35.000 37.000 38.000 45.000 3.000 11.200 1.960 34.886 °C
Temp ZONE5 30.000 31.000 32.000 34.000 39.000 42.000 50.000 7.000 11.000 2.298 34.286 °C
Temp ZONE6 29.000 30.000 30.000 31.000 33.000 34.000 38.000 3.000 4.000 1.004 31.589 °C

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

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



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 8.000 10.000 11.000 13.000 17.000 19.000 21.000 6.000 9.000 2.009 13.649 nSat 0.6694 2.852
TDOP 0.450 0.510 0.560 0.760 1.170 1.640 2.830 0.610 1.130 0.212 0.805 2.264 13.73

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

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

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



Server Offsets

peer offsets plot

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

Clock Offset is field 5 in the peerstats log file.



Server Offset 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 -9.978 -9.873 -7.869 1.310 6.960 13.031 14.937 14.829 22.904 4.061 1.075 ms 0.02473 4.904

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

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

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

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



Server Offset 104.234.61.117

peer offset 104.234.61.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.234.61.117 -11.180 -9.140 -3.447 1.426 6.606 12.091 16.244 10.053 21.231 3.430 1.519 ms -0.07377 5.449

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

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

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

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



Server Offset 107.172.222.7

peer offset 107.172.222.7 plot

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

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

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

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

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



Server Offset 134.215.155.177

peer offset 134.215.155.177 plot

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

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

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

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

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



Server Offset 139.84.137.244

peer offset 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 139.84.137.244 -76.084 -76.084 -67.500 -13.455 13.351 16.737 16.737 80.851 92.820 27.963 -20.103 ms -0.468 2.005

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

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

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

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



Server Offset 143.42.229.154

peer offset 143.42.229.154 plot

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

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

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

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

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



Server Offset 144.202.0.197

peer offset 144.202.0.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 144.202.0.197 -112.597 -112.597 -112.597 -0.542 1.509 1.509 1.509 114.106 114.106 56.383 -55.610 ms 0.0001555 1.001

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

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

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

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



Server Offset 147.88.195.53

peer offset 147.88.195.53 plot

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

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

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

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

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



Server Offset 149.248.12.167

peer offset 149.248.12.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.248.12.167 -8.248 -8.248 -5.145 2.102 8.205 12.647 12.647 13.350 20.895 4.129 1.825 ms 0.01569 3.465

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

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

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

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



Server Offset 149.28.200.179

peer offset 149.28.200.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 149.28.200.179 -15.182 -10.996 -7.700 0.875 6.594 11.091 14.392 14.294 22.087 3.870 0.627 ms -0.6716 5.971

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

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

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

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



Server Offset 155.248.196.28

peer offset 155.248.196.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 155.248.196.28 -7.263 -4.833 -2.819 0.165 4.387 7.586 11.821 7.206 12.418 2.282 0.520 ms 0.7572 5.018

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

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

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

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



Server Offset 157.245.125.229

peer offset 157.245.125.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 157.245.125.229 1.618 1.618 1.618 2.114 3.912 3.912 3.912 2.294 2.294 0.986 2.548 ms 0.5751 1.5

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

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

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

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



Server Offset 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -6.317 -6.317 -3.562 0.356 5.592 14.827 14.827 9.154 21.144 3.010 0.789 ms 1.452 9.498

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

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

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

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



Server Offset 162.159.200.123

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 -5.017 -4.357 -3.040 0.526 5.143 37.514 40.107 8.183 41.871 5.386 1.191 ms 5.394 38.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 170.187.147.56

peer offset 170.187.147.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 170.187.147.56 1.026 1.199 3.846 6.744 9.809 11.373 12.448 5.963 10.174 1.897 6.818 ms -0.2684 3.74

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

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

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

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



Server Offset 171.66.97.126

peer offset 171.66.97.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 171.66.97.126 -111.117 -111.117 -111.117 -1.864 2.857 2.857 2.857 113.973 113.973 55.954 -54.736 ms 0.002046 1.003

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

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

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

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



Server Offset 172.233.155.39

peer offset 172.233.155.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.233.155.39 -1.467 -1.004 0.504 3.923 6.683 9.443 9.891 6.178 10.447 1.888 3.780 ms -0.1655 3.462

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

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

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

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



Server Offset 172.234.25.10

peer offset 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.25.10 -378.349 -377.277 -1.613 7.945 13.980 16.005 16.638 15.592 393.281 71.028 -5.439 ms -5.005 26.14

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

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

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

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



Server Offset 172.234.37.140

peer offset 172.234.37.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.234.37.140 -384.852 -382.248 -15.994 -0.820 4.381 5.631 9.952 20.375 387.879 60.491 -11.217 ms -5.922 36.29

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

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

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

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



Server Offset 172.235.60.8

peer offset 172.235.60.8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.235.60.8 -4.609 -3.025 -1.374 1.899 6.639 7.668 9.759 8.013 10.693 2.337 2.181 ms 0.3878 3.311

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

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

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

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



Server Offset 172.238.164.57

peer offset 172.238.164.57 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 172.238.164.57 -20.678 -5.845 -4.128 -0.201 4.991 6.484 11.018 9.119 12.329 2.825 0.122 ms -0.1455 6.625

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

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

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

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



Server Offset 172.245.210.108

peer offset 172.245.210.108 plot

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

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

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

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

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



Server Offset 185.234.20.134

peer offset 185.234.20.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 185.234.20.134 -207.966 -206.319 4.562 42.236 55.508 222.373 228.892 50.946 428.693 46.855 38.001 ms -0.7219 18.78

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

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

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

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



Server Offset 194.0.5.123

peer offset 194.0.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.0.5.123 -452.715 -14.266 -5.786 1.183 7.269 11.033 30.250 13.055 25.299 25.253 -0.184 ms -16.99 303.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 198.137.202.56

peer offset 198.137.202.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.137.202.56 -206.226 -6.792 -4.823 -1.585 2.970 6.864 17.267 7.794 13.656 10.679 -1.881 ms -16.46 302.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 198.46.254.130

peer offset 198.46.254.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 198.46.254.130 -11.109 -10.105 -8.900 -0.000 6.524 48.594 50.250 15.424 58.699 6.597 0.210 ms 4.556 35.9

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

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

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

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



Server Offset 204.2.134.173

peer offset 204.2.134.173 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.2.134.173 -0.755 -0.755 -0.755 1.723 1.723 1.723 1.723 2.478 2.478 1.239 0.484 ms 0 1

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

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

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

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



Server Offset 206.210.192.99

peer offset 206.210.192.99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 206.210.192.99 3.732 3.732 3.732 10.882 12.986 12.986 12.986 9.255 9.255 2.868 9.737 ms -0.9345 2.785

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

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

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

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



Server Offset 209.177.158.85

peer offset 209.177.158.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.177.158.85 -30.375 -26.695 -4.423 -0.930 1.753 5.012 7.613 6.175 31.707 4.289 -1.516 ms -4.702 29.96

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

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

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

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



Server Offset 212.227.240.160

peer offset 212.227.240.160 plot

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

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

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

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

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



Server Offset 216.229.4.66

peer offset 216.229.4.66 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.229.4.66 -17.026 -11.915 -9.323 -0.727 3.365 13.045 13.185 12.689 24.960 3.711 -1.195 ms -0.3257 7.429

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

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

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

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



Server Offset 216.66.48.42

peer offset 216.66.48.42 plot

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

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

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

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

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



Server Offset 23.142.248.9

peer offset 23.142.248.9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.142.248.9 -263.459 -263.459 -262.784 -5.526 168.098 168.098 168.098 430.883 431.557 135.791 -14.334 ms -0.3337 2.497

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

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

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

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



Server Offset 23.150.41.122

peer offset 23.150.41.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.150.41.122 -3.912 -3.704 0.122 4.751 7.547 11.178 12.219 7.425 14.882 2.538 4.300 ms -0.6129 4.277

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

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

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

Clock 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 3.519 3.565 4.354 8.155 11.199 17.772 20.648 6.846 14.207 2.380 8.271 ms 1.527 9.709

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

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

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

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



Server Offset 23.155.72.147

peer offset 23.155.72.147 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.155.72.147 -392.987 -391.252 -12.441 -6.112 -0.837 1.703 7.397 11.604 392.955 61.955 -16.524 ms -5.782 34.56

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

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

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

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



Server Offset 23.161.104.133

peer offset 23.161.104.133 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.161.104.133 -120.099 -100.489 -82.609 -12.114 9.325 14.069 21.144 91.934 114.558 28.361 -20.416 ms -1.19 3.714

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

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

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

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



Server Offset 23.168.24.210

peer offset 23.168.24.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.168.24.210 -30.994 -9.946 -0.456 4.953 9.479 14.370 15.899 9.935 24.316 3.912 4.627 ms -3.016 28.6

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

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

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

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



Server Offset 23.186.168.123

peer offset 23.186.168.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.123 -18.265 -13.910 -9.299 -2.861 3.315 8.235 24.970 12.613 22.145 3.976 -2.910 ms 0.6185 9.406

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

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

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

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



Server Offset 23.186.168.126

peer offset 23.186.168.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.186.168.126 -114.793 -114.793 -114.793 -5.494 -0.844 -0.844 -0.844 113.950 113.950 54.847 -57.177 ms -0.005087 1.013

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

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

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

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



Server Offset 23.95.35.34

peer offset 23.95.35.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 23.95.35.34 -27.613 -7.115 -4.506 -1.130 1.000 3.097 8.679 5.506 10.212 2.944 -1.526 ms -4.974 44.45

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

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

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

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



Server Offset 2602:f590::23:161:104:133 (isere.sd.ysun.co)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:f590::23:161:104:133 (isere.sd.ysun.co) -471.581 -385.176 -54.827 -11.476 0.126 5.242 28.182 54.953 390.419 61.385 -26.183 ms -5.774 37.6

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

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

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

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



Server Offset 34.147.28.4

peer offset 34.147.28.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 34.147.28.4 -129.797 -97.451 -53.266 -8.090 4.141 9.142 11.849 57.407 106.593 21.047 -13.839 ms -2.49 10.74

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

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

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

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



Server Offset 38.45.64.130

peer offset 38.45.64.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 38.45.64.130 -257.312 -253.476 -19.339 5.468 8.969 174.253 177.823 28.308 427.728 37.148 1.973 ms -1.963 32.42

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

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

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

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



Server Offset 40.160.28.79

peer offset 40.160.28.79 plot

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

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

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

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

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



Server Offset 44.190.5.123

peer offset 44.190.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 44.190.5.123 -7.144 -7.144 -5.951 -0.158 3.398 3.755 3.755 9.349 10.899 2.890 -0.778 ms -0.2377 2.111

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

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

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

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



Server Offset 45.55.58.103

peer offset 45.55.58.103 plot

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

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

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

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

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



Server Offset 47.85.203.40

peer offset 47.85.203.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 47.85.203.40 -11.482 -4.542 -0.158 5.077 10.458 14.417 15.104 10.616 18.959 3.390 5.170 ms -0.3312 5.456

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

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

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

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



Server Offset 49.12.103.123

peer offset 49.12.103.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 49.12.103.123 -104.453 -96.809 -69.563 -6.827 5.026 15.191 21.860 74.590 112.001 23.583 -15.248 ms -1.71 5.611

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

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

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

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



Server Offset 5.161.111.190

peer offset 5.161.111.190 plot

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

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

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

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

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



Server Offset 5.161.94.12

peer offset 5.161.94.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.94.12 -26.311 -6.789 -5.364 -1.781 1.988 4.296 14.347 7.351 11.084 2.473 -1.710 ms -0.7917 18.97

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

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

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

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



Server Offset 50.117.3.95

peer offset 50.117.3.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.117.3.95 -13.393 -13.270 -8.900 -1.296 1.731 4.497 6.235 10.631 17.767 3.214 -1.929 ms -1.378 5.671

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

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

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

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



Server Offset 50.218.103.254

peer offset 50.218.103.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.218.103.254 -39.877 -17.266 -8.068 0.775 5.720 46.263 49.954 13.788 63.530 7.440 0.730 ms 2.027 26.4

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

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

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

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



Server Offset 51.81.226.229

peer offset 51.81.226.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 51.81.226.229 0.232 0.432 1.153 4.562 8.093 11.100 11.602 6.940 10.668 2.089 4.771 ms 0.385 3.649

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

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

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

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



Server Offset 64.251.10.152

peer offset 64.251.10.152 plot

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

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

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

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

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



Server Offset 65.182.224.39

peer offset 65.182.224.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 65.182.224.39 -19.040 -5.987 -1.484 1.519 6.164 11.148 17.628 7.648 17.136 3.038 1.696 ms -0.02657 18.42

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

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

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

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



Server Offset 65.182.224.60

peer offset 65.182.224.60 plot

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

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

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

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

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



Server Offset 72.14.186.59

peer offset 72.14.186.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 72.14.186.59 -10.962 -10.962 -6.498 5.272 7.467 8.444 8.444 13.965 19.405 4.884 3.065 ms -1.172 3.134

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

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

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

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



Server Offset 73.185.182.209

peer offset 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 73.185.182.209 -385.027 -380.946 -7.553 0.567 7.557 9.409 12.049 15.110 390.355 62.523 -9.596 ms -5.741 34.11

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

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

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

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



Server Offset 77.37.97.124

peer offset 77.37.97.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 77.37.97.124 -64.960 -64.960 -62.814 -13.281 12.547 12.582 12.582 75.362 77.541 22.383 -16.669 ms -0.5829 2.612

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

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

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

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



Server Offset 77.42.37.85

peer offset 77.42.37.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 77.42.37.85 -83.037 -83.037 -83.037 -1.405 13.595 13.595 13.595 96.633 96.633 29.560 -20.475 ms -0.8498 2.319

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

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

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

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



Server Offset 79.160.225.13

peer offset 79.160.225.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 79.160.225.13 -64.543 -64.543 -64.543 -8.196 0.842 0.842 0.842 65.386 65.386 19.527 -17.421 ms -1.173 3.163

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

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

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

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



Server Offset 83.228.206.15

peer offset 83.228.206.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 83.228.206.15 -137.287 -106.678 -85.463 -5.076 5.321 28.735 31.867 90.784 135.413 27.600 -16.729 ms -1.765 5.927

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

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

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

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



Refclock Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(0) -155.160 -152.369 -149.937 -140.323 -133.385 -131.084 -128.188 16.553 21.285 5.068 -140.872 ms -0.2936 2.486

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

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

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SHM(1) -6.110 -0.928 -0.680 -0.232 0.141 0.236 0.462 0.820 1.164 0.300 -0.248 ms -3.684 67.67

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

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

Clock Offset is field 5 in the peerstats log file.



Refclock Offset SOCK(1)

peer offset SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset SOCK(1) -7.601 -7.048 -6.766 -5.999 -2.052 -0.534 1.134 4.714 6.514 1.526 -5.391 ms 1.482 4.602

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

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

Clock Offset is field 5 in the peerstats log file.



Server Jitters

peer jitters plot

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.000 0.000 1.028 4.212 12.495 17.482 17.517 11.467 17.482 3.589 5.160 ms 1.325 5.087

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 104.234.61.117

peer jitter 104.234.61.117 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.234.61.117 0.000 0.735 1.495 3.548 13.550 26.903 29.916 12.055 26.168 4.494 4.883 ms 3.04 14.17

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 107.172.222.7

peer jitter 107.172.222.7 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 134.215.155.177

peer jitter 134.215.155.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 134.215.155.177 0.000 0.000 0.215 3.893 9.692 11.268 11.268 9.477 11.268 2.613 4.426 ms 0.7499 2.88

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 139.84.137.244

peer jitter 139.84.137.244 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 139.84.137.244 0.000 0.000 0.000 29.399 68.353 70.631 70.631 68.353 70.631 18.676 29.621 ms 0.1808 2.785

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 143.42.229.154

peer jitter 143.42.229.154 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 144.202.0.197

peer jitter 144.202.0.197 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 144.202.0.197 0.000 0.000 0.000 87.784 111.447 111.447 111.447 111.447 111.447 49.774 49.877 ms 0.05641 1.077

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 147.88.195.53

peer jitter 147.88.195.53 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 149.248.12.167

peer jitter 149.248.12.167 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.248.12.167 0.000 0.000 1.937 5.393 14.159 15.551 15.551 12.222 15.551 4.000 6.455 ms 0.6547 2.36

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 149.28.200.179

peer jitter 149.28.200.179 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 149.28.200.179 0.000 0.000 1.399 3.543 11.629 26.497 26.744 10.230 26.497 4.761 4.914 ms 3.113 13.79

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 155.248.196.28

peer jitter 155.248.196.28 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 155.248.196.28 0.000 0.589 0.940 3.258 9.816 16.282 21.738 8.876 15.693 3.024 4.022 ms 2.002 8.941

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 157.245.125.229

peer jitter 157.245.125.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 157.245.125.229 0.000 0.000 0.000 1.602 1.798 1.798 1.798 1.798 1.798 0.805 1.133 ms -0.676 1.5

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.000 0.000 0.676 2.983 9.026 15.209 15.209 8.350 15.209 2.634 3.497 ms 2.021 8.371

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.123

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.000 0.000 1.184 3.489 16.100 36.292 40.015 14.916 36.292 5.808 5.125 ms 3.477 18.08

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 170.187.147.56

peer jitter 170.187.147.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 170.187.147.56 0.000 0.000 0.910 2.839 12.056 56.163 57.472 11.146 56.163 7.201 5.030 ms 4.95 33.37

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 171.66.97.126

peer jitter 171.66.97.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 171.66.97.126 0.000 0.000 0.000 87.962 108.804 108.804 108.804 108.804 108.804 49.147 49.518 ms 0.04453 1.06

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.233.155.39

peer jitter 172.233.155.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.233.155.39 0.000 0.000 0.995 2.783 14.298 19.870 19.951 13.303 19.870 3.907 3.826 ms 2.866 11.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 172.234.25.10

peer jitter 172.234.25.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.25.10 0.000 0.000 1.365 4.096 9.848 14.966 20.475 8.483 14.966 3.089 4.974 ms 1.756 8.373

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.234.37.140

peer jitter 172.234.37.140 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.234.37.140 0.000 0.000 0.355 3.807 36.667 38.858 42.878 36.312 38.858 9.029 7.045 ms 2.543 9.046

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

Closer to 0s 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.584 1.079 2.829 12.374 19.184 20.770 11.296 18.601 3.457 3.835 ms 2.655 10.78

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 172.238.164.57

peer jitter 172.238.164.57 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 172.238.164.57 0.000 0.646 1.090 3.175 12.250 22.806 98.321 11.160 22.160 7.000 4.674 ms 9.521 121.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 172.245.210.108

peer jitter 172.245.210.108 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 3.805 39.386 75.816 198.429 206.604 72.011 198.429 31.157 42.221 ms 2.62 13.46

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.291 1.258 3.936 16.993 38.862 106.974 15.735 38.571 7.042 5.759 ms 5.589 54.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 198.137.202.56

peer jitter 198.137.202.56 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.137.202.56 0.000 0.755 1.178 3.161 12.596 31.040 170.481 11.418 30.284 8.714 4.938 ms 12.32 205.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 198.46.254.130

peer jitter 198.46.254.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 198.46.254.130 0.000 0.000 0.999 3.685 17.434 36.558 41.450 16.435 36.558 6.279 5.702 ms 2.802 13.08

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.2.134.173

peer jitter 204.2.134.173 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.2.134.173 0.000 0.000 0.000 2.478 2.478 2.478 2.478 2.478 2.478 1.239 1.239 ms 0 1

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 206.210.192.99

peer jitter 206.210.192.99 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 209.177.158.85

peer jitter 209.177.158.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.177.158.85 0.694 1.010 1.224 3.369 16.507 23.233 42.861 15.283 22.223 5.084 4.879 ms 3.957 25.58

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 212.227.240.160

peer jitter 212.227.240.160 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.229.4.66

peer jitter 216.229.4.66 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.229.4.66 0.000 0.000 1.118 3.126 13.486 18.864 19.152 12.368 18.864 3.617 4.133 ms 2.295 8.497

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.66.48.42

peer jitter 216.66.48.42 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.142.248.9

peer jitter 23.142.248.9 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.142.248.9 0.000 0.000 0.000 1.910 223.573 223.573 223.573 223.573 223.573 80.245 51.522 ms 1.16 2.531

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.150.41.122

peer jitter 23.150.41.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.150.41.122 0.000 0.000 1.463 3.505 23.193 35.393 36.946 21.730 35.393 7.103 5.730 ms 3.209 13.01

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.150.41.123

peer jitter 23.150.41.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.150.41.123 0.000 0.000 1.604 7.296 29.409 50.390 61.594 27.805 50.390 10.451 10.647 ms 2.2 9.046

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.155.72.147

peer jitter 23.155.72.147 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.155.72.147 0.000 0.000 1.155 3.406 36.728 38.286 43.030 35.574 38.286 9.343 6.981 ms 2.473 8.282

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.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 0.000 42.360 75.499 97.826 152.099 75.499 97.826 21.610 42.399 ms 0.6816 5.935

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.168.24.210

peer jitter 23.168.24.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.168.24.210 0.000 0.000 1.329 6.287 36.844 40.675 48.121 35.515 40.675 10.711 11.315 ms 1.333 4.184

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.123

peer jitter 23.186.168.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.123 0.000 0.225 1.294 4.222 16.356 21.070 28.697 15.062 20.845 4.635 5.583 ms 1.811 6.311

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.186.168.126

peer jitter 23.186.168.126 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.186.168.126 0.000 0.000 0.000 86.127 106.510 106.510 106.510 106.510 106.510 46.232 50.498 ms 0.03958 1.076

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 23.95.35.34

peer jitter 23.95.35.34 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 23.95.35.34 0.923 1.043 1.349 4.191 15.473 24.772 43.808 14.124 23.729 5.697 5.919 ms 3.136 17.03

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:f590::23:161:104:133 (isere.sd.ysun.co)

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

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 34.147.28.4

peer jitter 34.147.28.4 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 34.147.28.4 0.000 0.000 18.567 51.344 92.831 102.838 108.993 74.264 102.838 23.085 54.142 ms 0.002413 2.577

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 38.45.64.130

peer jitter 38.45.64.130 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 38.45.64.130 0.000 0.000 2.027 30.687 77.576 208.979 263.171 75.548 208.979 32.896 37.232 ms 3.604 20.96

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 40.160.28.79

peer jitter 40.160.28.79 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 44.190.5.123

peer jitter 44.190.5.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 44.190.5.123 0.000 0.000 1.096 3.713 6.087 7.846 7.846 4.992 7.846 1.629 3.721 ms 0.1742 3.376

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 45.55.58.103

peer jitter 45.55.58.103 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 47.85.203.40

peer jitter 47.85.203.40 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 49.12.103.123

peer jitter 49.12.103.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 49.12.103.123 0.000 0.000 8.494 52.028 95.543 105.971 112.348 87.049 105.971 24.109 52.611 ms -0.002461 2.709

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 5.161.111.190

peer jitter 5.161.111.190 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 5.161.94.12

peer jitter 5.161.94.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.94.12 0.000 0.726 1.062 4.573 30.285 60.359 81.956 29.223 59.633 11.411 9.222 ms 2.922 14.51

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 50.117.3.95

peer jitter 50.117.3.95 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.117.3.95 0.000 0.000 0.710 3.258 22.835 29.378 30.209 22.125 29.378 8.114 8.046 ms 1.002 2.77

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 50.218.103.254

peer jitter 50.218.103.254 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.218.103.254 0.000 0.000 1.605 10.036 31.573 43.704 46.371 29.968 43.704 9.984 12.026 ms 1.256 4.602

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 51.81.226.229

peer jitter 51.81.226.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 51.81.226.229 0.000 0.502 1.231 2.992 20.342 21.934 22.492 19.111 21.432 5.169 4.964 ms 2.15 6.691

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 64.251.10.152

peer jitter 64.251.10.152 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.251.10.152 0.000 0.662 1.310 2.937 14.783 23.548 24.751 13.473 22.886 4.514 4.810 ms 2.064 7.271

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 65.182.224.39

peer jitter 65.182.224.39 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 65.182.224.39 0.000 0.000 0.862 2.239 8.881 15.286 19.717 8.019 15.286 2.933 3.202 ms 2.506 10.58

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 65.182.224.60

peer jitter 65.182.224.60 plot

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

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 72.14.186.59

peer jitter 72.14.186.59 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 72.14.186.59 0.000 0.000 0.605 2.607 7.822 13.480 13.480 7.218 13.480 2.890 3.838 ms 0.9825 3.827

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 73.185.182.209

peer jitter 73.185.182.209 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.185.182.209 0.000 0.000 1.302 5.327 58.522 61.483 80.745 57.221 61.483 16.790 10.844 ms 2.513 7.96

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 77.37.97.124

peer jitter 77.37.97.124 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.37.97.124 0.000 0.000 0.000 37.688 62.650 66.768 66.768 62.650 66.768 21.573 32.407 ms -0.3942 1.864

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 77.42.37.85

peer jitter 77.42.37.85 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 77.42.37.85 0.000 0.000 0.000 33.065 79.065 79.065 79.065 79.065 79.065 26.327 27.862 ms 0.2787 1.786

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 79.160.225.13

peer jitter 79.160.225.13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 79.160.225.13 0.000 0.000 0.000 42.736 61.519 61.519 61.519 61.519 61.519 14.263 42.723 ms -1.798 6.524

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 83.228.206.15

peer jitter 83.228.206.15 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 83.228.206.15 0.000 0.000 26.174 58.345 95.964 116.045 155.978 69.791 116.045 22.450 58.259 ms 0.1172 4.217

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(0) 0.000 0.736 1.061 2.542 5.740 7.661 10.738 4.679 6.926 1.512 2.850 ms 1.226 5.031

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(1) 0.000 0.153 0.190 0.306 0.525 0.799 6.227 0.335 0.645 0.216 0.334 ms 14.1 308.4

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

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

RMS Jitter is field 8 in the peerstats log file.



Refclock RMS Jitter SOCK(1)

peer jitter SOCK(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter SOCK(1) 0.000 0.137 0.184 0.339 0.790 1.247 4.136 0.607 1.111 0.248 0.398 ms 5.412 59.73

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -7.584 10.456 10.888 11.804 22.292 22.641 120.802 11.404 12.185 5.046 15.636 ppm 2.178 37.87
Local Clock Time Offset -76.840 -6.890 -6.454 -2.145 1.600 4.125 116.829 8.054 11.015 3.814 -2.597 ms 1.989 182.3
Local RMS Frequency Jitter 0.0000 0.0053 0.0061 0.242 0.877 5.705 48.231 0.871 5.700 2.129 0.473 ppm 13.76 221.4
Local RMS Time Jitter 0.000 0.247 0.286 0.401 3.530 6.344 70.769 3.244 6.097 2.985 1.100 ms 13.95 247.1
Refclock Offset SHM(0) -155.160 -152.369 -149.937 -140.323 -133.385 -131.084 -128.188 16.553 21.285 5.068 -140.872 ms -0.2936 2.486
Refclock Offset SHM(1) -6.110 -0.928 -0.680 -0.232 0.141 0.236 0.462 0.820 1.164 0.300 -0.248 ms -3.684 67.67
Refclock Offset SOCK(1) -7.601 -7.048 -6.766 -5.999 -2.052 -0.534 1.134 4.714 6.514 1.526 -5.391 ms 1.482 4.602
Refclock RMS Jitter SHM(0) 0.000 0.736 1.061 2.542 5.740 7.661 10.738 4.679 6.926 1.512 2.850 ms 1.226 5.031
Refclock RMS Jitter SHM(1) 0.000 0.153 0.190 0.306 0.525 0.799 6.227 0.335 0.645 0.216 0.334 ms 14.1 308.4
Refclock RMS Jitter SOCK(1) 0.000 0.137 0.184 0.339 0.790 1.247 4.136 0.607 1.111 0.248 0.398 ms 5.412 59.73
Server Jitter 104.131.155.175 0.000 0.000 1.028 4.212 12.495 17.482 17.517 11.467 17.482 3.589 5.160 ms 1.325 5.087
Server Jitter 104.234.61.117 0.000 0.735 1.495 3.548 13.550 26.903 29.916 12.055 26.168 4.494 4.883 ms 3.04 14.17
Server Jitter 107.172.222.7 0.000 0.000 1.084 4.379 25.305 36.743 37.327 24.221 36.743 8.622 8.136 ms 1.606 4.837
Server Jitter 134.215.155.177 0.000 0.000 0.215 3.893 9.692 11.268 11.268 9.477 11.268 2.613 4.426 ms 0.7499 2.88
Server Jitter 139.84.137.244 0.000 0.000 0.000 29.399 68.353 70.631 70.631 68.353 70.631 18.676 29.621 ms 0.1808 2.785
Server Jitter 143.42.229.154 0.000 0.000 1.148 7.611 49.932 51.852 52.766 48.784 51.852 13.133 12.146 ms 1.725 5.461
Server Jitter 144.202.0.197 0.000 0.000 0.000 87.784 111.447 111.447 111.447 111.447 111.447 49.774 49.877 ms 0.05641 1.077
Server Jitter 147.88.195.53 0.000 0.000 0.000 41.577 77.749 93.726 95.821 77.749 93.726 21.527 41.634 ms -0.03586 2.951
Server Jitter 149.248.12.167 0.000 0.000 1.937 5.393 14.159 15.551 15.551 12.222 15.551 4.000 6.455 ms 0.6547 2.36
Server Jitter 149.28.200.179 0.000 0.000 1.399 3.543 11.629 26.497 26.744 10.230 26.497 4.761 4.914 ms 3.113 13.79
Server Jitter 155.248.196.28 0.000 0.589 0.940 3.258 9.816 16.282 21.738 8.876 15.693 3.024 4.022 ms 2.002 8.941
Server Jitter 157.245.125.229 0.000 0.000 0.000 1.602 1.798 1.798 1.798 1.798 1.798 0.805 1.133 ms -0.676 1.5
Server Jitter 162.159.200.1 0.000 0.000 0.676 2.983 9.026 15.209 15.209 8.350 15.209 2.634 3.497 ms 2.021 8.371
Server Jitter 162.159.200.123 0.000 0.000 1.184 3.489 16.100 36.292 40.015 14.916 36.292 5.808 5.125 ms 3.477 18.08
Server Jitter 170.187.147.56 0.000 0.000 0.910 2.839 12.056 56.163 57.472 11.146 56.163 7.201 5.030 ms 4.95 33.37
Server Jitter 171.66.97.126 0.000 0.000 0.000 87.962 108.804 108.804 108.804 108.804 108.804 49.147 49.518 ms 0.04453 1.06
Server Jitter 172.233.155.39 0.000 0.000 0.995 2.783 14.298 19.870 19.951 13.303 19.870 3.907 3.826 ms 2.866 11.26
Server Jitter 172.234.25.10 0.000 0.000 1.365 4.096 9.848 14.966 20.475 8.483 14.966 3.089 4.974 ms 1.756 8.373
Server Jitter 172.234.37.140 0.000 0.000 0.355 3.807 36.667 38.858 42.878 36.312 38.858 9.029 7.045 ms 2.543 9.046
Server Jitter 172.235.60.8 0.000 0.584 1.079 2.829 12.374 19.184 20.770 11.296 18.601 3.457 3.835 ms 2.655 10.78
Server Jitter 172.238.164.57 0.000 0.646 1.090 3.175 12.250 22.806 98.321 11.160 22.160 7.000 4.674 ms 9.521 121.7
Server Jitter 172.245.210.108 0.000 0.000 0.000 3.191 187.963 208.084 208.084 187.963 208.084 52.818 21.295 ms 2.724 8.749
Server Jitter 185.234.20.134 0.000 0.000 3.805 39.386 75.816 198.429 206.604 72.011 198.429 31.157 42.221 ms 2.62 13.46
Server Jitter 194.0.5.123 0.000 0.291 1.258 3.936 16.993 38.862 106.974 15.735 38.571 7.042 5.759 ms 5.589 54.16
Server Jitter 198.137.202.56 0.000 0.755 1.178 3.161 12.596 31.040 170.481 11.418 30.284 8.714 4.938 ms 12.32 205.7
Server Jitter 198.46.254.130 0.000 0.000 0.999 3.685 17.434 36.558 41.450 16.435 36.558 6.279 5.702 ms 2.802 13.08
Server Jitter 204.2.134.173 0.000 0.000 0.000 2.478 2.478 2.478 2.478 2.478 2.478 1.239 1.239 ms 0 1
Server Jitter 206.210.192.99 0.000 0.000 0.000 2.291 4.456 4.456 4.456 4.456 4.456 1.344 2.379 ms 0.04821 2.401
Server Jitter 209.177.158.85 0.694 1.010 1.224 3.369 16.507 23.233 42.861 15.283 22.223 5.084 4.879 ms 3.957 25.58
Server Jitter 212.227.240.160 0.000 0.000 0.000 5.333 13.898 13.898 13.898 13.898 13.898 4.106 5.460 ms 0.8261 3.059
Server Jitter 216.229.4.66 0.000 0.000 1.118 3.126 13.486 18.864 19.152 12.368 18.864 3.617 4.133 ms 2.295 8.497
Server Jitter 216.66.48.42 0.000 0.000 2.641 25.978 59.408 65.378 72.744 56.767 65.378 15.554 27.857 ms 0.5488 2.961
Server Jitter 23.142.248.9 0.000 0.000 0.000 1.910 223.573 223.573 223.573 223.573 223.573 80.245 51.522 ms 1.16 2.531
Server Jitter 23.150.41.122 0.000 0.000 1.463 3.505 23.193 35.393 36.946 21.730 35.393 7.103 5.730 ms 3.209 13.01
Server Jitter 23.150.41.123 0.000 0.000 1.604 7.296 29.409 50.390 61.594 27.805 50.390 10.451 10.647 ms 2.2 9.046
Server Jitter 23.155.72.147 0.000 0.000 1.155 3.406 36.728 38.286 43.030 35.574 38.286 9.343 6.981 ms 2.473 8.282
Server Jitter 23.161.104.133 0.000 0.000 0.000 42.360 75.499 97.826 152.099 75.499 97.826 21.610 42.399 ms 0.6816 5.935
Server Jitter 23.168.24.210 0.000 0.000 1.329 6.287 36.844 40.675 48.121 35.515 40.675 10.711 11.315 ms 1.333 4.184
Server Jitter 23.186.168.123 0.000 0.225 1.294 4.222 16.356 21.070 28.697 15.062 20.845 4.635 5.583 ms 1.811 6.311
Server Jitter 23.186.168.126 0.000 0.000 0.000 86.127 106.510 106.510 106.510 106.510 106.510 46.232 50.498 ms 0.03958 1.076
Server Jitter 23.95.35.34 0.923 1.043 1.349 4.191 15.473 24.772 43.808 14.124 23.729 5.697 5.919 ms 3.136 17.03
Server Jitter 2602:f590::23:161:104:133 (isere.sd.ysun.co) 0.000 0.000 7.038 40.173 63.744 78.005 83.945 56.706 78.005 17.076 39.669 ms -0.2518 2.788
Server Jitter 34.147.28.4 0.000 0.000 18.567 51.344 92.831 102.838 108.993 74.264 102.838 23.085 54.142 ms 0.002413 2.577
Server Jitter 38.45.64.130 0.000 0.000 2.027 30.687 77.576 208.979 263.171 75.548 208.979 32.896 37.232 ms 3.604 20.96
Server Jitter 40.160.28.79 0.000 1.801 6.063 24.301 44.703 52.503 53.020 38.640 50.702 10.983 25.335 ms 0.2798 2.796
Server Jitter 44.190.5.123 0.000 0.000 1.096 3.713 6.087 7.846 7.846 4.992 7.846 1.629 3.721 ms 0.1742 3.376
Server Jitter 45.55.58.103 0.000 0.000 0.000 85.863 108.041 108.041 108.041 108.041 108.041 46.518 50.518 ms 0.04903 1.088
Server Jitter 47.85.203.40 0.000 0.848 1.598 5.948 28.308 42.271 42.446 26.710 41.422 9.054 9.477 ms 1.937 6.968
Server Jitter 49.12.103.123 0.000 0.000 8.494 52.028 95.543 105.971 112.348 87.049 105.971 24.109 52.611 ms -0.002461 2.709
Server Jitter 5.161.111.190 0.000 0.887 1.554 4.668 21.349 37.015 37.112 19.795 36.128 7.669 8.606 ms 1.358 4.999
Server Jitter 5.161.94.12 0.000 0.726 1.062 4.573 30.285 60.359 81.956 29.223 59.633 11.411 9.222 ms 2.922 14.51
Server Jitter 50.117.3.95 0.000 0.000 0.710 3.258 22.835 29.378 30.209 22.125 29.378 8.114 8.046 ms 1.002 2.77
Server Jitter 50.218.103.254 0.000 0.000 1.605 10.036 31.573 43.704 46.371 29.968 43.704 9.984 12.026 ms 1.256 4.602
Server Jitter 51.81.226.229 0.000 0.502 1.231 2.992 20.342 21.934 22.492 19.111 21.432 5.169 4.964 ms 2.15 6.691
Server Jitter 64.251.10.152 0.000 0.662 1.310 2.937 14.783 23.548 24.751 13.473 22.886 4.514 4.810 ms 2.064 7.271
Server Jitter 65.182.224.39 0.000 0.000 0.862 2.239 8.881 15.286 19.717 8.019 15.286 2.933 3.202 ms 2.506 10.58
Server Jitter 65.182.224.60 0.000 0.000 2.004 3.445 7.058 10.501 10.501 5.054 10.501 1.855 3.928 ms 1.023 4.59
Server Jitter 72.14.186.59 0.000 0.000 0.605 2.607 7.822 13.480 13.480 7.218 13.480 2.890 3.838 ms 0.9825 3.827
Server Jitter 73.185.182.209 0.000 0.000 1.302 5.327 58.522 61.483 80.745 57.221 61.483 16.790 10.844 ms 2.513 7.96
Server Jitter 77.37.97.124 0.000 0.000 0.000 37.688 62.650 66.768 66.768 62.650 66.768 21.573 32.407 ms -0.3942 1.864
Server Jitter 77.42.37.85 0.000 0.000 0.000 33.065 79.065 79.065 79.065 79.065 79.065 26.327 27.862 ms 0.2787 1.786
Server Jitter 79.160.225.13 0.000 0.000 0.000 42.736 61.519 61.519 61.519 61.519 61.519 14.263 42.723 ms -1.798 6.524
Server Jitter 83.228.206.15 0.000 0.000 26.174 58.345 95.964 116.045 155.978 69.791 116.045 22.450 58.259 ms 0.1172 4.217
Server Offset 104.131.155.175 -9.978 -9.873 -7.869 1.310 6.960 13.031 14.937 14.829 22.904 4.061 1.075 ms 0.02473 4.904
Server Offset 104.234.61.117 -11.180 -9.140 -3.447 1.426 6.606 12.091 16.244 10.053 21.231 3.430 1.519 ms -0.07377 5.449
Server Offset 107.172.222.7 -12.642 -11.375 -7.178 1.882 7.310 12.947 14.359 14.488 24.322 3.982 1.625 ms -0.7389 5.565
Server Offset 134.215.155.177 -6.511 -6.511 -4.780 0.657 5.183 15.538 15.538 9.962 22.050 3.593 0.567 ms 1.062 6.279
Server Offset 139.84.137.244 -76.084 -76.084 -67.500 -13.455 13.351 16.737 16.737 80.851 92.820 27.963 -20.103 ms -0.468 2.005
Server Offset 143.42.229.154 -12.280 -11.918 -8.448 0.679 4.877 10.025 10.853 13.326 21.944 3.809 0.031 ms -0.9182 4.866
Server Offset 144.202.0.197 -112.597 -112.597 -112.597 -0.542 1.509 1.509 1.509 114.106 114.106 56.383 -55.610 ms 0.0001555 1.001
Server Offset 147.88.195.53 -119.005 -102.607 -78.625 -8.685 6.545 10.280 13.559 85.170 112.887 26.779 -18.851 ms -1.354 4.238
Server Offset 149.248.12.167 -8.248 -8.248 -5.145 2.102 8.205 12.647 12.647 13.350 20.895 4.129 1.825 ms 0.01569 3.465
Server Offset 149.28.200.179 -15.182 -10.996 -7.700 0.875 6.594 11.091 14.392 14.294 22.087 3.870 0.627 ms -0.6716 5.971
Server Offset 155.248.196.28 -7.263 -4.833 -2.819 0.165 4.387 7.586 11.821 7.206 12.418 2.282 0.520 ms 0.7572 5.018
Server Offset 157.245.125.229 1.618 1.618 1.618 2.114 3.912 3.912 3.912 2.294 2.294 0.986 2.548 ms 0.5751 1.5
Server Offset 162.159.200.1 -6.317 -6.317 -3.562 0.356 5.592 14.827 14.827 9.154 21.144 3.010 0.789 ms 1.452 9.498
Server Offset 162.159.200.123 -5.017 -4.357 -3.040 0.526 5.143 37.514 40.107 8.183 41.871 5.386 1.191 ms 5.394 38.2
Server Offset 170.187.147.56 1.026 1.199 3.846 6.744 9.809 11.373 12.448 5.963 10.174 1.897 6.818 ms -0.2684 3.74
Server Offset 171.66.97.126 -111.117 -111.117 -111.117 -1.864 2.857 2.857 2.857 113.973 113.973 55.954 -54.736 ms 0.002046 1.003
Server Offset 172.233.155.39 -1.467 -1.004 0.504 3.923 6.683 9.443 9.891 6.178 10.447 1.888 3.780 ms -0.1655 3.462
Server Offset 172.234.25.10 -378.349 -377.277 -1.613 7.945 13.980 16.005 16.638 15.592 393.281 71.028 -5.439 ms -5.005 26.14
Server Offset 172.234.37.140 -384.852 -382.248 -15.994 -0.820 4.381 5.631 9.952 20.375 387.879 60.491 -11.217 ms -5.922 36.29
Server Offset 172.235.60.8 -4.609 -3.025 -1.374 1.899 6.639 7.668 9.759 8.013 10.693 2.337 2.181 ms 0.3878 3.311
Server Offset 172.238.164.57 -20.678 -5.845 -4.128 -0.201 4.991 6.484 11.018 9.119 12.329 2.825 0.122 ms -0.1455 6.625
Server Offset 172.245.210.108 -261.506 -261.506 -251.411 0.386 170.775 173.801 173.801 422.186 435.307 82.626 -6.480 ms -0.7581 6.622
Server Offset 185.234.20.134 -207.966 -206.319 4.562 42.236 55.508 222.373 228.892 50.946 428.693 46.855 38.001 ms -0.7219 18.78
Server Offset 194.0.5.123 -452.715 -14.266 -5.786 1.183 7.269 11.033 30.250 13.055 25.299 25.253 -0.184 ms -16.99 303.6
Server Offset 198.137.202.56 -206.226 -6.792 -4.823 -1.585 2.970 6.864 17.267 7.794 13.656 10.679 -1.881 ms -16.46 302.5
Server Offset 198.46.254.130 -11.109 -10.105 -8.900 -0.000 6.524 48.594 50.250 15.424 58.699 6.597 0.210 ms 4.556 35.9
Server Offset 204.2.134.173 -0.755 -0.755 -0.755 1.723 1.723 1.723 1.723 2.478 2.478 1.239 0.484 ms 0 1
Server Offset 206.210.192.99 3.732 3.732 3.732 10.882 12.986 12.986 12.986 9.255 9.255 2.868 9.737 ms -0.9345 2.785
Server Offset 209.177.158.85 -30.375 -26.695 -4.423 -0.930 1.753 5.012 7.613 6.175 31.707 4.289 -1.516 ms -4.702 29.96
Server Offset 212.227.240.160 -12.742 -12.742 -12.742 -3.409 1.156 1.156 1.156 13.898 13.898 4.103 -3.640 ms -1.253 3.789
Server Offset 216.229.4.66 -17.026 -11.915 -9.323 -0.727 3.365 13.045 13.185 12.689 24.960 3.711 -1.195 ms -0.3257 7.429
Server Offset 216.66.48.42 -57.714 -48.968 -41.803 -10.099 4.232 45.537 48.178 46.035 94.505 15.518 -12.901 ms 0.07764 5.238
Server Offset 23.142.248.9 -263.459 -263.459 -262.784 -5.526 168.098 168.098 168.098 430.883 431.557 135.791 -14.334 ms -0.3337 2.497
Server Offset 23.150.41.122 -3.912 -3.704 0.122 4.751 7.547 11.178 12.219 7.425 14.882 2.538 4.300 ms -0.6129 4.277
Server Offset 23.150.41.123 3.519 3.565 4.354 8.155 11.199 17.772 20.648 6.846 14.207 2.380 8.271 ms 1.527 9.709
Server Offset 23.155.72.147 -392.987 -391.252 -12.441 -6.112 -0.837 1.703 7.397 11.604 392.955 61.955 -16.524 ms -5.782 34.56
Server Offset 23.161.104.133 -120.099 -100.489 -82.609 -12.114 9.325 14.069 21.144 91.934 114.558 28.361 -20.416 ms -1.19 3.714
Server Offset 23.168.24.210 -30.994 -9.946 -0.456 4.953 9.479 14.370 15.899 9.935 24.316 3.912 4.627 ms -3.016 28.6
Server Offset 23.186.168.123 -18.265 -13.910 -9.299 -2.861 3.315 8.235 24.970 12.613 22.145 3.976 -2.910 ms 0.6185 9.406
Server Offset 23.186.168.126 -114.793 -114.793 -114.793 -5.494 -0.844 -0.844 -0.844 113.950 113.950 54.847 -57.177 ms -0.005087 1.013
Server Offset 23.95.35.34 -27.613 -7.115 -4.506 -1.130 1.000 3.097 8.679 5.506 10.212 2.944 -1.526 ms -4.974 44.45
Server Offset 2602:f590::23:161:104:133 (isere.sd.ysun.co) -471.581 -385.176 -54.827 -11.476 0.126 5.242 28.182 54.953 390.419 61.385 -26.183 ms -5.774 37.6
Server Offset 34.147.28.4 -129.797 -97.451 -53.266 -8.090 4.141 9.142 11.849 57.407 106.593 21.047 -13.839 ms -2.49 10.74
Server Offset 38.45.64.130 -257.312 -253.476 -19.339 5.468 8.969 174.253 177.823 28.308 427.728 37.148 1.973 ms -1.963 32.42
Server Offset 40.160.28.79 -52.835 -52.513 -34.382 -5.004 1.626 5.643 7.374 36.008 58.156 10.906 -8.229 ms -2.157 7.89
Server Offset 44.190.5.123 -7.144 -7.144 -5.951 -0.158 3.398 3.755 3.755 9.349 10.899 2.890 -0.778 ms -0.2377 2.111
Server Offset 45.55.58.103 -110.343 -110.343 -110.343 0.562 3.360 3.360 3.360 113.703 113.703 54.930 -52.554 ms -0.005973 1.01
Server Offset 47.85.203.40 -11.482 -4.542 -0.158 5.077 10.458 14.417 15.104 10.616 18.959 3.390 5.170 ms -0.3312 5.456
Server Offset 49.12.103.123 -104.453 -96.809 -69.563 -6.827 5.026 15.191 21.860 74.590 112.001 23.583 -15.248 ms -1.71 5.611
Server Offset 5.161.111.190 -18.177 -13.919 -7.797 -3.175 1.189 3.412 7.582 8.985 17.330 3.150 -3.351 ms -0.7991 5.935
Server Offset 5.161.94.12 -26.311 -6.789 -5.364 -1.781 1.988 4.296 14.347 7.351 11.084 2.473 -1.710 ms -0.7917 18.97
Server Offset 50.117.3.95 -13.393 -13.270 -8.900 -1.296 1.731 4.497 6.235 10.631 17.767 3.214 -1.929 ms -1.378 5.671
Server Offset 50.218.103.254 -39.877 -17.266 -8.068 0.775 5.720 46.263 49.954 13.788 63.530 7.440 0.730 ms 2.027 26.4
Server Offset 51.81.226.229 0.232 0.432 1.153 4.562 8.093 11.100 11.602 6.940 10.668 2.089 4.771 ms 0.385 3.649
Server Offset 64.251.10.152 -9.929 -6.388 -4.004 -0.535 3.189 7.131 10.599 7.193 13.520 2.557 -0.405 ms 0.497 5.923
Server Offset 65.182.224.39 -19.040 -5.987 -1.484 1.519 6.164 11.148 17.628 7.648 17.136 3.038 1.696 ms -0.02657 18.42
Server Offset 65.182.224.60 -4.897 -4.897 -2.203 1.449 6.846 10.883 10.883 9.048 15.780 2.958 1.749 ms 0.4925 3.551
Server Offset 72.14.186.59 -10.962 -10.962 -6.498 5.272 7.467 8.444 8.444 13.965 19.405 4.884 3.065 ms -1.172 3.134
Server Offset 73.185.182.209 -385.027 -380.946 -7.553 0.567 7.557 9.409 12.049 15.110 390.355 62.523 -9.596 ms -5.741 34.11
Server Offset 77.37.97.124 -64.960 -64.960 -62.814 -13.281 12.547 12.582 12.582 75.362 77.541 22.383 -16.669 ms -0.5829 2.612
Server Offset 77.42.37.85 -83.037 -83.037 -83.037 -1.405 13.595 13.595 13.595 96.633 96.633 29.560 -20.475 ms -0.8498 2.319
Server Offset 79.160.225.13 -64.543 -64.543 -64.543 -8.196 0.842 0.842 0.842 65.386 65.386 19.527 -17.421 ms -1.173 3.163
Server Offset 83.228.206.15 -137.287 -106.678 -85.463 -5.076 5.321 28.735 31.867 90.784 135.413 27.600 -16.729 ms -1.765 5.927
TDOP 0.450 0.510 0.560 0.760 1.170 1.640 2.830 0.610 1.130 0.212 0.805 2.264 13.73
Temp /dev/sda 18.000 20.000 20.000 25.000 26.000 26.000 29.000 6.000 6.000 2.166 24.247 °C
Temp LM0 31.000 31.000 32.000 37.000 37.000 37.000 50.000 5.000 6.000 1.413 36.183 °C
Temp LM1 29.000 30.000 31.000 35.000 37.000 38.000 42.000 6.000 8.000 1.834 34.501 °C
Temp LM2 26.000 26.000 34.000 38.000 40.000 41.000 45.000 6.000 15.000 2.826 37.819 °C
Temp LM3 0.000 0.000 0.000 3.000 39.000 40.000 41.000 39.000 40.000 13.985 9.457 °C
Temp LM4 0.000 0.000 0.000 34.000 39.000 42.000 46.000 39.000 42.000 13.486 27.996 °C
Temp LM5 29.000 29.000 30.000 32.000 34.000 34.000 37.000 4.000 5.000 1.354 31.878 °C
Temp LM6 31.000 32.000 33.000 34.000 36.000 37.000 44.000 3.000 5.000 1.160 33.995 °C
Temp LM7 32.000 33.000 34.000 35.000 37.000 39.000 45.000 3.000 6.000 1.129 35.567 °C
Temp LM8 26.800 26.800 34.000 35.000 37.000 39.000 45.000 3.000 12.200 2.061 35.417 °C
Temp LM9 26.800 26.800 34.000 35.000 37.000 39.000 45.000 3.000 12.200 2.061 35.417 °C
Temp ZONE0 20.000 20.000 20.000 20.000 20.000 20.000 20.000 0.000 0.000 0.000 20.000 °C
Temp ZONE1 26.800 26.800 34.000 35.000 37.000 38.000 45.000 3.000 11.200 1.960 34.886 °C
Temp ZONE2 29.000 29.000 34.000 37.000 37.000 37.000 37.000 3.000 8.000 1.733 35.963 °C
Temp ZONE3 32.000 33.000 34.000 35.000 37.000 38.000 45.000 3.000 5.000 1.149 35.165 °C
Temp ZONE4 26.800 26.800 34.000 35.000 37.000 38.000 45.000 3.000 11.200 1.960 34.886 °C
Temp ZONE5 30.000 31.000 32.000 34.000 39.000 42.000 50.000 7.000 11.000 2.298 34.286 °C
Temp ZONE6 29.000 30.000 30.000 31.000 33.000 34.000 38.000 3.000 4.000 1.004 31.589 °C
nSats 8.000 10.000 11.000 13.000 17.000 19.000 21.000 6.000 9.000 2.009 13.649 nSat 0.6694 2.852
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!