Stats for the last 1, 7, 35, 98, 371, some days, or live gps data.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Time Offset | -95.988 | -4.517 | -0.732 | -0.035 | 0.645 | 1.136 | 105.238 | 1.376 | 5.652 | 1.019 | -0.116 | ms | 0.622 | 1711 | ||
| Local Clock Frequency Offset | -15.474 | 2.971 | 4.767 | 10.911 | 18.938 | 23.575 | 61.826 | 14.171 | 20.604 | 3.581 | 10.960 | ppm | 1.181 | 7.21 | ||
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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local RMS Time Jitter | 0.000 | 0.093 | 0.115 | 0.325 | 0.828 | 1.326 | 52.058 | 0.713 | 1.233 | 0.424 | 0.370 | ms | 47.34 | 4303 | ||
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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local RMS Frequency Jitter | 0.0000 | 0.0033 | 0.0041 | 0.0139 | 2.576 | 3.626 | 21.113 | 2.572 | 3.622 | 0.869 | 0.466 | ppm | 2.308 | 10.56 | ||
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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Offset | -95.988 | -4.517 | -0.732 | -0.035 | 0.645 | 1.136 | 105.238 | 1.376 | 5.652 | 1.019 | -0.116 | ms | 0.622 | 1711 | ||
The clock offsets of the local clock as a histogram.
The Local Clock Offset is field 3 from the loopstats log file.
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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Frequency Offset | -15.474 | 2.971 | 4.767 | 10.911 | 18.938 | 23.575 | 61.826 | 14.171 | 20.604 | 3.581 | 10.960 | ppm | 1.181 | 7.21 | ||
| Temp /dev/sda | 15.000 | 17.000 | 18.000 | 25.000 | 26.000 | 28.000 | 39.000 | 8.000 | 11.000 | 2.540 | 23.675 | °C | ||||
| Temp LM0 | 28.000 | 30.000 | 30.000 | 34.000 | 41.000 | 44.000 | 54.000 | 11.000 | 14.000 | 2.876 | 33.908 | °C | ||||
| Temp LM1 | 26.000 | 28.000 | 29.000 | 37.000 | 39.000 | 40.000 | 44.000 | 10.000 | 12.000 | 2.950 | 36.478 | °C | ||||
| Temp LM2 | 0.000 | 0.000 | 0.000 | 19.000 | 34.000 | 34.000 | 51.000 | 34.000 | 34.000 | 6.874 | 19.716 | °C | ||||
| Temp LM3 | 24.000 | 26.000 | 27.000 | 30.000 | 38.000 | 39.000 | 46.000 | 11.000 | 13.000 | 3.044 | 30.660 | °C | ||||
| Temp LM4 | 0.000 | 0.000 | 0.000 | 32.000 | 39.000 | 43.000 | 56.000 | 39.000 | 43.000 | 11.592 | 29.039 | °C | ||||
| Temp LM5 | 24.000 | 26.000 | 27.000 | 30.000 | 32.000 | 32.000 | 45.000 | 5.000 | 6.000 | 1.527 | 29.622 | °C | ||||
| Temp LM6 | 26.000 | 28.000 | 29.000 | 32.000 | 34.000 | 38.000 | 50.000 | 5.000 | 10.000 | 1.799 | 31.973 | °C | ||||
| Temp LM7 | 28.000 | 30.000 | 31.000 | 34.000 | 36.000 | 39.000 | 51.000 | 5.000 | 9.000 | 1.748 | 33.794 | °C | ||||
| Temp LM8 | 28.000 | 31.000 | 31.000 | 34.000 | 37.000 | 39.000 | 51.000 | 6.000 | 8.000 | 1.726 | 34.151 | °C | ||||
| Temp LM9 | 28.000 | 31.000 | 31.000 | 34.000 | 37.000 | 39.000 | 51.000 | 6.000 | 8.000 | 1.727 | 34.151 | °C | ||||
| Temp ZONE0 | 20.000 | 20.000 | 20.000 | 20.000 | 20.000 | 20.000 | 20.000 | 0.000 | 0.000 | 0.000 | 20.000 | °C | ||||
| Temp ZONE1 | 28.000 | 30.000 | 30.000 | 34.000 | 36.000 | 39.000 | 51.000 | 6.000 | 9.000 | 1.779 | 33.270 | °C | ||||
| Temp ZONE2 | 24.000 | 26.000 | 27.000 | 30.000 | 32.000 | 32.000 | 45.000 | 5.000 | 6.000 | 1.527 | 29.622 | °C | ||||
| Temp ZONE3 | 28.000 | 30.000 | 30.000 | 34.000 | 36.000 | 39.000 | 51.000 | 6.000 | 9.000 | 1.780 | 33.275 | °C | ||||
| Temp ZONE4 | 28.000 | 30.000 | 30.000 | 34.000 | 36.000 | 39.000 | 51.000 | 6.000 | 9.000 | 1.779 | 33.270 | °C | ||||
| Temp ZONE5 | 27.000 | 29.000 | 30.000 | 32.000 | 42.000 | 47.000 | 56.000 | 12.000 | 18.000 | 3.955 | 33.936 | °C | ||||
| Temp ZONE6 | 24.000 | 26.000 | 27.000 | 30.000 | 32.000 | 34.000 | 44.000 | 5.000 | 8.000 | 1.574 | 29.633 | °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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| nSats | 6.000 | 8.000 | 9.000 | 11.000 | 13.000 | 14.000 | 16.000 | 4.000 | 6.000 | 1.312 | 10.730 | nSat | 0.1329 | 3.353 | ||
| TDOP | 0.490 | 0.560 | 0.620 | 0.880 | 1.430 | 1.820 | 12.680 | 0.810 | 1.260 | 0.298 | 0.939 | 9.974 | 351.2 | |||
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.
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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 104.131.155.175 | -2.525 | -2.525 | -1.209 | 5.368 | 12.615 | 16.334 | 16.334 | 13.824 | 18.859 | 4.610 | 5.570 | ms | 0.3612 | 2.585 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 104.152.220.5 | 8.870 | 8.870 | 8.870 | 11.393 | 12.411 | 12.411 | 12.411 | 3.542 | 3.542 | 1.242 | 10.668 | ms | -0.1693 | 1.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 104.167.215.195 | -419.941 | -418.768 | -10.695 | 1.453 | 14.053 | 18.705 | 19.868 | 24.748 | 437.473 | 64.209 | -8.450 | ms | -5.837 | 36.7 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 104.167.241.253 | -1.130 | -1.130 | -1.130 | 3.827 | 174.956 | 174.956 | 174.956 | 176.087 | 176.087 | 77.809 | 54.544 | ms | 0.8304 | 1.696 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 104.234.61.117 | -21.499 | -3.096 | 2.445 | 5.568 | 7.901 | 10.166 | 442.381 | 5.456 | 13.262 | 14.127 | 5.812 | ms | 29.9 | 919.1 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 108.181.201.22 | -1.213 | -1.213 | -1.213 | 9.696 | 16.889 | 16.889 | 16.889 | 18.102 | 18.102 | 5.623 | 7.417 | ms | -0.02663 | 1.756 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 108.59.2.24 | 3.739 | 3.739 | 3.739 | 4.597 | 9.132 | 9.132 | 9.132 | 5.393 | 5.393 | 2.366 | 5.823 | ms | 0.6379 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 108.61.215.221 | -31.255 | -1.287 | 2.473 | 4.811 | 6.744 | 10.357 | 13.004 | 4.271 | 11.644 | 2.291 | 4.690 | ms | -7.298 | 118.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 108.61.56.35 | 4.613 | 4.613 | 4.613 | 6.012 | 10.829 | 10.829 | 10.829 | 6.216 | 6.216 | 1.882 | 6.640 | ms | 0.9579 | 2.876 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 108.61.73.243 | -4.642 | 0.420 | 2.263 | 5.013 | 7.453 | 8.990 | 442.001 | 5.190 | 8.569 | 20.919 | 5.974 | ms | 20.5 | 424.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 12.205.28.193 | -283.076 | 0.070 | 2.708 | 5.038 | 7.243 | 8.754 | 27.084 | 4.535 | 8.684 | 10.426 | 4.532 | ms | -21.85 | 507.3 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 12.71.198.242 | -567.986 | -567.986 | -567.986 | -8.926 | 5.527 | 5.527 | 5.527 | 573.513 | 573.513 | 281.819 | -249.816 | ms | -0.223 | 1.051 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 129.146.193.200 | -13.392 | -0.800 | 1.678 | 4.741 | 6.985 | 9.104 | 11.567 | 5.307 | 9.904 | 1.817 | 4.617 | ms | -2.078 | 20 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 131.153.171.250 | 2.305 | 2.305 | 2.305 | 6.214 | 6.977 | 6.977 | 6.977 | 4.672 | 4.672 | 2.047 | 5.165 | ms | -0.6341 | 1.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 131.239.5.43 | 0.782 | 0.782 | 0.782 | 4.026 | 4.797 | 4.797 | 4.797 | 4.014 | 4.014 | 1.405 | 3.356 | ms | -1.032 | 2.322 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 135.148.100.14 | -31.469 | -1.302 | 3.035 | 6.124 | 10.346 | 103.460 | 109.098 | 7.311 | 104.763 | 17.518 | 8.723 | ms | 4.784 | 26.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 137.110.222.27 | -5.819 | -4.877 | -2.098 | 0.991 | 5.793 | 7.199 | 10.485 | 7.892 | 12.076 | 2.211 | 1.182 | ms | 0.5731 | 5.051 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 137.190.2.4 | 8.262 | 8.262 | 8.262 | 10.422 | 12.347 | 12.347 | 12.347 | 4.085 | 4.085 | 1.243 | 10.194 | ms | 0.1927 | 2.51 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 139.177.202.26 | 2.369 | 2.369 | 2.369 | 5.594 | 13.217 | 13.217 | 13.217 | 10.848 | 10.848 | 3.941 | 6.958 | ms | 0.6 | 1.806 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 139.94.144.123 | 7.327 | 7.327 | 7.327 | 7.569 | 8.239 | 8.239 | 8.239 | 0.913 | 0.913 | 0.357 | 7.696 | ms | 0.4162 | 1.533 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 141.11.234.198 | -23.184 | -23.184 | -23.184 | 3.651 | 11.780 | 11.780 | 11.780 | 34.964 | 34.964 | 8.939 | 0.688 | ms | -1.28 | 4.6 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 141.11.89.193 | 2.147 | 2.147 | 2.147 | 3.363 | 5.337 | 5.337 | 5.337 | 3.190 | 3.190 | 1.124 | 3.580 | ms | 0.1122 | 1.688 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 142.202.190.19 | -170.488 | -170.488 | -169.889 | 6.947 | 228.113 | 229.915 | 229.915 | 398.002 | 400.403 | 122.650 | 52.253 | ms | 0.2226 | 2.25 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 143.42.229.154 | -11.954 | -6.689 | -1.054 | 2.237 | 5.081 | 8.112 | 286.021 | 6.135 | 14.801 | 24.501 | 4.211 | ms | 11.27 | 129.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 144.202.0.197 | 2.542 | 2.542 | 2.542 | 5.206 | 10.116 | 10.116 | 10.116 | 7.574 | 7.574 | 1.946 | 5.495 | ms | 0.6649 | 3.455 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 144.202.66.214 | -94.866 | -94.866 | -94.866 | -89.704 | -88.958 | -88.958 | -88.958 | 5.908 | 5.908 | 2.060 | -91.017 | ms | -0.812 | 2.336 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 148.135.119.56 | -5.445 | 1.427 | 3.360 | 5.509 | 7.418 | 8.507 | 19.874 | 4.057 | 7.080 | 1.420 | 5.461 | ms | -0.05811 | 13.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 149.248.12.167 | 6.974 | 6.974 | 6.974 | 12.448 | 13.486 | 13.486 | 13.486 | 6.511 | 6.511 | 2.871 | 10.594 | ms | -0.3694 | 1.196 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 149.28.200.179 | 1.712 | 1.712 | 3.167 | 5.584 | 10.014 | 25.332 | 25.332 | 6.847 | 23.620 | 3.335 | 5.924 | ms | 4.121 | 23.91 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 149.28.61.105 | 2.916 | 2.916 | 2.916 | 5.252 | 8.017 | 8.017 | 8.017 | 5.100 | 5.100 | 1.667 | 5.088 | ms | 0.4936 | 2.163 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 15.204.198.96 | -806.440 | -806.440 | -15.115 | 0.763 | 4.729 | 8.189 | 8.189 | 19.845 | 814.629 | 169.536 | -36.913 | ms | -4.304 | 19.54 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 15.204.87.223 | -36.284 | -8.344 | -5.158 | -1.169 | 2.341 | 163.102 | 164.832 | 7.498 | 171.447 | 20.085 | 0.950 | ms | 7.803 | 63.6 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 152.70.159.102 | -6.980 | -5.497 | -0.828 | 4.459 | 6.305 | 7.063 | 7.615 | 7.133 | 12.560 | 2.158 | 3.977 | ms | -2.312 | 10.07 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 158.51.134.123 | -10.744 | -0.727 | 2.796 | 5.537 | 7.546 | 9.931 | 15.474 | 4.750 | 10.658 | 1.791 | 5.449 | ms | -1.464 | 17.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 158.51.99.19 | -157.868 | -3.714 | 0.315 | 3.544 | 6.019 | 8.972 | 238.853 | 5.704 | 12.686 | 14.413 | 4.009 | ms | 11.84 | 228.2 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 162.159.200.1 | -9.293 | 0.540 | 3.446 | 5.735 | 8.150 | 9.709 | 14.000 | 4.704 | 9.169 | 1.683 | 5.771 | ms | -1.262 | 13.06 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 162.159.200.123 | -6.062 | -6.062 | -5.886 | -0.049 | 7.264 | 9.110 | 9.110 | 13.149 | 15.172 | 4.421 | 0.662 | ms | 0.1749 | 1.786 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 163.123.152.14 | 8.299 | 8.299 | 8.299 | 9.300 | 12.567 | 12.567 | 12.567 | 4.268 | 4.268 | 1.664 | 9.751 | ms | 0.9993 | 2.22 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 168.61.215.74 | -405.890 | -404.187 | -6.577 | 0.381 | 5.171 | 12.210 | 14.954 | 11.748 | 416.397 | 52.876 | -6.803 | ms | -7.353 | 55.33 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 170.187.147.56 | -0.641 | -0.241 | 1.518 | 4.094 | 6.492 | 7.541 | 8.261 | 4.974 | 7.782 | 1.471 | 4.099 | ms | -0.1755 | 3.293 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 172.233.157.223 | -4.047 | -4.047 | -4.047 | 3.553 | 5.955 | 5.955 | 5.955 | 10.002 | 10.002 | 3.165 | 2.404 | ms | -1.04 | 2.663 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 172.233.177.198 | -5.527 | -5.527 | -5.527 | 3.622 | 7.415 | 7.415 | 7.415 | 12.942 | 12.942 | 3.634 | 2.383 | ms | -0.9084 | 3.103 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 172.234.25.10 | 3.105 | 3.105 | 3.105 | 4.382 | 5.884 | 5.884 | 5.884 | 2.779 | 2.779 | 0.948 | 4.394 | ms | -0.02219 | 1.884 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 172.234.37.140 | -9.587 | -9.587 | -9.587 | 4.151 | 11.157 | 11.157 | 11.157 | 20.745 | 20.745 | 4.913 | 3.204 | ms | -0.9547 | 3.843 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 172.234.44.141 | -1.177 | -1.177 | -1.177 | 4.942 | 9.373 | 9.373 | 9.373 | 10.549 | 10.549 | 3.559 | 3.891 | ms | -0.2618 | 1.724 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 172.235.32.243 | 2.812 | 2.812 | 2.812 | 7.583 | 9.521 | 9.521 | 9.521 | 6.709 | 6.709 | 2.571 | 6.667 | ms | -0.3777 | 1.512 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 172.235.60.8 | 0.376 | 0.376 | 0.376 | 3.004 | 16.005 | 16.005 | 16.005 | 15.630 | 15.630 | 4.175 | 4.760 | ms | 1.627 | 4.998 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 172.98.15.13 | 11.306 | 11.306 | 11.306 | 16.540 | 17.265 | 17.265 | 17.265 | 5.959 | 5.959 | 2.760 | 14.156 | ms | 0.02368 | 1.037 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 173.230.154.254 | -28.157 | -28.157 | -28.157 | 4.886 | 11.041 | 11.041 | 11.041 | 39.197 | 39.197 | 13.119 | -0.101 | ms | -1.268 | 3.17 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 173.255.192.10 | -0.501 | -0.501 | -0.501 | 8.854 | 11.145 | 11.145 | 11.145 | 11.646 | 11.646 | 3.481 | 7.479 | ms | -1.158 | 3.37 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 173.255.255.133 | -3.792 | -2.842 | -0.056 | 3.924 | 6.553 | 465.031 | 470.949 | 6.609 | 467.873 | 54.595 | 10.371 | ms | 8.207 | 68.45 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 173.71.68.71 | -11.013 | -4.530 | -1.040 | 3.562 | 6.711 | 464.728 | 470.128 | 7.750 | 469.258 | 52.893 | 9.423 | ms | 8.484 | 73.13 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 173.73.96.68 | -18.437 | -0.510 | 1.981 | 4.646 | 6.731 | 10.129 | 13.198 | 4.750 | 10.640 | 1.878 | 4.544 | ms | -2.345 | 32.53 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 193.29.63.226 | -97.166 | -97.166 | -95.281 | 0.589 | 7.015 | 9.170 | 9.170 | 102.297 | 106.336 | 42.310 | -21.757 | ms | -1.137 | 2.322 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 198.137.202.32 | -1.462 | -1.396 | 1.619 | 5.827 | 7.932 | 11.548 | 12.433 | 6.313 | 12.944 | 1.882 | 5.599 | ms | -0.7187 | 6.807 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 198.199.14.19 | -4.168 | -4.168 | -4.168 | 3.527 | 9.207 | 9.207 | 9.207 | 13.374 | 13.374 | 3.647 | 3.201 | ms | -0.3311 | 2.34 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 198.211.103.209 | -15.435 | -15.435 | -7.248 | 1.023 | 11.374 | 11.645 | 11.645 | 18.622 | 27.080 | 5.487 | 1.111 | ms | -0.25 | 4.025 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 198.23.249.167 | 4.961 | 4.961 | 4.961 | 12.406 | 14.734 | 14.734 | 14.734 | 9.772 | 9.772 | 3.037 | 10.920 | ms | -0.6652 | 2.344 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 198.46.254.130 | -2.287 | 0.292 | 2.403 | 4.430 | 9.560 | 11.525 | 16.197 | 7.157 | 11.234 | 2.139 | 4.805 | ms | 1.192 | 5.984 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 198.60.22.240 | -144.129 | 0.237 | 8.087 | 11.026 | 13.035 | 16.771 | 294.299 | 4.948 | 16.534 | 23.436 | 11.946 | ms | 8.986 | 126.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 199.68.201.235 | 2.195 | 2.195 | 2.320 | 4.878 | 7.295 | 9.614 | 9.614 | 4.975 | 7.419 | 1.530 | 4.830 | ms | 1.056 | 5.383 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) | 0.214 | 2.406 | 3.442 | 5.288 | 7.200 | 7.864 | 9.487 | 3.758 | 5.458 | 1.200 | 5.303 | ms | -0.1227 | 3.446 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) | 0.989 | 0.989 | 0.989 | 6.668 | 7.419 | 7.419 | 7.419 | 6.430 | 6.430 | 2.339 | 5.470 | ms | -1.22 | 2.835 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:19f0:6401:400:5400:4ff:fec3:522a | -8.793 | -3.395 | -1.763 | 0.719 | 3.100 | 6.282 | 10.062 | 4.863 | 9.677 | 1.724 | 0.695 | ms | -0.118 | 8.702 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:418:3ff::53 (x.ns.gin.ntt.net) | 4.247 | 4.247 | 4.247 | 7.231 | 8.571 | 8.571 | 8.571 | 4.324 | 4.324 | 1.678 | 6.539 | ms | -0.2545 | 1.376 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:418:8405:4002::12 | -281.832 | -281.832 | -281.832 | 6.130 | 43.679 | 43.679 | 43.679 | 325.511 | 325.511 | 75.678 | -13.076 | ms | -3.151 | 11.39 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:418:8405:4002::3 | -0.825 | 1.964 | 3.144 | 5.203 | 8.084 | 23.850 | 24.486 | 4.940 | 21.886 | 3.270 | 5.666 | ms | 4.264 | 23.47 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) | -43.336 | -25.868 | -0.459 | 3.003 | 5.329 | 102.804 | 104.408 | 5.787 | 128.672 | 14.038 | 4.377 | ms | 5.842 | 42.8 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:470:1f07:24f::123 | 5.692 | 5.692 | 5.692 | 8.660 | 52.245 | 52.245 | 52.245 | 46.552 | 46.552 | 15.577 | 16.463 | ms | 1.347 | 3.154 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:470:1f07:d::5 (ns2.pads.ufrj.br) | -63.029 | -25.579 | -3.547 | 9.292 | 14.309 | 18.491 | 26.835 | 17.856 | 44.069 | 7.073 | 8.138 | ms | -3.936 | 26.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:470:1f2c:60:123:123:123:123 | -34.941 | -34.941 | -34.941 | 5.417 | 179.029 | 179.029 | 179.029 | 213.970 | 213.970 | 83.019 | 55.085 | ms | 0.6389 | 1.528 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:470:b:22d::123 | -4.739 | -4.739 | -4.577 | -2.037 | -0.635 | -0.179 | -0.179 | 3.943 | 4.560 | 1.286 | -2.350 | ms | -0.3618 | 2.047 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:470:e114::d6:12 (1.md.ntp.md) | -10.323 | -5.218 | -0.737 | 4.552 | 8.145 | 464.586 | 465.594 | 8.883 | 469.804 | 60.310 | 12.220 | ms | 7.342 | 55.02 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:470:e114::d6:c5 (t2.davehart.net) | 4.264 | 4.264 | 4.264 | 4.264 | 4.264 | 4.264 | 4.264 | 0.000 | 0.000 | 0.000 | 4.264 | ms | nan | nan | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:470:e8dc:10::123 | -0.028 | 0.001 | 0.004 | 0.006 | 0.009 | 0.011 | 589.091 | 0.005 | 0.010 | 20.006 | 0.687 | s | 29.38 | 864 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) | -809.971 | -4.133 | 0.925 | 5.173 | 7.699 | 8.851 | 11.403 | 6.774 | 12.984 | 41.024 | 2.773 | ms | -19.54 | 384.4 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com) | -0.195 | -0.167 | 1.359 | 3.625 | 5.714 | 8.822 | 8.875 | 4.355 | 8.989 | 1.443 | 3.675 | ms | 0.4961 | 4.819 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) | -157.180 | 0.965 | 3.243 | 5.473 | 7.719 | 9.995 | 23.242 | 4.475 | 9.030 | 5.538 | 5.305 | ms | -26.07 | 749.2 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:558:6014:17:8dc5:5575:5560:2cb6 | -281.200 | -281.200 | -126.154 | 4.670 | 171.115 | 172.773 | 172.773 | 297.269 | 453.972 | 76.160 | 7.959 | ms | -0.5863 | 8.15 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:559:2be:3::1001 | -175.433 | -175.433 | -170.364 | 6.118 | 11.772 | 14.071 | 14.071 | 182.136 | 189.504 | 60.406 | -18.925 | ms | -2.06 | 5.416 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2001:678:8::123 (any.time.nl) | -6.894 | -6.894 | -6.894 | 1.568 | 214.705 | 214.705 | 214.705 | 221.599 | 221.599 | 95.535 | 59.773 | ms | 0.9473 | 1.903 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 204.10.18.144 | 9.179 | 9.179 | 9.179 | 11.384 | 12.007 | 12.007 | 12.007 | 2.829 | 2.829 | 1.213 | 10.857 | ms | -0.5696 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 204.197.163.71 | -173.244 | -1.861 | 0.406 | 2.637 | 4.342 | 5.127 | 14.383 | 3.936 | 6.988 | 8.636 | 2.114 | ms | -19.71 | 398.6 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 204.2.134.162 | 3.726 | 3.726 | 3.726 | 9.487 | 10.513 | 10.513 | 10.513 | 6.787 | 6.787 | 2.284 | 8.433 | ms | -0.8439 | 2.293 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 205.233.73.201 | -29.812 | -29.812 | -18.984 | 8.160 | 221.194 | 221.908 | 221.908 | 240.177 | 251.721 | 109.553 | 72.756 | ms | 0.5569 | 1.346 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 208.113.130.146 | -807.971 | -2.044 | 0.597 | 5.657 | 8.325 | 10.241 | 17.688 | 7.728 | 12.286 | 41.081 | 3.296 | ms | -19.56 | 384.7 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 208.67.72.43 | -45.246 | -45.246 | -45.246 | -2.385 | 1.915 | 1.915 | 1.915 | 47.161 | 47.161 | 14.659 | -6.938 | ms | -2.157 | 5.869 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 208.67.72.50 | -411.370 | -407.370 | -12.259 | -1.276 | 14.804 | 461.290 | 467.446 | 27.063 | 868.660 | 105.580 | 8.636 | ms | 1.618 | 16.62 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 208.67.75.242 | -4.622 | -0.573 | 1.079 | 4.378 | 7.071 | 10.826 | 240.553 | 5.992 | 11.398 | 17.431 | 5.561 | ms | 13.06 | 173.8 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 212.227.240.160 | 0.447 | 1.367 | 2.617 | 5.039 | 7.008 | 11.813 | 14.498 | 4.391 | 10.446 | 1.596 | 5.037 | ms | 1.279 | 9.832 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 216.229.4.66 | -5.209 | -5.209 | -5.209 | 4.542 | 13.961 | 13.961 | 13.961 | 19.169 | 19.169 | 4.570 | 4.299 | ms | 0.05583 | 2.76 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 216.229.4.69 | -565.822 | -565.822 | -561.261 | 0.035 | 3.427 | 7.531 | 7.531 | 564.688 | 573.353 | 217.192 | -101.392 | ms | -1.65 | 3.722 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 216.240.36.24 | -5.803 | -5.803 | -2.568 | 1.026 | 7.930 | 10.160 | 10.160 | 10.498 | 15.963 | 3.307 | 1.221 | ms | 0.7489 | 4.49 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 216.31.17.12 | -13.524 | -13.524 | -13.524 | 1.518 | 6.326 | 6.326 | 6.326 | 19.850 | 19.850 | 5.541 | -1.109 | ms | -0.9513 | 3.269 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.111.186.186 | 0.800 | 0.800 | 0.800 | 2.292 | 3.617 | 3.617 | 3.617 | 2.817 | 2.817 | 0.849 | 2.280 | ms | -0.2598 | 2.078 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.131.160.7 | -14.783 | 1.244 | 2.750 | 5.398 | 7.474 | 8.521 | 12.984 | 4.724 | 7.277 | 1.521 | 5.330 | ms | -1.272 | 16.38 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.141.40.123 | 27.455 | 27.455 | 27.455 | 33.456 | 37.132 | 37.132 | 37.132 | 9.678 | 9.678 | 2.992 | 32.642 | ms | -0.3048 | 2.39 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.142.248.8 | 8.594 | 8.594 | 8.594 | 10.977 | 11.802 | 11.802 | 11.802 | 3.207 | 3.207 | 1.009 | 10.550 | ms | -0.8827 | 2.771 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.142.248.9 | -0.177 | -0.177 | -0.177 | 2.494 | 8.498 | 8.498 | 8.498 | 8.675 | 8.675 | 2.694 | 2.971 | ms | 0.6979 | 2.389 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.143.196.199 | 2.248 | 2.248 | 2.248 | 3.906 | 5.387 | 5.387 | 5.387 | 3.139 | 3.139 | 1.032 | 4.058 | ms | -0.2914 | 2.021 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.150.41.122 | -0.013 | -0.013 | 1.940 | 4.590 | 6.567 | 10.828 | 10.828 | 4.627 | 10.841 | 1.746 | 4.571 | ms | 0.5098 | 5.973 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.150.41.123 | -13.071 | -0.293 | 5.503 | 8.553 | 11.685 | 15.470 | 291.773 | 6.182 | 15.763 | 17.232 | 9.542 | ms | 15.97 | 260.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.155.40.38 | -288.208 | -156.059 | -4.815 | 1.534 | 4.285 | 10.104 | 18.366 | 9.100 | 166.163 | 22.289 | -1.539 | ms | -9.379 | 102 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.157.160.168 | -2.076 | -0.290 | 1.682 | 4.081 | 9.612 | 13.302 | 15.548 | 7.929 | 13.592 | 2.390 | 4.490 | ms | 1.867 | 8.727 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.168.136.132 | -37.613 | -37.613 | -37.613 | 5.175 | 9.499 | 9.499 | 9.499 | 47.112 | 47.112 | 13.628 | -0.158 | ms | -2.166 | 6.233 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.168.24.210 | 7.914 | 7.914 | 7.914 | 12.589 | 13.467 | 13.467 | 13.467 | 5.553 | 5.553 | 2.207 | 10.952 | ms | -0.2124 | 1.412 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.1 | -3.842 | -3.842 | -3.842 | 2.397 | 8.346 | 8.346 | 8.346 | 12.188 | 12.188 | 4.121 | 2.680 | ms | -0.2252 | 2.014 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.123 | -3.755 | -1.507 | 0.222 | 2.615 | 4.450 | 5.651 | 13.437 | 4.228 | 7.158 | 1.430 | 2.525 | ms | -0.02099 | 7.779 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.126 | -5.345 | -3.200 | -1.287 | 1.767 | 4.438 | 5.722 | 166.185 | 5.726 | 8.922 | 10.343 | 2.300 | ms | 15.19 | 239 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.127 | 2.017 | 2.017 | 2.017 | 5.113 | 8.863 | 8.863 | 8.863 | 6.846 | 6.846 | 2.456 | 5.105 | ms | 0.3935 | 1.998 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.128 | -571.345 | -2.646 | 0.616 | 3.786 | 5.861 | 6.834 | 11.189 | 5.245 | 9.479 | 32.846 | 1.503 | ms | -16.49 | 282.6 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.129 | -5.851 | -1.947 | -0.334 | 2.997 | 5.760 | 6.949 | 10.375 | 6.094 | 8.896 | 1.869 | 2.897 | ms | -0.2443 | 4.135 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.130 | -4.461 | -4.461 | -4.284 | 0.164 | 5.449 | 7.796 | 7.796 | 9.733 | 12.257 | 3.707 | 0.733 | ms | 0.06193 | 1.677 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.131 | -4.751 | -0.429 | 1.142 | 3.700 | 5.655 | 6.700 | 10.070 | 4.513 | 7.129 | 1.408 | 3.624 | ms | -0.5634 | 5.686 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.132 | -6.108 | -0.734 | 0.944 | 3.623 | 5.856 | 7.065 | 9.350 | 4.912 | 7.799 | 1.547 | 3.559 | ms | -0.388 | 4.285 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.186.168.3 | -11.209 | -6.287 | -3.243 | -0.938 | 9.206 | 10.476 | 11.413 | 12.449 | 16.763 | 3.379 | -0.171 | ms | 1.792 | 6.524 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.94.221.138 | 8.003 | 8.003 | 8.003 | 11.978 | 13.637 | 13.637 | 13.637 | 5.634 | 5.634 | 1.789 | 11.308 | ms | -0.8786 | 2.486 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 23.95.49.216 | -5.139 | -2.109 | 0.660 | 3.522 | 5.991 | 7.369 | 10.716 | 5.332 | 9.478 | 1.730 | 3.430 | ms | -0.7082 | 6.455 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 240b:4002:100:9f00:5bd1:9512:8a8b:25e | 1.797 | 1.797 | 1.797 | 4.344 | 8.047 | 8.047 | 8.047 | 6.249 | 6.249 | 2.182 | 4.694 | ms | 0.2446 | 1.809 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 240b:4004:108:200:8314:1a08:4cee:26d6 | -53.252 | -30.228 | -3.522 | 4.633 | 7.430 | 9.190 | 16.676 | 10.952 | 39.418 | 6.135 | 3.553 | ms | -4.789 | 30.29 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 240b:4004:108:200:8314:1a08:4cee:26d9 | 3.332 | 3.332 | 3.332 | 5.399 | 14.354 | 14.354 | 14.354 | 11.022 | 11.022 | 4.410 | 6.823 | ms | 1.061 | 2.259 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1700:3d24:740f:9524:529a:6489:d48f | 8.238 | 8.238 | 9.877 | 14.429 | 17.946 | 17.946 | 17.946 | 8.069 | 9.708 | 2.359 | 13.755 | ms | -0.5972 | 2.747 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1700:5455:a70::7b:1 | -809.818 | -809.818 | -802.944 | -1.720 | 6.474 | 21.994 | 21.994 | 809.418 | 831.812 | 176.723 | -42.075 | ms | -4.096 | 17.79 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 | -16.983 | -16.983 | 2.347 | 14.361 | 471.310 | 472.188 | 472.188 | 468.963 | 489.171 | 193.989 | 112.827 | ms | 1.297 | 2.69 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1700:5a0f:ee00::314:1b | -0.511 | 1.698 | 6.788 | 11.589 | 16.910 | 21.438 | 25.234 | 10.122 | 19.741 | 3.117 | 11.826 | ms | 0.01519 | 6.247 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1700:5a0f:ee00::314:2b | 0.372 | 0.372 | 0.372 | 12.636 | 16.769 | 16.769 | 16.769 | 16.398 | 16.398 | 3.764 | 12.100 | ms | -1.682 | 6.304 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1702:7400:9ac0::314:5a | 0.498 | 0.498 | 0.498 | 13.966 | 17.731 | 17.731 | 17.731 | 17.233 | 17.233 | 5.163 | 12.245 | ms | -1.274 | 3.293 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1702:7400:9ac0::5b | 0.162 | 0.162 | 0.162 | 8.450 | 11.368 | 11.368 | 11.368 | 11.206 | 11.206 | 3.725 | 6.660 | ms | -0.2939 | 1.735 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1f13:2c1:2e00::be00:5 | -282.490 | -1.401 | 3.361 | 6.350 | 9.277 | 21.057 | 75.600 | 5.916 | 22.458 | 11.306 | 6.295 | ms | -17.94 | 473.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) | -155.691 | -5.511 | -3.335 | 3.558 | 6.419 | 8.309 | 110.743 | 9.755 | 13.821 | 4.172 | 2.779 | ms | -7.728 | 503.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) | -159.116 | -6.028 | -1.808 | 3.899 | 6.770 | 8.633 | 99.329 | 8.578 | 14.661 | 4.630 | 3.294 | ms | -16.25 | 578.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) | -158.177 | -23.179 | -3.286 | 4.342 | 7.565 | 10.215 | 125.029 | 10.851 | 33.394 | 6.337 | 3.153 | ms | -6.944 | 182.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:2600::99 (ntp1.wiktel.com) | 10.504 | 10.504 | 10.504 | 11.340 | 11.340 | 11.340 | 11.340 | 0.836 | 0.836 | 0.418 | 10.922 | ms | -6.279e-15 | 1 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c00::f03c:91ff:fe05:b640 (dev.smatwebdesign.com) | 10.745 | 10.745 | 10.745 | 10.745 | 10.745 | 10.745 | 10.745 | 0.000 | 0.000 | 0.000 | 10.745 | ms | nan | nan | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) | -7.895 | -0.183 | 1.291 | 4.437 | 7.174 | 9.401 | 23.862 | 5.883 | 9.584 | 1.951 | 4.342 | ms | 0.3005 | 6.816 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c00:e000:318::1 (jane.qotw.net) | -28.246 | -0.004 | 1.379 | 3.315 | 5.169 | 6.398 | 10.314 | 3.789 | 6.402 | 1.515 | 3.268 | ms | -6.661 | 141.7 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) | 2.725 | 2.725 | 2.725 | 5.114 | 14.625 | 14.625 | 14.625 | 11.900 | 11.900 | 4.070 | 5.808 | ms | 1.545 | 3.777 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c01:e000:7e6::123 (time1.sigi.net) | -170.467 | 0.374 | 3.399 | 5.684 | 7.901 | 8.850 | 11.725 | 4.503 | 8.476 | 9.664 | 5.114 | ms | -17.67 | 320.7 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c02::f03c:92ff:fe96:dc0 | -21.719 | -4.622 | -0.261 | 6.280 | 12.408 | 13.569 | 18.625 | 12.669 | 18.191 | 3.801 | 6.313 | ms | -1.28 | 11.52 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c02::f03c:94ff:fe59:f411 | 3.748 | 3.748 | 3.748 | 6.064 | 12.748 | 12.748 | 12.748 | 9.000 | 9.000 | 3.879 | 7.163 | ms | 0.6006 | 1.484 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net) | -1.758 | 0.272 | 2.422 | 5.290 | 7.506 | 11.065 | 14.186 | 5.084 | 10.793 | 1.733 | 5.279 | ms | 0.2754 | 6.817 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) | 0.867 | 0.867 | 1.114 | 3.790 | 6.386 | 7.915 | 7.915 | 5.272 | 7.048 | 1.512 | 3.637 | ms | 0.418 | 3.502 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) | -572.795 | -572.795 | -572.795 | -9.263 | 4.262 | 4.262 | 4.262 | 577.057 | 577.057 | 280.556 | -253.542 | ms | -0.2234 | 1.051 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) | -11.563 | -4.087 | -0.894 | 6.068 | 13.355 | 21.391 | 26.413 | 14.249 | 25.478 | 4.903 | 6.241 | ms | 0.36 | 5.024 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c03::f03c:94ff:fe59:d3de | 2.854 | 2.854 | 2.854 | 2.958 | 4.537 | 4.537 | 4.537 | 1.683 | 1.683 | 0.770 | 3.449 | ms | 0.6976 | 1.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c03:e002:1300::10 (ntp.electronmill.com) | -3.742 | -3.742 | -3.742 | 3.270 | 6.177 | 6.177 | 6.177 | 9.919 | 9.919 | 3.310 | 1.757 | ms | -0.3528 | 1.728 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c06::f03c:94ff:fee2:9c28 | 5.742 | 5.742 | 5.742 | 7.946 | 15.389 | 15.389 | 15.389 | 9.646 | 9.646 | 3.904 | 8.785 | ms | 1.004 | 2.198 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:3c06::f03c:94ff:fee2:c53a | 7.934 | 7.934 | 7.934 | 10.652 | 34.769 | 34.769 | 34.769 | 26.835 | 26.835 | 12.061 | 17.785 | ms | 0.6803 | 1.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:4040:3037:e600::1 | 2.842 | 2.842 | 2.842 | 6.051 | 6.051 | 6.051 | 6.051 | 3.209 | 3.209 | 1.605 | 4.447 | ms | -8.009e-16 | 1 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2600:4040:e0da:f000::cbb9:201a | -99.353 | -99.353 | -97.880 | 3.306 | 8.180 | 46.292 | 46.292 | 106.060 | 145.645 | 34.906 | -8.837 | ms | -1.974 | 5.486 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2601:18a:8081:3600:a923:2e66:e3d2:8c95 | -2.328 | -2.328 | -2.328 | 8.140 | 10.732 | 10.732 | 10.732 | 13.060 | 13.060 | 4.378 | 6.247 | ms | -0.9586 | 2.744 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:291:69::8 (time2.tritan-bb.net) | -87.855 | -87.855 | -87.855 | -86.413 | -85.482 | -85.482 | -85.482 | 2.373 | 2.373 | 0.712 | -86.511 | ms | -0.5905 | 2.861 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:291:69::9 (time.tritan-bb.net) | -570.253 | -570.253 | -566.451 | 6.098 | 295.584 | 297.286 | 297.286 | 862.034 | 867.538 | 189.440 | -9.823 | ms | -1.679 | 6.932 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) | -158.684 | -3.707 | -0.110 | 2.070 | 4.337 | 8.146 | 25.990 | 4.448 | 11.853 | 7.539 | 1.731 | ms | -18.9 | 391.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net) | 7.226 | 7.226 | 7.226 | 8.619 | 9.227 | 9.227 | 9.227 | 2.002 | 2.002 | 0.838 | 8.357 | ms | -0.4377 | 1.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:2eb:2:95:1234:5678:9abc:def0 | -177.116 | -4.361 | -1.059 | 2.594 | 6.566 | 8.773 | 240.974 | 7.624 | 13.133 | 11.661 | 2.870 | ms | 12.1 | 337.6 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:80b:5000::36 (time.meme.holdings) | -26.339 | -9.392 | 1.266 | 5.949 | 9.817 | 23.455 | 24.890 | 8.551 | 32.847 | 4.707 | 5.688 | ms | -2.123 | 23.68 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) | -2.396 | -2.396 | -2.396 | 0.924 | 11.083 | 11.083 | 11.083 | 13.479 | 13.479 | 4.287 | 2.602 | ms | 0.7321 | 2.194 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) | -412.469 | -410.991 | -8.504 | 2.281 | 14.386 | 25.256 | 77.682 | 22.890 | 436.248 | 59.543 | -5.197 | ms | -6.469 | 44.15 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:f9bd:80:100::a (time.circlevps.net) | -64.334 | -0.054 | 2.880 | 5.079 | 7.169 | 10.479 | 288.638 | 4.288 | 10.533 | 17.604 | 5.956 | ms | 15.32 | 246.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:fc2f:100:9800::dead:beef | -48.947 | -0.453 | 3.020 | 6.675 | 10.815 | 15.794 | 240.110 | 7.795 | 16.247 | 16.385 | 7.836 | ms | 13.11 | 183.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) | -2.937 | -2.937 | -2.937 | 3.954 | 9.493 | 9.493 | 9.493 | 12.430 | 12.430 | 3.348 | 4.033 | ms | -0.4303 | 3.037 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:fe2e:3:d:f9:c7ff:fef5:379c | 3.035 | 3.035 | 3.035 | 6.211 | 8.657 | 8.657 | 8.657 | 5.622 | 5.622 | 1.762 | 5.927 | ms | -0.1747 | 2.107 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:feda:30:ae86:2fc:98ff:fecf:fe94 | -8.543 | -4.131 | 0.620 | 3.457 | 5.982 | 7.057 | 10.590 | 5.362 | 11.188 | 1.910 | 3.332 | ms | -1.439 | 10.13 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:ff06:725:100::123 (oldtime2.sigi.net) | -8.456 | 0.658 | 2.953 | 4.980 | 7.081 | 8.916 | 11.994 | 4.128 | 8.258 | 1.545 | 5.012 | ms | -1.787 | 18.35 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2602:ff23:50:3c2::1 (dns-e.ns4v.icu) | -414.428 | -412.103 | -11.870 | 2.663 | 20.110 | 279.792 | 280.771 | 31.980 | 691.895 | 70.162 | 0.900 | ms | -2.687 | 27.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:0:8369:0:ba11:ba11:ba11 | -422.469 | -422.469 | -419.944 | -5.879 | 4.024 | 4.850 | 4.850 | 423.968 | 427.319 | 143.126 | -63.235 | ms | -2.082 | 5.347 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:0:8369:1111:1111:1111:1112 | -55.331 | -55.331 | -24.536 | -3.892 | 276.097 | 276.136 | 276.136 | 300.633 | 331.467 | 96.209 | 43.048 | ms | 1.624 | 4.338 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:0:8369:607:e532:d534:7109 | -20.164 | -20.164 | -20.164 | -5.038 | -0.723 | -0.723 | -0.723 | 19.441 | 19.441 | 5.152 | -6.685 | ms | -1.218 | 3.706 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:0:8369::bad:babe | -16.649 | -16.649 | -12.050 | -3.794 | 3.680 | 3.680 | 3.680 | 15.730 | 20.329 | 5.040 | -4.943 | ms | -0.3208 | 2.65 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:0:8369::bad:beef | -10.534 | -10.534 | -10.534 | -4.440 | -0.095 | -0.095 | -0.095 | 10.439 | 10.439 | 2.730 | -5.174 | ms | -0.1283 | 2.373 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:0:8369::f00d:feed | -17.667 | -17.667 | -15.791 | -5.100 | 453.988 | 458.206 | 458.206 | 469.779 | 475.874 | 188.222 | 87.341 | ms | 1.435 | 3.061 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:0:8369::feeb:dab | -19.462 | -19.462 | -14.510 | -5.358 | 453.345 | 453.880 | 453.880 | 467.855 | 473.342 | 152.281 | 49.860 | ms | 2.262 | 6.129 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:0:8369:feed:feed:feed:feed | -18.686 | -18.686 | -18.686 | -5.363 | -1.212 | -1.212 | -1.212 | 17.474 | 17.474 | 4.007 | -6.304 | ms | -1.91 | 6.79 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:400e:ea00:ccfe:ba34:7215:d4f6 | -3.394 | 0.533 | 3.024 | 5.787 | 9.133 | 10.071 | 10.972 | 6.109 | 9.538 | 1.912 | 5.800 | ms | -0.3737 | 4.794 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:6:b900:6b54:1390:4afd:814a | -420.366 | -420.366 | -420.366 | -15.121 | 2.174 | 2.174 | 2.174 | 422.540 | 422.540 | 183.604 | -122.964 | ms | -0.9887 | 1.983 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c020:6:b900:ed2f:b442:fee7:d9b9 | -9.081 | -9.081 | -9.081 | -3.889 | -1.558 | -1.558 | -1.558 | 7.523 | 7.523 | 2.325 | -4.454 | ms | -0.9557 | 3.036 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c024:c005:a600:8eb1:2863:5838:9880 | 6.649 | 6.649 | 6.649 | 6.649 | 6.649 | 6.649 | 6.649 | 0.000 | 0.000 | 0.000 | 6.649 | ms | nan | nan | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2603:c024:c005:a600:efb6:d213:cad8:251d | 1.713 | 1.713 | 1.713 | 11.865 | 68.213 | 68.213 | 68.213 | 66.499 | 66.499 | 21.793 | 19.547 | ms | 1.448 | 3.682 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:180:f3::4a4 (dutch.arpnet.net) | 13.327 | 13.327 | 13.327 | 16.038 | 19.997 | 19.997 | 19.997 | 6.670 | 6.670 | 2.064 | 16.117 | ms | 0.6723 | 2.663 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 | 4.360 | 4.360 | 7.868 | 9.469 | 13.253 | 17.815 | 17.815 | 5.385 | 13.455 | 2.164 | 9.765 | ms | 1.273 | 7.496 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:2dc0:100:4d6:: | 6.451 | 6.451 | 6.451 | 7.846 | 12.197 | 12.197 | 12.197 | 5.746 | 5.746 | 2.175 | 8.548 | ms | 0.9328 | 2.204 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) | 1.015 | 4.439 | 6.129 | 8.198 | 10.741 | 12.700 | 28.542 | 4.612 | 8.261 | 1.536 | 8.275 | ms | 1.156 | 15.73 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:2dc0:202:300::140d (ovh.maxhost.io) | -10.884 | -6.103 | -4.364 | -1.787 | 0.663 | 2.038 | 13.335 | 5.027 | 8.141 | 1.665 | -1.837 | ms | 0.09333 | 10.2 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) | -49.930 | -36.749 | -6.555 | 2.041 | 5.114 | 6.502 | 22.290 | 11.670 | 43.251 | 5.807 | 0.770 | ms | -4.61 | 31.25 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:4300:a:299::164 | -9.675 | -9.675 | -6.261 | -0.158 | 3.067 | 3.865 | 3.865 | 9.328 | 13.539 | 3.536 | -1.195 | ms | -0.6405 | 2.55 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) | -802.674 | -802.674 | -802.674 | 2.272 | 9.840 | 9.840 | 9.840 | 812.514 | 812.514 | 371.058 | -243.393 | ms | -0.8332 | 1.694 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) | 4.759 | 4.759 | 4.759 | 5.795 | 36.164 | 36.164 | 36.164 | 31.405 | 31.405 | 14.567 | 15.573 | ms | 0.7044 | 1.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) | -97.614 | -97.614 | -97.614 | -96.252 | -95.198 | -95.198 | -95.198 | 2.416 | 2.416 | 0.727 | -96.393 | ms | -0.05135 | 2.552 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) | -40.303 | -1.773 | 0.146 | 2.726 | 5.501 | 103.648 | 104.341 | 5.355 | 105.421 | 14.429 | 4.427 | ms | 6.057 | 42.23 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) | -6.372 | -6.372 | -3.109 | 11.458 | 218.960 | 218.960 | 218.960 | 222.069 | 225.332 | 83.767 | 47.473 | ms | 1.451 | 3.181 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2604:a880:800:a1::ec9:5001 | -127.479 | -127.479 | -5.442 | 6.181 | 17.508 | 17.508 | 17.508 | 22.949 | 144.987 | 29.551 | -0.176 | ms | -3.971 | 17.23 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2605:4840:3:fb19::1 (chi3.us.ntp.li) | -278.261 | -8.779 | -1.179 | 2.716 | 7.022 | 29.833 | 89.152 | 8.201 | 38.612 | 10.597 | 2.909 | ms | -14.92 | 445.8 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2605:6400:488d:2eda:eee9:fe8d:4543:d471 | 6.277 | 6.277 | 6.277 | 10.872 | 10.872 | 10.872 | 10.872 | 4.595 | 4.595 | 2.297 | 8.574 | ms | -5.457e-16 | 1 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2605:6400:488d:3686:546d:c03c:1689:20c | 0.063 | 0.063 | 0.063 | 10.815 | 77.942 | 77.942 | 77.942 | 77.879 | 77.879 | 31.733 | 28.904 | ms | 0.6938 | 1.564 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2605:6400:84e1::123 (oldtime3.sigi.net) | -12.468 | -0.445 | 2.966 | 5.204 | 7.923 | 15.345 | 240.273 | 4.957 | 15.790 | 21.764 | 7.308 | ms | 10.33 | 108.7 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) | -1.370 | -1.370 | -1.370 | 3.697 | 9.921 | 9.921 | 9.921 | 11.292 | 11.292 | 2.854 | 4.172 | ms | 0.1428 | 3.178 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2606:4700:f1::1 (time.cloudflare.com) | -170.499 | -2.387 | 1.875 | 5.798 | 8.576 | 10.646 | 290.015 | 6.701 | 13.032 | 6.047 | 5.706 | ms | 25.59 | 1216 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2606:4700:f1::123 (time.cloudflare.com) | -810.498 | -1.710 | 1.692 | 5.712 | 8.542 | 10.936 | 468.641 | 6.850 | 12.646 | 18.089 | 5.451 | ms | -22.5 | 1230 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2606:82c0:21::e (time1.lshiy.com) | -0.038 | -0.038 | -0.038 | 3.161 | 6.774 | 6.774 | 6.774 | 6.812 | 6.812 | 2.191 | 3.162 | ms | 0.2345 | 1.83 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2606:82c0:22::e (time2.lshiy.com) | -105.777 | -105.777 | -105.777 | 5.198 | 20.159 | 20.159 | 20.159 | 125.937 | 125.937 | 51.276 | -28.296 | ms | -0.6878 | 1.513 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2606:82c0:23::e (time3.lshiy.com) | 5.344 | 5.344 | 5.344 | 9.330 | 14.292 | 14.292 | 14.292 | 8.948 | 8.948 | 2.315 | 9.378 | ms | 0.5098 | 2.778 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2606:8fc0::9 (farmhand.gac.edu) | -11.058 | 0.976 | 2.338 | 4.612 | 7.297 | 8.866 | 10.402 | 4.959 | 7.890 | 1.640 | 4.640 | ms | -1.936 | 22.88 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:5600:182:500::1 (ntp-1.jonlight.com) | -568.165 | -568.165 | -568.165 | -0.446 | 11.465 | 11.465 | 11.465 | 579.631 | 579.631 | 265.791 | -190.495 | ms | -0.701 | 1.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:7c80:54:3::32 | -3.794 | 0.787 | 2.562 | 4.809 | 7.594 | 10.557 | 88.040 | 5.032 | 9.770 | 2.850 | 4.977 | ms | 17.49 | 477.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:7c80:54:3::56 (owners.kjsl.com) | -806.909 | -806.909 | -5.703 | 0.187 | 5.818 | 9.156 | 9.156 | 11.521 | 816.065 | 173.398 | -38.752 | ms | -4.188 | 18.54 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:9000:7000:23:216:3cff:fe25:38d7 | -3.352 | -0.375 | 0.741 | 4.354 | 8.207 | 9.388 | 11.040 | 7.466 | 9.763 | 2.317 | 4.364 | ms | -0.006342 | 2.996 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:9d00:2000:16::9269:208a | 3.459 | 3.459 | 3.459 | 6.758 | 17.615 | 17.615 | 17.615 | 14.156 | 14.156 | 4.848 | 8.704 | ms | 0.9497 | 2.577 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:b500:410:7700::1 | -559.793 | -559.793 | -555.696 | 15.880 | 247.041 | 247.131 | 247.131 | 802.737 | 806.924 | 201.270 | 7.227 | ms | -1.662 | 5.994 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f014:9e00::1 | -0.782 | -0.782 | -0.782 | 3.789 | 12.363 | 12.363 | 12.363 | 13.145 | 13.145 | 4.161 | 4.437 | ms | 0.4965 | 2.056 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f014:9e00::2 | -2.137 | -2.137 | 0.533 | 8.769 | 175.012 | 176.141 | 176.141 | 174.479 | 178.278 | 60.511 | 32.888 | ms | 1.871 | 4.578 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f047:8400::1 (xmpp.party) | 0.817 | 0.817 | 0.817 | 2.977 | 10.973 | 10.973 | 10.973 | 10.156 | 10.156 | 4.368 | 4.922 | ms | 0.5796 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f04e:fd00::1 | -0.324 | -0.324 | -0.324 | 4.901 | 12.270 | 12.270 | 12.270 | 12.594 | 12.594 | 3.373 | 4.498 | ms | 0.7124 | 3.491 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) | -64.809 | -64.809 | -64.809 | -61.044 | -58.237 | -58.237 | -58.237 | 6.572 | 6.572 | 2.268 | -61.730 | ms | -0.02717 | 1.823 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) | 2.778 | 2.778 | 2.778 | 7.838 | 13.194 | 13.194 | 13.194 | 10.416 | 10.416 | 3.298 | 7.750 | ms | 0.1317 | 1.92 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at) | 10.032 | 10.032 | 10.032 | 11.425 | 11.681 | 11.681 | 11.681 | 1.649 | 1.649 | 0.725 | 11.046 | ms | -0.6413 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) | -54.918 | -54.918 | -15.203 | 8.457 | 29.615 | 29.615 | 29.615 | 44.818 | 84.533 | 17.098 | 5.713 | ms | -2.027 | 8.409 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) | -2.373 | -2.373 | -1.407 | 3.297 | 10.246 | 11.084 | 11.084 | 11.653 | 13.458 | 3.531 | 3.807 | ms | 0.3808 | 2.37 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f06d:f200::1 | 4.821 | 4.821 | 4.821 | 6.467 | 10.874 | 10.874 | 10.874 | 6.053 | 6.053 | 2.364 | 6.907 | ms | 0.9511 | 2.168 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f1c0:f075:9900::1 | 1.361 | 1.361 | 1.361 | 9.304 | 14.348 | 14.348 | 14.348 | 12.987 | 12.987 | 4.266 | 7.460 | ms | 0.02239 | 1.598 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f298:5:101d:f816:3eff:fefd:8817 | -174.467 | -174.467 | -172.715 | 3.910 | 20.484 | 20.484 | 20.484 | 193.199 | 194.951 | 64.078 | -20.926 | ms | -1.945 | 4.813 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f3c8:3803:1::6 | -6.026 | -6.026 | -6.026 | 2.471 | 214.987 | 214.987 | 214.987 | 221.013 | 221.013 | 95.937 | 61.079 | ms | 0.9476 | 1.902 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) | -23.263 | -23.263 | -23.263 | -10.419 | 26.993 | 26.993 | 26.993 | 50.256 | 50.256 | 13.527 | -6.124 | ms | 0.7442 | 2.94 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) | 6.293 | 6.293 | 6.293 | 9.644 | 16.365 | 16.365 | 16.365 | 10.072 | 10.072 | 2.800 | 10.002 | ms | 0.8431 | 3.217 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:f710:35::29c:0:8 | -3.482 | -1.256 | 1.976 | 4.319 | 6.532 | 9.029 | 12.497 | 4.556 | 10.285 | 1.590 | 4.260 | ms | -0.3604 | 7.445 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) | -158.123 | -147.850 | 2.263 | 4.616 | 6.829 | 9.746 | 12.552 | 4.567 | 157.597 | 16.136 | 3.032 | ms | -9.47 | 91.61 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:ff50:0:1a::20 (ntpool1.603.newcontinuum.net) | -14.580 | -1.076 | 2.585 | 5.159 | 7.783 | 10.675 | 20.139 | 5.198 | 11.751 | 2.118 | 5.115 | ms | -1.077 | 26.82 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com) | 4.183 | 4.183 | 4.183 | 8.895 | 11.415 | 11.415 | 11.415 | 7.232 | 7.232 | 2.452 | 8.699 | ms | -0.9315 | 2.629 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com) | -1.149 | 2.215 | 3.649 | 5.831 | 7.768 | 8.933 | 13.205 | 4.119 | 6.718 | 1.345 | 5.804 | ms | -0.08604 | 5.422 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com) | -0.204 | 1.225 | 2.738 | 5.129 | 7.083 | 8.347 | 13.313 | 4.345 | 7.123 | 1.394 | 5.057 | ms | 0.1497 | 5.842 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:6:2000:104::48 (excalibur.prolixium.com) | 2.517 | 2.517 | 3.243 | 6.638 | 12.412 | 13.371 | 13.371 | 9.170 | 10.854 | 2.456 | 6.987 | ms | 0.675 | 3.466 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:83:8000:140::b (tic.lbl.gov) | -64.202 | -16.454 | -0.037 | 2.751 | 5.105 | 7.089 | 169.920 | 5.142 | 23.543 | 8.350 | 2.692 | ms | 14.74 | 314 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:83:8000:140::c (toc.lbl.gov) | -8.902 | -3.197 | 0.915 | 6.115 | 12.932 | 16.845 | 18.523 | 12.018 | 20.042 | 3.819 | 6.351 | ms | 0.131 | 4.597 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:8d:c000::f (blotch.image1tech.net) | -12.501 | -12.501 | -12.501 | 0.670 | 15.127 | 15.127 | 15.127 | 27.628 | 27.628 | 9.564 | -0.984 | ms | 0.2932 | 2 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) | -7.979 | -7.979 | -7.979 | -0.845 | 213.035 | 213.035 | 213.035 | 221.015 | 221.015 | 98.515 | 62.052 | ms | 0.8326 | 1.697 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:b0:2000:102::1:123 (time-h.den.codehof.net) | -107.407 | -107.407 | -107.407 | -66.747 | 92.475 | 92.475 | 92.475 | 199.883 | 199.883 | 57.820 | -44.390 | ms | 1.21 | 3.478 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2620:b0:2000:102::2:123 (time-he.den.codehof.net) | -44.889 | -44.889 | -44.889 | 22.240 | 34.334 | 34.334 | 34.334 | 79.222 | 79.222 | 22.949 | 14.406 | ms | -2.048 | 5.652 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) | -810.640 | -40.702 | -15.277 | 4.110 | 9.383 | 13.664 | 465.738 | 24.660 | 54.366 | 16.541 | 1.332 | ms | -14.29 | 855.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) | -178.311 | -43.668 | -16.808 | 2.946 | 8.688 | 11.600 | 209.396 | 25.496 | 55.268 | 11.262 | -0.012 | ms | -2.659 | 64.31 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2a01:4ff:1f0:c33f::1 | -6.622 | -4.223 | 1.110 | 4.402 | 6.109 | 6.738 | 12.640 | 4.999 | 10.961 | 1.896 | 4.103 | ms | -2.247 | 12.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2a01:4ff:f0:e33b::1 | -0.405 | 1.341 | 2.664 | 4.973 | 7.287 | 11.950 | 20.955 | 4.623 | 10.609 | 1.794 | 5.000 | ms | 2.539 | 21.23 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2a01:4ff:f0:ebce::1 (zero.txryan.com) | 8.384 | 8.384 | 8.384 | 34.231 | 34.231 | 34.231 | 34.231 | 25.847 | 25.847 | 12.924 | 21.307 | ms | 1.962e-16 | 1 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) | -51.215 | -51.215 | -51.215 | 6.741 | 19.073 | 19.073 | 19.073 | 70.288 | 70.288 | 23.048 | -2.114 | ms | -1.242 | 3.142 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) | -13.885 | -5.062 | 1.103 | 3.811 | 6.136 | 7.963 | 13.358 | 5.032 | 13.025 | 2.029 | 3.639 | ms | -2.051 | 16.32 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 38.81.211.177 | 10.240 | 10.240 | 10.240 | 12.392 | 14.243 | 14.243 | 14.243 | 4.003 | 4.003 | 1.494 | 12.099 | ms | 0.05225 | 1.572 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 44.190.5.123 | -619.209 | 0.544 | 2.443 | 5.227 | 7.382 | 8.611 | 28.290 | 4.939 | 8.067 | 8.826 | 4.882 | ms | -52.41 | 3377 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.33.53.84 | -7.486 | -0.752 | 1.768 | 4.092 | 5.904 | 7.268 | 9.925 | 4.136 | 8.020 | 1.462 | 4.030 | ms | -1.366 | 12.35 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.55.126.202 | -4.945 | 0.288 | 1.840 | 4.396 | 6.776 | 8.592 | 12.903 | 4.936 | 8.304 | 1.542 | 4.413 | ms | -0.1068 | 6.675 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.55.58.103 | -2.720 | -2.720 | -1.021 | 6.381 | 9.087 | 10.740 | 10.740 | 10.108 | 13.460 | 2.718 | 5.713 | ms | -1.293 | 5.373 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.61.187.39 | -3.631 | -3.631 | -3.631 | 4.490 | 13.757 | 13.757 | 13.757 | 17.388 | 17.388 | 4.830 | 3.741 | ms | 0.536 | 3.14 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.63.54.13 | -14.116 | -0.809 | 2.451 | 5.749 | 9.193 | 15.128 | 27.310 | 6.742 | 15.937 | 2.596 | 5.789 | ms | 0.6719 | 17.26 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.79.35.159 | 3.746 | 3.746 | 3.746 | 7.855 | 8.568 | 8.568 | 8.568 | 4.821 | 4.821 | 2.112 | 6.125 | ms | 0.01386 | 1.093 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.79.51.42 | -45.604 | -45.604 | -45.604 | 8.683 | 108.150 | 108.150 | 108.150 | 153.754 | 153.754 | 57.087 | 39.510 | ms | 0.07989 | 1.347 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.83.234.123 | -296.062 | -296.062 | -36.862 | 5.462 | 11.429 | 15.325 | 15.325 | 48.291 | 311.387 | 44.156 | -5.332 | ms | -5.514 | 35.05 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 45.84.199.136 | -110.729 | -110.729 | -110.729 | -97.871 | 9.546 | 9.546 | 9.546 | 120.275 | 120.275 | 54.799 | -52.941 | ms | 0.172 | 1.055 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 46.37.96.107 | -808.769 | -33.538 | -1.905 | 5.043 | 7.457 | 8.750 | 17.475 | 9.362 | 42.288 | 37.739 | 2.042 | ms | -20.74 | 443.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 5.161.111.190 | -0.126 | 0.940 | 2.843 | 5.553 | 7.484 | 8.513 | 15.050 | 4.641 | 7.573 | 1.526 | 5.470 | ms | 0.2432 | 8.093 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 5.78.62.36 | -8.523 | -2.092 | 0.307 | 5.929 | 11.849 | 15.869 | 16.396 | 11.542 | 17.960 | 3.566 | 6.030 | ms | 0.08899 | 3.94 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 50.117.3.52 | -8.085 | -8.085 | -8.085 | -6.204 | -5.368 | -5.368 | -5.368 | 2.717 | 2.717 | 0.914 | -6.560 | ms | -0.319 | 1.928 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 50.117.3.95 | -146.276 | -146.276 | -146.276 | 8.636 | 18.465 | 18.465 | 18.465 | 164.741 | 164.741 | 63.106 | -20.370 | ms | -1.48 | 3.224 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 50.205.57.38 | -13.612 | 0.957 | 2.871 | 5.422 | 7.494 | 10.271 | 20.357 | 4.623 | 9.314 | 1.625 | 5.423 | ms | -0.1843 | 22.87 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 50.218.103.254 | -15.904 | -15.904 | -12.655 | 6.918 | 11.696 | 11.835 | 11.835 | 24.351 | 27.738 | 7.169 | 4.954 | ms | -1.516 | 4.534 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 51.81.20.76 | 2.414 | 2.414 | 2.414 | 7.712 | 11.524 | 11.524 | 11.524 | 9.111 | 9.111 | 3.247 | 7.454 | ms | -0.2642 | 1.777 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 51.81.226.229 | -178.118 | -178.118 | -168.711 | 4.809 | 12.384 | 22.510 | 22.510 | 181.095 | 200.627 | 42.711 | -5.129 | ms | -3.647 | 14.49 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 64.142.54.12 | 9.100 | 9.100 | 9.100 | 11.576 | 22.059 | 22.059 | 22.059 | 12.959 | 12.959 | 3.920 | 12.706 | ms | 1.335 | 3.639 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 64.6.144.6 | -8.057 | -7.831 | -5.650 | -1.925 | 2.191 | 462.576 | 467.377 | 7.840 | 470.408 | 54.569 | 4.472 | ms | 8.286 | 69.79 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 64.79.100.197 | -5.398 | -1.308 | 0.115 | 2.437 | 4.257 | 5.695 | 7.196 | 4.142 | 7.002 | 1.439 | 2.356 | ms | -1.086 | 9.14 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 65.100.46.164 | -12.522 | -2.725 | -0.387 | 4.920 | 11.409 | 15.307 | 17.739 | 11.796 | 18.032 | 3.731 | 5.348 | ms | 0.01927 | 4.589 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 65.100.46.166 | 0.249 | 1.083 | 2.398 | 5.335 | 7.816 | 11.010 | 13.272 | 5.418 | 9.928 | 1.740 | 5.341 | ms | 0.2817 | 4.931 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 65.182.224.39 | 1.814 | 1.814 | 1.814 | 2.848 | 5.791 | 5.791 | 5.791 | 3.977 | 3.977 | 1.315 | 3.059 | ms | 1.249 | 3.327 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 66.118.229.14 | 5.362 | 5.362 | 5.362 | 9.349 | 9.349 | 9.349 | 9.349 | 3.986 | 3.986 | 1.993 | 7.355 | ms | 6.268e-16 | 1 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 66.118.230.14 | 5.529 | 5.529 | 5.529 | 5.949 | 10.275 | 10.275 | 10.275 | 4.746 | 4.746 | 2.145 | 7.251 | ms | 0.6868 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 66.118.231.14 | -27.328 | -27.328 | -11.996 | 6.282 | 12.740 | 46.019 | 46.019 | 24.736 | 73.347 | 10.790 | 3.288 | ms | 0.6884 | 8.099 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 66.42.71.197 | -4.404 | 1.164 | 3.246 | 6.075 | 8.417 | 9.829 | 440.870 | 5.171 | 8.665 | 20.411 | 6.942 | ms | 20.87 | 439.3 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 66.59.198.94 | -3.193 | -3.193 | -3.193 | 1.753 | 7.991 | 7.991 | 7.991 | 11.183 | 11.183 | 3.576 | 2.287 | ms | 0.3048 | 1.825 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 66.85.78.80 | -17.366 | -13.001 | -7.268 | -1.837 | 1.018 | 6.542 | 10.757 | 8.286 | 19.543 | 3.003 | -2.223 | ms | -0.8402 | 8.685 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 67.217.240.178 | -2.392 | -2.392 | -2.392 | 7.224 | 15.021 | 15.021 | 15.021 | 17.413 | 17.413 | 4.868 | 6.427 | ms | -0.1827 | 2.554 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 67.217.246.127 | -4.257 | -3.477 | -0.379 | 2.528 | 6.202 | 9.675 | 10.219 | 6.580 | 13.152 | 2.004 | 2.572 | ms | 0.5419 | 6.199 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 67.217.246.204 | -407.881 | -405.967 | -8.458 | 0.106 | 11.835 | 17.296 | 21.211 | 20.293 | 423.263 | 62.932 | -8.808 | ms | -6.1 | 38.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 68.234.48.70 | -2.973 | -2.973 | -2.973 | 9.512 | 47.817 | 47.817 | 47.817 | 50.790 | 50.790 | 12.262 | 11.128 | ms | 2.266 | 7.46 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 69.48.203.16 | 2.540 | 2.540 | 2.540 | 7.439 | 10.588 | 10.588 | 10.588 | 8.048 | 8.048 | 2.329 | 7.070 | ms | -0.4418 | 2.4 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 69.89.207.199 | -35.854 | -1.651 | 0.462 | 2.952 | 7.621 | 102.532 | 105.829 | 7.159 | 104.183 | 11.033 | 4.295 | ms | 8.078 | 73.06 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 69.89.207.99 | -2.776 | -1.101 | 0.455 | 2.909 | 4.665 | 5.551 | 6.408 | 4.210 | 6.652 | 1.304 | 2.772 | ms | -0.6304 | 4.142 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 71.123.46.186 | -0.765 | -0.089 | 1.160 | 4.514 | 7.163 | 9.760 | 10.300 | 6.003 | 9.849 | 1.893 | 4.465 | ms | 0.0854 | 3.856 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 71.19.144.140 | -3.221 | -3.221 | -3.221 | 4.015 | 7.428 | 7.428 | 7.428 | 10.649 | 10.649 | 2.867 | 3.283 | ms | -0.3728 | 2.496 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 72.14.183.39 | 0.355 | 1.411 | 3.334 | 5.496 | 7.837 | 9.588 | 11.748 | 4.503 | 8.177 | 1.427 | 5.487 | ms | 0.1324 | 4.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 72.14.186.59 | 2.611 | 2.611 | 2.611 | 5.374 | 7.023 | 7.023 | 7.023 | 4.412 | 4.412 | 1.489 | 5.305 | ms | -0.8276 | 2.527 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 72.30.35.89 | 8.994 | 8.994 | 8.994 | 12.518 | 13.297 | 13.297 | 13.297 | 4.303 | 4.303 | 1.872 | 11.603 | ms | -0.6164 | 1.5 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 72.46.53.234 | -35.275 | -35.275 | -35.275 | 69.197 | 105.228 | 105.228 | 105.228 | 140.503 | 140.503 | 52.722 | 51.699 | ms | -0.2012 | 1.301 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 72.46.61.205 | -285.110 | -285.110 | -285.110 | 6.157 | 16.075 | 16.075 | 16.075 | 301.185 | 301.185 | 73.049 | -25.856 | ms | -2.768 | 9.979 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 73.185.182.209 | -2.743 | 0.925 | 2.341 | 5.411 | 8.588 | 10.253 | 11.822 | 6.247 | 9.328 | 1.947 | 5.428 | ms | -0.05719 | 3.857 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 73.65.80.137 | -809.727 | -809.727 | -9.135 | -1.384 | 3.688 | 7.510 | 7.510 | 12.823 | 817.238 | 169.002 | -38.192 | ms | -4.333 | 19.79 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 74.119.243.5 | 1.643 | 1.643 | 1.643 | 7.015 | 7.452 | 7.452 | 7.452 | 5.809 | 5.809 | 2.661 | 4.585 | ms | -0.008075 | 1.037 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 74.208.117.38 | -8.056 | -8.056 | -8.056 | -3.727 | 11.177 | 11.177 | 11.177 | 19.233 | 19.233 | 5.901 | -2.284 | ms | 1.09 | 3.094 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 74.208.14.149 | -5.945 | -5.945 | -5.945 | 8.847 | 11.709 | 11.709 | 11.709 | 17.654 | 17.654 | 5.690 | 5.541 | ms | -1.091 | 3.04 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 74.208.25.46 | -15.748 | -3.661 | -0.778 | 4.701 | 12.042 | 18.695 | 486.710 | 12.821 | 22.356 | 25.682 | 6.852 | ms | 13.83 | 211.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 83.147.242.172 | -3.579 | 1.082 | 2.797 | 5.135 | 7.484 | 9.790 | 14.032 | 4.687 | 8.708 | 1.518 | 5.170 | ms | 0.1286 | 6.052 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 99.28.14.242 | -568.386 | -3.525 | 0.460 | 4.626 | 9.607 | 12.913 | 287.104 | 9.147 | 16.438 | 32.755 | 4.526 | ms | -10.49 | 234.8 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SHM(0) | -8.145 | -7.741 | -6.910 | -0.148 | -0.109 | -0.002 | 0.005 | 6.801 | 7.739 | 1.814 | -0.648 | s | -3.304 | 11.99 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SHM(1) | -8.010 | -7.008 | -6.007 | -0.000 | 0.000 | 0.000 | 0.001 | 6.007 | 7.009 | 1.650 | -0.444 | s | -3.48 | 13.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SHM(2) | -485.911 | -170.410 | -96.976 | 0.232 | 8.581 | 17.676 | 44.156 | 105.557 | 188.086 | 36.108 | -11.840 | ms | -2.926 | 11.7 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SHM(3) | -12.883 | -6.851 | -1.301 | -0.400 | 0.421 | 0.870 | 12.496 | 1.722 | 7.720 | 1.098 | -0.538 | ms | -3.968 | 23.18 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SOCK(0) | -597.294 | -177.834 | -174.616 | -0.939 | 7.355 | 181.993 | 236.678 | 181.971 | 359.827 | 80.136 | -30.176 | ms | -0.5305 | 3.565 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SOCK(1) | -52.048 | -1.787 | -0.992 | -0.087 | 0.869 | 1.335 | 230.276 | 1.862 | 3.123 | 1.166 | -0.087 | ms | 129.6 | 2.566e+04 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SOCK(2) | -181.172 | -176.994 | -173.059 | -163.444 | -157.121 | -154.860 | -148.505 | 15.938 | 22.134 | 4.800 | -164.015 | ms | -0.5576 | 3.253 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SOCK(3) | -3,009.455 | -0.960 | -0.610 | -0.079 | 0.535 | 0.918 | 4.447 | 1.145 | 1.878 | 17.175 | -0.177 | ms | -175.1 | 3.068e+04 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 104.131.155.175 | 0.000 | 0.000 | 0.000 | 3.656 | 17.731 | 18.171 | 18.171 | 17.731 | 18.171 | 4.618 | 5.158 | ms | 1.714 | 5.382 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 104.152.220.5 | 0.000 | 0.000 | 0.000 | 1.578 | 3.071 | 3.071 | 3.071 | 3.071 | 3.071 | 0.957 | 1.621 | ms | -0.1526 | 2.323 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 104.167.215.195 | 0.000 | 0.000 | 1.736 | 5.117 | 35.856 | 66.707 | 67.627 | 34.119 | 66.707 | 12.331 | 8.977 | ms | 3.401 | 14.81 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 104.167.241.253 | 0.000 | 0.000 | 0.000 | 2.362 | 8.036 | 8.036 | 8.036 | 8.036 | 8.036 | 2.290 | 2.983 | ms | 0.6267 | 2.554 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 104.234.61.117 | 0.000 | 0.842 | 1.258 | 3.320 | 13.812 | 22.021 | 62.066 | 12.553 | 21.179 | 4.667 | 4.606 | ms | 4.224 | 29.96 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 108.181.201.22 | 0.000 | 0.000 | 0.000 | 5.514 | 12.431 | 12.431 | 12.431 | 12.431 | 12.431 | 3.786 | 5.054 | ms | 0.5181 | 2.09 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 108.59.2.24 | 0.000 | 0.000 | 0.000 | 2.687 | 4.534 | 4.534 | 4.534 | 4.534 | 4.534 | 1.862 | 2.407 | ms | -0.2221 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 108.61.215.221 | 0.000 | 0.650 | 1.101 | 3.005 | 15.157 | 28.430 | 54.452 | 14.056 | 27.780 | 5.946 | 4.747 | ms | 4.248 | 27.48 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 108.61.56.35 | 0.000 | 0.000 | 0.000 | 2.555 | 4.944 | 4.944 | 4.944 | 4.944 | 4.944 | 1.407 | 2.414 | ms | -0.1572 | 2.553 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 108.61.73.243 | 0.000 | 0.907 | 1.559 | 10.783 | 44.654 | 63.282 | 117.163 | 43.095 | 62.375 | 14.580 | 14.492 | ms | 2.088 | 8.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 12.205.28.193 | 0.000 | 0.893 | 1.308 | 3.371 | 17.565 | 41.353 | 240.147 | 16.257 | 40.460 | 13.847 | 5.912 | ms | 11.77 | 168.2 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 12.71.198.242 | 0.000 | 0.000 | 0.000 | 2.476 | 14.247 | 14.247 | 14.247 | 14.247 | 14.247 | 4.389 | 3.547 | ms | 1.44 | 4.115 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 129.146.193.200 | 0.000 | 0.590 | 1.131 | 3.244 | 17.511 | 33.383 | 70.718 | 16.380 | 32.793 | 6.398 | 4.966 | ms | 4.738 | 34.45 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 131.153.171.250 | 0.000 | 0.000 | 0.000 | 0.763 | 4.308 | 4.308 | 4.308 | 4.308 | 4.308 | 1.877 | 1.690 | ms | 0.6205 | 1.5 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 131.239.5.43 | 0.000 | 0.000 | 0.000 | 1.655 | 3.135 | 3.135 | 3.135 | 3.135 | 3.135 | 0.882 | 1.743 | ms | -0.2966 | 2.893 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 135.148.100.14 | 0.000 | 0.923 | 1.623 | 14.224 | 55.544 | 71.155 | 96.799 | 53.922 | 70.232 | 15.396 | 16.541 | ms | 1.978 | 8.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 137.110.222.27 | 0.000 | 0.932 | 1.375 | 3.330 | 15.276 | 22.565 | 61.468 | 13.901 | 21.633 | 5.668 | 4.627 | ms | 6.016 | 52.38 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 137.190.2.4 | 0.000 | 0.000 | 0.000 | 1.069 | 2.723 | 2.723 | 2.723 | 2.723 | 2.723 | 1.044 | 1.057 | ms | 0.5061 | 1.605 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 139.177.202.26 | 0.000 | 0.000 | 0.000 | 1.560 | 6.528 | 6.528 | 6.528 | 6.528 | 6.528 | 1.992 | 1.908 | ms | 1.039 | 3.07 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 139.94.144.123 | 0.000 | 0.000 | 0.000 | 1.501 | 2.945 | 2.945 | 2.945 | 2.945 | 2.945 | 1.260 | 1.529 | ms | 0.002279 | 1.271 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 141.11.234.198 | 0.000 | 0.000 | 0.000 | 8.942 | 58.361 | 58.361 | 58.361 | 58.361 | 58.361 | 19.957 | 16.134 | ms | 1.387 | 3.303 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 141.11.89.193 | 0.000 | 0.000 | 0.000 | 1.558 | 2.015 | 2.015 | 2.015 | 2.015 | 2.015 | 0.652 | 1.474 | ms | -1.441 | 3.889 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 142.202.190.19 | 0.000 | 0.000 | 0.000 | 2.175 | 6.985 | 16.409 | 16.409 | 6.985 | 16.409 | 3.192 | 2.973 | ms | 2.438 | 10.54 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 143.42.229.154 | 0.000 | 0.761 | 1.401 | 5.355 | 36.230 | 71.873 | 89.094 | 34.829 | 71.112 | 13.059 | 10.927 | ms | 2.601 | 11.68 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 144.202.0.197 | 0.000 | 0.000 | 0.000 | 2.470 | 4.307 | 4.307 | 4.307 | 4.307 | 4.307 | 1.435 | 2.296 | ms | -0.2563 | 1.847 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 144.202.66.214 | 0.000 | 0.000 | 0.000 | 3.268 | 3.564 | 3.564 | 3.564 | 3.564 | 3.564 | 1.326 | 2.411 | ms | -0.873 | 2.102 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 148.135.119.56 | 0.000 | 0.920 | 1.304 | 3.191 | 12.314 | 24.154 | 205.114 | 11.011 | 23.234 | 7.147 | 4.555 | ms | 16.37 | 414.4 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 149.248.12.167 | 0.000 | 0.000 | 0.000 | 1.415 | 6.547 | 6.547 | 6.547 | 6.547 | 6.547 | 2.701 | 2.851 | ms | 0.3599 | 1.282 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 149.28.200.179 | 0.000 | 0.000 | 1.448 | 3.887 | 18.634 | 19.531 | 19.531 | 17.186 | 19.531 | 5.389 | 6.126 | ms | 1.504 | 3.906 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 149.28.61.105 | 0.000 | 0.000 | 0.000 | 2.466 | 4.280 | 4.280 | 4.280 | 4.280 | 4.280 | 1.264 | 2.154 | ms | -0.03175 | 2.746 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 15.204.198.96 | 0.000 | 0.000 | 1.528 | 9.635 | 18.188 | 24.740 | 24.740 | 16.661 | 24.740 | 6.496 | 9.205 | ms | 0.2143 | 1.632 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 15.204.87.223 | 0.000 | 0.000 | 1.093 | 3.116 | 14.025 | 23.083 | 37.321 | 12.932 | 23.083 | 4.456 | 4.482 | ms | 3.12 | 16.52 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 152.70.159.102 | 0.257 | 0.811 | 1.110 | 2.906 | 7.178 | 8.346 | 9.641 | 6.068 | 7.535 | 1.765 | 3.259 | ms | 1.066 | 3.889 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 158.51.134.123 | 0.000 | 0.801 | 1.375 | 4.189 | 72.788 | 183.366 | 259.136 | 71.413 | 182.565 | 32.046 | 14.704 | ms | 4.273 | 24.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 158.51.99.19 | 0.000 | 0.861 | 1.216 | 3.317 | 19.810 | 51.816 | 228.673 | 18.594 | 50.955 | 13.195 | 6.155 | ms | 10.51 | 149.8 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 162.159.200.1 | 0.000 | 0.595 | 1.140 | 3.020 | 13.359 | 21.989 | 98.350 | 12.219 | 21.395 | 5.104 | 4.291 | ms | 7.845 | 117.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 162.159.200.123 | 0.000 | 0.000 | 0.000 | 3.085 | 9.842 | 12.427 | 12.427 | 9.842 | 12.427 | 2.969 | 3.852 | ms | 1.147 | 3.88 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 163.123.152.14 | 0.000 | 0.000 | 0.000 | 3.728 | 4.357 | 4.357 | 4.357 | 4.357 | 4.357 | 1.674 | 2.791 | ms | -0.9099 | 2.151 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 168.61.215.74 | 0.000 | 0.494 | 1.143 | 3.432 | 10.228 | 15.888 | 22.601 | 9.085 | 15.395 | 3.074 | 4.248 | ms | 2.002 | 9.176 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 170.187.147.56 | 0.000 | 0.824 | 1.119 | 3.127 | 15.294 | 35.711 | 154.182 | 14.175 | 34.886 | 9.178 | 5.070 | ms | 11.83 | 185.3 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 172.233.157.223 | 0.000 | 0.000 | 0.000 | 2.179 | 8.001 | 8.001 | 8.001 | 8.001 | 8.001 | 2.598 | 2.911 | ms | 0.8956 | 2.43 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 172.233.177.198 | 0.000 | 0.000 | 0.000 | 5.156 | 9.581 | 9.581 | 9.581 | 9.581 | 9.581 | 2.646 | 5.415 | ms | -0.2803 | 2.993 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 172.234.25.10 | 0.000 | 0.000 | 0.000 | 1.180 | 2.779 | 2.779 | 2.779 | 2.779 | 2.779 | 0.771 | 1.320 | ms | 0.2545 | 3.074 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 172.234.37.140 | 0.000 | 0.000 | 0.000 | 5.761 | 13.618 | 13.618 | 13.618 | 13.618 | 13.618 | 3.635 | 5.254 | ms | 0.5438 | 2.723 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 172.234.44.141 | 0.000 | 0.000 | 0.000 | 2.374 | 7.577 | 7.577 | 7.577 | 7.577 | 7.577 | 2.262 | 3.093 | ms | 0.8517 | 2.644 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 172.235.32.243 | 0.000 | 0.000 | 0.000 | 1.782 | 11.715 | 11.715 | 11.715 | 11.715 | 11.715 | 4.266 | 3.663 | ms | 1.132 | 2.703 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 172.235.60.8 | 0.000 | 0.000 | 0.000 | 2.985 | 13.407 | 13.407 | 13.407 | 13.407 | 13.407 | 3.264 | 4.071 | ms | 1.906 | 6.336 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 172.98.15.13 | 0.000 | 0.000 | 0.000 | 6.095 | 6.104 | 6.104 | 6.104 | 6.104 | 6.104 | 2.880 | 3.231 | ms | -0.02367 | 1.032 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 173.230.154.254 | 0.000 | 0.000 | 0.000 | 17.669 | 34.968 | 34.968 | 34.968 | 34.968 | 34.968 | 10.793 | 16.118 | ms | 0.0947 | 2.297 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 173.255.192.10 | 0.000 | 0.000 | 0.000 | 2.331 | 9.584 | 9.584 | 9.584 | 9.584 | 9.584 | 2.608 | 3.116 | ms | 1.465 | 4.472 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 173.255.255.133 | 0.000 | 0.153 | 1.038 | 3.303 | 14.750 | 23.112 | 28.677 | 13.712 | 22.959 | 4.499 | 4.721 | ms | 2.482 | 9.648 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 173.71.68.71 | 0.000 | 0.627 | 1.250 | 6.765 | 34.293 | 47.740 | 57.792 | 33.043 | 47.112 | 10.711 | 11.124 | ms | 1.434 | 5.181 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 173.73.96.68 | 0.000 | 0.897 | 1.335 | 4.957 | 36.764 | 55.951 | 66.282 | 35.430 | 55.054 | 10.516 | 9.643 | ms | 2.204 | 8.641 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 193.29.63.226 | 0.000 | 0.000 | 0.000 | 2.362 | 6.790 | 7.768 | 7.768 | 6.790 | 7.768 | 1.752 | 2.617 | ms | 1.293 | 4.972 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 198.137.202.32 | 0.000 | 0.671 | 1.209 | 3.297 | 12.402 | 17.407 | 31.925 | 11.193 | 16.736 | 3.746 | 4.236 | ms | 3.509 | 20.09 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 198.199.14.19 | 0.000 | 0.000 | 0.000 | 4.868 | 19.360 | 19.360 | 19.360 | 19.360 | 19.360 | 6.619 | 7.607 | ms | 0.7297 | 1.985 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 198.211.103.209 | 0.000 | 0.000 | 0.000 | 3.750 | 13.433 | 21.945 | 21.945 | 13.433 | 21.945 | 4.568 | 5.256 | ms | 1.672 | 6.209 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 198.23.249.167 | 0.000 | 0.000 | 0.000 | 3.316 | 6.091 | 6.091 | 6.091 | 6.091 | 6.091 | 1.952 | 2.701 | ms | 0.1314 | 2.028 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 198.46.254.130 | 0.000 | 0.789 | 1.171 | 3.308 | 24.735 | 39.397 | 60.567 | 23.564 | 38.608 | 8.364 | 6.211 | ms | 3.337 | 16.34 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 198.60.22.240 | 0.000 | 0.717 | 1.162 | 3.134 | 14.200 | 31.742 | 43.551 | 13.038 | 31.025 | 5.322 | 4.655 | ms | 3.973 | 22.32 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 199.68.201.235 | 0.000 | 0.000 | 1.107 | 3.083 | 4.994 | 5.795 | 5.795 | 3.886 | 5.795 | 1.244 | 3.083 | ms | -0.137 | 2.992 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) | 0.000 | 1.001 | 1.378 | 3.306 | 22.350 | 55.353 | 68.490 | 20.972 | 54.352 | 9.914 | 6.937 | ms | 3.502 | 16.46 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) | 0.000 | 0.000 | 0.000 | 6.706 | 10.790 | 10.790 | 10.790 | 10.790 | 10.790 | 3.771 | 6.760 | ms | -0.8058 | 2.409 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:19f0:6401:400:5400:4ff:fec3:522a | 0.000 | 0.984 | 1.317 | 3.458 | 15.872 | 41.672 | 50.559 | 14.555 | 40.688 | 6.685 | 5.283 | ms | 4.293 | 24.81 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:418:3ff::53 (x.ns.gin.ntt.net) | 0.000 | 0.000 | 0.000 | 14.048 | 17.951 | 17.951 | 17.951 | 17.951 | 17.951 | 7.508 | 10.420 | ms | -0.3643 | 1.295 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:418:8405:4002::12 | 0.000 | 0.000 | 0.000 | 20.750 | 257.784 | 257.784 | 257.784 | 257.784 | 257.784 | 84.275 | 57.575 | ms | 1.804 | 4.559 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:418:8405:4002::3 | 0.000 | 0.917 | 1.531 | 3.892 | 17.833 | 21.114 | 27.069 | 16.302 | 20.197 | 4.267 | 5.019 | ms | 2.538 | 9.839 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) | 0.000 | 1.136 | 2.036 | 12.122 | 41.039 | 72.944 | 118.845 | 39.003 | 71.808 | 15.175 | 15.560 | ms | 2.609 | 13.81 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:470:1f07:24f::123 | 0.000 | 0.000 | 0.000 | 25.254 | 42.613 | 42.613 | 42.613 | 42.613 | 42.613 | 13.314 | 18.607 | ms | 0.05496 | 1.858 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:470:1f07:d::5 (santuario.pads.ufrj.br) | 0.000 | 3.918 | 11.337 | 50.561 | 92.819 | 107.373 | 129.666 | 81.481 | 103.455 | 23.640 | 51.292 | ms | 0.199 | 2.763 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:470:1f2c:60:123:123:123:123 | 0.000 | 0.000 | 0.000 | 20.430 | 35.954 | 35.954 | 35.954 | 35.954 | 35.954 | 11.405 | 14.554 | ms | 0.1812 | 1.824 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:470:b:22d::123 | 0.000 | 0.000 | 1.754 | 4.530 | 7.600 | 11.131 | 11.131 | 5.846 | 11.131 | 2.457 | 4.623 | ms | 0.5328 | 3.13 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:470:e114::d6:12 (1.md.ntp.md) | 0.000 | 0.000 | 1.372 | 6.665 | 25.048 | 45.230 | 56.378 | 23.676 | 45.230 | 8.605 | 9.563 | ms | 2.052 | 9.185 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:470:e114::d6:c5 (t2.davehart.net) | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | ns | nan | nan | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:470:e8dc:10::123 | 0.000 | 0.001 | 0.001 | 0.004 | 0.021 | 0.074 | 589.082 | 0.020 | 0.073 | 24.776 | 1.685 | s | 18.39 | 390.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) | 0.000 | 1.102 | 1.686 | 10.928 | 48.225 | 61.432 | 219.778 | 46.539 | 60.331 | 15.215 | 14.564 | ms | 2.947 | 25.72 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com) | 0.000 | 0.840 | 1.365 | 3.070 | 12.046 | 16.376 | 19.485 | 10.681 | 15.537 | 3.227 | 3.896 | ms | 2.632 | 10.33 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) | 0.000 | 0.830 | 1.150 | 3.284 | 24.575 | 55.936 | 146.741 | 23.425 | 55.106 | 10.291 | 6.585 | ms | 4.523 | 32.1 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:558:6014:17:8dc5:5575:5560:2cb6 | 0.000 | 0.000 | 0.000 | 4.253 | 65.155 | 123.941 | 123.941 | 65.155 | 123.941 | 24.032 | 13.461 | ms | 3.066 | 13.01 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:559:2be:3::1001 | 0.000 | 0.000 | 0.000 | 2.941 | 26.115 | 53.390 | 53.390 | 26.115 | 53.390 | 13.022 | 8.500 | ms | 2.056 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2001:678:8::123 (any.time.nl) | 0.000 | 0.000 | 0.000 | 3.773 | 8.575 | 8.575 | 8.575 | 8.575 | 8.575 | 2.594 | 3.773 | ms | 0.2015 | 1.856 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 204.10.18.144 | 0.000 | 0.000 | 0.000 | 0.624 | 2.536 | 2.536 | 2.536 | 2.536 | 2.536 | 1.079 | 1.053 | ms | 0.5341 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 204.197.163.71 | 0.000 | 0.686 | 1.095 | 3.220 | 7.493 | 17.061 | 50.513 | 6.398 | 16.375 | 3.155 | 3.763 | ms | 6.631 | 80.71 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 204.2.134.162 | 0.000 | 0.000 | 0.000 | 1.171 | 6.096 | 6.096 | 6.096 | 6.096 | 6.096 | 1.827 | 2.047 | ms | 0.8441 | 2.681 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 205.233.73.201 | 0.000 | 0.000 | 0.000 | 3.092 | 11.938 | 16.572 | 16.572 | 11.938 | 16.572 | 3.752 | 3.827 | ms | 1.821 | 6.541 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 208.113.130.146 | 0.000 | 0.861 | 1.394 | 5.061 | 43.913 | 76.684 | 232.036 | 42.519 | 75.823 | 18.779 | 11.712 | ms | 5.666 | 52.59 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 208.67.72.43 | 0.000 | 0.000 | 0.000 | 20.684 | 46.773 | 46.773 | 46.773 | 46.773 | 46.773 | 14.479 | 19.405 | ms | 0.3984 | 2.247 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 208.67.72.50 | 0.000 | 0.000 | 1.610 | 9.928 | 32.633 | 65.428 | 66.592 | 31.023 | 65.428 | 11.583 | 11.986 | ms | 2.324 | 10.54 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 208.67.75.242 | 0.000 | 0.872 | 1.265 | 3.563 | 19.825 | 36.345 | 45.510 | 18.560 | 35.473 | 6.747 | 6.278 | ms | 2.54 | 10.94 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 212.227.240.160 | 0.000 | 0.916 | 1.250 | 3.935 | 19.802 | 39.736 | 56.197 | 18.552 | 38.820 | 7.597 | 6.975 | ms | 2.834 | 13.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 216.229.4.66 | 0.000 | 0.000 | 0.000 | 4.281 | 7.579 | 7.579 | 7.579 | 7.579 | 7.579 | 2.200 | 3.859 | ms | -0.3889 | 2.271 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 216.229.4.69 | 0.000 | 0.000 | 0.000 | 2.477 | 5.003 | 5.695 | 5.695 | 5.003 | 5.695 | 1.718 | 2.457 | ms | 0.2191 | 2.013 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 216.240.36.24 | 0.000 | 0.000 | 0.000 | 2.248 | 8.229 | 18.352 | 18.352 | 8.229 | 18.352 | 4.048 | 3.754 | ms | 2.262 | 8.332 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 216.31.17.12 | 0.000 | 0.000 | 0.000 | 4.094 | 14.330 | 14.330 | 14.330 | 14.330 | 14.330 | 4.001 | 4.883 | ms | 1.185 | 3.801 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.111.186.186 | 0.000 | 0.000 | 0.000 | 1.132 | 1.974 | 1.974 | 1.974 | 1.974 | 1.974 | 0.537 | 1.129 | ms | -0.4905 | 3.028 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.131.160.7 | 0.000 | 0.872 | 1.351 | 3.468 | 10.877 | 32.018 | 126.894 | 9.526 | 31.146 | 7.978 | 4.861 | ms | 9.331 | 108.7 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.141.40.123 | 0.000 | 0.000 | 0.000 | 3.979 | 5.911 | 5.911 | 5.911 | 5.911 | 5.911 | 1.921 | 3.290 | ms | -0.4708 | 2.11 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.142.248.8 | 0.000 | 0.000 | 0.000 | 1.269 | 2.327 | 2.327 | 2.327 | 2.327 | 2.327 | 0.866 | 1.154 | ms | -0.1197 | 1.574 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.142.248.9 | 0.000 | 0.000 | 0.000 | 2.599 | 5.085 | 5.085 | 5.085 | 5.085 | 5.085 | 1.807 | 2.480 | ms | -0.03191 | 1.728 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.143.196.199 | 0.000 | 0.000 | 0.000 | 1.033 | 2.250 | 2.250 | 2.250 | 2.250 | 2.250 | 0.756 | 1.094 | ms | -0.06783 | 1.795 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.150.41.122 | 0.000 | 0.000 | 1.319 | 2.973 | 16.917 | 17.402 | 17.402 | 15.598 | 17.402 | 4.356 | 4.490 | ms | 1.961 | 5.842 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.150.41.123 | 0.000 | 0.770 | 1.248 | 3.330 | 18.440 | 37.814 | 51.306 | 17.192 | 37.044 | 6.206 | 5.284 | ms | 3.425 | 17.13 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.155.40.38 | 0.000 | 0.000 | 1.081 | 3.356 | 34.022 | 117.881 | 142.893 | 32.940 | 117.881 | 18.722 | 8.653 | ms | 5.033 | 31.38 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.157.160.168 | 0.000 | 0.572 | 1.303 | 4.681 | 21.589 | 31.517 | 57.034 | 20.286 | 30.944 | 8.008 | 7.992 | ms | 2.366 | 12.25 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.168.136.132 | 0.000 | 0.000 | 0.000 | 19.641 | 37.023 | 37.023 | 37.023 | 37.023 | 37.023 | 8.847 | 19.801 | ms | -0.3743 | 3.622 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.168.24.210 | 0.000 | 0.000 | 0.000 | 4.522 | 5.887 | 5.887 | 5.887 | 5.887 | 5.887 | 2.451 | 2.822 | ms | 0.06634 | 1.208 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.1 | 0.000 | 0.000 | 0.000 | 6.006 | 60.335 | 60.335 | 60.335 | 60.335 | 60.335 | 27.624 | 25.467 | ms | 0.3959 | 1.179 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.123 | 0.000 | 0.794 | 1.193 | 3.052 | 8.245 | 20.200 | 30.025 | 7.052 | 19.406 | 3.089 | 3.701 | ms | 3.772 | 21.92 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.126 | 0.000 | 0.695 | 1.121 | 3.001 | 10.669 | 41.147 | 100.230 | 9.548 | 40.452 | 8.625 | 4.647 | ms | 7.962 | 75.3 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.127 | 0.000 | 0.000 | 0.000 | 6.846 | 25.786 | 25.786 | 25.786 | 25.786 | 25.786 | 9.961 | 9.050 | ms | 0.9537 | 2.186 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.128 | 0.000 | 0.814 | 1.329 | 3.310 | 8.610 | 17.200 | 23.748 | 7.281 | 16.386 | 2.792 | 3.875 | ms | 2.955 | 14.86 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.129 | 0.000 | 0.711 | 1.257 | 3.428 | 8.497 | 17.161 | 40.189 | 7.240 | 16.450 | 3.103 | 4.098 | ms | 4.318 | 37.33 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.130 | 0.000 | 0.000 | 0.000 | 3.466 | 73.799 | 73.994 | 73.994 | 73.799 | 73.994 | 19.691 | 9.038 | ms | 2.942 | 9.824 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.131 | 0.000 | 0.749 | 1.266 | 3.133 | 8.261 | 15.037 | 223.184 | 6.995 | 14.289 | 9.704 | 4.117 | ms | 21.04 | 473.4 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.132 | 0.000 | 0.902 | 1.266 | 3.346 | 9.317 | 18.281 | 72.944 | 8.051 | 17.379 | 3.794 | 4.152 | ms | 6.892 | 91.34 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.186.168.3 | 0.000 | 0.983 | 1.613 | 5.204 | 23.217 | 48.252 | 65.816 | 21.604 | 47.269 | 8.431 | 8.574 | ms | 2.567 | 13.3 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.94.221.138 | 0.000 | 0.000 | 0.000 | 1.546 | 4.125 | 4.125 | 4.125 | 4.125 | 4.125 | 1.215 | 1.733 | ms | 0.7763 | 2.642 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 23.95.49.216 | 0.000 | 0.804 | 1.089 | 2.946 | 11.443 | 17.019 | 159.086 | 10.354 | 16.216 | 7.100 | 4.020 | ms | 17.62 | 379.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 240b:4002:100:9f00:5bd1:9512:8a8b:25e | 0.000 | 0.000 | 0.000 | 4.287 | 5.971 | 5.971 | 5.971 | 5.971 | 5.971 | 2.062 | 3.825 | ms | -0.9946 | 2.639 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d6 | 0.000 | 0.839 | 1.416 | 3.601 | 24.535 | 54.985 | 74.237 | 23.119 | 54.146 | 9.449 | 6.322 | ms | 4.13 | 22.24 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d9 | 0.000 | 0.000 | 0.000 | 19.678 | 21.828 | 21.828 | 21.828 | 21.828 | 21.828 | 8.593 | 13.132 | ms | -0.5264 | 1.711 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1700:3d24:740f:9524:529a:6489:d48f | 0.000 | 0.000 | 0.000 | 1.447 | 8.923 | 8.923 | 8.923 | 8.923 | 8.923 | 2.239 | 2.142 | ms | 1.358 | 4.664 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1700:5455:a70::7b:1 | 0.000 | 0.000 | 1.444 | 4.653 | 23.669 | 27.142 | 27.142 | 22.225 | 27.142 | 7.742 | 8.428 | ms | 1.002 | 2.547 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 | 0.000 | 0.000 | 0.000 | 4.182 | 17.559 | 24.762 | 24.762 | 17.559 | 24.762 | 6.282 | 6.670 | ms | 1.239 | 3.969 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1700:5a0f:ee00::314:1b | 0.000 | 0.000 | 1.037 | 3.806 | 18.648 | 21.885 | 23.803 | 17.611 | 21.885 | 5.224 | 5.597 | ms | 1.78 | 5.219 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1700:5a0f:ee00::314:2b | 0.000 | 0.000 | 0.000 | 2.121 | 13.811 | 13.811 | 13.811 | 13.811 | 13.811 | 3.373 | 3.376 | ms | 1.687 | 5.974 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1702:7400:9ac0::314:5a | 0.000 | 0.000 | 0.000 | 2.413 | 15.160 | 15.160 | 15.160 | 15.160 | 15.160 | 4.523 | 4.818 | ms | 1.082 | 3.061 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1702:7400:9ac0::5b | 0.000 | 0.000 | 0.000 | 2.689 | 7.877 | 7.877 | 7.877 | 7.877 | 7.877 | 2.509 | 3.387 | ms | 0.6509 | 2.164 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1f13:2c1:2e00::be00:5 | 0.000 | 0.941 | 1.487 | 3.653 | 25.297 | 93.488 | 214.829 | 23.809 | 92.548 | 16.422 | 7.675 | ms | 6.759 | 62.66 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) | 0.000 | 0.828 | 1.199 | 3.431 | 23.880 | 51.731 | 185.361 | 22.681 | 50.903 | 10.201 | 6.540 | ms | 5.398 | 51.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) | 0.000 | 0.843 | 1.231 | 3.701 | 42.194 | 71.171 | 179.382 | 40.963 | 70.328 | 15.038 | 9.840 | ms | 3.503 | 20.94 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) | 0.000 | 0.847 | 1.293 | 8.517 | 54.411 | 80.426 | 168.874 | 53.118 | 79.579 | 17.941 | 15.355 | ms | 2.103 | 8.678 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:2600::99 (ntp1.wiktel.com) | 0.000 | 0.000 | 0.000 | 1.922 | 1.922 | 1.922 | 1.922 | 1.922 | 1.922 | 0.961 | 0.961 | ms | 0 | 1 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c00::f03c:91ff:fe05:b640 (dev.smatwebdesign.com) | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | ns | nan | nan | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) | 0.000 | 0.894 | 1.371 | 3.443 | 16.948 | 34.487 | 151.451 | 15.577 | 33.593 | 7.361 | 5.349 | ms | 7.69 | 104.6 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c00:e000:318::1 (jane.qotw.net) | 0.000 | 0.936 | 1.251 | 3.291 | 18.596 | 45.542 | 55.919 | 17.345 | 44.606 | 7.258 | 5.661 | ms | 3.76 | 20.2 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) | 0.000 | 0.000 | 0.000 | 6.110 | 10.609 | 10.609 | 10.609 | 10.609 | 10.609 | 3.299 | 4.985 | ms | 0.1951 | 2.331 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c01:e000:7e6::123 (time1.sigi.net) | 0.000 | 0.707 | 1.268 | 3.208 | 8.867 | 20.528 | 87.783 | 7.599 | 19.821 | 4.889 | 4.141 | ms | 8.54 | 111.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c02::f03c:92ff:fe96:dc0 | 0.000 | 0.719 | 1.293 | 3.642 | 35.596 | 64.763 | 70.185 | 34.303 | 64.043 | 13.117 | 8.439 | ms | 3.086 | 12.43 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c02::f03c:94ff:fe59:f411 | 0.000 | 0.000 | 0.000 | 5.394 | 7.516 | 7.516 | 7.516 | 7.516 | 7.516 | 2.647 | 4.557 | ms | -0.5602 | 1.96 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net) | 0.000 | 0.565 | 1.299 | 3.371 | 13.487 | 24.586 | 25.970 | 12.188 | 24.021 | 4.283 | 4.701 | ms | 2.398 | 9.74 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) | 0.000 | 0.000 | 0.717 | 3.878 | 10.414 | 16.432 | 16.432 | 9.697 | 16.432 | 3.233 | 4.061 | ms | 1.999 | 7.801 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) | 0.000 | 0.000 | 0.000 | 4.625 | 9.182 | 9.182 | 9.182 | 9.182 | 9.182 | 3.008 | 4.335 | ms | -0.05862 | 1.872 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) | 0.000 | 1.135 | 1.788 | 5.529 | 12.197 | 16.663 | 19.149 | 10.409 | 15.527 | 3.521 | 6.155 | ms | 0.8396 | 3.495 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c03::f03c:94ff:fe59:d3de | 0.000 | 0.000 | 0.000 | 9.141 | 10.648 | 10.648 | 10.648 | 10.648 | 10.648 | 4.705 | 6.597 | ms | -0.6531 | 1.5 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c03:e002:1300::10 (ntp.electronmill.com) | 0.000 | 0.000 | 0.000 | 3.877 | 7.718 | 7.718 | 7.718 | 7.718 | 7.718 | 2.384 | 3.718 | ms | 0.3575 | 1.964 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c06::f03c:94ff:fee2:9c28 | 0.000 | 0.000 | 0.000 | 9.325 | 30.736 | 30.736 | 30.736 | 30.736 | 30.736 | 11.553 | 11.593 | ms | 0.8589 | 2.149 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:3c06::f03c:94ff:fee2:c53a | 0.000 | 0.000 | 0.000 | 15.615 | 24.117 | 24.117 | 24.117 | 24.117 | 24.117 | 9.987 | 13.244 | ms | -0.3427 | 1.5 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:4040:3037:e600::1 | 2.236 | 2.236 | 2.236 | 3.952 | 3.952 | 3.952 | 3.952 | 1.716 | 1.716 | 0.858 | 3.094 | ms | 8.189e-16 | 1 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2600:4040:e0da:f000::cbb9:201a | 0.000 | 0.000 | 0.547 | 12.110 | 32.149 | 45.133 | 45.133 | 31.602 | 45.133 | 10.649 | 11.858 | ms | 1.048 | 3.818 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2601:18a:8081:3600:a923:2e66:e3d2:8c95 | 0.000 | 0.000 | 0.000 | 6.012 | 12.408 | 12.408 | 12.408 | 12.408 | 12.408 | 3.817 | 6.403 | ms | -0.07568 | 2.393 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:291:69::8 (time2.tritan-bb.net) | 0.000 | 0.000 | 0.000 | 0.970 | 1.844 | 1.844 | 1.844 | 1.844 | 1.844 | 0.552 | 0.976 | ms | -0.2468 | 2.677 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:291:69::9 (time.tritan-bb.net) | 0.000 | 0.000 | 0.000 | 2.884 | 5.429 | 9.048 | 9.048 | 5.429 | 9.048 | 1.821 | 2.641 | ms | 0.7531 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) | 0.000 | 0.874 | 1.319 | 3.515 | 15.422 | 39.407 | 139.194 | 14.104 | 38.533 | 7.928 | 5.320 | ms | 7.573 | 87.13 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net) | 0.000 | 0.000 | 0.000 | 1.197 | 1.816 | 1.816 | 1.816 | 1.816 | 1.816 | 0.754 | 1.004 | ms | -0.3667 | 1.5 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:2eb:2:95:1234:5678:9abc:def0 | 0.000 | 0.928 | 1.412 | 3.654 | 26.243 | 55.859 | 262.579 | 24.831 | 54.931 | 13.247 | 7.544 | ms | 8.809 | 126 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:80b:5000::36 (time.meme.holdings) | 0.000 | 0.000 | 5.795 | 21.991 | 77.525 | 84.174 | 87.838 | 71.730 | 84.174 | 21.109 | 29.343 | ms | 0.9157 | 3.126 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) | 0.000 | 0.000 | 0.000 | 4.593 | 9.349 | 9.349 | 9.349 | 9.349 | 9.349 | 2.587 | 4.904 | ms | -0.09123 | 2.375 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) | 0.000 | 0.000 | 1.361 | 5.466 | 56.326 | 77.816 | 96.144 | 54.966 | 77.816 | 18.343 | 13.281 | ms | 2.257 | 7.758 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:f9bd:80:100::a (time.circlevps.net) | 0.000 | 0.956 | 1.406 | 3.442 | 16.785 | 30.859 | 88.641 | 15.379 | 29.903 | 6.152 | 5.167 | ms | 5.025 | 42.76 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:fc2f:100:9800::dead:beef | 0.000 | 1.459 | 2.342 | 5.528 | 63.917 | 165.490 | 259.248 | 61.575 | 164.031 | 29.613 | 15.005 | ms | 4.444 | 25.38 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) | 0.000 | 0.000 | 0.000 | 4.184 | 9.370 | 9.370 | 9.370 | 9.370 | 9.370 | 2.625 | 4.132 | ms | 0.213 | 2.817 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:fe2e:3:d:f9:c7ff:fef5:379c | 0.000 | 0.000 | 0.000 | 2.011 | 3.424 | 3.424 | 3.424 | 3.424 | 3.424 | 0.929 | 1.786 | ms | -0.1796 | 2.962 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:feda:30:ae86:2fc:98ff:fecf:fe94 | 0.482 | 0.800 | 1.196 | 3.125 | 10.174 | 19.107 | 34.513 | 8.978 | 18.307 | 3.601 | 3.930 | ms | 4.587 | 32.02 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:ff06:725:100::123 (oldtime2.sigi.net) | 0.000 | 0.766 | 1.309 | 3.362 | 12.735 | 19.380 | 20.540 | 11.426 | 18.614 | 3.361 | 4.167 | ms | 2.76 | 11.34 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2602:ff23:50:3c2::1 (dns-e.ns4v.icu) | 0.000 | 0.000 | 1.368 | 4.208 | 41.300 | 69.376 | 73.583 | 39.933 | 69.376 | 12.652 | 8.050 | ms | 3.515 | 15.2 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:0:8369:0:ba11:ba11:ba11 | 0.000 | 0.000 | 0.000 | 3.480 | 14.814 | 17.914 | 17.914 | 14.814 | 17.914 | 3.983 | 4.366 | ms | 1.511 | 5.581 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:0:8369:1111:1111:1111:1112 | 0.000 | 0.000 | 0.000 | 7.900 | 74.324 | 99.180 | 99.180 | 74.324 | 99.180 | 20.465 | 14.476 | ms | 2.431 | 9.472 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:0:8369:607:e532:d534:7109 | 0.000 | 0.000 | 0.000 | 2.471 | 17.374 | 17.374 | 17.374 | 17.374 | 17.374 | 4.277 | 3.926 | ms | 1.788 | 6.072 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:0:8369::bad:babe | 0.000 | 0.000 | 0.000 | 5.795 | 16.059 | 16.059 | 16.059 | 16.059 | 16.059 | 4.220 | 6.109 | ms | 0.5934 | 2.891 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:0:8369::bad:beef | 0.000 | 0.000 | 0.000 | 3.311 | 12.865 | 12.865 | 12.865 | 12.865 | 12.865 | 4.951 | 5.440 | ms | 0.6499 | 1.683 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:0:8369::f00d:feed | 0.000 | 0.000 | 0.000 | 3.051 | 11.156 | 19.041 | 19.041 | 11.156 | 19.041 | 4.036 | 4.160 | ms | 2.143 | 8.32 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:0:8369::feeb:dab | 0.000 | 0.000 | 0.000 | 3.564 | 11.129 | 12.564 | 12.564 | 11.129 | 12.564 | 2.944 | 3.733 | ms | 0.8869 | 3.775 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:0:8369:feed:feed:feed:feed | 0.000 | 0.000 | 0.000 | 3.112 | 13.323 | 13.323 | 13.323 | 13.323 | 13.323 | 3.317 | 3.712 | ms | 1.612 | 5.406 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:400e:ea00:ccfe:ba34:7215:d4f6 | 0.000 | 0.859 | 1.303 | 3.227 | 14.318 | 24.304 | 43.492 | 13.015 | 23.445 | 5.129 | 4.743 | ms | 4.134 | 25.63 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:6:b900:6b54:1390:4afd:814a | 0.000 | 0.000 | 0.000 | 4.457 | 16.191 | 16.191 | 16.191 | 16.191 | 16.191 | 4.707 | 5.327 | ms | 0.744 | 2.635 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c020:6:b900:ed2f:b442:fee7:d9b9 | 0.000 | 0.000 | 0.000 | 2.967 | 6.929 | 6.929 | 6.929 | 6.929 | 6.929 | 2.490 | 2.410 | ms | 0.6756 | 2.153 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c024:c005:a600:8eb1:2863:5838:9880 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | ns | nan | nan | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2603:c024:c005:a600:efb6:d213:cad8:251d | 0.000 | 0.000 | 0.000 | 14.820 | 57.595 | 57.595 | 57.595 | 57.595 | 57.595 | 17.229 | 20.244 | ms | 1.209 | 3.457 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:180:f3::4a4 (dutch.arpnet.net) | 0.000 | 0.000 | 0.000 | 1.362 | 4.226 | 4.226 | 4.226 | 4.226 | 4.226 | 1.566 | 1.904 | ms | 0.4456 | 1.597 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 | 0.000 | 0.000 | 1.769 | 15.711 | 48.002 | 49.094 | 49.094 | 46.233 | 49.094 | 11.410 | 15.959 | ms | 1.156 | 4.594 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:2dc0:100:4d6:: | 0.000 | 0.000 | 0.000 | 3.514 | 4.351 | 4.351 | 4.351 | 4.351 | 4.351 | 1.632 | 2.616 | ms | -0.6871 | 1.99 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) | 0.000 | 1.045 | 1.533 | 3.726 | 22.901 | 53.226 | 197.927 | 21.368 | 52.181 | 12.375 | 7.465 | ms | 8.524 | 115.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:2dc0:202:300::140d (ovh.maxhost.io) | 0.000 | 0.965 | 1.366 | 3.498 | 9.087 | 21.237 | 71.985 | 7.721 | 20.272 | 3.773 | 4.317 | ms | 5.523 | 60.29 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) | 0.000 | 0.906 | 1.363 | 3.338 | 10.703 | 34.136 | 119.042 | 9.340 | 33.230 | 6.208 | 4.661 | ms | 7.131 | 78.29 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:4300:a:299::164 | 0.000 | 0.000 | 0.000 | 3.582 | 6.183 | 11.304 | 11.304 | 6.183 | 11.304 | 2.417 | 3.650 | ms | 1.209 | 5.485 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) | 0.000 | 0.000 | 0.000 | 3.639 | 13.829 | 13.829 | 13.829 | 13.829 | 13.829 | 3.432 | 4.353 | ms | 1.336 | 4.939 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) | 0.000 | 0.000 | 0.000 | 21.487 | 31.405 | 31.405 | 31.405 | 31.405 | 31.405 | 13.108 | 17.631 | ms | -0.4158 | 1.5 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) | 0.000 | 0.000 | 0.000 | 0.869 | 1.657 | 1.657 | 1.657 | 1.657 | 1.657 | 0.479 | 0.845 | ms | -0.09905 | 2.996 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) | 0.000 | 0.965 | 1.447 | 3.716 | 18.849 | 29.446 | 120.523 | 17.402 | 28.481 | 10.597 | 5.665 | ms | 8.209 | 79.46 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) | 0.000 | 0.000 | 0.000 | 8.010 | 25.574 | 25.574 | 25.574 | 25.574 | 25.574 | 6.576 | 8.369 | ms | 0.7283 | 3.152 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2604:a880:800:a1::ec9:5001 | 0.000 | 0.000 | 0.000 | 3.038 | 144.987 | 144.987 | 144.987 | 144.987 | 144.987 | 40.690 | 27.266 | ms | 1.51 | 4.267 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2605:4840:3:fb19::1 (chi3.us.ntp.li) | 0.000 | 3.032 | 6.591 | 21.939 | 58.467 | 76.100 | 242.923 | 51.875 | 73.068 | 18.011 | 25.799 | ms | 3.949 | 40.23 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | ns | nan | nan | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2605:6400:488d:3686:546d:c03c:1689:20c | 0.000 | 0.000 | 0.000 | 1.372 | 9.116 | 9.116 | 9.116 | 9.116 | 9.116 | 3.886 | 3.057 | ms | 0.6883 | 1.57 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2605:6400:84e1::123 (oldtime3.sigi.net) | 0.000 | 0.812 | 1.378 | 3.695 | 19.761 | 29.574 | 60.134 | 18.383 | 28.763 | 6.442 | 6.210 | ms | 2.693 | 13.31 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) | 0.000 | 0.000 | 0.000 | 3.793 | 7.878 | 7.878 | 7.878 | 7.878 | 7.878 | 2.024 | 4.070 | ms | 0.0771 | 3.251 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2606:4700:f1::1 (time.cloudflare.com) | 0.000 | 0.880 | 1.332 | 3.435 | 17.260 | 44.212 | 400.941 | 15.928 | 43.332 | 10.385 | 5.565 | ms | 13.94 | 349.8 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2606:4700:f1::123 (time.cloudflare.com) | 0.000 | 0.872 | 1.300 | 3.388 | 15.212 | 42.335 | 198.701 | 13.912 | 41.464 | 8.326 | 5.194 | ms | 8.666 | 117.4 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2606:82c0:21::e (time1.lshiy.com) | 0.000 | 0.000 | 0.000 | 16.075 | 42.362 | 42.362 | 42.362 | 42.362 | 42.362 | 15.446 | 17.687 | ms | 0.3682 | 1.594 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2606:82c0:22::e (time2.lshiy.com) | 0.000 | 0.000 | 0.000 | 5.690 | 24.843 | 24.843 | 24.843 | 24.843 | 24.843 | 7.304 | 7.682 | ms | 1.18 | 3.539 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2606:82c0:23::e (time3.lshiy.com) | 0.000 | 0.000 | 0.000 | 3.263 | 8.248 | 8.248 | 8.248 | 8.248 | 8.248 | 2.337 | 3.284 | ms | 0.2294 | 2.606 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2606:8fc0::9 (farmhand.gac.edu) | 0.000 | 0.823 | 1.320 | 3.357 | 18.249 | 30.285 | 37.736 | 16.930 | 29.461 | 5.445 | 4.927 | ms | 3.33 | 15.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:5600:182:500::1 (ntp-1.jonlight.com) | 0.000 | 0.000 | 0.000 | 10.156 | 45.021 | 45.021 | 45.021 | 45.021 | 45.021 | 12.499 | 11.485 | ms | 1.431 | 4.572 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:7c80:54:3::32 | 0.000 | 0.899 | 1.412 | 3.457 | 14.925 | 33.748 | 127.511 | 13.513 | 32.849 | 6.683 | 5.030 | ms | 6.948 | 78.13 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:7c80:54:3::56 (owners.kjsl.com) | 0.000 | 0.000 | 1.298 | 3.181 | 22.900 | 24.794 | 24.794 | 21.602 | 24.794 | 5.837 | 5.520 | ms | 2.225 | 7.106 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:9000:7000:23:216:3cff:fe25:38d7 | 0.000 | 0.598 | 1.211 | 3.188 | 11.275 | 18.776 | 101.037 | 10.064 | 18.178 | 7.917 | 4.641 | ms | 9.393 | 106.3 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:9d00:2000:16::9269:208a | 0.000 | 0.000 | 0.000 | 14.156 | 32.768 | 32.768 | 32.768 | 32.768 | 32.768 | 13.320 | 17.348 | ms | 0.07984 | 1.353 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:b500:410:7700::1 | 0.000 | 0.000 | 0.000 | 3.930 | 45.349 | 48.813 | 48.813 | 45.349 | 48.813 | 11.282 | 7.651 | ms | 2.727 | 9.768 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f014:9e00::1 | 0.000 | 0.000 | 0.000 | 4.356 | 10.370 | 10.370 | 10.370 | 10.370 | 10.370 | 2.391 | 5.036 | ms | 0.1939 | 4.09 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f014:9e00::2 | 0.000 | 0.000 | 0.000 | 4.033 | 19.038 | 31.195 | 31.195 | 19.038 | 31.195 | 7.047 | 6.391 | ms | 1.868 | 6.607 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f047:8400::1 (xmpp.party) | 0.000 | 0.000 | 0.000 | 2.160 | 5.723 | 5.723 | 5.723 | 5.723 | 5.723 | 2.360 | 2.628 | ms | 0.2895 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f04e:fd00::1 | 0.000 | 0.000 | 0.000 | 4.264 | 7.362 | 7.362 | 7.362 | 7.362 | 7.362 | 2.269 | 3.950 | ms | -0.238 | 2.144 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 3.311 | 58.981 | 58.981 | 58.981 | 58.981 | 58.981 | 21.215 | 11.609 | ms | 1.777 | 4.18 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 2.496 | 6.975 | 6.975 | 6.975 | 6.975 | 6.975 | 2.053 | 2.689 | ms | 0.7637 | 2.799 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 0.000 | 1.285 | 1.285 | 1.285 | 1.285 | 1.285 | 0.606 | 0.428 | ms | 0.7071 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 18.803 | 82.310 | 82.310 | 82.310 | 82.310 | 82.310 | 18.917 | 21.241 | ms | 1.617 | 5.891 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 3.713 | 17.103 | 17.166 | 17.166 | 17.103 | 17.166 | 4.236 | 4.518 | ms | 1.905 | 6.172 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f06d:f200::1 | 0.000 | 0.000 | 0.000 | 13.001 | 14.124 | 14.124 | 14.124 | 14.124 | 14.124 | 5.551 | 9.074 | ms | -0.8153 | 2.019 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f1c0:f075:9900::1 | 0.000 | 0.000 | 0.000 | 2.615 | 9.511 | 9.511 | 9.511 | 9.511 | 9.511 | 2.632 | 3.371 | ms | 1.055 | 3.399 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f298:5:101d:f816:3eff:fefd:8817 | 0.000 | 0.000 | 0.000 | 3.238 | 15.794 | 15.794 | 15.794 | 15.794 | 15.794 | 3.672 | 4.170 | ms | 1.423 | 5.487 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f3c8:3803:1::6 | 0.000 | 0.000 | 0.000 | 3.665 | 9.888 | 9.888 | 9.888 | 9.888 | 9.888 | 3.130 | 3.728 | ms | 0.7664 | 2.592 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) | 0.000 | 0.000 | 0.000 | 7.826 | 42.881 | 42.881 | 42.881 | 42.881 | 42.881 | 11.996 | 12.673 | ms | 0.9758 | 3.228 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) | 0.000 | 0.000 | 0.000 | 2.953 | 7.543 | 7.543 | 7.543 | 7.543 | 7.543 | 1.917 | 3.128 | ms | 0.7412 | 3.627 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:f710:35::29c:0:8 | 0.000 | 0.993 | 1.374 | 7.413 | 35.124 | 57.993 | 80.866 | 33.750 | 57.000 | 11.814 | 11.251 | ms | 2.307 | 10.35 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) | 0.000 | 0.000 | 1.354 | 3.620 | 17.136 | 24.570 | 151.167 | 15.782 | 24.570 | 12.993 | 6.037 | ms | 9.835 | 109.2 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:ff50:0:1a::20 (ntpool1.603.newcontinuum.net) | 0.000 | 1.124 | 1.413 | 3.785 | 21.590 | 37.597 | 46.508 | 20.178 | 36.474 | 6.962 | 5.709 | ms | 3.417 | 14.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com) | 0.000 | 0.000 | 0.000 | 1.304 | 6.107 | 6.107 | 6.107 | 6.107 | 6.107 | 2.114 | 2.122 | ms | 1.095 | 2.75 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com) | 0.000 | 0.850 | 1.305 | 3.226 | 9.081 | 20.463 | 88.888 | 7.777 | 19.613 | 6.010 | 4.299 | ms | 9.492 | 117.8 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com) | 0.000 | 1.030 | 1.385 | 3.505 | 11.942 | 27.673 | 108.020 | 10.557 | 26.644 | 5.728 | 4.753 | ms | 8.065 | 109.2 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:6:2000:104::48 (excalibur.prolixium.com) | 0.000 | 0.000 | 2.622 | 12.553 | 39.943 | 40.439 | 40.439 | 37.321 | 40.439 | 11.586 | 13.847 | ms | 1.25 | 3.545 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:83:8000:140::b (tic.lbl.gov) | 0.000 | 0.880 | 1.380 | 3.683 | 18.060 | 54.396 | 107.171 | 16.680 | 53.516 | 8.265 | 5.655 | ms | 5.524 | 41.14 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:83:8000:140::c (toc.lbl.gov) | 0.000 | 1.106 | 1.584 | 3.636 | 9.935 | 22.754 | 23.037 | 8.351 | 21.648 | 3.401 | 4.570 | ms | 2.971 | 15.07 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:8d:c000::f (blotch.image1tech.net) | 0.000 | 0.000 | 0.000 | 11.399 | 23.001 | 23.001 | 23.001 | 23.001 | 23.001 | 6.886 | 11.933 | ms | -0.1456 | 2.635 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) | 0.000 | 0.000 | 0.000 | 4.268 | 26.331 | 26.331 | 26.331 | 26.331 | 26.331 | 6.810 | 6.258 | ms | 1.9 | 6.02 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:b0:2000:102::1:123 (time-h.den.codehof.net) | 0.000 | 0.000 | 0.000 | 44.659 | 162.644 | 162.644 | 162.644 | 162.644 | 162.644 | 50.617 | 46.606 | ms | 1.096 | 3.207 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2620:b0:2000:102::2:123 (time-he.den.codehof.net) | 0.000 | 0.000 | 0.000 | 5.132 | 67.520 | 67.520 | 67.520 | 67.520 | 67.520 | 21.171 | 12.422 | ms | 2.131 | 5.771 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) | 0.000 | 3.102 | 10.574 | 51.882 | 98.388 | 112.804 | 271.797 | 87.814 | 109.702 | 26.577 | 53.021 | ms | 0.3589 | 3.418 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) | 0.000 | 2.597 | 7.095 | 49.586 | 96.418 | 109.785 | 234.358 | 89.323 | 107.188 | 26.910 | 50.228 | ms | 0.2493 | 2.738 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2a01:4ff:1f0:c33f::1 | 0.715 | 0.995 | 1.297 | 3.029 | 8.683 | 38.764 | 93.092 | 7.386 | 37.769 | 7.222 | 4.284 | ms | 8.873 | 96.72 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2a01:4ff:f0:e33b::1 | 0.000 | 0.947 | 1.569 | 3.545 | 15.711 | 44.810 | 56.968 | 14.143 | 43.863 | 7.049 | 5.515 | ms | 4.531 | 27.82 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2a01:4ff:f0:ebce::1 (zero.txryan.com) | 0.000 | 0.000 | 0.000 | 25.847 | 25.847 | 25.847 | 25.847 | 25.847 | 25.847 | 12.924 | 12.924 | ms | 0 | 1 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) | 0.000 | 0.000 | 0.000 | 32.068 | 70.288 | 70.288 | 70.288 | 70.288 | 70.288 | 19.572 | 34.261 | ms | 0.1428 | 3.002 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) | 0.000 | 0.704 | 1.300 | 3.254 | 8.736 | 20.805 | 38.483 | 7.436 | 20.101 | 3.869 | 4.053 | ms | 4.955 | 35.18 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 38.81.211.177 | 0.000 | 0.000 | 0.000 | 2.318 | 3.899 | 3.899 | 3.899 | 3.899 | 3.899 | 1.177 | 2.044 | ms | -0.2148 | 2.563 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 44.190.5.123 | 0.000 | 0.806 | 1.180 | 3.163 | 12.299 | 25.128 | 625.327 | 11.119 | 24.321 | 9.581 | 4.586 | ms | 37.95 | 2277 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.33.53.84 | 0.000 | 0.797 | 1.151 | 2.983 | 8.003 | 17.186 | 26.784 | 6.852 | 16.388 | 2.964 | 3.630 | ms | 4.203 | 28.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.55.126.202 | 0.000 | 0.865 | 1.268 | 3.641 | 19.337 | 43.121 | 76.922 | 18.069 | 42.255 | 8.466 | 6.840 | ms | 3.775 | 22.63 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.55.58.103 | 0.000 | 0.000 | 3.600 | 14.076 | 49.919 | 53.742 | 53.742 | 46.319 | 53.742 | 15.712 | 19.196 | ms | 0.8351 | 2.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.61.187.39 | 0.000 | 0.000 | 0.000 | 6.005 | 10.131 | 10.131 | 10.131 | 10.131 | 10.131 | 3.234 | 5.663 | ms | -0.1351 | 2.072 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.63.54.13 | 0.000 | 0.750 | 1.267 | 3.451 | 16.818 | 30.433 | 69.818 | 15.550 | 29.683 | 6.186 | 5.088 | ms | 4.745 | 33.4 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.79.35.159 | 0.000 | 0.000 | 0.000 | 0.712 | 4.702 | 4.702 | 4.702 | 4.702 | 4.702 | 1.855 | 1.527 | ms | 1.069 | 2.278 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.79.51.42 | 0.000 | 0.000 | 0.000 | 11.729 | 96.151 | 96.151 | 96.151 | 96.151 | 96.151 | 29.987 | 22.678 | ms | 1.636 | 4.376 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.83.234.123 | 0.000 | 0.000 | 0.000 | 38.377 | 69.832 | 100.538 | 100.538 | 69.832 | 100.538 | 25.273 | 34.042 | ms | 0.07115 | 2.108 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 45.84.199.136 | 0.000 | 0.000 | 0.000 | 7.227 | 34.845 | 34.845 | 34.845 | 34.845 | 34.845 | 11.450 | 10.051 | ms | 1.254 | 3.184 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 46.37.96.107 | 0.000 | 0.762 | 1.136 | 3.173 | 17.249 | 45.839 | 76.855 | 16.113 | 45.077 | 7.508 | 5.080 | ms | 4.938 | 32.2 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 5.161.111.190 | 0.000 | 0.953 | 1.350 | 3.302 | 16.344 | 28.113 | 46.484 | 14.994 | 27.160 | 5.641 | 5.310 | ms | 3.199 | 16.81 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 5.78.62.36 | 0.000 | 0.814 | 1.189 | 3.214 | 7.458 | 14.625 | 17.905 | 6.268 | 13.811 | 2.404 | 3.674 | ms | 2.621 | 12.87 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 50.117.3.52 | 0.000 | 0.000 | 0.000 | 1.241 | 1.948 | 1.948 | 1.948 | 1.948 | 1.948 | 0.616 | 1.028 | ms | -0.1887 | 2.181 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 50.117.3.95 | 0.000 | 0.000 | 0.000 | 4.938 | 9.600 | 9.600 | 9.600 | 9.600 | 9.600 | 3.585 | 4.705 | ms | -0.06002 | 1.66 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 50.205.57.38 | 0.000 | 0.902 | 1.257 | 3.354 | 19.270 | 37.488 | 52.487 | 18.013 | 36.586 | 7.068 | 6.193 | ms | 2.927 | 14.35 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 50.218.103.254 | 0.000 | 0.000 | 0.000 | 8.493 | 18.950 | 22.640 | 22.640 | 18.950 | 22.640 | 6.893 | 8.251 | ms | 0.2712 | 1.803 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 51.81.20.76 | 0.000 | 0.000 | 0.000 | 2.794 | 18.439 | 18.439 | 18.439 | 18.439 | 18.439 | 4.702 | 4.747 | ms | 2.128 | 6.656 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 51.81.226.229 | 0.000 | 0.000 | 0.000 | 4.457 | 13.199 | 16.706 | 16.706 | 13.199 | 16.706 | 3.893 | 5.097 | ms | 1.296 | 4.495 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 64.142.54.12 | 0.000 | 0.000 | 0.000 | 4.301 | 11.521 | 11.521 | 11.521 | 11.521 | 11.521 | 2.947 | 4.784 | ms | 0.8351 | 3.574 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 64.6.144.6 | 0.000 | 0.000 | 1.245 | 3.287 | 10.197 | 18.416 | 26.199 | 8.952 | 18.416 | 3.211 | 3.974 | ms | 3.158 | 16.39 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 64.79.100.197 | 0.000 | 0.000 | 0.817 | 2.208 | 16.989 | 29.767 | 29.820 | 16.172 | 29.767 | 5.117 | 3.706 | ms | 3.407 | 14.88 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 65.100.46.164 | 0.000 | 0.902 | 1.495 | 3.180 | 12.652 | 17.404 | 21.093 | 11.158 | 16.502 | 3.401 | 4.380 | ms | 2.274 | 8.459 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 65.100.46.166 | 0.000 | 0.877 | 1.365 | 3.588 | 16.248 | 25.653 | 30.128 | 14.883 | 24.777 | 4.652 | 4.994 | ms | 2.701 | 11.07 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 65.182.224.39 | 0.000 | 0.000 | 0.000 | 2.070 | 2.943 | 2.943 | 2.943 | 2.943 | 2.943 | 0.933 | 1.809 | ms | -0.8566 | 2.777 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 66.118.229.14 | 0.000 | 0.000 | 0.000 | 3.453 | 3.453 | 3.453 | 3.453 | 3.453 | 3.453 | 1.727 | 1.727 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 66.118.230.14 | 0.000 | 0.000 | 0.000 | 4.746 | 14.826 | 14.826 | 14.826 | 14.826 | 14.826 | 6.182 | 6.524 | ms | 0.4076 | 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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 66.118.231.14 | 0.000 | 0.000 | 1.373 | 34.816 | 55.552 | 77.497 | 77.497 | 54.179 | 77.497 | 19.015 | 31.982 | ms | -0.09999 | 2.355 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 66.42.71.197 | 0.000 | 0.804 | 1.223 | 3.207 | 11.673 | 20.952 | 36.891 | 10.450 | 20.148 | 3.804 | 4.239 | ms | 3.293 | 17.16 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 66.59.198.94 | 0.000 | 0.000 | 0.000 | 4.307 | 12.760 | 12.760 | 12.760 | 12.760 | 12.760 | 3.136 | 4.798 | ms | 1.209 | 4.406 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 66.85.78.80 | 0.000 | 0.710 | 1.266 | 3.085 | 24.810 | 104.082 | 110.853 | 23.544 | 103.372 | 13.847 | 7.360 | ms | 4.933 | 32.11 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 67.217.240.178 | 0.000 | 0.000 | 0.000 | 3.911 | 8.284 | 8.284 | 8.284 | 8.284 | 8.284 | 2.440 | 3.645 | ms | 0.07159 | 2.595 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 67.217.246.127 | 0.000 | 0.544 | 1.405 | 3.301 | 20.244 | 36.524 | 37.261 | 18.839 | 35.979 | 7.198 | 6.206 | ms | 2.642 | 10.4 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 67.217.246.204 | 0.000 | 0.000 | 1.357 | 5.632 | 21.877 | 32.520 | 37.970 | 20.520 | 32.520 | 7.317 | 8.853 | ms | 1.244 | 4.444 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 68.234.48.70 | 0.000 | 0.000 | 0.000 | 15.255 | 37.426 | 37.426 | 37.426 | 37.426 | 37.426 | 11.694 | 11.915 | ms | 0.673 | 2.554 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 69.48.203.16 | 0.000 | 0.000 | 0.000 | 2.915 | 5.617 | 5.617 | 5.617 | 5.617 | 5.617 | 1.492 | 2.928 | ms | -0.1583 | 2.911 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 69.89.207.199 | 0.000 | 0.891 | 1.620 | 3.855 | 12.202 | 28.244 | 103.870 | 10.582 | 27.353 | 8.861 | 5.489 | ms | 9.201 | 98.89 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 69.89.207.99 | 0.000 | 0.731 | 1.075 | 2.902 | 14.207 | 29.139 | 217.779 | 13.132 | 28.408 | 10.138 | 4.919 | ms | 14.31 | 275.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 71.123.46.186 | 0.000 | 0.798 | 1.369 | 11.462 | 50.388 | 59.457 | 63.511 | 49.020 | 58.659 | 13.810 | 13.720 | ms | 1.912 | 6.345 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 71.19.144.140 | 0.000 | 0.000 | 0.000 | 2.244 | 28.288 | 28.288 | 28.288 | 28.288 | 28.288 | 6.176 | 4.071 | ms | 3.331 | 13.18 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 72.14.183.39 | 0.000 | 0.942 | 1.271 | 2.876 | 12.455 | 20.388 | 26.598 | 11.184 | 19.446 | 3.773 | 3.910 | ms | 3.136 | 14.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 72.14.186.59 | 0.000 | 0.000 | 0.000 | 1.353 | 7.812 | 7.812 | 7.812 | 7.812 | 7.812 | 2.791 | 2.333 | ms | 1.36 | 3.086 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 72.30.35.89 | 0.000 | 0.000 | 0.000 | 0.779 | 4.898 | 4.898 | 4.898 | 4.898 | 4.898 | 2.149 | 1.892 | ms | 0.6381 | 1.5 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 72.46.53.234 | 0.000 | 0.000 | 0.000 | 3.818 | 99.485 | 99.485 | 99.485 | 99.485 | 99.485 | 27.363 | 16.024 | ms | 2.181 | 6.785 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 72.46.61.205 | 0.000 | 0.000 | 0.000 | 41.508 | 79.056 | 79.056 | 79.056 | 79.056 | 79.056 | 23.710 | 34.029 | ms | -0.07087 | 1.973 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 73.185.182.209 | 0.000 | 1.188 | 1.697 | 3.815 | 25.345 | 43.709 | 79.900 | 23.648 | 42.521 | 9.600 | 8.061 | ms | 2.934 | 14.97 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 73.65.80.137 | 0.000 | 0.000 | 1.979 | 4.758 | 26.082 | 30.271 | 30.271 | 24.103 | 30.271 | 7.745 | 8.134 | ms | 1.314 | 3.612 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 74.119.243.5 | 0.000 | 0.000 | 0.000 | 3.388 | 6.563 | 6.563 | 6.563 | 6.563 | 6.563 | 2.635 | 2.597 | ms | 0.4823 | 1.635 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 74.208.117.38 | 0.000 | 0.000 | 0.000 | 5.816 | 17.030 | 17.030 | 17.030 | 17.030 | 17.030 | 4.139 | 6.213 | ms | 1.416 | 5.194 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 74.208.14.149 | 0.000 | 0.000 | 0.000 | 8.875 | 13.149 | 13.149 | 13.149 | 13.149 | 13.149 | 4.272 | 6.919 | ms | -0.2182 | 2.001 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 74.208.25.46 | 0.000 | 1.565 | 2.194 | 4.573 | 14.163 | 52.935 | 406.747 | 11.968 | 51.370 | 15.638 | 6.943 | ms | 15.57 | 327 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 83.147.242.172 | 0.000 | 0.865 | 1.203 | 3.118 | 8.571 | 19.379 | 60.098 | 7.369 | 18.514 | 3.741 | 3.896 | ms | 6.442 | 69.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.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 99.28.14.242 | 0.000 | 0.847 | 1.309 | 3.374 | 21.044 | 61.650 | 143.840 | 19.736 | 60.804 | 10.772 | 6.757 | ms | 5.713 | 49.82 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SHM(0) | 0.000 | 0.000 | 0.001 | 0.001 | 0.078 | 0.493 | 6.177 | 0.077 | 0.493 | 0.096 | 0.019 | s | 18.82 | 846.6 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SHM(1) | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.724 | 6.000 | 0.000 | 0.724 | 0.114 | 0.017 | s | 12.3 | 342.8 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SHM(2) | 0.000 | 0.596 | 0.974 | 22.845 | 63.079 | 96.454 | 477.593 | 62.105 | 95.858 | 22.843 | 25.694 | ms | 1.494 | 7.776 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SHM(3) | 0.000 | 0.053 | 0.073 | 0.253 | 0.779 | 1.033 | 12.858 | 0.706 | 0.980 | 0.254 | 0.313 | ms | 5.463 | 140.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SOCK(0) | 0.000 | 0.451 | 0.658 | 1.622 | 4.097 | 7.521 | 199.488 | 3.438 | 7.070 | 2.193 | 1.979 | ms | 33.87 | 2074 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SOCK(1) | 0.000 | 0.202 | 0.228 | 0.344 | 0.696 | 0.956 | 104.304 | 0.469 | 0.754 | 0.542 | 0.389 | ms | 122 | 1.84e+04 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SOCK(2) | 0.000 | 0.600 | 0.948 | 2.374 | 5.637 | 7.241 | 11.212 | 4.689 | 6.641 | 1.481 | 2.715 | ms | 1.233 | 5.001 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SOCK(3) | 0.000 | 0.196 | 0.221 | 0.324 | 0.536 | 0.729 | 3,009.547 | 0.315 | 0.533 | 17.171 | 0.461 | ms | 152.2 | 2.388e+04 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Frequency Offset | -15.474 | 2.971 | 4.767 | 10.911 | 18.938 | 23.575 | 61.826 | 14.171 | 20.604 | 3.581 | 10.960 | ppm | 1.181 | 7.21 | ||
| Local Clock Time Offset | -95.988 | -4.517 | -0.732 | -0.035 | 0.645 | 1.136 | 105.238 | 1.376 | 5.652 | 1.019 | -0.116 | ms | 0.622 | 1711 | ||
| Local RMS Frequency Jitter | 0.0000 | 0.0033 | 0.0041 | 0.0139 | 2.576 | 3.626 | 21.113 | 2.572 | 3.622 | 0.869 | 0.466 | ppm | 2.308 | 10.56 | ||
| Local RMS Time Jitter | 0.000 | 0.093 | 0.115 | 0.325 | 0.828 | 1.326 | 52.058 | 0.713 | 1.233 | 0.424 | 0.370 | ms | 47.34 | 4303 | ||
| Server Jitter 104.131.155.175 | 0.000 | 0.000 | 0.000 | 3.656 | 17.731 | 18.171 | 18.171 | 17.731 | 18.171 | 4.618 | 5.158 | ms | 1.714 | 5.382 | ||
| Server Jitter 104.152.220.5 | 0.000 | 0.000 | 0.000 | 1.578 | 3.071 | 3.071 | 3.071 | 3.071 | 3.071 | 0.957 | 1.621 | ms | -0.1526 | 2.323 | ||
| Server Jitter 104.167.215.195 | 0.000 | 0.000 | 1.736 | 5.117 | 35.856 | 66.707 | 67.627 | 34.119 | 66.707 | 12.331 | 8.977 | ms | 3.401 | 14.81 | ||
| Server Jitter 104.167.241.253 | 0.000 | 0.000 | 0.000 | 2.362 | 8.036 | 8.036 | 8.036 | 8.036 | 8.036 | 2.290 | 2.983 | ms | 0.6267 | 2.554 | ||
| Server Jitter 104.234.61.117 | 0.000 | 0.842 | 1.258 | 3.320 | 13.812 | 22.021 | 62.066 | 12.553 | 21.179 | 4.667 | 4.606 | ms | 4.224 | 29.96 | ||
| Server Jitter 108.181.201.22 | 0.000 | 0.000 | 0.000 | 5.514 | 12.431 | 12.431 | 12.431 | 12.431 | 12.431 | 3.786 | 5.054 | ms | 0.5181 | 2.09 | ||
| Server Jitter 108.59.2.24 | 0.000 | 0.000 | 0.000 | 2.687 | 4.534 | 4.534 | 4.534 | 4.534 | 4.534 | 1.862 | 2.407 | ms | -0.2221 | 1.5 | ||
| Server Jitter 108.61.215.221 | 0.000 | 0.650 | 1.101 | 3.005 | 15.157 | 28.430 | 54.452 | 14.056 | 27.780 | 5.946 | 4.747 | ms | 4.248 | 27.48 | ||
| Server Jitter 108.61.56.35 | 0.000 | 0.000 | 0.000 | 2.555 | 4.944 | 4.944 | 4.944 | 4.944 | 4.944 | 1.407 | 2.414 | ms | -0.1572 | 2.553 | ||
| Server Jitter 108.61.73.243 | 0.000 | 0.907 | 1.559 | 10.783 | 44.654 | 63.282 | 117.163 | 43.095 | 62.375 | 14.580 | 14.492 | ms | 2.088 | 8.9 | ||
| Server Jitter 12.205.28.193 | 0.000 | 0.893 | 1.308 | 3.371 | 17.565 | 41.353 | 240.147 | 16.257 | 40.460 | 13.847 | 5.912 | ms | 11.77 | 168.2 | ||
| Server Jitter 12.71.198.242 | 0.000 | 0.000 | 0.000 | 2.476 | 14.247 | 14.247 | 14.247 | 14.247 | 14.247 | 4.389 | 3.547 | ms | 1.44 | 4.115 | ||
| Server Jitter 129.146.193.200 | 0.000 | 0.590 | 1.131 | 3.244 | 17.511 | 33.383 | 70.718 | 16.380 | 32.793 | 6.398 | 4.966 | ms | 4.738 | 34.45 | ||
| Server Jitter 131.153.171.250 | 0.000 | 0.000 | 0.000 | 0.763 | 4.308 | 4.308 | 4.308 | 4.308 | 4.308 | 1.877 | 1.690 | ms | 0.6205 | 1.5 | ||
| Server Jitter 131.239.5.43 | 0.000 | 0.000 | 0.000 | 1.655 | 3.135 | 3.135 | 3.135 | 3.135 | 3.135 | 0.882 | 1.743 | ms | -0.2966 | 2.893 | ||
| Server Jitter 135.148.100.14 | 0.000 | 0.923 | 1.623 | 14.224 | 55.544 | 71.155 | 96.799 | 53.922 | 70.232 | 15.396 | 16.541 | ms | 1.978 | 8.077 | ||
| Server Jitter 137.110.222.27 | 0.000 | 0.932 | 1.375 | 3.330 | 15.276 | 22.565 | 61.468 | 13.901 | 21.633 | 5.668 | 4.627 | ms | 6.016 | 52.38 | ||
| Server Jitter 137.190.2.4 | 0.000 | 0.000 | 0.000 | 1.069 | 2.723 | 2.723 | 2.723 | 2.723 | 2.723 | 1.044 | 1.057 | ms | 0.5061 | 1.605 | ||
| Server Jitter 139.177.202.26 | 0.000 | 0.000 | 0.000 | 1.560 | 6.528 | 6.528 | 6.528 | 6.528 | 6.528 | 1.992 | 1.908 | ms | 1.039 | 3.07 | ||
| Server Jitter 139.94.144.123 | 0.000 | 0.000 | 0.000 | 1.501 | 2.945 | 2.945 | 2.945 | 2.945 | 2.945 | 1.260 | 1.529 | ms | 0.002279 | 1.271 | ||
| Server Jitter 141.11.234.198 | 0.000 | 0.000 | 0.000 | 8.942 | 58.361 | 58.361 | 58.361 | 58.361 | 58.361 | 19.957 | 16.134 | ms | 1.387 | 3.303 | ||
| Server Jitter 141.11.89.193 | 0.000 | 0.000 | 0.000 | 1.558 | 2.015 | 2.015 | 2.015 | 2.015 | 2.015 | 0.652 | 1.474 | ms | -1.441 | 3.889 | ||
| Server Jitter 142.202.190.19 | 0.000 | 0.000 | 0.000 | 2.175 | 6.985 | 16.409 | 16.409 | 6.985 | 16.409 | 3.192 | 2.973 | ms | 2.438 | 10.54 | ||
| Server Jitter 143.42.229.154 | 0.000 | 0.761 | 1.401 | 5.355 | 36.230 | 71.873 | 89.094 | 34.829 | 71.112 | 13.059 | 10.927 | ms | 2.601 | 11.68 | ||
| Server Jitter 144.202.0.197 | 0.000 | 0.000 | 0.000 | 2.470 | 4.307 | 4.307 | 4.307 | 4.307 | 4.307 | 1.435 | 2.296 | ms | -0.2563 | 1.847 | ||
| Server Jitter 144.202.66.214 | 0.000 | 0.000 | 0.000 | 3.268 | 3.564 | 3.564 | 3.564 | 3.564 | 3.564 | 1.326 | 2.411 | ms | -0.873 | 2.102 | ||
| Server Jitter 148.135.119.56 | 0.000 | 0.920 | 1.304 | 3.191 | 12.314 | 24.154 | 205.114 | 11.011 | 23.234 | 7.147 | 4.555 | ms | 16.37 | 414.4 | ||
| Server Jitter 149.248.12.167 | 0.000 | 0.000 | 0.000 | 1.415 | 6.547 | 6.547 | 6.547 | 6.547 | 6.547 | 2.701 | 2.851 | ms | 0.3599 | 1.282 | ||
| Server Jitter 149.28.200.179 | 0.000 | 0.000 | 1.448 | 3.887 | 18.634 | 19.531 | 19.531 | 17.186 | 19.531 | 5.389 | 6.126 | ms | 1.504 | 3.906 | ||
| Server Jitter 149.28.61.105 | 0.000 | 0.000 | 0.000 | 2.466 | 4.280 | 4.280 | 4.280 | 4.280 | 4.280 | 1.264 | 2.154 | ms | -0.03175 | 2.746 | ||
| Server Jitter 15.204.198.96 | 0.000 | 0.000 | 1.528 | 9.635 | 18.188 | 24.740 | 24.740 | 16.661 | 24.740 | 6.496 | 9.205 | ms | 0.2143 | 1.632 | ||
| Server Jitter 15.204.87.223 | 0.000 | 0.000 | 1.093 | 3.116 | 14.025 | 23.083 | 37.321 | 12.932 | 23.083 | 4.456 | 4.482 | ms | 3.12 | 16.52 | ||
| Server Jitter 152.70.159.102 | 0.257 | 0.811 | 1.110 | 2.906 | 7.178 | 8.346 | 9.641 | 6.068 | 7.535 | 1.765 | 3.259 | ms | 1.066 | 3.889 | ||
| Server Jitter 158.51.134.123 | 0.000 | 0.801 | 1.375 | 4.189 | 72.788 | 183.366 | 259.136 | 71.413 | 182.565 | 32.046 | 14.704 | ms | 4.273 | 24.03 | ||
| Server Jitter 158.51.99.19 | 0.000 | 0.861 | 1.216 | 3.317 | 19.810 | 51.816 | 228.673 | 18.594 | 50.955 | 13.195 | 6.155 | ms | 10.51 | 149.8 | ||
| Server Jitter 162.159.200.1 | 0.000 | 0.595 | 1.140 | 3.020 | 13.359 | 21.989 | 98.350 | 12.219 | 21.395 | 5.104 | 4.291 | ms | 7.845 | 117.5 | ||
| Server Jitter 162.159.200.123 | 0.000 | 0.000 | 0.000 | 3.085 | 9.842 | 12.427 | 12.427 | 9.842 | 12.427 | 2.969 | 3.852 | ms | 1.147 | 3.88 | ||
| Server Jitter 163.123.152.14 | 0.000 | 0.000 | 0.000 | 3.728 | 4.357 | 4.357 | 4.357 | 4.357 | 4.357 | 1.674 | 2.791 | ms | -0.9099 | 2.151 | ||
| Server Jitter 168.61.215.74 | 0.000 | 0.494 | 1.143 | 3.432 | 10.228 | 15.888 | 22.601 | 9.085 | 15.395 | 3.074 | 4.248 | ms | 2.002 | 9.176 | ||
| Server Jitter 170.187.147.56 | 0.000 | 0.824 | 1.119 | 3.127 | 15.294 | 35.711 | 154.182 | 14.175 | 34.886 | 9.178 | 5.070 | ms | 11.83 | 185.3 | ||
| Server Jitter 172.233.157.223 | 0.000 | 0.000 | 0.000 | 2.179 | 8.001 | 8.001 | 8.001 | 8.001 | 8.001 | 2.598 | 2.911 | ms | 0.8956 | 2.43 | ||
| Server Jitter 172.233.177.198 | 0.000 | 0.000 | 0.000 | 5.156 | 9.581 | 9.581 | 9.581 | 9.581 | 9.581 | 2.646 | 5.415 | ms | -0.2803 | 2.993 | ||
| Server Jitter 172.234.25.10 | 0.000 | 0.000 | 0.000 | 1.180 | 2.779 | 2.779 | 2.779 | 2.779 | 2.779 | 0.771 | 1.320 | ms | 0.2545 | 3.074 | ||
| Server Jitter 172.234.37.140 | 0.000 | 0.000 | 0.000 | 5.761 | 13.618 | 13.618 | 13.618 | 13.618 | 13.618 | 3.635 | 5.254 | ms | 0.5438 | 2.723 | ||
| Server Jitter 172.234.44.141 | 0.000 | 0.000 | 0.000 | 2.374 | 7.577 | 7.577 | 7.577 | 7.577 | 7.577 | 2.262 | 3.093 | ms | 0.8517 | 2.644 | ||
| Server Jitter 172.235.32.243 | 0.000 | 0.000 | 0.000 | 1.782 | 11.715 | 11.715 | 11.715 | 11.715 | 11.715 | 4.266 | 3.663 | ms | 1.132 | 2.703 | ||
| Server Jitter 172.235.60.8 | 0.000 | 0.000 | 0.000 | 2.985 | 13.407 | 13.407 | 13.407 | 13.407 | 13.407 | 3.264 | 4.071 | ms | 1.906 | 6.336 | ||
| Server Jitter 172.98.15.13 | 0.000 | 0.000 | 0.000 | 6.095 | 6.104 | 6.104 | 6.104 | 6.104 | 6.104 | 2.880 | 3.231 | ms | -0.02367 | 1.032 | ||
| Server Jitter 173.230.154.254 | 0.000 | 0.000 | 0.000 | 17.669 | 34.968 | 34.968 | 34.968 | 34.968 | 34.968 | 10.793 | 16.118 | ms | 0.0947 | 2.297 | ||
| Server Jitter 173.255.192.10 | 0.000 | 0.000 | 0.000 | 2.331 | 9.584 | 9.584 | 9.584 | 9.584 | 9.584 | 2.608 | 3.116 | ms | 1.465 | 4.472 | ||
| Server Jitter 173.255.255.133 | 0.000 | 0.153 | 1.038 | 3.303 | 14.750 | 23.112 | 28.677 | 13.712 | 22.959 | 4.499 | 4.721 | ms | 2.482 | 9.648 | ||
| Server Jitter 173.71.68.71 | 0.000 | 0.627 | 1.250 | 6.765 | 34.293 | 47.740 | 57.792 | 33.043 | 47.112 | 10.711 | 11.124 | ms | 1.434 | 5.181 | ||
| Server Jitter 173.73.96.68 | 0.000 | 0.897 | 1.335 | 4.957 | 36.764 | 55.951 | 66.282 | 35.430 | 55.054 | 10.516 | 9.643 | ms | 2.204 | 8.641 | ||
| Server Jitter 193.29.63.226 | 0.000 | 0.000 | 0.000 | 2.362 | 6.790 | 7.768 | 7.768 | 6.790 | 7.768 | 1.752 | 2.617 | ms | 1.293 | 4.972 | ||
| Server Jitter 198.137.202.32 | 0.000 | 0.671 | 1.209 | 3.297 | 12.402 | 17.407 | 31.925 | 11.193 | 16.736 | 3.746 | 4.236 | ms | 3.509 | 20.09 | ||
| Server Jitter 198.199.14.19 | 0.000 | 0.000 | 0.000 | 4.868 | 19.360 | 19.360 | 19.360 | 19.360 | 19.360 | 6.619 | 7.607 | ms | 0.7297 | 1.985 | ||
| Server Jitter 198.211.103.209 | 0.000 | 0.000 | 0.000 | 3.750 | 13.433 | 21.945 | 21.945 | 13.433 | 21.945 | 4.568 | 5.256 | ms | 1.672 | 6.209 | ||
| Server Jitter 198.23.249.167 | 0.000 | 0.000 | 0.000 | 3.316 | 6.091 | 6.091 | 6.091 | 6.091 | 6.091 | 1.952 | 2.701 | ms | 0.1314 | 2.028 | ||
| Server Jitter 198.46.254.130 | 0.000 | 0.789 | 1.171 | 3.308 | 24.735 | 39.397 | 60.567 | 23.564 | 38.608 | 8.364 | 6.211 | ms | 3.337 | 16.34 | ||
| Server Jitter 198.60.22.240 | 0.000 | 0.717 | 1.162 | 3.134 | 14.200 | 31.742 | 43.551 | 13.038 | 31.025 | 5.322 | 4.655 | ms | 3.973 | 22.32 | ||
| Server Jitter 199.68.201.235 | 0.000 | 0.000 | 1.107 | 3.083 | 4.994 | 5.795 | 5.795 | 3.886 | 5.795 | 1.244 | 3.083 | ms | -0.137 | 2.992 | ||
| Server Jitter 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) | 0.000 | 1.001 | 1.378 | 3.306 | 22.350 | 55.353 | 68.490 | 20.972 | 54.352 | 9.914 | 6.937 | ms | 3.502 | 16.46 | ||
| Server Jitter 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) | 0.000 | 0.000 | 0.000 | 6.706 | 10.790 | 10.790 | 10.790 | 10.790 | 10.790 | 3.771 | 6.760 | ms | -0.8058 | 2.409 | ||
| Server Jitter 2001:19f0:6401:400:5400:4ff:fec3:522a | 0.000 | 0.984 | 1.317 | 3.458 | 15.872 | 41.672 | 50.559 | 14.555 | 40.688 | 6.685 | 5.283 | ms | 4.293 | 24.81 | ||
| Server Jitter 2001:418:3ff::53 (x.ns.gin.ntt.net) | 0.000 | 0.000 | 0.000 | 14.048 | 17.951 | 17.951 | 17.951 | 17.951 | 17.951 | 7.508 | 10.420 | ms | -0.3643 | 1.295 | ||
| Server Jitter 2001:418:8405:4002::12 | 0.000 | 0.000 | 0.000 | 20.750 | 257.784 | 257.784 | 257.784 | 257.784 | 257.784 | 84.275 | 57.575 | ms | 1.804 | 4.559 | ||
| Server Jitter 2001:418:8405:4002::3 | 0.000 | 0.917 | 1.531 | 3.892 | 17.833 | 21.114 | 27.069 | 16.302 | 20.197 | 4.267 | 5.019 | ms | 2.538 | 9.839 | ||
| Server Jitter 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) | 0.000 | 1.136 | 2.036 | 12.122 | 41.039 | 72.944 | 118.845 | 39.003 | 71.808 | 15.175 | 15.560 | ms | 2.609 | 13.81 | ||
| Server Jitter 2001:470:1f07:24f::123 | 0.000 | 0.000 | 0.000 | 25.254 | 42.613 | 42.613 | 42.613 | 42.613 | 42.613 | 13.314 | 18.607 | ms | 0.05496 | 1.858 | ||
| Server Jitter 2001:470:1f07:d::5 (santuario.pads.ufrj.br) | 0.000 | 3.918 | 11.337 | 50.561 | 92.819 | 107.373 | 129.666 | 81.481 | 103.455 | 23.640 | 51.292 | ms | 0.199 | 2.763 | ||
| Server Jitter 2001:470:1f2c:60:123:123:123:123 | 0.000 | 0.000 | 0.000 | 20.430 | 35.954 | 35.954 | 35.954 | 35.954 | 35.954 | 11.405 | 14.554 | ms | 0.1812 | 1.824 | ||
| Server Jitter 2001:470:b:22d::123 | 0.000 | 0.000 | 1.754 | 4.530 | 7.600 | 11.131 | 11.131 | 5.846 | 11.131 | 2.457 | 4.623 | ms | 0.5328 | 3.13 | ||
| Server Jitter 2001:470:e114::d6:12 (1.md.ntp.md) | 0.000 | 0.000 | 1.372 | 6.665 | 25.048 | 45.230 | 56.378 | 23.676 | 45.230 | 8.605 | 9.563 | ms | 2.052 | 9.185 | ||
| Server Jitter 2001:470:e114::d6:c5 (t2.davehart.net) | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | ns | nan | nan | ||
| Server Jitter 2001:470:e8dc:10::123 | 0.000 | 0.001 | 0.001 | 0.004 | 0.021 | 0.074 | 589.082 | 0.020 | 0.073 | 24.776 | 1.685 | s | 18.39 | 390.9 | ||
| Server Jitter 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) | 0.000 | 1.102 | 1.686 | 10.928 | 48.225 | 61.432 | 219.778 | 46.539 | 60.331 | 15.215 | 14.564 | ms | 2.947 | 25.72 | ||
| Server Jitter 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com) | 0.000 | 0.840 | 1.365 | 3.070 | 12.046 | 16.376 | 19.485 | 10.681 | 15.537 | 3.227 | 3.896 | ms | 2.632 | 10.33 | ||
| Server Jitter 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) | 0.000 | 0.830 | 1.150 | 3.284 | 24.575 | 55.936 | 146.741 | 23.425 | 55.106 | 10.291 | 6.585 | ms | 4.523 | 32.1 | ||
| Server Jitter 2001:558:6014:17:8dc5:5575:5560:2cb6 | 0.000 | 0.000 | 0.000 | 4.253 | 65.155 | 123.941 | 123.941 | 65.155 | 123.941 | 24.032 | 13.461 | ms | 3.066 | 13.01 | ||
| Server Jitter 2001:559:2be:3::1001 | 0.000 | 0.000 | 0.000 | 2.941 | 26.115 | 53.390 | 53.390 | 26.115 | 53.390 | 13.022 | 8.500 | ms | 2.056 | 6.691 | ||
| Server Jitter 2001:678:8::123 (any.time.nl) | 0.000 | 0.000 | 0.000 | 3.773 | 8.575 | 8.575 | 8.575 | 8.575 | 8.575 | 2.594 | 3.773 | ms | 0.2015 | 1.856 | ||
| Server Jitter 204.10.18.144 | 0.000 | 0.000 | 0.000 | 0.624 | 2.536 | 2.536 | 2.536 | 2.536 | 2.536 | 1.079 | 1.053 | ms | 0.5341 | 1.5 | ||
| Server Jitter 204.197.163.71 | 0.000 | 0.686 | 1.095 | 3.220 | 7.493 | 17.061 | 50.513 | 6.398 | 16.375 | 3.155 | 3.763 | ms | 6.631 | 80.71 | ||
| Server Jitter 204.2.134.162 | 0.000 | 0.000 | 0.000 | 1.171 | 6.096 | 6.096 | 6.096 | 6.096 | 6.096 | 1.827 | 2.047 | ms | 0.8441 | 2.681 | ||
| Server Jitter 205.233.73.201 | 0.000 | 0.000 | 0.000 | 3.092 | 11.938 | 16.572 | 16.572 | 11.938 | 16.572 | 3.752 | 3.827 | ms | 1.821 | 6.541 | ||
| Server Jitter 208.113.130.146 | 0.000 | 0.861 | 1.394 | 5.061 | 43.913 | 76.684 | 232.036 | 42.519 | 75.823 | 18.779 | 11.712 | ms | 5.666 | 52.59 | ||
| Server Jitter 208.67.72.43 | 0.000 | 0.000 | 0.000 | 20.684 | 46.773 | 46.773 | 46.773 | 46.773 | 46.773 | 14.479 | 19.405 | ms | 0.3984 | 2.247 | ||
| Server Jitter 208.67.72.50 | 0.000 | 0.000 | 1.610 | 9.928 | 32.633 | 65.428 | 66.592 | 31.023 | 65.428 | 11.583 | 11.986 | ms | 2.324 | 10.54 | ||
| Server Jitter 208.67.75.242 | 0.000 | 0.872 | 1.265 | 3.563 | 19.825 | 36.345 | 45.510 | 18.560 | 35.473 | 6.747 | 6.278 | ms | 2.54 | 10.94 | ||
| Server Jitter 212.227.240.160 | 0.000 | 0.916 | 1.250 | 3.935 | 19.802 | 39.736 | 56.197 | 18.552 | 38.820 | 7.597 | 6.975 | ms | 2.834 | 13.58 | ||
| Server Jitter 216.229.4.66 | 0.000 | 0.000 | 0.000 | 4.281 | 7.579 | 7.579 | 7.579 | 7.579 | 7.579 | 2.200 | 3.859 | ms | -0.3889 | 2.271 | ||
| Server Jitter 216.229.4.69 | 0.000 | 0.000 | 0.000 | 2.477 | 5.003 | 5.695 | 5.695 | 5.003 | 5.695 | 1.718 | 2.457 | ms | 0.2191 | 2.013 | ||
| Server Jitter 216.240.36.24 | 0.000 | 0.000 | 0.000 | 2.248 | 8.229 | 18.352 | 18.352 | 8.229 | 18.352 | 4.048 | 3.754 | ms | 2.262 | 8.332 | ||
| Server Jitter 216.31.17.12 | 0.000 | 0.000 | 0.000 | 4.094 | 14.330 | 14.330 | 14.330 | 14.330 | 14.330 | 4.001 | 4.883 | ms | 1.185 | 3.801 | ||
| Server Jitter 23.111.186.186 | 0.000 | 0.000 | 0.000 | 1.132 | 1.974 | 1.974 | 1.974 | 1.974 | 1.974 | 0.537 | 1.129 | ms | -0.4905 | 3.028 | ||
| Server Jitter 23.131.160.7 | 0.000 | 0.872 | 1.351 | 3.468 | 10.877 | 32.018 | 126.894 | 9.526 | 31.146 | 7.978 | 4.861 | ms | 9.331 | 108.7 | ||
| Server Jitter 23.141.40.123 | 0.000 | 0.000 | 0.000 | 3.979 | 5.911 | 5.911 | 5.911 | 5.911 | 5.911 | 1.921 | 3.290 | ms | -0.4708 | 2.11 | ||
| Server Jitter 23.142.248.8 | 0.000 | 0.000 | 0.000 | 1.269 | 2.327 | 2.327 | 2.327 | 2.327 | 2.327 | 0.866 | 1.154 | ms | -0.1197 | 1.574 | ||
| Server Jitter 23.142.248.9 | 0.000 | 0.000 | 0.000 | 2.599 | 5.085 | 5.085 | 5.085 | 5.085 | 5.085 | 1.807 | 2.480 | ms | -0.03191 | 1.728 | ||
| Server Jitter 23.143.196.199 | 0.000 | 0.000 | 0.000 | 1.033 | 2.250 | 2.250 | 2.250 | 2.250 | 2.250 | 0.756 | 1.094 | ms | -0.06783 | 1.795 | ||
| Server Jitter 23.150.41.122 | 0.000 | 0.000 | 1.319 | 2.973 | 16.917 | 17.402 | 17.402 | 15.598 | 17.402 | 4.356 | 4.490 | ms | 1.961 | 5.842 | ||
| Server Jitter 23.150.41.123 | 0.000 | 0.770 | 1.248 | 3.330 | 18.440 | 37.814 | 51.306 | 17.192 | 37.044 | 6.206 | 5.284 | ms | 3.425 | 17.13 | ||
| Server Jitter 23.155.40.38 | 0.000 | 0.000 | 1.081 | 3.356 | 34.022 | 117.881 | 142.893 | 32.940 | 117.881 | 18.722 | 8.653 | ms | 5.033 | 31.38 | ||
| Server Jitter 23.157.160.168 | 0.000 | 0.572 | 1.303 | 4.681 | 21.589 | 31.517 | 57.034 | 20.286 | 30.944 | 8.008 | 7.992 | ms | 2.366 | 12.25 | ||
| Server Jitter 23.168.136.132 | 0.000 | 0.000 | 0.000 | 19.641 | 37.023 | 37.023 | 37.023 | 37.023 | 37.023 | 8.847 | 19.801 | ms | -0.3743 | 3.622 | ||
| Server Jitter 23.168.24.210 | 0.000 | 0.000 | 0.000 | 4.522 | 5.887 | 5.887 | 5.887 | 5.887 | 5.887 | 2.451 | 2.822 | ms | 0.06634 | 1.208 | ||
| Server Jitter 23.186.168.1 | 0.000 | 0.000 | 0.000 | 6.006 | 60.335 | 60.335 | 60.335 | 60.335 | 60.335 | 27.624 | 25.467 | ms | 0.3959 | 1.179 | ||
| Server Jitter 23.186.168.123 | 0.000 | 0.794 | 1.193 | 3.052 | 8.245 | 20.200 | 30.025 | 7.052 | 19.406 | 3.089 | 3.701 | ms | 3.772 | 21.92 | ||
| Server Jitter 23.186.168.126 | 0.000 | 0.695 | 1.121 | 3.001 | 10.669 | 41.147 | 100.230 | 9.548 | 40.452 | 8.625 | 4.647 | ms | 7.962 | 75.3 | ||
| Server Jitter 23.186.168.127 | 0.000 | 0.000 | 0.000 | 6.846 | 25.786 | 25.786 | 25.786 | 25.786 | 25.786 | 9.961 | 9.050 | ms | 0.9537 | 2.186 | ||
| Server Jitter 23.186.168.128 | 0.000 | 0.814 | 1.329 | 3.310 | 8.610 | 17.200 | 23.748 | 7.281 | 16.386 | 2.792 | 3.875 | ms | 2.955 | 14.86 | ||
| Server Jitter 23.186.168.129 | 0.000 | 0.711 | 1.257 | 3.428 | 8.497 | 17.161 | 40.189 | 7.240 | 16.450 | 3.103 | 4.098 | ms | 4.318 | 37.33 | ||
| Server Jitter 23.186.168.130 | 0.000 | 0.000 | 0.000 | 3.466 | 73.799 | 73.994 | 73.994 | 73.799 | 73.994 | 19.691 | 9.038 | ms | 2.942 | 9.824 | ||
| Server Jitter 23.186.168.131 | 0.000 | 0.749 | 1.266 | 3.133 | 8.261 | 15.037 | 223.184 | 6.995 | 14.289 | 9.704 | 4.117 | ms | 21.04 | 473.4 | ||
| Server Jitter 23.186.168.132 | 0.000 | 0.902 | 1.266 | 3.346 | 9.317 | 18.281 | 72.944 | 8.051 | 17.379 | 3.794 | 4.152 | ms | 6.892 | 91.34 | ||
| Server Jitter 23.186.168.3 | 0.000 | 0.983 | 1.613 | 5.204 | 23.217 | 48.252 | 65.816 | 21.604 | 47.269 | 8.431 | 8.574 | ms | 2.567 | 13.3 | ||
| Server Jitter 23.94.221.138 | 0.000 | 0.000 | 0.000 | 1.546 | 4.125 | 4.125 | 4.125 | 4.125 | 4.125 | 1.215 | 1.733 | ms | 0.7763 | 2.642 | ||
| Server Jitter 23.95.49.216 | 0.000 | 0.804 | 1.089 | 2.946 | 11.443 | 17.019 | 159.086 | 10.354 | 16.216 | 7.100 | 4.020 | ms | 17.62 | 379.9 | ||
| Server Jitter 240b:4002:100:9f00:5bd1:9512:8a8b:25e | 0.000 | 0.000 | 0.000 | 4.287 | 5.971 | 5.971 | 5.971 | 5.971 | 5.971 | 2.062 | 3.825 | ms | -0.9946 | 2.639 | ||
| Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d6 | 0.000 | 0.839 | 1.416 | 3.601 | 24.535 | 54.985 | 74.237 | 23.119 | 54.146 | 9.449 | 6.322 | ms | 4.13 | 22.24 | ||
| Server Jitter 240b:4004:108:200:8314:1a08:4cee:26d9 | 0.000 | 0.000 | 0.000 | 19.678 | 21.828 | 21.828 | 21.828 | 21.828 | 21.828 | 8.593 | 13.132 | ms | -0.5264 | 1.711 | ||
| Server Jitter 2600:1700:3d24:740f:9524:529a:6489:d48f | 0.000 | 0.000 | 0.000 | 1.447 | 8.923 | 8.923 | 8.923 | 8.923 | 8.923 | 2.239 | 2.142 | ms | 1.358 | 4.664 | ||
| Server Jitter 2600:1700:5455:a70::7b:1 | 0.000 | 0.000 | 1.444 | 4.653 | 23.669 | 27.142 | 27.142 | 22.225 | 27.142 | 7.742 | 8.428 | ms | 1.002 | 2.547 | ||
| Server Jitter 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 | 0.000 | 0.000 | 0.000 | 4.182 | 17.559 | 24.762 | 24.762 | 17.559 | 24.762 | 6.282 | 6.670 | ms | 1.239 | 3.969 | ||
| Server Jitter 2600:1700:5a0f:ee00::314:1b | 0.000 | 0.000 | 1.037 | 3.806 | 18.648 | 21.885 | 23.803 | 17.611 | 21.885 | 5.224 | 5.597 | ms | 1.78 | 5.219 | ||
| Server Jitter 2600:1700:5a0f:ee00::314:2b | 0.000 | 0.000 | 0.000 | 2.121 | 13.811 | 13.811 | 13.811 | 13.811 | 13.811 | 3.373 | 3.376 | ms | 1.687 | 5.974 | ||
| Server Jitter 2600:1702:7400:9ac0::314:5a | 0.000 | 0.000 | 0.000 | 2.413 | 15.160 | 15.160 | 15.160 | 15.160 | 15.160 | 4.523 | 4.818 | ms | 1.082 | 3.061 | ||
| Server Jitter 2600:1702:7400:9ac0::5b | 0.000 | 0.000 | 0.000 | 2.689 | 7.877 | 7.877 | 7.877 | 7.877 | 7.877 | 2.509 | 3.387 | ms | 0.6509 | 2.164 | ||
| Server Jitter 2600:1f13:2c1:2e00::be00:5 | 0.000 | 0.941 | 1.487 | 3.653 | 25.297 | 93.488 | 214.829 | 23.809 | 92.548 | 16.422 | 7.675 | ms | 6.759 | 62.66 | ||
| Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) | 0.000 | 0.828 | 1.199 | 3.431 | 23.880 | 51.731 | 185.361 | 22.681 | 50.903 | 10.201 | 6.540 | ms | 5.398 | 51.08 | ||
| Server Jitter 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) | 0.000 | 0.843 | 1.231 | 3.701 | 42.194 | 71.171 | 179.382 | 40.963 | 70.328 | 15.038 | 9.840 | ms | 3.503 | 20.94 | ||
| Server Jitter 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) | 0.000 | 0.847 | 1.293 | 8.517 | 54.411 | 80.426 | 168.874 | 53.118 | 79.579 | 17.941 | 15.355 | ms | 2.103 | 8.678 | ||
| Server Jitter 2600:2600::99 (ntp1.wiktel.com) | 0.000 | 0.000 | 0.000 | 1.922 | 1.922 | 1.922 | 1.922 | 1.922 | 1.922 | 0.961 | 0.961 | ms | 0 | 1 | ||
| Server Jitter 2600:3c00::f03c:91ff:fe05:b640 (dev.smatwebdesign.com) | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | ns | nan | nan | ||
| Server Jitter 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) | 0.000 | 0.894 | 1.371 | 3.443 | 16.948 | 34.487 | 151.451 | 15.577 | 33.593 | 7.361 | 5.349 | ms | 7.69 | 104.6 | ||
| Server Jitter 2600:3c00:e000:318::1 (jane.qotw.net) | 0.000 | 0.936 | 1.251 | 3.291 | 18.596 | 45.542 | 55.919 | 17.345 | 44.606 | 7.258 | 5.661 | ms | 3.76 | 20.2 | ||
| Server Jitter 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) | 0.000 | 0.000 | 0.000 | 6.110 | 10.609 | 10.609 | 10.609 | 10.609 | 10.609 | 3.299 | 4.985 | ms | 0.1951 | 2.331 | ||
| Server Jitter 2600:3c01:e000:7e6::123 (time1.sigi.net) | 0.000 | 0.707 | 1.268 | 3.208 | 8.867 | 20.528 | 87.783 | 7.599 | 19.821 | 4.889 | 4.141 | ms | 8.54 | 111.9 | ||
| Server Jitter 2600:3c02::f03c:92ff:fe96:dc0 | 0.000 | 0.719 | 1.293 | 3.642 | 35.596 | 64.763 | 70.185 | 34.303 | 64.043 | 13.117 | 8.439 | ms | 3.086 | 12.43 | ||
| Server Jitter 2600:3c02::f03c:94ff:fe59:f411 | 0.000 | 0.000 | 0.000 | 5.394 | 7.516 | 7.516 | 7.516 | 7.516 | 7.516 | 2.647 | 4.557 | ms | -0.5602 | 1.96 | ||
| Server Jitter 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net) | 0.000 | 0.565 | 1.299 | 3.371 | 13.487 | 24.586 | 25.970 | 12.188 | 24.021 | 4.283 | 4.701 | ms | 2.398 | 9.74 | ||
| Server Jitter 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) | 0.000 | 0.000 | 0.717 | 3.878 | 10.414 | 16.432 | 16.432 | 9.697 | 16.432 | 3.233 | 4.061 | ms | 1.999 | 7.801 | ||
| Server Jitter 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) | 0.000 | 0.000 | 0.000 | 4.625 | 9.182 | 9.182 | 9.182 | 9.182 | 9.182 | 3.008 | 4.335 | ms | -0.05862 | 1.872 | ||
| Server Jitter 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) | 0.000 | 1.135 | 1.788 | 5.529 | 12.197 | 16.663 | 19.149 | 10.409 | 15.527 | 3.521 | 6.155 | ms | 0.8396 | 3.495 | ||
| Server Jitter 2600:3c03::f03c:94ff:fe59:d3de | 0.000 | 0.000 | 0.000 | 9.141 | 10.648 | 10.648 | 10.648 | 10.648 | 10.648 | 4.705 | 6.597 | ms | -0.6531 | 1.5 | ||
| Server Jitter 2600:3c03:e002:1300::10 (ntp.electronmill.com) | 0.000 | 0.000 | 0.000 | 3.877 | 7.718 | 7.718 | 7.718 | 7.718 | 7.718 | 2.384 | 3.718 | ms | 0.3575 | 1.964 | ||
| Server Jitter 2600:3c06::f03c:94ff:fee2:9c28 | 0.000 | 0.000 | 0.000 | 9.325 | 30.736 | 30.736 | 30.736 | 30.736 | 30.736 | 11.553 | 11.593 | ms | 0.8589 | 2.149 | ||
| Server Jitter 2600:3c06::f03c:94ff:fee2:c53a | 0.000 | 0.000 | 0.000 | 15.615 | 24.117 | 24.117 | 24.117 | 24.117 | 24.117 | 9.987 | 13.244 | ms | -0.3427 | 1.5 | ||
| Server Jitter 2600:4040:3037:e600::1 | 2.236 | 2.236 | 2.236 | 3.952 | 3.952 | 3.952 | 3.952 | 1.716 | 1.716 | 0.858 | 3.094 | ms | 8.189e-16 | 1 | ||
| Server Jitter 2600:4040:e0da:f000::cbb9:201a | 0.000 | 0.000 | 0.547 | 12.110 | 32.149 | 45.133 | 45.133 | 31.602 | 45.133 | 10.649 | 11.858 | ms | 1.048 | 3.818 | ||
| Server Jitter 2601:18a:8081:3600:a923:2e66:e3d2:8c95 | 0.000 | 0.000 | 0.000 | 6.012 | 12.408 | 12.408 | 12.408 | 12.408 | 12.408 | 3.817 | 6.403 | ms | -0.07568 | 2.393 | ||
| Server Jitter 2602:291:69::8 (time2.tritan-bb.net) | 0.000 | 0.000 | 0.000 | 0.970 | 1.844 | 1.844 | 1.844 | 1.844 | 1.844 | 0.552 | 0.976 | ms | -0.2468 | 2.677 | ||
| Server Jitter 2602:291:69::9 (time.tritan-bb.net) | 0.000 | 0.000 | 0.000 | 2.884 | 5.429 | 9.048 | 9.048 | 5.429 | 9.048 | 1.821 | 2.641 | ms | 0.7531 | 4.59 | ||
| Server Jitter 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) | 0.000 | 0.874 | 1.319 | 3.515 | 15.422 | 39.407 | 139.194 | 14.104 | 38.533 | 7.928 | 5.320 | ms | 7.573 | 87.13 | ||
| Server Jitter 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net) | 0.000 | 0.000 | 0.000 | 1.197 | 1.816 | 1.816 | 1.816 | 1.816 | 1.816 | 0.754 | 1.004 | ms | -0.3667 | 1.5 | ||
| Server Jitter 2602:2eb:2:95:1234:5678:9abc:def0 | 0.000 | 0.928 | 1.412 | 3.654 | 26.243 | 55.859 | 262.579 | 24.831 | 54.931 | 13.247 | 7.544 | ms | 8.809 | 126 | ||
| Server Jitter 2602:80b:5000::36 (time.meme.holdings) | 0.000 | 0.000 | 5.795 | 21.991 | 77.525 | 84.174 | 87.838 | 71.730 | 84.174 | 21.109 | 29.343 | ms | 0.9157 | 3.126 | ||
| Server Jitter 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) | 0.000 | 0.000 | 0.000 | 4.593 | 9.349 | 9.349 | 9.349 | 9.349 | 9.349 | 2.587 | 4.904 | ms | -0.09123 | 2.375 | ||
| Server Jitter 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) | 0.000 | 0.000 | 1.361 | 5.466 | 56.326 | 77.816 | 96.144 | 54.966 | 77.816 | 18.343 | 13.281 | ms | 2.257 | 7.758 | ||
| Server Jitter 2602:f9bd:80:100::a (time.circlevps.net) | 0.000 | 0.956 | 1.406 | 3.442 | 16.785 | 30.859 | 88.641 | 15.379 | 29.903 | 6.152 | 5.167 | ms | 5.025 | 42.76 | ||
| Server Jitter 2602:fc2f:100:9800::dead:beef | 0.000 | 1.459 | 2.342 | 5.528 | 63.917 | 165.490 | 259.248 | 61.575 | 164.031 | 29.613 | 15.005 | ms | 4.444 | 25.38 | ||
| Server Jitter 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) | 0.000 | 0.000 | 0.000 | 4.184 | 9.370 | 9.370 | 9.370 | 9.370 | 9.370 | 2.625 | 4.132 | ms | 0.213 | 2.817 | ||
| Server Jitter 2602:fe2e:3:d:f9:c7ff:fef5:379c | 0.000 | 0.000 | 0.000 | 2.011 | 3.424 | 3.424 | 3.424 | 3.424 | 3.424 | 0.929 | 1.786 | ms | -0.1796 | 2.962 | ||
| Server Jitter 2602:feda:30:ae86:2fc:98ff:fecf:fe94 | 0.482 | 0.800 | 1.196 | 3.125 | 10.174 | 19.107 | 34.513 | 8.978 | 18.307 | 3.601 | 3.930 | ms | 4.587 | 32.02 | ||
| Server Jitter 2602:ff06:725:100::123 (oldtime2.sigi.net) | 0.000 | 0.766 | 1.309 | 3.362 | 12.735 | 19.380 | 20.540 | 11.426 | 18.614 | 3.361 | 4.167 | ms | 2.76 | 11.34 | ||
| Server Jitter 2602:ff23:50:3c2::1 (dns-e.ns4v.icu) | 0.000 | 0.000 | 1.368 | 4.208 | 41.300 | 69.376 | 73.583 | 39.933 | 69.376 | 12.652 | 8.050 | ms | 3.515 | 15.2 | ||
| Server Jitter 2603:c020:0:8369:0:ba11:ba11:ba11 | 0.000 | 0.000 | 0.000 | 3.480 | 14.814 | 17.914 | 17.914 | 14.814 | 17.914 | 3.983 | 4.366 | ms | 1.511 | 5.581 | ||
| Server Jitter 2603:c020:0:8369:1111:1111:1111:1112 | 0.000 | 0.000 | 0.000 | 7.900 | 74.324 | 99.180 | 99.180 | 74.324 | 99.180 | 20.465 | 14.476 | ms | 2.431 | 9.472 | ||
| Server Jitter 2603:c020:0:8369:607:e532:d534:7109 | 0.000 | 0.000 | 0.000 | 2.471 | 17.374 | 17.374 | 17.374 | 17.374 | 17.374 | 4.277 | 3.926 | ms | 1.788 | 6.072 | ||
| Server Jitter 2603:c020:0:8369::bad:babe | 0.000 | 0.000 | 0.000 | 5.795 | 16.059 | 16.059 | 16.059 | 16.059 | 16.059 | 4.220 | 6.109 | ms | 0.5934 | 2.891 | ||
| Server Jitter 2603:c020:0:8369::bad:beef | 0.000 | 0.000 | 0.000 | 3.311 | 12.865 | 12.865 | 12.865 | 12.865 | 12.865 | 4.951 | 5.440 | ms | 0.6499 | 1.683 | ||
| Server Jitter 2603:c020:0:8369::f00d:feed | 0.000 | 0.000 | 0.000 | 3.051 | 11.156 | 19.041 | 19.041 | 11.156 | 19.041 | 4.036 | 4.160 | ms | 2.143 | 8.32 | ||
| Server Jitter 2603:c020:0:8369::feeb:dab | 0.000 | 0.000 | 0.000 | 3.564 | 11.129 | 12.564 | 12.564 | 11.129 | 12.564 | 2.944 | 3.733 | ms | 0.8869 | 3.775 | ||
| Server Jitter 2603:c020:0:8369:feed:feed:feed:feed | 0.000 | 0.000 | 0.000 | 3.112 | 13.323 | 13.323 | 13.323 | 13.323 | 13.323 | 3.317 | 3.712 | ms | 1.612 | 5.406 | ||
| Server Jitter 2603:c020:400e:ea00:ccfe:ba34:7215:d4f6 | 0.000 | 0.859 | 1.303 | 3.227 | 14.318 | 24.304 | 43.492 | 13.015 | 23.445 | 5.129 | 4.743 | ms | 4.134 | 25.63 | ||
| Server Jitter 2603:c020:6:b900:6b54:1390:4afd:814a | 0.000 | 0.000 | 0.000 | 4.457 | 16.191 | 16.191 | 16.191 | 16.191 | 16.191 | 4.707 | 5.327 | ms | 0.744 | 2.635 | ||
| Server Jitter 2603:c020:6:b900:ed2f:b442:fee7:d9b9 | 0.000 | 0.000 | 0.000 | 2.967 | 6.929 | 6.929 | 6.929 | 6.929 | 6.929 | 2.490 | 2.410 | ms | 0.6756 | 2.153 | ||
| Server Jitter 2603:c024:c005:a600:8eb1:2863:5838:9880 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | ns | nan | nan | ||
| Server Jitter 2603:c024:c005:a600:efb6:d213:cad8:251d | 0.000 | 0.000 | 0.000 | 14.820 | 57.595 | 57.595 | 57.595 | 57.595 | 57.595 | 17.229 | 20.244 | ms | 1.209 | 3.457 | ||
| Server Jitter 2604:180:f3::4a4 (dutch.arpnet.net) | 0.000 | 0.000 | 0.000 | 1.362 | 4.226 | 4.226 | 4.226 | 4.226 | 4.226 | 1.566 | 1.904 | ms | 0.4456 | 1.597 | ||
| Server Jitter 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 | 0.000 | 0.000 | 1.769 | 15.711 | 48.002 | 49.094 | 49.094 | 46.233 | 49.094 | 11.410 | 15.959 | ms | 1.156 | 4.594 | ||
| Server Jitter 2604:2dc0:100:4d6:: | 0.000 | 0.000 | 0.000 | 3.514 | 4.351 | 4.351 | 4.351 | 4.351 | 4.351 | 1.632 | 2.616 | ms | -0.6871 | 1.99 | ||
| Server Jitter 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) | 0.000 | 1.045 | 1.533 | 3.726 | 22.901 | 53.226 | 197.927 | 21.368 | 52.181 | 12.375 | 7.465 | ms | 8.524 | 115.9 | ||
| Server Jitter 2604:2dc0:202:300::140d (ovh.maxhost.io) | 0.000 | 0.965 | 1.366 | 3.498 | 9.087 | 21.237 | 71.985 | 7.721 | 20.272 | 3.773 | 4.317 | ms | 5.523 | 60.29 | ||
| Server Jitter 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) | 0.000 | 0.906 | 1.363 | 3.338 | 10.703 | 34.136 | 119.042 | 9.340 | 33.230 | 6.208 | 4.661 | ms | 7.131 | 78.29 | ||
| Server Jitter 2604:4300:a:299::164 | 0.000 | 0.000 | 0.000 | 3.582 | 6.183 | 11.304 | 11.304 | 6.183 | 11.304 | 2.417 | 3.650 | ms | 1.209 | 5.485 | ||
| Server Jitter 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) | 0.000 | 0.000 | 0.000 | 3.639 | 13.829 | 13.829 | 13.829 | 13.829 | 13.829 | 3.432 | 4.353 | ms | 1.336 | 4.939 | ||
| Server Jitter 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) | 0.000 | 0.000 | 0.000 | 21.487 | 31.405 | 31.405 | 31.405 | 31.405 | 31.405 | 13.108 | 17.631 | ms | -0.4158 | 1.5 | ||
| Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) | 0.000 | 0.000 | 0.000 | 0.869 | 1.657 | 1.657 | 1.657 | 1.657 | 1.657 | 0.479 | 0.845 | ms | -0.09905 | 2.996 | ||
| Server Jitter 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) | 0.000 | 0.965 | 1.447 | 3.716 | 18.849 | 29.446 | 120.523 | 17.402 | 28.481 | 10.597 | 5.665 | ms | 8.209 | 79.46 | ||
| Server Jitter 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) | 0.000 | 0.000 | 0.000 | 8.010 | 25.574 | 25.574 | 25.574 | 25.574 | 25.574 | 6.576 | 8.369 | ms | 0.7283 | 3.152 | ||
| Server Jitter 2604:a880:800:a1::ec9:5001 | 0.000 | 0.000 | 0.000 | 3.038 | 144.987 | 144.987 | 144.987 | 144.987 | 144.987 | 40.690 | 27.266 | ms | 1.51 | 4.267 | ||
| Server Jitter 2605:4840:3:fb19::1 (chi3.us.ntp.li) | 0.000 | 3.032 | 6.591 | 21.939 | 58.467 | 76.100 | 242.923 | 51.875 | 73.068 | 18.011 | 25.799 | ms | 3.949 | 40.23 | ||
| Server Jitter 2605:6400:488d:2eda:eee9:fe8d:4543:d471 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | ns | nan | nan | ||
| Server Jitter 2605:6400:488d:3686:546d:c03c:1689:20c | 0.000 | 0.000 | 0.000 | 1.372 | 9.116 | 9.116 | 9.116 | 9.116 | 9.116 | 3.886 | 3.057 | ms | 0.6883 | 1.57 | ||
| Server Jitter 2605:6400:84e1::123 (oldtime3.sigi.net) | 0.000 | 0.812 | 1.378 | 3.695 | 19.761 | 29.574 | 60.134 | 18.383 | 28.763 | 6.442 | 6.210 | ms | 2.693 | 13.31 | ||
| Server Jitter 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) | 0.000 | 0.000 | 0.000 | 3.793 | 7.878 | 7.878 | 7.878 | 7.878 | 7.878 | 2.024 | 4.070 | ms | 0.0771 | 3.251 | ||
| Server Jitter 2606:4700:f1::1 (time.cloudflare.com) | 0.000 | 0.880 | 1.332 | 3.435 | 17.260 | 44.212 | 400.941 | 15.928 | 43.332 | 10.385 | 5.565 | ms | 13.94 | 349.8 | ||
| Server Jitter 2606:4700:f1::123 (time.cloudflare.com) | 0.000 | 0.872 | 1.300 | 3.388 | 15.212 | 42.335 | 198.701 | 13.912 | 41.464 | 8.326 | 5.194 | ms | 8.666 | 117.4 | ||
| Server Jitter 2606:82c0:21::e (time1.lshiy.com) | 0.000 | 0.000 | 0.000 | 16.075 | 42.362 | 42.362 | 42.362 | 42.362 | 42.362 | 15.446 | 17.687 | ms | 0.3682 | 1.594 | ||
| Server Jitter 2606:82c0:22::e (time2.lshiy.com) | 0.000 | 0.000 | 0.000 | 5.690 | 24.843 | 24.843 | 24.843 | 24.843 | 24.843 | 7.304 | 7.682 | ms | 1.18 | 3.539 | ||
| Server Jitter 2606:82c0:23::e (time3.lshiy.com) | 0.000 | 0.000 | 0.000 | 3.263 | 8.248 | 8.248 | 8.248 | 8.248 | 8.248 | 2.337 | 3.284 | ms | 0.2294 | 2.606 | ||
| Server Jitter 2606:8fc0::9 (farmhand.gac.edu) | 0.000 | 0.823 | 1.320 | 3.357 | 18.249 | 30.285 | 37.736 | 16.930 | 29.461 | 5.445 | 4.927 | ms | 3.33 | 15.01 | ||
| Server Jitter 2607:5600:182:500::1 (ntp-1.jonlight.com) | 0.000 | 0.000 | 0.000 | 10.156 | 45.021 | 45.021 | 45.021 | 45.021 | 45.021 | 12.499 | 11.485 | ms | 1.431 | 4.572 | ||
| Server Jitter 2607:7c80:54:3::32 | 0.000 | 0.899 | 1.412 | 3.457 | 14.925 | 33.748 | 127.511 | 13.513 | 32.849 | 6.683 | 5.030 | ms | 6.948 | 78.13 | ||
| Server Jitter 2607:7c80:54:3::56 (owners.kjsl.com) | 0.000 | 0.000 | 1.298 | 3.181 | 22.900 | 24.794 | 24.794 | 21.602 | 24.794 | 5.837 | 5.520 | ms | 2.225 | 7.106 | ||
| Server Jitter 2607:9000:7000:23:216:3cff:fe25:38d7 | 0.000 | 0.598 | 1.211 | 3.188 | 11.275 | 18.776 | 101.037 | 10.064 | 18.178 | 7.917 | 4.641 | ms | 9.393 | 106.3 | ||
| Server Jitter 2607:9d00:2000:16::9269:208a | 0.000 | 0.000 | 0.000 | 14.156 | 32.768 | 32.768 | 32.768 | 32.768 | 32.768 | 13.320 | 17.348 | ms | 0.07984 | 1.353 | ||
| Server Jitter 2607:b500:410:7700::1 | 0.000 | 0.000 | 0.000 | 3.930 | 45.349 | 48.813 | 48.813 | 45.349 | 48.813 | 11.282 | 7.651 | ms | 2.727 | 9.768 | ||
| Server Jitter 2607:f1c0:f014:9e00::1 | 0.000 | 0.000 | 0.000 | 4.356 | 10.370 | 10.370 | 10.370 | 10.370 | 10.370 | 2.391 | 5.036 | ms | 0.1939 | 4.09 | ||
| Server Jitter 2607:f1c0:f014:9e00::2 | 0.000 | 0.000 | 0.000 | 4.033 | 19.038 | 31.195 | 31.195 | 19.038 | 31.195 | 7.047 | 6.391 | ms | 1.868 | 6.607 | ||
| Server Jitter 2607:f1c0:f047:8400::1 (xmpp.party) | 0.000 | 0.000 | 0.000 | 2.160 | 5.723 | 5.723 | 5.723 | 5.723 | 5.723 | 2.360 | 2.628 | ms | 0.2895 | 1.5 | ||
| Server Jitter 2607:f1c0:f04e:fd00::1 | 0.000 | 0.000 | 0.000 | 4.264 | 7.362 | 7.362 | 7.362 | 7.362 | 7.362 | 2.269 | 3.950 | ms | -0.238 | 2.144 | ||
| Server Jitter 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 3.311 | 58.981 | 58.981 | 58.981 | 58.981 | 58.981 | 21.215 | 11.609 | ms | 1.777 | 4.18 | ||
| Server Jitter 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 2.496 | 6.975 | 6.975 | 6.975 | 6.975 | 6.975 | 2.053 | 2.689 | ms | 0.7637 | 2.799 | ||
| Server Jitter 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 0.000 | 1.285 | 1.285 | 1.285 | 1.285 | 1.285 | 0.606 | 0.428 | ms | 0.7071 | 1.5 | ||
| Server Jitter 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 18.803 | 82.310 | 82.310 | 82.310 | 82.310 | 82.310 | 18.917 | 21.241 | ms | 1.617 | 5.891 | ||
| Server Jitter 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) | 0.000 | 0.000 | 0.000 | 3.713 | 17.103 | 17.166 | 17.166 | 17.103 | 17.166 | 4.236 | 4.518 | ms | 1.905 | 6.172 | ||
| Server Jitter 2607:f1c0:f06d:f200::1 | 0.000 | 0.000 | 0.000 | 13.001 | 14.124 | 14.124 | 14.124 | 14.124 | 14.124 | 5.551 | 9.074 | ms | -0.8153 | 2.019 | ||
| Server Jitter 2607:f1c0:f075:9900::1 | 0.000 | 0.000 | 0.000 | 2.615 | 9.511 | 9.511 | 9.511 | 9.511 | 9.511 | 2.632 | 3.371 | ms | 1.055 | 3.399 | ||
| Server Jitter 2607:f298:5:101d:f816:3eff:fefd:8817 | 0.000 | 0.000 | 0.000 | 3.238 | 15.794 | 15.794 | 15.794 | 15.794 | 15.794 | 3.672 | 4.170 | ms | 1.423 | 5.487 | ||
| Server Jitter 2607:f3c8:3803:1::6 | 0.000 | 0.000 | 0.000 | 3.665 | 9.888 | 9.888 | 9.888 | 9.888 | 9.888 | 3.130 | 3.728 | ms | 0.7664 | 2.592 | ||
| Server Jitter 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) | 0.000 | 0.000 | 0.000 | 7.826 | 42.881 | 42.881 | 42.881 | 42.881 | 42.881 | 11.996 | 12.673 | ms | 0.9758 | 3.228 | ||
| Server Jitter 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) | 0.000 | 0.000 | 0.000 | 2.953 | 7.543 | 7.543 | 7.543 | 7.543 | 7.543 | 1.917 | 3.128 | ms | 0.7412 | 3.627 | ||
| Server Jitter 2607:f710:35::29c:0:8 | 0.000 | 0.993 | 1.374 | 7.413 | 35.124 | 57.993 | 80.866 | 33.750 | 57.000 | 11.814 | 11.251 | ms | 2.307 | 10.35 | ||
| Server Jitter 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) | 0.000 | 0.000 | 1.354 | 3.620 | 17.136 | 24.570 | 151.167 | 15.782 | 24.570 | 12.993 | 6.037 | ms | 9.835 | 109.2 | ||
| Server Jitter 2607:ff50:0:1a::20 (ntpool1.603.newcontinuum.net) | 0.000 | 1.124 | 1.413 | 3.785 | 21.590 | 37.597 | 46.508 | 20.178 | 36.474 | 6.962 | 5.709 | ms | 3.417 | 14.9 | ||
| Server Jitter 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com) | 0.000 | 0.000 | 0.000 | 1.304 | 6.107 | 6.107 | 6.107 | 6.107 | 6.107 | 2.114 | 2.122 | ms | 1.095 | 2.75 | ||
| Server Jitter 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com) | 0.000 | 0.850 | 1.305 | 3.226 | 9.081 | 20.463 | 88.888 | 7.777 | 19.613 | 6.010 | 4.299 | ms | 9.492 | 117.8 | ||
| Server Jitter 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com) | 0.000 | 1.030 | 1.385 | 3.505 | 11.942 | 27.673 | 108.020 | 10.557 | 26.644 | 5.728 | 4.753 | ms | 8.065 | 109.2 | ||
| Server Jitter 2620:6:2000:104::48 (excalibur.prolixium.com) | 0.000 | 0.000 | 2.622 | 12.553 | 39.943 | 40.439 | 40.439 | 37.321 | 40.439 | 11.586 | 13.847 | ms | 1.25 | 3.545 | ||
| Server Jitter 2620:83:8000:140::b (tic.lbl.gov) | 0.000 | 0.880 | 1.380 | 3.683 | 18.060 | 54.396 | 107.171 | 16.680 | 53.516 | 8.265 | 5.655 | ms | 5.524 | 41.14 | ||
| Server Jitter 2620:83:8000:140::c (toc.lbl.gov) | 0.000 | 1.106 | 1.584 | 3.636 | 9.935 | 22.754 | 23.037 | 8.351 | 21.648 | 3.401 | 4.570 | ms | 2.971 | 15.07 | ||
| Server Jitter 2620:8d:c000::f (blotch.image1tech.net) | 0.000 | 0.000 | 0.000 | 11.399 | 23.001 | 23.001 | 23.001 | 23.001 | 23.001 | 6.886 | 11.933 | ms | -0.1456 | 2.635 | ||
| Server Jitter 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) | 0.000 | 0.000 | 0.000 | 4.268 | 26.331 | 26.331 | 26.331 | 26.331 | 26.331 | 6.810 | 6.258 | ms | 1.9 | 6.02 | ||
| Server Jitter 2620:b0:2000:102::1:123 (time-h.den.codehof.net) | 0.000 | 0.000 | 0.000 | 44.659 | 162.644 | 162.644 | 162.644 | 162.644 | 162.644 | 50.617 | 46.606 | ms | 1.096 | 3.207 | ||
| Server Jitter 2620:b0:2000:102::2:123 (time-he.den.codehof.net) | 0.000 | 0.000 | 0.000 | 5.132 | 67.520 | 67.520 | 67.520 | 67.520 | 67.520 | 21.171 | 12.422 | ms | 2.131 | 5.771 | ||
| Server Jitter 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) | 0.000 | 3.102 | 10.574 | 51.882 | 98.388 | 112.804 | 271.797 | 87.814 | 109.702 | 26.577 | 53.021 | ms | 0.3589 | 3.418 | ||
| Server Jitter 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) | 0.000 | 2.597 | 7.095 | 49.586 | 96.418 | 109.785 | 234.358 | 89.323 | 107.188 | 26.910 | 50.228 | ms | 0.2493 | 2.738 | ||
| Server Jitter 2a01:4ff:1f0:c33f::1 | 0.715 | 0.995 | 1.297 | 3.029 | 8.683 | 38.764 | 93.092 | 7.386 | 37.769 | 7.222 | 4.284 | ms | 8.873 | 96.72 | ||
| Server Jitter 2a01:4ff:f0:e33b::1 | 0.000 | 0.947 | 1.569 | 3.545 | 15.711 | 44.810 | 56.968 | 14.143 | 43.863 | 7.049 | 5.515 | ms | 4.531 | 27.82 | ||
| Server Jitter 2a01:4ff:f0:ebce::1 (zero.txryan.com) | 0.000 | 0.000 | 0.000 | 25.847 | 25.847 | 25.847 | 25.847 | 25.847 | 25.847 | 12.924 | 12.924 | ms | 0 | 1 | ||
| Server Jitter 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) | 0.000 | 0.000 | 0.000 | 32.068 | 70.288 | 70.288 | 70.288 | 70.288 | 70.288 | 19.572 | 34.261 | ms | 0.1428 | 3.002 | ||
| Server Jitter 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) | 0.000 | 0.704 | 1.300 | 3.254 | 8.736 | 20.805 | 38.483 | 7.436 | 20.101 | 3.869 | 4.053 | ms | 4.955 | 35.18 | ||
| Server Jitter 38.81.211.177 | 0.000 | 0.000 | 0.000 | 2.318 | 3.899 | 3.899 | 3.899 | 3.899 | 3.899 | 1.177 | 2.044 | ms | -0.2148 | 2.563 | ||
| Server Jitter 44.190.5.123 | 0.000 | 0.806 | 1.180 | 3.163 | 12.299 | 25.128 | 625.327 | 11.119 | 24.321 | 9.581 | 4.586 | ms | 37.95 | 2277 | ||
| Server Jitter 45.33.53.84 | 0.000 | 0.797 | 1.151 | 2.983 | 8.003 | 17.186 | 26.784 | 6.852 | 16.388 | 2.964 | 3.630 | ms | 4.203 | 28.01 | ||
| Server Jitter 45.55.126.202 | 0.000 | 0.865 | 1.268 | 3.641 | 19.337 | 43.121 | 76.922 | 18.069 | 42.255 | 8.466 | 6.840 | ms | 3.775 | 22.63 | ||
| Server Jitter 45.55.58.103 | 0.000 | 0.000 | 3.600 | 14.076 | 49.919 | 53.742 | 53.742 | 46.319 | 53.742 | 15.712 | 19.196 | ms | 0.8351 | 2.371 | ||
| Server Jitter 45.61.187.39 | 0.000 | 0.000 | 0.000 | 6.005 | 10.131 | 10.131 | 10.131 | 10.131 | 10.131 | 3.234 | 5.663 | ms | -0.1351 | 2.072 | ||
| Server Jitter 45.63.54.13 | 0.000 | 0.750 | 1.267 | 3.451 | 16.818 | 30.433 | 69.818 | 15.550 | 29.683 | 6.186 | 5.088 | ms | 4.745 | 33.4 | ||
| Server Jitter 45.79.35.159 | 0.000 | 0.000 | 0.000 | 0.712 | 4.702 | 4.702 | 4.702 | 4.702 | 4.702 | 1.855 | 1.527 | ms | 1.069 | 2.278 | ||
| Server Jitter 45.79.51.42 | 0.000 | 0.000 | 0.000 | 11.729 | 96.151 | 96.151 | 96.151 | 96.151 | 96.151 | 29.987 | 22.678 | ms | 1.636 | 4.376 | ||
| Server Jitter 45.83.234.123 | 0.000 | 0.000 | 0.000 | 38.377 | 69.832 | 100.538 | 100.538 | 69.832 | 100.538 | 25.273 | 34.042 | ms | 0.07115 | 2.108 | ||
| Server Jitter 45.84.199.136 | 0.000 | 0.000 | 0.000 | 7.227 | 34.845 | 34.845 | 34.845 | 34.845 | 34.845 | 11.450 | 10.051 | ms | 1.254 | 3.184 | ||
| Server Jitter 46.37.96.107 | 0.000 | 0.762 | 1.136 | 3.173 | 17.249 | 45.839 | 76.855 | 16.113 | 45.077 | 7.508 | 5.080 | ms | 4.938 | 32.2 | ||
| Server Jitter 5.161.111.190 | 0.000 | 0.953 | 1.350 | 3.302 | 16.344 | 28.113 | 46.484 | 14.994 | 27.160 | 5.641 | 5.310 | ms | 3.199 | 16.81 | ||
| Server Jitter 5.78.62.36 | 0.000 | 0.814 | 1.189 | 3.214 | 7.458 | 14.625 | 17.905 | 6.268 | 13.811 | 2.404 | 3.674 | ms | 2.621 | 12.87 | ||
| Server Jitter 50.117.3.52 | 0.000 | 0.000 | 0.000 | 1.241 | 1.948 | 1.948 | 1.948 | 1.948 | 1.948 | 0.616 | 1.028 | ms | -0.1887 | 2.181 | ||
| Server Jitter 50.117.3.95 | 0.000 | 0.000 | 0.000 | 4.938 | 9.600 | 9.600 | 9.600 | 9.600 | 9.600 | 3.585 | 4.705 | ms | -0.06002 | 1.66 | ||
| Server Jitter 50.205.57.38 | 0.000 | 0.902 | 1.257 | 3.354 | 19.270 | 37.488 | 52.487 | 18.013 | 36.586 | 7.068 | 6.193 | ms | 2.927 | 14.35 | ||
| Server Jitter 50.218.103.254 | 0.000 | 0.000 | 0.000 | 8.493 | 18.950 | 22.640 | 22.640 | 18.950 | 22.640 | 6.893 | 8.251 | ms | 0.2712 | 1.803 | ||
| Server Jitter 51.81.20.76 | 0.000 | 0.000 | 0.000 | 2.794 | 18.439 | 18.439 | 18.439 | 18.439 | 18.439 | 4.702 | 4.747 | ms | 2.128 | 6.656 | ||
| Server Jitter 51.81.226.229 | 0.000 | 0.000 | 0.000 | 4.457 | 13.199 | 16.706 | 16.706 | 13.199 | 16.706 | 3.893 | 5.097 | ms | 1.296 | 4.495 | ||
| Server Jitter 64.142.54.12 | 0.000 | 0.000 | 0.000 | 4.301 | 11.521 | 11.521 | 11.521 | 11.521 | 11.521 | 2.947 | 4.784 | ms | 0.8351 | 3.574 | ||
| Server Jitter 64.6.144.6 | 0.000 | 0.000 | 1.245 | 3.287 | 10.197 | 18.416 | 26.199 | 8.952 | 18.416 | 3.211 | 3.974 | ms | 3.158 | 16.39 | ||
| Server Jitter 64.79.100.197 | 0.000 | 0.000 | 0.817 | 2.208 | 16.989 | 29.767 | 29.820 | 16.172 | 29.767 | 5.117 | 3.706 | ms | 3.407 | 14.88 | ||
| Server Jitter 65.100.46.164 | 0.000 | 0.902 | 1.495 | 3.180 | 12.652 | 17.404 | 21.093 | 11.158 | 16.502 | 3.401 | 4.380 | ms | 2.274 | 8.459 | ||
| Server Jitter 65.100.46.166 | 0.000 | 0.877 | 1.365 | 3.588 | 16.248 | 25.653 | 30.128 | 14.883 | 24.777 | 4.652 | 4.994 | ms | 2.701 | 11.07 | ||
| Server Jitter 65.182.224.39 | 0.000 | 0.000 | 0.000 | 2.070 | 2.943 | 2.943 | 2.943 | 2.943 | 2.943 | 0.933 | 1.809 | ms | -0.8566 | 2.777 | ||
| Server Jitter 66.118.229.14 | 0.000 | 0.000 | 0.000 | 3.453 | 3.453 | 3.453 | 3.453 | 3.453 | 3.453 | 1.727 | 1.727 | ms | 0 | 1 | ||
| Server Jitter 66.118.230.14 | 0.000 | 0.000 | 0.000 | 4.746 | 14.826 | 14.826 | 14.826 | 14.826 | 14.826 | 6.182 | 6.524 | ms | 0.4076 | 1.5 | ||
| Server Jitter 66.118.231.14 | 0.000 | 0.000 | 1.373 | 34.816 | 55.552 | 77.497 | 77.497 | 54.179 | 77.497 | 19.015 | 31.982 | ms | -0.09999 | 2.355 | ||
| Server Jitter 66.42.71.197 | 0.000 | 0.804 | 1.223 | 3.207 | 11.673 | 20.952 | 36.891 | 10.450 | 20.148 | 3.804 | 4.239 | ms | 3.293 | 17.16 | ||
| Server Jitter 66.59.198.94 | 0.000 | 0.000 | 0.000 | 4.307 | 12.760 | 12.760 | 12.760 | 12.760 | 12.760 | 3.136 | 4.798 | ms | 1.209 | 4.406 | ||
| Server Jitter 66.85.78.80 | 0.000 | 0.710 | 1.266 | 3.085 | 24.810 | 104.082 | 110.853 | 23.544 | 103.372 | 13.847 | 7.360 | ms | 4.933 | 32.11 | ||
| Server Jitter 67.217.240.178 | 0.000 | 0.000 | 0.000 | 3.911 | 8.284 | 8.284 | 8.284 | 8.284 | 8.284 | 2.440 | 3.645 | ms | 0.07159 | 2.595 | ||
| Server Jitter 67.217.246.127 | 0.000 | 0.544 | 1.405 | 3.301 | 20.244 | 36.524 | 37.261 | 18.839 | 35.979 | 7.198 | 6.206 | ms | 2.642 | 10.4 | ||
| Server Jitter 67.217.246.204 | 0.000 | 0.000 | 1.357 | 5.632 | 21.877 | 32.520 | 37.970 | 20.520 | 32.520 | 7.317 | 8.853 | ms | 1.244 | 4.444 | ||
| Server Jitter 68.234.48.70 | 0.000 | 0.000 | 0.000 | 15.255 | 37.426 | 37.426 | 37.426 | 37.426 | 37.426 | 11.694 | 11.915 | ms | 0.673 | 2.554 | ||
| Server Jitter 69.48.203.16 | 0.000 | 0.000 | 0.000 | 2.915 | 5.617 | 5.617 | 5.617 | 5.617 | 5.617 | 1.492 | 2.928 | ms | -0.1583 | 2.911 | ||
| Server Jitter 69.89.207.199 | 0.000 | 0.891 | 1.620 | 3.855 | 12.202 | 28.244 | 103.870 | 10.582 | 27.353 | 8.861 | 5.489 | ms | 9.201 | 98.89 | ||
| Server Jitter 69.89.207.99 | 0.000 | 0.731 | 1.075 | 2.902 | 14.207 | 29.139 | 217.779 | 13.132 | 28.408 | 10.138 | 4.919 | ms | 14.31 | 275.9 | ||
| Server Jitter 71.123.46.186 | 0.000 | 0.798 | 1.369 | 11.462 | 50.388 | 59.457 | 63.511 | 49.020 | 58.659 | 13.810 | 13.720 | ms | 1.912 | 6.345 | ||
| Server Jitter 71.19.144.140 | 0.000 | 0.000 | 0.000 | 2.244 | 28.288 | 28.288 | 28.288 | 28.288 | 28.288 | 6.176 | 4.071 | ms | 3.331 | 13.18 | ||
| Server Jitter 72.14.183.39 | 0.000 | 0.942 | 1.271 | 2.876 | 12.455 | 20.388 | 26.598 | 11.184 | 19.446 | 3.773 | 3.910 | ms | 3.136 | 14.03 | ||
| Server Jitter 72.14.186.59 | 0.000 | 0.000 | 0.000 | 1.353 | 7.812 | 7.812 | 7.812 | 7.812 | 7.812 | 2.791 | 2.333 | ms | 1.36 | 3.086 | ||
| Server Jitter 72.30.35.89 | 0.000 | 0.000 | 0.000 | 0.779 | 4.898 | 4.898 | 4.898 | 4.898 | 4.898 | 2.149 | 1.892 | ms | 0.6381 | 1.5 | ||
| Server Jitter 72.46.53.234 | 0.000 | 0.000 | 0.000 | 3.818 | 99.485 | 99.485 | 99.485 | 99.485 | 99.485 | 27.363 | 16.024 | ms | 2.181 | 6.785 | ||
| Server Jitter 72.46.61.205 | 0.000 | 0.000 | 0.000 | 41.508 | 79.056 | 79.056 | 79.056 | 79.056 | 79.056 | 23.710 | 34.029 | ms | -0.07087 | 1.973 | ||
| Server Jitter 73.185.182.209 | 0.000 | 1.188 | 1.697 | 3.815 | 25.345 | 43.709 | 79.900 | 23.648 | 42.521 | 9.600 | 8.061 | ms | 2.934 | 14.97 | ||
| Server Jitter 73.65.80.137 | 0.000 | 0.000 | 1.979 | 4.758 | 26.082 | 30.271 | 30.271 | 24.103 | 30.271 | 7.745 | 8.134 | ms | 1.314 | 3.612 | ||
| Server Jitter 74.119.243.5 | 0.000 | 0.000 | 0.000 | 3.388 | 6.563 | 6.563 | 6.563 | 6.563 | 6.563 | 2.635 | 2.597 | ms | 0.4823 | 1.635 | ||
| Server Jitter 74.208.117.38 | 0.000 | 0.000 | 0.000 | 5.816 | 17.030 | 17.030 | 17.030 | 17.030 | 17.030 | 4.139 | 6.213 | ms | 1.416 | 5.194 | ||
| Server Jitter 74.208.14.149 | 0.000 | 0.000 | 0.000 | 8.875 | 13.149 | 13.149 | 13.149 | 13.149 | 13.149 | 4.272 | 6.919 | ms | -0.2182 | 2.001 | ||
| Server Jitter 74.208.25.46 | 0.000 | 1.565 | 2.194 | 4.573 | 14.163 | 52.935 | 406.747 | 11.968 | 51.370 | 15.638 | 6.943 | ms | 15.57 | 327 | ||
| Server Jitter 83.147.242.172 | 0.000 | 0.865 | 1.203 | 3.118 | 8.571 | 19.379 | 60.098 | 7.369 | 18.514 | 3.741 | 3.896 | ms | 6.442 | 69.26 | ||
| Server Jitter 99.28.14.242 | 0.000 | 0.847 | 1.309 | 3.374 | 21.044 | 61.650 | 143.840 | 19.736 | 60.804 | 10.772 | 6.757 | ms | 5.713 | 49.82 | ||
| Server Jitter SHM(0) | 0.000 | 0.000 | 0.001 | 0.001 | 0.078 | 0.493 | 6.177 | 0.077 | 0.493 | 0.096 | 0.019 | s | 18.82 | 846.6 | ||
| Server Jitter SHM(1) | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.724 | 6.000 | 0.000 | 0.724 | 0.114 | 0.017 | s | 12.3 | 342.8 | ||
| Server Jitter SHM(2) | 0.000 | 0.596 | 0.974 | 22.845 | 63.079 | 96.454 | 477.593 | 62.105 | 95.858 | 22.843 | 25.694 | ms | 1.494 | 7.776 | ||
| Server Jitter SHM(3) | 0.000 | 0.053 | 0.073 | 0.253 | 0.779 | 1.033 | 12.858 | 0.706 | 0.980 | 0.254 | 0.313 | ms | 5.463 | 140.9 | ||
| Server Jitter SOCK(0) | 0.000 | 0.451 | 0.658 | 1.622 | 4.097 | 7.521 | 199.488 | 3.438 | 7.070 | 2.193 | 1.979 | ms | 33.87 | 2074 | ||
| Server Jitter SOCK(1) | 0.000 | 0.202 | 0.228 | 0.344 | 0.696 | 0.956 | 104.304 | 0.469 | 0.754 | 0.542 | 0.389 | ms | 122 | 1.84e+04 | ||
| Server Jitter SOCK(2) | 0.000 | 0.600 | 0.948 | 2.374 | 5.637 | 7.241 | 11.212 | 4.689 | 6.641 | 1.481 | 2.715 | ms | 1.233 | 5.001 | ||
| Server Jitter SOCK(3) | 0.000 | 0.196 | 0.221 | 0.324 | 0.536 | 0.729 | 3,009.547 | 0.315 | 0.533 | 17.171 | 0.461 | ms | 152.2 | 2.388e+04 | ||
| Server Offset 104.131.155.175 | -2.525 | -2.525 | -1.209 | 5.368 | 12.615 | 16.334 | 16.334 | 13.824 | 18.859 | 4.610 | 5.570 | ms | 0.3612 | 2.585 | ||
| Server Offset 104.152.220.5 | 8.870 | 8.870 | 8.870 | 11.393 | 12.411 | 12.411 | 12.411 | 3.542 | 3.542 | 1.242 | 10.668 | ms | -0.1693 | 1.649 | ||
| Server Offset 104.167.215.195 | -419.941 | -418.768 | -10.695 | 1.453 | 14.053 | 18.705 | 19.868 | 24.748 | 437.473 | 64.209 | -8.450 | ms | -5.837 | 36.7 | ||
| Server Offset 104.167.241.253 | -1.130 | -1.130 | -1.130 | 3.827 | 174.956 | 174.956 | 174.956 | 176.087 | 176.087 | 77.809 | 54.544 | ms | 0.8304 | 1.696 | ||
| Server Offset 104.234.61.117 | -21.499 | -3.096 | 2.445 | 5.568 | 7.901 | 10.166 | 442.381 | 5.456 | 13.262 | 14.127 | 5.812 | ms | 29.9 | 919.1 | ||
| Server Offset 108.181.201.22 | -1.213 | -1.213 | -1.213 | 9.696 | 16.889 | 16.889 | 16.889 | 18.102 | 18.102 | 5.623 | 7.417 | ms | -0.02663 | 1.756 | ||
| Server Offset 108.59.2.24 | 3.739 | 3.739 | 3.739 | 4.597 | 9.132 | 9.132 | 9.132 | 5.393 | 5.393 | 2.366 | 5.823 | ms | 0.6379 | 1.5 | ||
| Server Offset 108.61.215.221 | -31.255 | -1.287 | 2.473 | 4.811 | 6.744 | 10.357 | 13.004 | 4.271 | 11.644 | 2.291 | 4.690 | ms | -7.298 | 118.5 | ||
| Server Offset 108.61.56.35 | 4.613 | 4.613 | 4.613 | 6.012 | 10.829 | 10.829 | 10.829 | 6.216 | 6.216 | 1.882 | 6.640 | ms | 0.9579 | 2.876 | ||
| Server Offset 108.61.73.243 | -4.642 | 0.420 | 2.263 | 5.013 | 7.453 | 8.990 | 442.001 | 5.190 | 8.569 | 20.919 | 5.974 | ms | 20.5 | 424.1 | ||
| Server Offset 12.205.28.193 | -283.076 | 0.070 | 2.708 | 5.038 | 7.243 | 8.754 | 27.084 | 4.535 | 8.684 | 10.426 | 4.532 | ms | -21.85 | 507.3 | ||
| Server Offset 12.71.198.242 | -567.986 | -567.986 | -567.986 | -8.926 | 5.527 | 5.527 | 5.527 | 573.513 | 573.513 | 281.819 | -249.816 | ms | -0.223 | 1.051 | ||
| Server Offset 129.146.193.200 | -13.392 | -0.800 | 1.678 | 4.741 | 6.985 | 9.104 | 11.567 | 5.307 | 9.904 | 1.817 | 4.617 | ms | -2.078 | 20 | ||
| Server Offset 131.153.171.250 | 2.305 | 2.305 | 2.305 | 6.214 | 6.977 | 6.977 | 6.977 | 4.672 | 4.672 | 2.047 | 5.165 | ms | -0.6341 | 1.5 | ||
| Server Offset 131.239.5.43 | 0.782 | 0.782 | 0.782 | 4.026 | 4.797 | 4.797 | 4.797 | 4.014 | 4.014 | 1.405 | 3.356 | ms | -1.032 | 2.322 | ||
| Server Offset 135.148.100.14 | -31.469 | -1.302 | 3.035 | 6.124 | 10.346 | 103.460 | 109.098 | 7.311 | 104.763 | 17.518 | 8.723 | ms | 4.784 | 26.74 | ||
| Server Offset 137.110.222.27 | -5.819 | -4.877 | -2.098 | 0.991 | 5.793 | 7.199 | 10.485 | 7.892 | 12.076 | 2.211 | 1.182 | ms | 0.5731 | 5.051 | ||
| Server Offset 137.190.2.4 | 8.262 | 8.262 | 8.262 | 10.422 | 12.347 | 12.347 | 12.347 | 4.085 | 4.085 | 1.243 | 10.194 | ms | 0.1927 | 2.51 | ||
| Server Offset 139.177.202.26 | 2.369 | 2.369 | 2.369 | 5.594 | 13.217 | 13.217 | 13.217 | 10.848 | 10.848 | 3.941 | 6.958 | ms | 0.6 | 1.806 | ||
| Server Offset 139.94.144.123 | 7.327 | 7.327 | 7.327 | 7.569 | 8.239 | 8.239 | 8.239 | 0.913 | 0.913 | 0.357 | 7.696 | ms | 0.4162 | 1.533 | ||
| Server Offset 141.11.234.198 | -23.184 | -23.184 | -23.184 | 3.651 | 11.780 | 11.780 | 11.780 | 34.964 | 34.964 | 8.939 | 0.688 | ms | -1.28 | 4.6 | ||
| Server Offset 141.11.89.193 | 2.147 | 2.147 | 2.147 | 3.363 | 5.337 | 5.337 | 5.337 | 3.190 | 3.190 | 1.124 | 3.580 | ms | 0.1122 | 1.688 | ||
| Server Offset 142.202.190.19 | -170.488 | -170.488 | -169.889 | 6.947 | 228.113 | 229.915 | 229.915 | 398.002 | 400.403 | 122.650 | 52.253 | ms | 0.2226 | 2.25 | ||
| Server Offset 143.42.229.154 | -11.954 | -6.689 | -1.054 | 2.237 | 5.081 | 8.112 | 286.021 | 6.135 | 14.801 | 24.501 | 4.211 | ms | 11.27 | 129.1 | ||
| Server Offset 144.202.0.197 | 2.542 | 2.542 | 2.542 | 5.206 | 10.116 | 10.116 | 10.116 | 7.574 | 7.574 | 1.946 | 5.495 | ms | 0.6649 | 3.455 | ||
| Server Offset 144.202.66.214 | -94.866 | -94.866 | -94.866 | -89.704 | -88.958 | -88.958 | -88.958 | 5.908 | 5.908 | 2.060 | -91.017 | ms | -0.812 | 2.336 | ||
| Server Offset 148.135.119.56 | -5.445 | 1.427 | 3.360 | 5.509 | 7.418 | 8.507 | 19.874 | 4.057 | 7.080 | 1.420 | 5.461 | ms | -0.05811 | 13.56 | ||
| Server Offset 149.248.12.167 | 6.974 | 6.974 | 6.974 | 12.448 | 13.486 | 13.486 | 13.486 | 6.511 | 6.511 | 2.871 | 10.594 | ms | -0.3694 | 1.196 | ||
| Server Offset 149.28.200.179 | 1.712 | 1.712 | 3.167 | 5.584 | 10.014 | 25.332 | 25.332 | 6.847 | 23.620 | 3.335 | 5.924 | ms | 4.121 | 23.91 | ||
| Server Offset 149.28.61.105 | 2.916 | 2.916 | 2.916 | 5.252 | 8.017 | 8.017 | 8.017 | 5.100 | 5.100 | 1.667 | 5.088 | ms | 0.4936 | 2.163 | ||
| Server Offset 15.204.198.96 | -806.440 | -806.440 | -15.115 | 0.763 | 4.729 | 8.189 | 8.189 | 19.845 | 814.629 | 169.536 | -36.913 | ms | -4.304 | 19.54 | ||
| Server Offset 15.204.87.223 | -36.284 | -8.344 | -5.158 | -1.169 | 2.341 | 163.102 | 164.832 | 7.498 | 171.447 | 20.085 | 0.950 | ms | 7.803 | 63.6 | ||
| Server Offset 152.70.159.102 | -6.980 | -5.497 | -0.828 | 4.459 | 6.305 | 7.063 | 7.615 | 7.133 | 12.560 | 2.158 | 3.977 | ms | -2.312 | 10.07 | ||
| Server Offset 158.51.134.123 | -10.744 | -0.727 | 2.796 | 5.537 | 7.546 | 9.931 | 15.474 | 4.750 | 10.658 | 1.791 | 5.449 | ms | -1.464 | 17.2 | ||
| Server Offset 158.51.99.19 | -157.868 | -3.714 | 0.315 | 3.544 | 6.019 | 8.972 | 238.853 | 5.704 | 12.686 | 14.413 | 4.009 | ms | 11.84 | 228.2 | ||
| Server Offset 162.159.200.1 | -9.293 | 0.540 | 3.446 | 5.735 | 8.150 | 9.709 | 14.000 | 4.704 | 9.169 | 1.683 | 5.771 | ms | -1.262 | 13.06 | ||
| Server Offset 162.159.200.123 | -6.062 | -6.062 | -5.886 | -0.049 | 7.264 | 9.110 | 9.110 | 13.149 | 15.172 | 4.421 | 0.662 | ms | 0.1749 | 1.786 | ||
| Server Offset 163.123.152.14 | 8.299 | 8.299 | 8.299 | 9.300 | 12.567 | 12.567 | 12.567 | 4.268 | 4.268 | 1.664 | 9.751 | ms | 0.9993 | 2.22 | ||
| Server Offset 168.61.215.74 | -405.890 | -404.187 | -6.577 | 0.381 | 5.171 | 12.210 | 14.954 | 11.748 | 416.397 | 52.876 | -6.803 | ms | -7.353 | 55.33 | ||
| Server Offset 170.187.147.56 | -0.641 | -0.241 | 1.518 | 4.094 | 6.492 | 7.541 | 8.261 | 4.974 | 7.782 | 1.471 | 4.099 | ms | -0.1755 | 3.293 | ||
| Server Offset 172.233.157.223 | -4.047 | -4.047 | -4.047 | 3.553 | 5.955 | 5.955 | 5.955 | 10.002 | 10.002 | 3.165 | 2.404 | ms | -1.04 | 2.663 | ||
| Server Offset 172.233.177.198 | -5.527 | -5.527 | -5.527 | 3.622 | 7.415 | 7.415 | 7.415 | 12.942 | 12.942 | 3.634 | 2.383 | ms | -0.9084 | 3.103 | ||
| Server Offset 172.234.25.10 | 3.105 | 3.105 | 3.105 | 4.382 | 5.884 | 5.884 | 5.884 | 2.779 | 2.779 | 0.948 | 4.394 | ms | -0.02219 | 1.884 | ||
| Server Offset 172.234.37.140 | -9.587 | -9.587 | -9.587 | 4.151 | 11.157 | 11.157 | 11.157 | 20.745 | 20.745 | 4.913 | 3.204 | ms | -0.9547 | 3.843 | ||
| Server Offset 172.234.44.141 | -1.177 | -1.177 | -1.177 | 4.942 | 9.373 | 9.373 | 9.373 | 10.549 | 10.549 | 3.559 | 3.891 | ms | -0.2618 | 1.724 | ||
| Server Offset 172.235.32.243 | 2.812 | 2.812 | 2.812 | 7.583 | 9.521 | 9.521 | 9.521 | 6.709 | 6.709 | 2.571 | 6.667 | ms | -0.3777 | 1.512 | ||
| Server Offset 172.235.60.8 | 0.376 | 0.376 | 0.376 | 3.004 | 16.005 | 16.005 | 16.005 | 15.630 | 15.630 | 4.175 | 4.760 | ms | 1.627 | 4.998 | ||
| Server Offset 172.98.15.13 | 11.306 | 11.306 | 11.306 | 16.540 | 17.265 | 17.265 | 17.265 | 5.959 | 5.959 | 2.760 | 14.156 | ms | 0.02368 | 1.037 | ||
| Server Offset 173.230.154.254 | -28.157 | -28.157 | -28.157 | 4.886 | 11.041 | 11.041 | 11.041 | 39.197 | 39.197 | 13.119 | -0.101 | ms | -1.268 | 3.17 | ||
| Server Offset 173.255.192.10 | -0.501 | -0.501 | -0.501 | 8.854 | 11.145 | 11.145 | 11.145 | 11.646 | 11.646 | 3.481 | 7.479 | ms | -1.158 | 3.37 | ||
| Server Offset 173.255.255.133 | -3.792 | -2.842 | -0.056 | 3.924 | 6.553 | 465.031 | 470.949 | 6.609 | 467.873 | 54.595 | 10.371 | ms | 8.207 | 68.45 | ||
| Server Offset 173.71.68.71 | -11.013 | -4.530 | -1.040 | 3.562 | 6.711 | 464.728 | 470.128 | 7.750 | 469.258 | 52.893 | 9.423 | ms | 8.484 | 73.13 | ||
| Server Offset 173.73.96.68 | -18.437 | -0.510 | 1.981 | 4.646 | 6.731 | 10.129 | 13.198 | 4.750 | 10.640 | 1.878 | 4.544 | ms | -2.345 | 32.53 | ||
| Server Offset 193.29.63.226 | -97.166 | -97.166 | -95.281 | 0.589 | 7.015 | 9.170 | 9.170 | 102.297 | 106.336 | 42.310 | -21.757 | ms | -1.137 | 2.322 | ||
| Server Offset 198.137.202.32 | -1.462 | -1.396 | 1.619 | 5.827 | 7.932 | 11.548 | 12.433 | 6.313 | 12.944 | 1.882 | 5.599 | ms | -0.7187 | 6.807 | ||
| Server Offset 198.199.14.19 | -4.168 | -4.168 | -4.168 | 3.527 | 9.207 | 9.207 | 9.207 | 13.374 | 13.374 | 3.647 | 3.201 | ms | -0.3311 | 2.34 | ||
| Server Offset 198.211.103.209 | -15.435 | -15.435 | -7.248 | 1.023 | 11.374 | 11.645 | 11.645 | 18.622 | 27.080 | 5.487 | 1.111 | ms | -0.25 | 4.025 | ||
| Server Offset 198.23.249.167 | 4.961 | 4.961 | 4.961 | 12.406 | 14.734 | 14.734 | 14.734 | 9.772 | 9.772 | 3.037 | 10.920 | ms | -0.6652 | 2.344 | ||
| Server Offset 198.46.254.130 | -2.287 | 0.292 | 2.403 | 4.430 | 9.560 | 11.525 | 16.197 | 7.157 | 11.234 | 2.139 | 4.805 | ms | 1.192 | 5.984 | ||
| Server Offset 198.60.22.240 | -144.129 | 0.237 | 8.087 | 11.026 | 13.035 | 16.771 | 294.299 | 4.948 | 16.534 | 23.436 | 11.946 | ms | 8.986 | 126.2 | ||
| Server Offset 199.68.201.235 | 2.195 | 2.195 | 2.320 | 4.878 | 7.295 | 9.614 | 9.614 | 4.975 | 7.419 | 1.530 | 4.830 | ms | 1.056 | 5.383 | ||
| Server Offset 2001:19f0:1000:9b31:5400:5ff:fe67:bab4 (ntp.swyn.net) | 0.214 | 2.406 | 3.442 | 5.288 | 7.200 | 7.864 | 9.487 | 3.758 | 5.458 | 1.200 | 5.303 | ms | -0.1227 | 3.446 | ||
| Server Offset 2001:19f0:1590:5123:1057:a11:da7a:1 (lithium.constant.com) | 0.989 | 0.989 | 0.989 | 6.668 | 7.419 | 7.419 | 7.419 | 6.430 | 6.430 | 2.339 | 5.470 | ms | -1.22 | 2.835 | ||
| Server Offset 2001:19f0:6401:400:5400:4ff:fec3:522a | -8.793 | -3.395 | -1.763 | 0.719 | 3.100 | 6.282 | 10.062 | 4.863 | 9.677 | 1.724 | 0.695 | ms | -0.118 | 8.702 | ||
| Server Offset 2001:418:3ff::53 (x.ns.gin.ntt.net) | 4.247 | 4.247 | 4.247 | 7.231 | 8.571 | 8.571 | 8.571 | 4.324 | 4.324 | 1.678 | 6.539 | ms | -0.2545 | 1.376 | ||
| Server Offset 2001:418:8405:4002::12 | -281.832 | -281.832 | -281.832 | 6.130 | 43.679 | 43.679 | 43.679 | 325.511 | 325.511 | 75.678 | -13.076 | ms | -3.151 | 11.39 | ||
| Server Offset 2001:418:8405:4002::3 | -0.825 | 1.964 | 3.144 | 5.203 | 8.084 | 23.850 | 24.486 | 4.940 | 21.886 | 3.270 | 5.666 | ms | 4.264 | 23.47 | ||
| Server Offset 2001:470:1f07:198::123 (vps-lga1.orleans.ddnss.de) | -43.336 | -25.868 | -0.459 | 3.003 | 5.329 | 102.804 | 104.408 | 5.787 | 128.672 | 14.038 | 4.377 | ms | 5.842 | 42.8 | ||
| Server Offset 2001:470:1f07:24f::123 | 5.692 | 5.692 | 5.692 | 8.660 | 52.245 | 52.245 | 52.245 | 46.552 | 46.552 | 15.577 | 16.463 | ms | 1.347 | 3.154 | ||
| Server Offset 2001:470:1f07:d::5 (ns2.pads.ufrj.br) | -63.029 | -25.579 | -3.547 | 9.292 | 14.309 | 18.491 | 26.835 | 17.856 | 44.069 | 7.073 | 8.138 | ms | -3.936 | 26.2 | ||
| Server Offset 2001:470:1f2c:60:123:123:123:123 | -34.941 | -34.941 | -34.941 | 5.417 | 179.029 | 179.029 | 179.029 | 213.970 | 213.970 | 83.019 | 55.085 | ms | 0.6389 | 1.528 | ||
| Server Offset 2001:470:b:22d::123 | -4.739 | -4.739 | -4.577 | -2.037 | -0.635 | -0.179 | -0.179 | 3.943 | 4.560 | 1.286 | -2.350 | ms | -0.3618 | 2.047 | ||
| Server Offset 2001:470:e114::d6:12 (1.md.ntp.md) | -10.323 | -5.218 | -0.737 | 4.552 | 8.145 | 464.586 | 465.594 | 8.883 | 469.804 | 60.310 | 12.220 | ms | 7.342 | 55.02 | ||
| Server Offset 2001:470:e114::d6:c5 (t2.davehart.net) | 4.264 | 4.264 | 4.264 | 4.264 | 4.264 | 4.264 | 4.264 | 0.000 | 0.000 | 0.000 | 4.264 | ms | nan | nan | ||
| Server Offset 2001:470:e8dc:10::123 | -0.028 | 0.001 | 0.004 | 0.006 | 0.009 | 0.011 | 589.091 | 0.005 | 0.010 | 20.006 | 0.687 | s | 29.38 | 864 | ||
| Server Offset 2001:4998:58:183a::1000 (t2.time.bf1.yahoo.com) | -809.971 | -4.133 | 0.925 | 5.173 | 7.699 | 8.851 | 11.403 | 6.774 | 12.984 | 41.024 | 2.773 | ms | -19.54 | 384.4 | ||
| Server Offset 2001:4998:c:1028::1000 (t1.time.gq1.yahoo.com) | -0.195 | -0.167 | 1.359 | 3.625 | 5.714 | 8.822 | 8.875 | 4.355 | 8.989 | 1.443 | 3.675 | ms | 0.4961 | 4.819 | ||
| Server Offset 2001:4998:c:1028::1001 (t2.time.gq1.yahoo.com) | -157.180 | 0.965 | 3.243 | 5.473 | 7.719 | 9.995 | 23.242 | 4.475 | 9.030 | 5.538 | 5.305 | ms | -26.07 | 749.2 | ||
| Server Offset 2001:558:6014:17:8dc5:5575:5560:2cb6 | -281.200 | -281.200 | -126.154 | 4.670 | 171.115 | 172.773 | 172.773 | 297.269 | 453.972 | 76.160 | 7.959 | ms | -0.5863 | 8.15 | ||
| Server Offset 2001:559:2be:3::1001 | -175.433 | -175.433 | -170.364 | 6.118 | 11.772 | 14.071 | 14.071 | 182.136 | 189.504 | 60.406 | -18.925 | ms | -2.06 | 5.416 | ||
| Server Offset 2001:678:8::123 (any.time.nl) | -6.894 | -6.894 | -6.894 | 1.568 | 214.705 | 214.705 | 214.705 | 221.599 | 221.599 | 95.535 | 59.773 | ms | 0.9473 | 1.903 | ||
| Server Offset 204.10.18.144 | 9.179 | 9.179 | 9.179 | 11.384 | 12.007 | 12.007 | 12.007 | 2.829 | 2.829 | 1.213 | 10.857 | ms | -0.5696 | 1.5 | ||
| Server Offset 204.197.163.71 | -173.244 | -1.861 | 0.406 | 2.637 | 4.342 | 5.127 | 14.383 | 3.936 | 6.988 | 8.636 | 2.114 | ms | -19.71 | 398.6 | ||
| Server Offset 204.2.134.162 | 3.726 | 3.726 | 3.726 | 9.487 | 10.513 | 10.513 | 10.513 | 6.787 | 6.787 | 2.284 | 8.433 | ms | -0.8439 | 2.293 | ||
| Server Offset 205.233.73.201 | -29.812 | -29.812 | -18.984 | 8.160 | 221.194 | 221.908 | 221.908 | 240.177 | 251.721 | 109.553 | 72.756 | ms | 0.5569 | 1.346 | ||
| Server Offset 208.113.130.146 | -807.971 | -2.044 | 0.597 | 5.657 | 8.325 | 10.241 | 17.688 | 7.728 | 12.286 | 41.081 | 3.296 | ms | -19.56 | 384.7 | ||
| Server Offset 208.67.72.43 | -45.246 | -45.246 | -45.246 | -2.385 | 1.915 | 1.915 | 1.915 | 47.161 | 47.161 | 14.659 | -6.938 | ms | -2.157 | 5.869 | ||
| Server Offset 208.67.72.50 | -411.370 | -407.370 | -12.259 | -1.276 | 14.804 | 461.290 | 467.446 | 27.063 | 868.660 | 105.580 | 8.636 | ms | 1.618 | 16.62 | ||
| Server Offset 208.67.75.242 | -4.622 | -0.573 | 1.079 | 4.378 | 7.071 | 10.826 | 240.553 | 5.992 | 11.398 | 17.431 | 5.561 | ms | 13.06 | 173.8 | ||
| Server Offset 212.227.240.160 | 0.447 | 1.367 | 2.617 | 5.039 | 7.008 | 11.813 | 14.498 | 4.391 | 10.446 | 1.596 | 5.037 | ms | 1.279 | 9.832 | ||
| Server Offset 216.229.4.66 | -5.209 | -5.209 | -5.209 | 4.542 | 13.961 | 13.961 | 13.961 | 19.169 | 19.169 | 4.570 | 4.299 | ms | 0.05583 | 2.76 | ||
| Server Offset 216.229.4.69 | -565.822 | -565.822 | -561.261 | 0.035 | 3.427 | 7.531 | 7.531 | 564.688 | 573.353 | 217.192 | -101.392 | ms | -1.65 | 3.722 | ||
| Server Offset 216.240.36.24 | -5.803 | -5.803 | -2.568 | 1.026 | 7.930 | 10.160 | 10.160 | 10.498 | 15.963 | 3.307 | 1.221 | ms | 0.7489 | 4.49 | ||
| Server Offset 216.31.17.12 | -13.524 | -13.524 | -13.524 | 1.518 | 6.326 | 6.326 | 6.326 | 19.850 | 19.850 | 5.541 | -1.109 | ms | -0.9513 | 3.269 | ||
| Server Offset 23.111.186.186 | 0.800 | 0.800 | 0.800 | 2.292 | 3.617 | 3.617 | 3.617 | 2.817 | 2.817 | 0.849 | 2.280 | ms | -0.2598 | 2.078 | ||
| Server Offset 23.131.160.7 | -14.783 | 1.244 | 2.750 | 5.398 | 7.474 | 8.521 | 12.984 | 4.724 | 7.277 | 1.521 | 5.330 | ms | -1.272 | 16.38 | ||
| Server Offset 23.141.40.123 | 27.455 | 27.455 | 27.455 | 33.456 | 37.132 | 37.132 | 37.132 | 9.678 | 9.678 | 2.992 | 32.642 | ms | -0.3048 | 2.39 | ||
| Server Offset 23.142.248.8 | 8.594 | 8.594 | 8.594 | 10.977 | 11.802 | 11.802 | 11.802 | 3.207 | 3.207 | 1.009 | 10.550 | ms | -0.8827 | 2.771 | ||
| Server Offset 23.142.248.9 | -0.177 | -0.177 | -0.177 | 2.494 | 8.498 | 8.498 | 8.498 | 8.675 | 8.675 | 2.694 | 2.971 | ms | 0.6979 | 2.389 | ||
| Server Offset 23.143.196.199 | 2.248 | 2.248 | 2.248 | 3.906 | 5.387 | 5.387 | 5.387 | 3.139 | 3.139 | 1.032 | 4.058 | ms | -0.2914 | 2.021 | ||
| Server Offset 23.150.41.122 | -0.013 | -0.013 | 1.940 | 4.590 | 6.567 | 10.828 | 10.828 | 4.627 | 10.841 | 1.746 | 4.571 | ms | 0.5098 | 5.973 | ||
| Server Offset 23.150.41.123 | -13.071 | -0.293 | 5.503 | 8.553 | 11.685 | 15.470 | 291.773 | 6.182 | 15.763 | 17.232 | 9.542 | ms | 15.97 | 260.9 | ||
| Server Offset 23.155.40.38 | -288.208 | -156.059 | -4.815 | 1.534 | 4.285 | 10.104 | 18.366 | 9.100 | 166.163 | 22.289 | -1.539 | ms | -9.379 | 102 | ||
| Server Offset 23.157.160.168 | -2.076 | -0.290 | 1.682 | 4.081 | 9.612 | 13.302 | 15.548 | 7.929 | 13.592 | 2.390 | 4.490 | ms | 1.867 | 8.727 | ||
| Server Offset 23.168.136.132 | -37.613 | -37.613 | -37.613 | 5.175 | 9.499 | 9.499 | 9.499 | 47.112 | 47.112 | 13.628 | -0.158 | ms | -2.166 | 6.233 | ||
| Server Offset 23.168.24.210 | 7.914 | 7.914 | 7.914 | 12.589 | 13.467 | 13.467 | 13.467 | 5.553 | 5.553 | 2.207 | 10.952 | ms | -0.2124 | 1.412 | ||
| Server Offset 23.186.168.1 | -3.842 | -3.842 | -3.842 | 2.397 | 8.346 | 8.346 | 8.346 | 12.188 | 12.188 | 4.121 | 2.680 | ms | -0.2252 | 2.014 | ||
| Server Offset 23.186.168.123 | -3.755 | -1.507 | 0.222 | 2.615 | 4.450 | 5.651 | 13.437 | 4.228 | 7.158 | 1.430 | 2.525 | ms | -0.02099 | 7.779 | ||
| Server Offset 23.186.168.126 | -5.345 | -3.200 | -1.287 | 1.767 | 4.438 | 5.722 | 166.185 | 5.726 | 8.922 | 10.343 | 2.300 | ms | 15.19 | 239 | ||
| Server Offset 23.186.168.127 | 2.017 | 2.017 | 2.017 | 5.113 | 8.863 | 8.863 | 8.863 | 6.846 | 6.846 | 2.456 | 5.105 | ms | 0.3935 | 1.998 | ||
| Server Offset 23.186.168.128 | -571.345 | -2.646 | 0.616 | 3.786 | 5.861 | 6.834 | 11.189 | 5.245 | 9.479 | 32.846 | 1.503 | ms | -16.49 | 282.6 | ||
| Server Offset 23.186.168.129 | -5.851 | -1.947 | -0.334 | 2.997 | 5.760 | 6.949 | 10.375 | 6.094 | 8.896 | 1.869 | 2.897 | ms | -0.2443 | 4.135 | ||
| Server Offset 23.186.168.130 | -4.461 | -4.461 | -4.284 | 0.164 | 5.449 | 7.796 | 7.796 | 9.733 | 12.257 | 3.707 | 0.733 | ms | 0.06193 | 1.677 | ||
| Server Offset 23.186.168.131 | -4.751 | -0.429 | 1.142 | 3.700 | 5.655 | 6.700 | 10.070 | 4.513 | 7.129 | 1.408 | 3.624 | ms | -0.5634 | 5.686 | ||
| Server Offset 23.186.168.132 | -6.108 | -0.734 | 0.944 | 3.623 | 5.856 | 7.065 | 9.350 | 4.912 | 7.799 | 1.547 | 3.559 | ms | -0.388 | 4.285 | ||
| Server Offset 23.186.168.3 | -11.209 | -6.287 | -3.243 | -0.938 | 9.206 | 10.476 | 11.413 | 12.449 | 16.763 | 3.379 | -0.171 | ms | 1.792 | 6.524 | ||
| Server Offset 23.94.221.138 | 8.003 | 8.003 | 8.003 | 11.978 | 13.637 | 13.637 | 13.637 | 5.634 | 5.634 | 1.789 | 11.308 | ms | -0.8786 | 2.486 | ||
| Server Offset 23.95.49.216 | -5.139 | -2.109 | 0.660 | 3.522 | 5.991 | 7.369 | 10.716 | 5.332 | 9.478 | 1.730 | 3.430 | ms | -0.7082 | 6.455 | ||
| Server Offset 240b:4002:100:9f00:5bd1:9512:8a8b:25e | 1.797 | 1.797 | 1.797 | 4.344 | 8.047 | 8.047 | 8.047 | 6.249 | 6.249 | 2.182 | 4.694 | ms | 0.2446 | 1.809 | ||
| Server Offset 240b:4004:108:200:8314:1a08:4cee:26d6 | -53.252 | -30.228 | -3.522 | 4.633 | 7.430 | 9.190 | 16.676 | 10.952 | 39.418 | 6.135 | 3.553 | ms | -4.789 | 30.29 | ||
| Server Offset 240b:4004:108:200:8314:1a08:4cee:26d9 | 3.332 | 3.332 | 3.332 | 5.399 | 14.354 | 14.354 | 14.354 | 11.022 | 11.022 | 4.410 | 6.823 | ms | 1.061 | 2.259 | ||
| Server Offset 2600:1700:3d24:740f:9524:529a:6489:d48f | 8.238 | 8.238 | 9.877 | 14.429 | 17.946 | 17.946 | 17.946 | 8.069 | 9.708 | 2.359 | 13.755 | ms | -0.5972 | 2.747 | ||
| Server Offset 2600:1700:5455:a70::7b:1 | -809.818 | -809.818 | -802.944 | -1.720 | 6.474 | 21.994 | 21.994 | 809.418 | 831.812 | 176.723 | -42.075 | ms | -4.096 | 17.79 | ||
| Server Offset 2600:1700:5a0f:ee00:78cf:8c0:e759:65d3 | -16.983 | -16.983 | 2.347 | 14.361 | 471.310 | 472.188 | 472.188 | 468.963 | 489.171 | 193.989 | 112.827 | ms | 1.297 | 2.69 | ||
| Server Offset 2600:1700:5a0f:ee00::314:1b | -0.511 | 1.698 | 6.788 | 11.589 | 16.910 | 21.438 | 25.234 | 10.122 | 19.741 | 3.117 | 11.826 | ms | 0.01519 | 6.247 | ||
| Server Offset 2600:1700:5a0f:ee00::314:2b | 0.372 | 0.372 | 0.372 | 12.636 | 16.769 | 16.769 | 16.769 | 16.398 | 16.398 | 3.764 | 12.100 | ms | -1.682 | 6.304 | ||
| Server Offset 2600:1702:7400:9ac0::314:5a | 0.498 | 0.498 | 0.498 | 13.966 | 17.731 | 17.731 | 17.731 | 17.233 | 17.233 | 5.163 | 12.245 | ms | -1.274 | 3.293 | ||
| Server Offset 2600:1702:7400:9ac0::5b | 0.162 | 0.162 | 0.162 | 8.450 | 11.368 | 11.368 | 11.368 | 11.206 | 11.206 | 3.725 | 6.660 | ms | -0.2939 | 1.735 | ||
| Server Offset 2600:1f13:2c1:2e00::be00:5 | -282.490 | -1.401 | 3.361 | 6.350 | 9.277 | 21.057 | 75.600 | 5.916 | 22.458 | 11.306 | 6.295 | ms | -17.94 | 473.5 | ||
| Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) | -155.691 | -5.511 | -3.335 | 3.558 | 6.419 | 8.309 | 110.743 | 9.755 | 13.821 | 4.172 | 2.779 | ms | -7.728 | 503.4 | ||
| Server Offset 2600:1f16:42a:1d00:2169:fe07:2acc:6002 (ohio.time.system76.com) | -159.116 | -6.028 | -1.808 | 3.899 | 6.770 | 8.633 | 99.329 | 8.578 | 14.661 | 4.630 | 3.294 | ms | -16.25 | 578.4 | ||
| Server Offset 2600:1f18:4c51:e200:e142:210a:306d:4872 (virginia.time.system76.com) | -158.177 | -23.179 | -3.286 | 4.342 | 7.565 | 10.215 | 125.029 | 10.851 | 33.394 | 6.337 | 3.153 | ms | -6.944 | 182.2 | ||
| Server Offset 2600:2600::99 (ntp1.wiktel.com) | 10.504 | 10.504 | 10.504 | 11.340 | 11.340 | 11.340 | 11.340 | 0.836 | 0.836 | 0.418 | 10.922 | ms | -6.279e-15 | 1 | ||
| Server Offset 2600:3c00::f03c:91ff:fe05:b640 (dev.smatwebdesign.com) | 10.745 | 10.745 | 10.745 | 10.745 | 10.745 | 10.745 | 10.745 | 0.000 | 0.000 | 0.000 | 10.745 | ms | nan | nan | ||
| Server Offset 2600:3c00:e000:256::123:0 (ntp5-2.mattnordhoffdns.net) | -7.895 | -0.183 | 1.291 | 4.437 | 7.174 | 9.401 | 23.862 | 5.883 | 9.584 | 1.951 | 4.342 | ms | 0.3005 | 6.816 | ||
| Server Offset 2600:3c00:e000:318::1 (jane.qotw.net) | -28.246 | -0.004 | 1.379 | 3.315 | 5.169 | 6.398 | 10.314 | 3.789 | 6.402 | 1.515 | 3.268 | ms | -6.661 | 141.7 | ||
| Server Offset 2600:3c01::f03c:93ff:fe5b:8a7d (us-west-1.clearnet.pw) | 2.725 | 2.725 | 2.725 | 5.114 | 14.625 | 14.625 | 14.625 | 11.900 | 11.900 | 4.070 | 5.808 | ms | 1.545 | 3.777 | ||
| Server Offset 2600:3c01:e000:7e6::123 (time1.sigi.net) | -170.467 | 0.374 | 3.399 | 5.684 | 7.901 | 8.850 | 11.725 | 4.503 | 8.476 | 9.664 | 5.114 | ms | -17.67 | 320.7 | ||
| Server Offset 2600:3c02::f03c:92ff:fe96:dc0 | -21.719 | -4.622 | -0.261 | 6.280 | 12.408 | 13.569 | 18.625 | 12.669 | 18.191 | 3.801 | 6.313 | ms | -1.28 | 11.52 | ||
| Server Offset 2600:3c02::f03c:94ff:fe59:f411 | 3.748 | 3.748 | 3.748 | 6.064 | 12.748 | 12.748 | 12.748 | 9.000 | 9.000 | 3.879 | 7.163 | ms | 0.6006 | 1.484 | ||
| Server Offset 2600:3c02:e000:74::123:0 (atl-ntp2-0.mattnordhoffdns.net) | -1.758 | 0.272 | 2.422 | 5.290 | 7.506 | 11.065 | 14.186 | 5.084 | 10.793 | 1.733 | 5.279 | ms | 0.2754 | 6.817 | ||
| Server Offset 2600:3c02:e000:bc::123:0 (ntp7-2.mattnordhoffdns.net) | 0.867 | 0.867 | 1.114 | 3.790 | 6.386 | 7.915 | 7.915 | 5.272 | 7.048 | 1.512 | 3.637 | ms | 0.418 | 3.502 | ||
| Server Offset 2600:3c02:e001:1d00::123:0 (atl-ntp0-0.mattnordhoffdns.net) | -572.795 | -572.795 | -572.795 | -9.263 | 4.262 | 4.262 | 4.262 | 577.057 | 577.057 | 280.556 | -253.542 | ms | -0.2234 | 1.051 | ||
| Server Offset 2600:3c03::f03c:91ff:fedf:1e98 (li1.forfun.net) | -11.563 | -4.087 | -0.894 | 6.068 | 13.355 | 21.391 | 26.413 | 14.249 | 25.478 | 4.903 | 6.241 | ms | 0.36 | 5.024 | ||
| Server Offset 2600:3c03::f03c:94ff:fe59:d3de | 2.854 | 2.854 | 2.854 | 2.958 | 4.537 | 4.537 | 4.537 | 1.683 | 1.683 | 0.770 | 3.449 | ms | 0.6976 | 1.5 | ||
| Server Offset 2600:3c03:e002:1300::10 (ntp.electronmill.com) | -3.742 | -3.742 | -3.742 | 3.270 | 6.177 | 6.177 | 6.177 | 9.919 | 9.919 | 3.310 | 1.757 | ms | -0.3528 | 1.728 | ||
| Server Offset 2600:3c06::f03c:94ff:fee2:9c28 | 5.742 | 5.742 | 5.742 | 7.946 | 15.389 | 15.389 | 15.389 | 9.646 | 9.646 | 3.904 | 8.785 | ms | 1.004 | 2.198 | ||
| Server Offset 2600:3c06::f03c:94ff:fee2:c53a | 7.934 | 7.934 | 7.934 | 10.652 | 34.769 | 34.769 | 34.769 | 26.835 | 26.835 | 12.061 | 17.785 | ms | 0.6803 | 1.5 | ||
| Server Offset 2600:4040:3037:e600::1 | 2.842 | 2.842 | 2.842 | 6.051 | 6.051 | 6.051 | 6.051 | 3.209 | 3.209 | 1.605 | 4.447 | ms | -8.009e-16 | 1 | ||
| Server Offset 2600:4040:e0da:f000::cbb9:201a | -99.353 | -99.353 | -97.880 | 3.306 | 8.180 | 46.292 | 46.292 | 106.060 | 145.645 | 34.906 | -8.837 | ms | -1.974 | 5.486 | ||
| Server Offset 2601:18a:8081:3600:a923:2e66:e3d2:8c95 | -2.328 | -2.328 | -2.328 | 8.140 | 10.732 | 10.732 | 10.732 | 13.060 | 13.060 | 4.378 | 6.247 | ms | -0.9586 | 2.744 | ||
| Server Offset 2602:291:69::8 (time2.tritan-bb.net) | -87.855 | -87.855 | -87.855 | -86.413 | -85.482 | -85.482 | -85.482 | 2.373 | 2.373 | 0.712 | -86.511 | ms | -0.5905 | 2.861 | ||
| Server Offset 2602:291:69::9 (time.tritan-bb.net) | -570.253 | -570.253 | -566.451 | 6.098 | 295.584 | 297.286 | 297.286 | 862.034 | 867.538 | 189.440 | -9.823 | ms | -1.679 | 6.932 | ||
| Server Offset 2602:2b7:d11:f4::122 (s2-b.time.mci1.us.rozint.net) | -158.684 | -3.707 | -0.110 | 2.070 | 4.337 | 8.146 | 25.990 | 4.448 | 11.853 | 7.539 | 1.731 | ms | -18.9 | 391.6 | ||
| Server Offset 2602:2b7:d11:f4::123 (s2-a.time.mci1.us.rozint.net) | 7.226 | 7.226 | 7.226 | 8.619 | 9.227 | 9.227 | 9.227 | 2.002 | 2.002 | 0.838 | 8.357 | ms | -0.4377 | 1.5 | ||
| Server Offset 2602:2eb:2:95:1234:5678:9abc:def0 | -177.116 | -4.361 | -1.059 | 2.594 | 6.566 | 8.773 | 240.974 | 7.624 | 13.133 | 11.661 | 2.870 | ms | 12.1 | 337.6 | ||
| Server Offset 2602:80b:5000::36 (time.meme.holdings) | -26.339 | -9.392 | 1.266 | 5.949 | 9.817 | 23.455 | 24.890 | 8.551 | 32.847 | 4.707 | 5.688 | ms | -2.123 | 23.68 | ||
| Server Offset 2602:81b:9000::c10c (time.sea.ordinaladvisors.com) | -2.396 | -2.396 | -2.396 | 0.924 | 11.083 | 11.083 | 11.083 | 13.479 | 13.479 | 4.287 | 2.602 | ms | 0.7321 | 2.194 | ||
| Server Offset 2602:f9ba:69::210 (as393746.customer.mci.tritan-bb.net) | -412.469 | -410.991 | -8.504 | 2.281 | 14.386 | 25.256 | 77.682 | 22.890 | 436.248 | 59.543 | -5.197 | ms | -6.469 | 44.15 | ||
| Server Offset 2602:f9bd:80:100::a (time.circlevps.net) | -64.334 | -0.054 | 2.880 | 5.079 | 7.169 | 10.479 | 288.638 | 4.288 | 10.533 | 17.604 | 5.956 | ms | 15.32 | 246.4 | ||
| Server Offset 2602:fc2f:100:9800::dead:beef | -48.947 | -0.453 | 3.020 | 6.675 | 10.815 | 15.794 | 240.110 | 7.795 | 16.247 | 16.385 | 7.836 | ms | 13.11 | 183.2 | ||
| Server Offset 2602:fd50:100:108:3491:d3b2:eef8:f324 (ntp.netlinkify.com) | -2.937 | -2.937 | -2.937 | 3.954 | 9.493 | 9.493 | 9.493 | 12.430 | 12.430 | 3.348 | 4.033 | ms | -0.4303 | 3.037 | ||
| Server Offset 2602:fe2e:3:d:f9:c7ff:fef5:379c | 3.035 | 3.035 | 3.035 | 6.211 | 8.657 | 8.657 | 8.657 | 5.622 | 5.622 | 1.762 | 5.927 | ms | -0.1747 | 2.107 | ||
| Server Offset 2602:feda:30:ae86:2fc:98ff:fecf:fe94 | -8.543 | -4.131 | 0.620 | 3.457 | 5.982 | 7.057 | 10.590 | 5.362 | 11.188 | 1.910 | 3.332 | ms | -1.439 | 10.13 | ||
| Server Offset 2602:ff06:725:100::123 (oldtime2.sigi.net) | -8.456 | 0.658 | 2.953 | 4.980 | 7.081 | 8.916 | 11.994 | 4.128 | 8.258 | 1.545 | 5.012 | ms | -1.787 | 18.35 | ||
| Server Offset 2602:ff23:50:3c2::1 (dns-e.ns4v.icu) | -414.428 | -412.103 | -11.870 | 2.663 | 20.110 | 279.792 | 280.771 | 31.980 | 691.895 | 70.162 | 0.900 | ms | -2.687 | 27.89 | ||
| Server Offset 2603:c020:0:8369:0:ba11:ba11:ba11 | -422.469 | -422.469 | -419.944 | -5.879 | 4.024 | 4.850 | 4.850 | 423.968 | 427.319 | 143.126 | -63.235 | ms | -2.082 | 5.347 | ||
| Server Offset 2603:c020:0:8369:1111:1111:1111:1112 | -55.331 | -55.331 | -24.536 | -3.892 | 276.097 | 276.136 | 276.136 | 300.633 | 331.467 | 96.209 | 43.048 | ms | 1.624 | 4.338 | ||
| Server Offset 2603:c020:0:8369:607:e532:d534:7109 | -20.164 | -20.164 | -20.164 | -5.038 | -0.723 | -0.723 | -0.723 | 19.441 | 19.441 | 5.152 | -6.685 | ms | -1.218 | 3.706 | ||
| Server Offset 2603:c020:0:8369::bad:babe | -16.649 | -16.649 | -12.050 | -3.794 | 3.680 | 3.680 | 3.680 | 15.730 | 20.329 | 5.040 | -4.943 | ms | -0.3208 | 2.65 | ||
| Server Offset 2603:c020:0:8369::bad:beef | -10.534 | -10.534 | -10.534 | -4.440 | -0.095 | -0.095 | -0.095 | 10.439 | 10.439 | 2.730 | -5.174 | ms | -0.1283 | 2.373 | ||
| Server Offset 2603:c020:0:8369::f00d:feed | -17.667 | -17.667 | -15.791 | -5.100 | 453.988 | 458.206 | 458.206 | 469.779 | 475.874 | 188.222 | 87.341 | ms | 1.435 | 3.061 | ||
| Server Offset 2603:c020:0:8369::feeb:dab | -19.462 | -19.462 | -14.510 | -5.358 | 453.345 | 453.880 | 453.880 | 467.855 | 473.342 | 152.281 | 49.860 | ms | 2.262 | 6.129 | ||
| Server Offset 2603:c020:0:8369:feed:feed:feed:feed | -18.686 | -18.686 | -18.686 | -5.363 | -1.212 | -1.212 | -1.212 | 17.474 | 17.474 | 4.007 | -6.304 | ms | -1.91 | 6.79 | ||
| Server Offset 2603:c020:400e:ea00:ccfe:ba34:7215:d4f6 | -3.394 | 0.533 | 3.024 | 5.787 | 9.133 | 10.071 | 10.972 | 6.109 | 9.538 | 1.912 | 5.800 | ms | -0.3737 | 4.794 | ||
| Server Offset 2603:c020:6:b900:6b54:1390:4afd:814a | -420.366 | -420.366 | -420.366 | -15.121 | 2.174 | 2.174 | 2.174 | 422.540 | 422.540 | 183.604 | -122.964 | ms | -0.9887 | 1.983 | ||
| Server Offset 2603:c020:6:b900:ed2f:b442:fee7:d9b9 | -9.081 | -9.081 | -9.081 | -3.889 | -1.558 | -1.558 | -1.558 | 7.523 | 7.523 | 2.325 | -4.454 | ms | -0.9557 | 3.036 | ||
| Server Offset 2603:c024:c005:a600:8eb1:2863:5838:9880 | 6.649 | 6.649 | 6.649 | 6.649 | 6.649 | 6.649 | 6.649 | 0.000 | 0.000 | 0.000 | 6.649 | ms | nan | nan | ||
| Server Offset 2603:c024:c005:a600:efb6:d213:cad8:251d | 1.713 | 1.713 | 1.713 | 11.865 | 68.213 | 68.213 | 68.213 | 66.499 | 66.499 | 21.793 | 19.547 | ms | 1.448 | 3.682 | ||
| Server Offset 2604:180:f3::4a4 (dutch.arpnet.net) | 13.327 | 13.327 | 13.327 | 16.038 | 19.997 | 19.997 | 19.997 | 6.670 | 6.670 | 2.064 | 16.117 | ms | 0.6723 | 2.663 | ||
| Server Offset 2604:2dc0:100:25e2:2ab9:2b59:40e7:1 | 4.360 | 4.360 | 7.868 | 9.469 | 13.253 | 17.815 | 17.815 | 5.385 | 13.455 | 2.164 | 9.765 | ms | 1.273 | 7.496 | ||
| Server Offset 2604:2dc0:100:4d6:: | 6.451 | 6.451 | 6.451 | 7.846 | 12.197 | 12.197 | 12.197 | 5.746 | 5.746 | 2.175 | 8.548 | ms | 0.9328 | 2.204 | ||
| Server Offset 2604:2dc0:101:200::151 (vps-646a3726.vps.ovh.us) | 1.015 | 4.439 | 6.129 | 8.198 | 10.741 | 12.700 | 28.542 | 4.612 | 8.261 | 1.536 | 8.275 | ms | 1.156 | 15.73 | ||
| Server Offset 2604:2dc0:202:300::140d (ovh.maxhost.io) | -10.884 | -6.103 | -4.364 | -1.787 | 0.663 | 2.038 | 13.335 | 5.027 | 8.141 | 1.665 | -1.837 | ms | 0.09333 | 10.2 | ||
| Server Offset 2604:2dc0:202:300::2459 (zt-rt-west.us.lanningnetworks.com) | -49.930 | -36.749 | -6.555 | 2.041 | 5.114 | 6.502 | 22.290 | 11.670 | 43.251 | 5.807 | 0.770 | ms | -4.61 | 31.25 | ||
| Server Offset 2604:4300:a:299::164 | -9.675 | -9.675 | -6.261 | -0.158 | 3.067 | 3.865 | 3.865 | 9.328 | 13.539 | 3.536 | -1.195 | ms | -0.6405 | 2.55 | ||
| Server Offset 2604:4500:6:7c9::186 (us-east-2.clearnet.pw) | -802.674 | -802.674 | -802.674 | 2.272 | 9.840 | 9.840 | 9.840 | 812.514 | 812.514 | 371.058 | -243.393 | ms | -0.8332 | 1.694 | ||
| Server Offset 2604:8800:52:81:38:229:52:9 (ntp08.cymru.com) | 4.759 | 4.759 | 4.759 | 5.795 | 36.164 | 36.164 | 36.164 | 31.405 | 31.405 | 14.567 | 15.573 | ms | 0.7044 | 1.5 | ||
| Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) | -97.614 | -97.614 | -97.614 | -96.252 | -95.198 | -95.198 | -95.198 | 2.416 | 2.416 | 0.727 | -96.393 | ms | -0.05135 | 2.552 | ||
| Server Offset 2604:a880:1:20::1fd:1001 (jitter.tickadj.net) | -40.303 | -1.773 | 0.146 | 2.726 | 5.501 | 103.648 | 104.341 | 5.355 | 105.421 | 14.429 | 4.427 | ms | 6.057 | 42.23 | ||
| Server Offset 2604:a880:400:d0::4ed:f001 (unifi.versadns.com) | -6.372 | -6.372 | -3.109 | 11.458 | 218.960 | 218.960 | 218.960 | 222.069 | 225.332 | 83.767 | 47.473 | ms | 1.451 | 3.181 | ||
| Server Offset 2604:a880:800:a1::ec9:5001 | -127.479 | -127.479 | -5.442 | 6.181 | 17.508 | 17.508 | 17.508 | 22.949 | 144.987 | 29.551 | -0.176 | ms | -3.971 | 17.23 | ||
| Server Offset 2605:4840:3:fb19::1 (chi3.us.ntp.li) | -278.261 | -8.779 | -1.179 | 2.716 | 7.022 | 29.833 | 89.152 | 8.201 | 38.612 | 10.597 | 2.909 | ms | -14.92 | 445.8 | ||
| Server Offset 2605:6400:488d:2eda:eee9:fe8d:4543:d471 | 6.277 | 6.277 | 6.277 | 10.872 | 10.872 | 10.872 | 10.872 | 4.595 | 4.595 | 2.297 | 8.574 | ms | -5.457e-16 | 1 | ||
| Server Offset 2605:6400:488d:3686:546d:c03c:1689:20c | 0.063 | 0.063 | 0.063 | 10.815 | 77.942 | 77.942 | 77.942 | 77.879 | 77.879 | 31.733 | 28.904 | ms | 0.6938 | 1.564 | ||
| Server Offset 2605:6400:84e1::123 (oldtime3.sigi.net) | -12.468 | -0.445 | 2.966 | 5.204 | 7.923 | 15.345 | 240.273 | 4.957 | 15.790 | 21.764 | 7.308 | ms | 10.33 | 108.7 | ||
| Server Offset 2605:6f01:2000:18::94ee:fcbe (vps-buf1.orleans.ddnss.de) | -1.370 | -1.370 | -1.370 | 3.697 | 9.921 | 9.921 | 9.921 | 11.292 | 11.292 | 2.854 | 4.172 | ms | 0.1428 | 3.178 | ||
| Server Offset 2606:4700:f1::1 (time.cloudflare.com) | -170.499 | -2.387 | 1.875 | 5.798 | 8.576 | 10.646 | 290.015 | 6.701 | 13.032 | 6.047 | 5.706 | ms | 25.59 | 1216 | ||
| Server Offset 2606:4700:f1::123 (time.cloudflare.com) | -810.498 | -1.710 | 1.692 | 5.712 | 8.542 | 10.936 | 468.641 | 6.850 | 12.646 | 18.089 | 5.451 | ms | -22.5 | 1230 | ||
| Server Offset 2606:82c0:21::e (time1.lshiy.com) | -0.038 | -0.038 | -0.038 | 3.161 | 6.774 | 6.774 | 6.774 | 6.812 | 6.812 | 2.191 | 3.162 | ms | 0.2345 | 1.83 | ||
| Server Offset 2606:82c0:22::e (time2.lshiy.com) | -105.777 | -105.777 | -105.777 | 5.198 | 20.159 | 20.159 | 20.159 | 125.937 | 125.937 | 51.276 | -28.296 | ms | -0.6878 | 1.513 | ||
| Server Offset 2606:82c0:23::e (time3.lshiy.com) | 5.344 | 5.344 | 5.344 | 9.330 | 14.292 | 14.292 | 14.292 | 8.948 | 8.948 | 2.315 | 9.378 | ms | 0.5098 | 2.778 | ||
| Server Offset 2606:8fc0::9 (farmhand.gac.edu) | -11.058 | 0.976 | 2.338 | 4.612 | 7.297 | 8.866 | 10.402 | 4.959 | 7.890 | 1.640 | 4.640 | ms | -1.936 | 22.88 | ||
| Server Offset 2607:5600:182:500::1 (ntp-1.jonlight.com) | -568.165 | -568.165 | -568.165 | -0.446 | 11.465 | 11.465 | 11.465 | 579.631 | 579.631 | 265.791 | -190.495 | ms | -0.701 | 1.5 | ||
| Server Offset 2607:7c80:54:3::32 | -3.794 | 0.787 | 2.562 | 4.809 | 7.594 | 10.557 | 88.040 | 5.032 | 9.770 | 2.850 | 4.977 | ms | 17.49 | 477.9 | ||
| Server Offset 2607:7c80:54:3::56 (owners.kjsl.com) | -806.909 | -806.909 | -5.703 | 0.187 | 5.818 | 9.156 | 9.156 | 11.521 | 816.065 | 173.398 | -38.752 | ms | -4.188 | 18.54 | ||
| Server Offset 2607:9000:7000:23:216:3cff:fe25:38d7 | -3.352 | -0.375 | 0.741 | 4.354 | 8.207 | 9.388 | 11.040 | 7.466 | 9.763 | 2.317 | 4.364 | ms | -0.006342 | 2.996 | ||
| Server Offset 2607:9d00:2000:16::9269:208a | 3.459 | 3.459 | 3.459 | 6.758 | 17.615 | 17.615 | 17.615 | 14.156 | 14.156 | 4.848 | 8.704 | ms | 0.9497 | 2.577 | ||
| Server Offset 2607:b500:410:7700::1 | -559.793 | -559.793 | -555.696 | 15.880 | 247.041 | 247.131 | 247.131 | 802.737 | 806.924 | 201.270 | 7.227 | ms | -1.662 | 5.994 | ||
| Server Offset 2607:f1c0:f014:9e00::1 | -0.782 | -0.782 | -0.782 | 3.789 | 12.363 | 12.363 | 12.363 | 13.145 | 13.145 | 4.161 | 4.437 | ms | 0.4965 | 2.056 | ||
| Server Offset 2607:f1c0:f014:9e00::2 | -2.137 | -2.137 | 0.533 | 8.769 | 175.012 | 176.141 | 176.141 | 174.479 | 178.278 | 60.511 | 32.888 | ms | 1.871 | 4.578 | ||
| Server Offset 2607:f1c0:f047:8400::1 (xmpp.party) | 0.817 | 0.817 | 0.817 | 2.977 | 10.973 | 10.973 | 10.973 | 10.156 | 10.156 | 4.368 | 4.922 | ms | 0.5796 | 1.5 | ||
| Server Offset 2607:f1c0:f04e:fd00::1 | -0.324 | -0.324 | -0.324 | 4.901 | 12.270 | 12.270 | 12.270 | 12.594 | 12.594 | 3.373 | 4.498 | ms | 0.7124 | 3.491 | ||
| Server Offset 2607:f1c0:f06b:5000:: (ntp11.kernfusion.at) | -64.809 | -64.809 | -64.809 | -61.044 | -58.237 | -58.237 | -58.237 | 6.572 | 6.572 | 2.268 | -61.730 | ms | -0.02717 | 1.823 | ||
| Server Offset 2607:f1c0:f06b:5000::1 (ntp11.kernfusion.at) | 2.778 | 2.778 | 2.778 | 7.838 | 13.194 | 13.194 | 13.194 | 10.416 | 10.416 | 3.298 | 7.750 | ms | 0.1317 | 1.92 | ||
| Server Offset 2607:f1c0:f06b:5000::2 (ntp11.kernfusion.at) | 10.032 | 10.032 | 10.032 | 11.425 | 11.681 | 11.681 | 11.681 | 1.649 | 1.649 | 0.725 | 11.046 | ms | -0.6413 | 1.5 | ||
| Server Offset 2607:f1c0:f06b:5000::3 (ntp11.kernfusion.at) | -54.918 | -54.918 | -15.203 | 8.457 | 29.615 | 29.615 | 29.615 | 44.818 | 84.533 | 17.098 | 5.713 | ms | -2.027 | 8.409 | ||
| Server Offset 2607:f1c0:f06b:5000::4 (ntp11.kernfusion.at) | -2.373 | -2.373 | -1.407 | 3.297 | 10.246 | 11.084 | 11.084 | 11.653 | 13.458 | 3.531 | 3.807 | ms | 0.3808 | 2.37 | ||
| Server Offset 2607:f1c0:f06d:f200::1 | 4.821 | 4.821 | 4.821 | 6.467 | 10.874 | 10.874 | 10.874 | 6.053 | 6.053 | 2.364 | 6.907 | ms | 0.9511 | 2.168 | ||
| Server Offset 2607:f1c0:f075:9900::1 | 1.361 | 1.361 | 1.361 | 9.304 | 14.348 | 14.348 | 14.348 | 12.987 | 12.987 | 4.266 | 7.460 | ms | 0.02239 | 1.598 | ||
| Server Offset 2607:f298:5:101d:f816:3eff:fefd:8817 | -174.467 | -174.467 | -172.715 | 3.910 | 20.484 | 20.484 | 20.484 | 193.199 | 194.951 | 64.078 | -20.926 | ms | -1.945 | 4.813 | ||
| Server Offset 2607:f3c8:3803:1::6 | -6.026 | -6.026 | -6.026 | 2.471 | 214.987 | 214.987 | 214.987 | 221.013 | 221.013 | 95.937 | 61.079 | ms | 0.9476 | 1.902 | ||
| Server Offset 2607:f5b7:1:44::123 (ntp.wdc2.us.leaseweb.net) | -23.263 | -23.263 | -23.263 | -10.419 | 26.993 | 26.993 | 26.993 | 50.256 | 50.256 | 13.527 | -6.124 | ms | 0.7442 | 2.94 | ||
| Server Offset 2607:f710:35::29c:0:1 (ntp6.kernfusion.at) | 6.293 | 6.293 | 6.293 | 9.644 | 16.365 | 16.365 | 16.365 | 10.072 | 10.072 | 2.800 | 10.002 | ms | 0.8431 | 3.217 | ||
| Server Offset 2607:f710:35::29c:0:8 | -3.482 | -1.256 | 1.976 | 4.319 | 6.532 | 9.029 | 12.497 | 4.556 | 10.285 | 1.590 | 4.260 | ms | -0.3604 | 7.445 | ||
| Server Offset 2607:ff50:0:1a::10 (ntpool0.603.newcontinuum.net) | -158.123 | -147.850 | 2.263 | 4.616 | 6.829 | 9.746 | 12.552 | 4.567 | 157.597 | 16.136 | 3.032 | ms | -9.47 | 91.61 | ||
| Server Offset 2607:ff50:0:1a::20 (ntpool1.603.newcontinuum.net) | -14.580 | -1.076 | 2.585 | 5.159 | 7.783 | 10.675 | 20.139 | 5.198 | 11.751 | 2.118 | 5.115 | ms | -1.077 | 26.82 | ||
| Server Offset 2607:ff50:0:20::5ca1:ab1e (junia.packetexport.com) | 4.183 | 4.183 | 4.183 | 8.895 | 11.415 | 11.415 | 11.415 | 7.232 | 7.232 | 2.452 | 8.699 | ms | -0.9315 | 2.629 | ||
| Server Offset 2620:138:5000:0:5054:ff:fe89:6673 (time.nullroutenetworks.com) | -1.149 | 2.215 | 3.649 | 5.831 | 7.768 | 8.933 | 13.205 | 4.119 | 6.718 | 1.345 | 5.804 | ms | -0.08604 | 5.422 | ||
| Server Offset 2620:149:a23:4000::1e2 (uschi5-ntp-004.aaplimg.com) | -0.204 | 1.225 | 2.738 | 5.129 | 7.083 | 8.347 | 13.313 | 4.345 | 7.123 | 1.394 | 5.057 | ms | 0.1497 | 5.842 | ||
| Server Offset 2620:6:2000:104::48 (excalibur.prolixium.com) | 2.517 | 2.517 | 3.243 | 6.638 | 12.412 | 13.371 | 13.371 | 9.170 | 10.854 | 2.456 | 6.987 | ms | 0.675 | 3.466 | ||
| Server Offset 2620:83:8000:140::b (tic.lbl.gov) | -64.202 | -16.454 | -0.037 | 2.751 | 5.105 | 7.089 | 169.920 | 5.142 | 23.543 | 8.350 | 2.692 | ms | 14.74 | 314 | ||
| Server Offset 2620:83:8000:140::c (toc.lbl.gov) | -8.902 | -3.197 | 0.915 | 6.115 | 12.932 | 16.845 | 18.523 | 12.018 | 20.042 | 3.819 | 6.351 | ms | 0.131 | 4.597 | ||
| Server Offset 2620:8d:c000::f (blotch.image1tech.net) | -12.501 | -12.501 | -12.501 | 0.670 | 15.127 | 15.127 | 15.127 | 27.628 | 27.628 | 9.564 | -0.984 | ms | 0.2932 | 2 | ||
| Server Offset 2620:9a:e000:1061::2:165 (ntp-demo4.centerclick.com) | -7.979 | -7.979 | -7.979 | -0.845 | 213.035 | 213.035 | 213.035 | 221.015 | 221.015 | 98.515 | 62.052 | ms | 0.8326 | 1.697 | ||
| Server Offset 2620:b0:2000:102::1:123 (time-h.den.codehof.net) | -107.407 | -107.407 | -107.407 | -66.747 | 92.475 | 92.475 | 92.475 | 199.883 | 199.883 | 57.820 | -44.390 | ms | 1.21 | 3.478 | ||
| Server Offset 2620:b0:2000:102::2:123 (time-he.den.codehof.net) | -44.889 | -44.889 | -44.889 | 22.240 | 34.334 | 34.334 | 34.334 | 79.222 | 79.222 | 22.949 | 14.406 | ms | -2.048 | 5.652 | ||
| Server Offset 2a01:3f7:2:44::8 (sth1-ts.nts.netnod.se) | -810.640 | -40.702 | -15.277 | 4.110 | 9.383 | 13.664 | 465.738 | 24.660 | 54.366 | 16.541 | 1.332 | ms | -14.29 | 855.9 | ||
| Server Offset 2a01:3f7:2:44::9 (sth2-ts.nts.netnod.se) | -178.311 | -43.668 | -16.808 | 2.946 | 8.688 | 11.600 | 209.396 | 25.496 | 55.268 | 11.262 | -0.012 | ms | -2.659 | 64.31 | ||
| Server Offset 2a01:4ff:1f0:c33f::1 | -6.622 | -4.223 | 1.110 | 4.402 | 6.109 | 6.738 | 12.640 | 4.999 | 10.961 | 1.896 | 4.103 | ms | -2.247 | 12.45 | ||
| Server Offset 2a01:4ff:f0:e33b::1 | -0.405 | 1.341 | 2.664 | 4.973 | 7.287 | 11.950 | 20.955 | 4.623 | 10.609 | 1.794 | 5.000 | ms | 2.539 | 21.23 | ||
| Server Offset 2a01:4ff:f0:ebce::1 (zero.txryan.com) | 8.384 | 8.384 | 8.384 | 34.231 | 34.231 | 34.231 | 34.231 | 25.847 | 25.847 | 12.924 | 21.307 | ms | 1.962e-16 | 1 | ||
| Server Offset 2a01:7e03::f03c:95ff:fef8:ac8c (sushi.ruselabs.com) | -51.215 | -51.215 | -51.215 | 6.741 | 19.073 | 19.073 | 19.073 | 70.288 | 70.288 | 23.048 | -2.114 | ms | -1.242 | 3.142 | ||
| Server Offset 2a05:dfc1:cb1:201:: (ntp.zeus.frumentum.media) | -13.885 | -5.062 | 1.103 | 3.811 | 6.136 | 7.963 | 13.358 | 5.032 | 13.025 | 2.029 | 3.639 | ms | -2.051 | 16.32 | ||
| Server Offset 38.81.211.177 | 10.240 | 10.240 | 10.240 | 12.392 | 14.243 | 14.243 | 14.243 | 4.003 | 4.003 | 1.494 | 12.099 | ms | 0.05225 | 1.572 | ||
| Server Offset 44.190.5.123 | -619.209 | 0.544 | 2.443 | 5.227 | 7.382 | 8.611 | 28.290 | 4.939 | 8.067 | 8.826 | 4.882 | ms | -52.41 | 3377 | ||
| Server Offset 45.33.53.84 | -7.486 | -0.752 | 1.768 | 4.092 | 5.904 | 7.268 | 9.925 | 4.136 | 8.020 | 1.462 | 4.030 | ms | -1.366 | 12.35 | ||
| Server Offset 45.55.126.202 | -4.945 | 0.288 | 1.840 | 4.396 | 6.776 | 8.592 | 12.903 | 4.936 | 8.304 | 1.542 | 4.413 | ms | -0.1068 | 6.675 | ||
| Server Offset 45.55.58.103 | -2.720 | -2.720 | -1.021 | 6.381 | 9.087 | 10.740 | 10.740 | 10.108 | 13.460 | 2.718 | 5.713 | ms | -1.293 | 5.373 | ||
| Server Offset 45.61.187.39 | -3.631 | -3.631 | -3.631 | 4.490 | 13.757 | 13.757 | 13.757 | 17.388 | 17.388 | 4.830 | 3.741 | ms | 0.536 | 3.14 | ||
| Server Offset 45.63.54.13 | -14.116 | -0.809 | 2.451 | 5.749 | 9.193 | 15.128 | 27.310 | 6.742 | 15.937 | 2.596 | 5.789 | ms | 0.6719 | 17.26 | ||
| Server Offset 45.79.35.159 | 3.746 | 3.746 | 3.746 | 7.855 | 8.568 | 8.568 | 8.568 | 4.821 | 4.821 | 2.112 | 6.125 | ms | 0.01386 | 1.093 | ||
| Server Offset 45.79.51.42 | -45.604 | -45.604 | -45.604 | 8.683 | 108.150 | 108.150 | 108.150 | 153.754 | 153.754 | 57.087 | 39.510 | ms | 0.07989 | 1.347 | ||
| Server Offset 45.83.234.123 | -296.062 | -296.062 | -36.862 | 5.462 | 11.429 | 15.325 | 15.325 | 48.291 | 311.387 | 44.156 | -5.332 | ms | -5.514 | 35.05 | ||
| Server Offset 45.84.199.136 | -110.729 | -110.729 | -110.729 | -97.871 | 9.546 | 9.546 | 9.546 | 120.275 | 120.275 | 54.799 | -52.941 | ms | 0.172 | 1.055 | ||
| Server Offset 46.37.96.107 | -808.769 | -33.538 | -1.905 | 5.043 | 7.457 | 8.750 | 17.475 | 9.362 | 42.288 | 37.739 | 2.042 | ms | -20.74 | 443.5 | ||
| Server Offset 5.161.111.190 | -0.126 | 0.940 | 2.843 | 5.553 | 7.484 | 8.513 | 15.050 | 4.641 | 7.573 | 1.526 | 5.470 | ms | 0.2432 | 8.093 | ||
| Server Offset 5.78.62.36 | -8.523 | -2.092 | 0.307 | 5.929 | 11.849 | 15.869 | 16.396 | 11.542 | 17.960 | 3.566 | 6.030 | ms | 0.08899 | 3.94 | ||
| Server Offset 50.117.3.52 | -8.085 | -8.085 | -8.085 | -6.204 | -5.368 | -5.368 | -5.368 | 2.717 | 2.717 | 0.914 | -6.560 | ms | -0.319 | 1.928 | ||
| Server Offset 50.117.3.95 | -146.276 | -146.276 | -146.276 | 8.636 | 18.465 | 18.465 | 18.465 | 164.741 | 164.741 | 63.106 | -20.370 | ms | -1.48 | 3.224 | ||
| Server Offset 50.205.57.38 | -13.612 | 0.957 | 2.871 | 5.422 | 7.494 | 10.271 | 20.357 | 4.623 | 9.314 | 1.625 | 5.423 | ms | -0.1843 | 22.87 | ||
| Server Offset 50.218.103.254 | -15.904 | -15.904 | -12.655 | 6.918 | 11.696 | 11.835 | 11.835 | 24.351 | 27.738 | 7.169 | 4.954 | ms | -1.516 | 4.534 | ||
| Server Offset 51.81.20.76 | 2.414 | 2.414 | 2.414 | 7.712 | 11.524 | 11.524 | 11.524 | 9.111 | 9.111 | 3.247 | 7.454 | ms | -0.2642 | 1.777 | ||
| Server Offset 51.81.226.229 | -178.118 | -178.118 | -168.711 | 4.809 | 12.384 | 22.510 | 22.510 | 181.095 | 200.627 | 42.711 | -5.129 | ms | -3.647 | 14.49 | ||
| Server Offset 64.142.54.12 | 9.100 | 9.100 | 9.100 | 11.576 | 22.059 | 22.059 | 22.059 | 12.959 | 12.959 | 3.920 | 12.706 | ms | 1.335 | 3.639 | ||
| Server Offset 64.6.144.6 | -8.057 | -7.831 | -5.650 | -1.925 | 2.191 | 462.576 | 467.377 | 7.840 | 470.408 | 54.569 | 4.472 | ms | 8.286 | 69.79 | ||
| Server Offset 64.79.100.197 | -5.398 | -1.308 | 0.115 | 2.437 | 4.257 | 5.695 | 7.196 | 4.142 | 7.002 | 1.439 | 2.356 | ms | -1.086 | 9.14 | ||
| Server Offset 65.100.46.164 | -12.522 | -2.725 | -0.387 | 4.920 | 11.409 | 15.307 | 17.739 | 11.796 | 18.032 | 3.731 | 5.348 | ms | 0.01927 | 4.589 | ||
| Server Offset 65.100.46.166 | 0.249 | 1.083 | 2.398 | 5.335 | 7.816 | 11.010 | 13.272 | 5.418 | 9.928 | 1.740 | 5.341 | ms | 0.2817 | 4.931 | ||
| Server Offset 65.182.224.39 | 1.814 | 1.814 | 1.814 | 2.848 | 5.791 | 5.791 | 5.791 | 3.977 | 3.977 | 1.315 | 3.059 | ms | 1.249 | 3.327 | ||
| Server Offset 66.118.229.14 | 5.362 | 5.362 | 5.362 | 9.349 | 9.349 | 9.349 | 9.349 | 3.986 | 3.986 | 1.993 | 7.355 | ms | 6.268e-16 | 1 | ||
| Server Offset 66.118.230.14 | 5.529 | 5.529 | 5.529 | 5.949 | 10.275 | 10.275 | 10.275 | 4.746 | 4.746 | 2.145 | 7.251 | ms | 0.6868 | 1.5 | ||
| Server Offset 66.118.231.14 | -27.328 | -27.328 | -11.996 | 6.282 | 12.740 | 46.019 | 46.019 | 24.736 | 73.347 | 10.790 | 3.288 | ms | 0.6884 | 8.099 | ||
| Server Offset 66.42.71.197 | -4.404 | 1.164 | 3.246 | 6.075 | 8.417 | 9.829 | 440.870 | 5.171 | 8.665 | 20.411 | 6.942 | ms | 20.87 | 439.3 | ||
| Server Offset 66.59.198.94 | -3.193 | -3.193 | -3.193 | 1.753 | 7.991 | 7.991 | 7.991 | 11.183 | 11.183 | 3.576 | 2.287 | ms | 0.3048 | 1.825 | ||
| Server Offset 66.85.78.80 | -17.366 | -13.001 | -7.268 | -1.837 | 1.018 | 6.542 | 10.757 | 8.286 | 19.543 | 3.003 | -2.223 | ms | -0.8402 | 8.685 | ||
| Server Offset 67.217.240.178 | -2.392 | -2.392 | -2.392 | 7.224 | 15.021 | 15.021 | 15.021 | 17.413 | 17.413 | 4.868 | 6.427 | ms | -0.1827 | 2.554 | ||
| Server Offset 67.217.246.127 | -4.257 | -3.477 | -0.379 | 2.528 | 6.202 | 9.675 | 10.219 | 6.580 | 13.152 | 2.004 | 2.572 | ms | 0.5419 | 6.199 | ||
| Server Offset 67.217.246.204 | -407.881 | -405.967 | -8.458 | 0.106 | 11.835 | 17.296 | 21.211 | 20.293 | 423.263 | 62.932 | -8.808 | ms | -6.1 | 38.56 | ||
| Server Offset 68.234.48.70 | -2.973 | -2.973 | -2.973 | 9.512 | 47.817 | 47.817 | 47.817 | 50.790 | 50.790 | 12.262 | 11.128 | ms | 2.266 | 7.46 | ||
| Server Offset 69.48.203.16 | 2.540 | 2.540 | 2.540 | 7.439 | 10.588 | 10.588 | 10.588 | 8.048 | 8.048 | 2.329 | 7.070 | ms | -0.4418 | 2.4 | ||
| Server Offset 69.89.207.199 | -35.854 | -1.651 | 0.462 | 2.952 | 7.621 | 102.532 | 105.829 | 7.159 | 104.183 | 11.033 | 4.295 | ms | 8.078 | 73.06 | ||
| Server Offset 69.89.207.99 | -2.776 | -1.101 | 0.455 | 2.909 | 4.665 | 5.551 | 6.408 | 4.210 | 6.652 | 1.304 | 2.772 | ms | -0.6304 | 4.142 | ||
| Server Offset 71.123.46.186 | -0.765 | -0.089 | 1.160 | 4.514 | 7.163 | 9.760 | 10.300 | 6.003 | 9.849 | 1.893 | 4.465 | ms | 0.0854 | 3.856 | ||
| Server Offset 71.19.144.140 | -3.221 | -3.221 | -3.221 | 4.015 | 7.428 | 7.428 | 7.428 | 10.649 | 10.649 | 2.867 | 3.283 | ms | -0.3728 | 2.496 | ||
| Server Offset 72.14.183.39 | 0.355 | 1.411 | 3.334 | 5.496 | 7.837 | 9.588 | 11.748 | 4.503 | 8.177 | 1.427 | 5.487 | ms | 0.1324 | 4.785 | ||
| Server Offset 72.14.186.59 | 2.611 | 2.611 | 2.611 | 5.374 | 7.023 | 7.023 | 7.023 | 4.412 | 4.412 | 1.489 | 5.305 | ms | -0.8276 | 2.527 | ||
| Server Offset 72.30.35.89 | 8.994 | 8.994 | 8.994 | 12.518 | 13.297 | 13.297 | 13.297 | 4.303 | 4.303 | 1.872 | 11.603 | ms | -0.6164 | 1.5 | ||
| Server Offset 72.46.53.234 | -35.275 | -35.275 | -35.275 | 69.197 | 105.228 | 105.228 | 105.228 | 140.503 | 140.503 | 52.722 | 51.699 | ms | -0.2012 | 1.301 | ||
| Server Offset 72.46.61.205 | -285.110 | -285.110 | -285.110 | 6.157 | 16.075 | 16.075 | 16.075 | 301.185 | 301.185 | 73.049 | -25.856 | ms | -2.768 | 9.979 | ||
| Server Offset 73.185.182.209 | -2.743 | 0.925 | 2.341 | 5.411 | 8.588 | 10.253 | 11.822 | 6.247 | 9.328 | 1.947 | 5.428 | ms | -0.05719 | 3.857 | ||
| Server Offset 73.65.80.137 | -809.727 | -809.727 | -9.135 | -1.384 | 3.688 | 7.510 | 7.510 | 12.823 | 817.238 | 169.002 | -38.192 | ms | -4.333 | 19.79 | ||
| Server Offset 74.119.243.5 | 1.643 | 1.643 | 1.643 | 7.015 | 7.452 | 7.452 | 7.452 | 5.809 | 5.809 | 2.661 | 4.585 | ms | -0.008075 | 1.037 | ||
| Server Offset 74.208.117.38 | -8.056 | -8.056 | -8.056 | -3.727 | 11.177 | 11.177 | 11.177 | 19.233 | 19.233 | 5.901 | -2.284 | ms | 1.09 | 3.094 | ||
| Server Offset 74.208.14.149 | -5.945 | -5.945 | -5.945 | 8.847 | 11.709 | 11.709 | 11.709 | 17.654 | 17.654 | 5.690 | 5.541 | ms | -1.091 | 3.04 | ||
| Server Offset 74.208.25.46 | -15.748 | -3.661 | -0.778 | 4.701 | 12.042 | 18.695 | 486.710 | 12.821 | 22.356 | 25.682 | 6.852 | ms | 13.83 | 211.5 | ||
| Server Offset 83.147.242.172 | -3.579 | 1.082 | 2.797 | 5.135 | 7.484 | 9.790 | 14.032 | 4.687 | 8.708 | 1.518 | 5.170 | ms | 0.1286 | 6.052 | ||
| Server Offset 99.28.14.242 | -568.386 | -3.525 | 0.460 | 4.626 | 9.607 | 12.913 | 287.104 | 9.147 | 16.438 | 32.755 | 4.526 | ms | -10.49 | 234.8 | ||
| Server Offset SHM(0) | -8.145 | -7.741 | -6.910 | -0.148 | -0.109 | -0.002 | 0.005 | 6.801 | 7.739 | 1.814 | -0.648 | s | -3.304 | 11.99 | ||
| Server Offset SHM(1) | -8.010 | -7.008 | -6.007 | -0.000 | 0.000 | 0.000 | 0.001 | 6.007 | 7.009 | 1.650 | -0.444 | s | -3.48 | 13.2 | ||
| Server Offset SHM(2) | -485.911 | -170.410 | -96.976 | 0.232 | 8.581 | 17.676 | 44.156 | 105.557 | 188.086 | 36.108 | -11.840 | ms | -2.926 | 11.7 | ||
| Server Offset SHM(3) | -12.883 | -6.851 | -1.301 | -0.400 | 0.421 | 0.870 | 12.496 | 1.722 | 7.720 | 1.098 | -0.538 | ms | -3.968 | 23.18 | ||
| Server Offset SOCK(0) | -597.294 | -177.834 | -174.616 | -0.939 | 7.355 | 181.993 | 236.678 | 181.971 | 359.827 | 80.136 | -30.176 | ms | -0.5305 | 3.565 | ||
| Server Offset SOCK(1) | -52.048 | -1.787 | -0.992 | -0.087 | 0.869 | 1.335 | 230.276 | 1.862 | 3.123 | 1.166 | -0.087 | ms | 129.6 | 2.566e+04 | ||
| Server Offset SOCK(2) | -181.172 | -176.994 | -173.059 | -163.444 | -157.121 | -154.860 | -148.505 | 15.938 | 22.134 | 4.800 | -164.015 | ms | -0.5576 | 3.253 | ||
| Server Offset SOCK(3) | -3,009.455 | -0.960 | -0.610 | -0.079 | 0.535 | 0.918 | 4.447 | 1.145 | 1.878 | 17.175 | -0.177 | ms | -175.1 | 3.068e+04 | ||
| TDOP | 0.490 | 0.560 | 0.620 | 0.880 | 1.430 | 1.820 | 12.680 | 0.810 | 1.260 | 0.298 | 0.939 | 9.974 | 351.2 | |||
| Temp /dev/sda | 15.000 | 17.000 | 18.000 | 25.000 | 26.000 | 28.000 | 39.000 | 8.000 | 11.000 | 2.540 | 23.675 | °C | ||||
| Temp LM0 | 28.000 | 30.000 | 30.000 | 34.000 | 41.000 | 44.000 | 54.000 | 11.000 | 14.000 | 2.876 | 33.908 | °C | ||||
| Temp LM1 | 26.000 | 28.000 | 29.000 | 37.000 | 39.000 | 40.000 | 44.000 | 10.000 | 12.000 | 2.950 | 36.478 | °C | ||||
| Temp LM2 | 0.000 | 0.000 | 0.000 | 19.000 | 34.000 | 34.000 | 51.000 | 34.000 | 34.000 | 6.874 | 19.716 | °C | ||||
| Temp LM3 | 24.000 | 26.000 | 27.000 | 30.000 | 38.000 | 39.000 | 46.000 | 11.000 | 13.000 | 3.044 | 30.660 | °C | ||||
| Temp LM4 | 0.000 | 0.000 | 0.000 | 32.000 | 39.000 | 43.000 | 56.000 | 39.000 | 43.000 | 11.592 | 29.039 | °C | ||||
| Temp LM5 | 24.000 | 26.000 | 27.000 | 30.000 | 32.000 | 32.000 | 45.000 | 5.000 | 6.000 | 1.527 | 29.622 | °C | ||||
| Temp LM6 | 26.000 | 28.000 | 29.000 | 32.000 | 34.000 | 38.000 | 50.000 | 5.000 | 10.000 | 1.799 | 31.973 | °C | ||||
| Temp LM7 | 28.000 | 30.000 | 31.000 | 34.000 | 36.000 | 39.000 | 51.000 | 5.000 | 9.000 | 1.748 | 33.794 | °C | ||||
| Temp LM8 | 28.000 | 31.000 | 31.000 | 34.000 | 37.000 | 39.000 | 51.000 | 6.000 | 8.000 | 1.726 | 34.151 | °C | ||||
| Temp LM9 | 28.000 | 31.000 | 31.000 | 34.000 | 37.000 | 39.000 | 51.000 | 6.000 | 8.000 | 1.727 | 34.151 | °C | ||||
| Temp ZONE0 | 20.000 | 20.000 | 20.000 | 20.000 | 20.000 | 20.000 | 20.000 | 0.000 | 0.000 | 0.000 | 20.000 | °C | ||||
| Temp ZONE1 | 28.000 | 30.000 | 30.000 | 34.000 | 36.000 | 39.000 | 51.000 | 6.000 | 9.000 | 1.779 | 33.270 | °C | ||||
| Temp ZONE2 | 24.000 | 26.000 | 27.000 | 30.000 | 32.000 | 32.000 | 45.000 | 5.000 | 6.000 | 1.527 | 29.622 | °C | ||||
| Temp ZONE3 | 28.000 | 30.000 | 30.000 | 34.000 | 36.000 | 39.000 | 51.000 | 6.000 | 9.000 | 1.780 | 33.275 | °C | ||||
| Temp ZONE4 | 28.000 | 30.000 | 30.000 | 34.000 | 36.000 | 39.000 | 51.000 | 6.000 | 9.000 | 1.779 | 33.270 | °C | ||||
| Temp ZONE5 | 27.000 | 29.000 | 30.000 | 32.000 | 42.000 | 47.000 | 56.000 | 12.000 | 18.000 | 3.955 | 33.936 | °C | ||||
| Temp ZONE6 | 24.000 | 26.000 | 27.000 | 30.000 | 32.000 | 34.000 | 44.000 | 5.000 | 8.000 | 1.574 | 29.633 | °C | ||||
| nSats | 6.000 | 8.000 | 9.000 | 11.000 | 13.000 | 14.000 | 16.000 | 4.000 | 6.000 | 1.312 | 10.730 | nSat | 0.1329 | 3.353 | ||
Stats for the last 1, 7, 35, 98, 371, some days, or live gps data.