Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
Local Clock Time Offset | -3.889 | -1.779 | -1.217 | 0.029 | 1.078 | 1.506 | 6.090 | 2.295 | 3.285 | 0.705 | -0.005 | µs | -4.26 | 11.52 | ||
Local Clock Frequency Offset | -563.171 | -556.717 | -523.819 | -368.744 | -178.497 | -163.193 | -159.180 | 345.322 | 393.524 | 116.627 | -358.294 | ppb | -79.61 | 374.1 |
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.361 | 0.507 | 0.604 | 0.877 | 1.254 | 1.446 | 3.126 | 0.650 | 0.939 | 0.202 | 0.897 | µs | 52.02 | 229.3 |
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 | 154.000 | 202.000 | 234.000 | 330.000 | 460.000 | 530.000 | 1,821.000 | 226.000 | 328.000 | 74.526 | 336.762 | 10e-12 | 56.75 | 302.7 |
The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.
Lower is better. An ideal clock would be a horizontal line at 0ppm.
RMS Frequency Jitter is field 6 in the loopstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
Local Clock Offset | -3.889 | -1.779 | -1.217 | 0.029 | 1.078 | 1.506 | 6.090 | 2.295 | 3.285 | 0.705 | -0.005 | µs | -4.26 | 11.52 |
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 | -563.171 | -556.717 | -523.819 | -368.744 | -178.497 | -163.193 | -159.180 | 345.322 | 393.524 | 116.627 | -358.294 | ppb | -79.61 | 374.1 | ||
Temp ZONE0 | 43.470 | 44.008 | 44.008 | 45.622 | 47.774 | 48.312 | 48.312 | 3.766 | 4.304 | 1.121 | 45.860 | °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 | 8.000 | 10.000 | 12.000 | 12.000 | 12.000 | 4.000 | 4.000 | 1.083 | 9.739 | nSat | 534.2 | 4467 | ||
TDOP | 0.490 | 0.520 | 0.560 | 0.800 | 1.240 | 1.400 | 3.120 | 0.680 | 0.880 | 0.210 | 0.846 | 37.98 | 158.6 |
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 162.159.200.1 | -0.081 | 1.389 | 3.658 | 4.759 | 8.742 | 11.357 | 11.587 | 5.084 | 9.968 | 1.528 | 5.143 | ms | 22.1 | 90.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 162.159.200.123 | 0.587 | 1.920 | 2.847 | 4.694 | 7.867 | 11.027 | 15.425 | 5.020 | 9.107 | 1.501 | 4.776 | ms | 18.9 | 79.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 169.229.128.134 | -1.963 | -0.106 | 0.790 | 2.877 | 5.945 | 8.274 | 10.057 | 5.155 | 8.380 | 1.580 | 2.759 | ms | 3.926 | 13.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 173.11.101.155 | -6.106 | -3.056 | -2.144 | 0.709 | 4.273 | 7.288 | 24.939 | 6.417 | 10.344 | 2.169 | 0.900 | ms | 0.4813 | 19.67 |
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
Server Offset 192.12.19.20 | -0.506 | 0.784 | 1.604 | 3.758 | 6.676 | 8.807 | 12.592 | 5.072 | 8.023 | 1.495 | 3.714 | ms | 9.15 | 34.63 |
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the 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.184.148 | -1.145 | 1.582 | 2.404 | 6.696 | 9.492 | 13.308 | 14.110 | 7.087 | 11.726 | 2.068 | 6.369 | ms | 15.25 | 49.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 50.116.42.84 | 2.591 | 3.354 | 4.314 | 5.847 | 8.662 | 11.944 | 14.656 | 4.348 | 8.591 | 1.417 | 6.095 | ms | 48.08 | 224.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 52.10.183.132 | -1.381 | 1.160 | 2.254 | 3.968 | 7.035 | 9.311 | 12.264 | 4.781 | 8.151 | 1.470 | 4.124 | ms | 12.78 | 48.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 64.142.122.36 | -3.244 | -0.668 | 0.598 | 2.859 | 5.810 | 7.753 | 10.207 | 5.213 | 8.421 | 1.561 | 2.771 | ms | 3.61 | 12.66 |
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
Server Offset 66.220.9.122 | -0.939 | 0.368 | 1.167 | 3.332 | 6.334 | 9.554 | 14.117 | 5.167 | 9.185 | 1.652 | 3.280 | ms | 5.694 | 23.72 |
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the 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) | -102.307 | -101.332 | -99.981 | -97.022 | -94.912 | -94.131 | -92.614 | 5.069 | 7.202 | 1.496 | -97.185 | ms | -2.874e+05 | 1.897e+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 SHM(1) | -3.890 | -1.780 | -1.218 | 0.030 | 1.079 | 1.507 | 6.091 | 2.297 | 3.287 | 0.706 | -0.005 | µs | -4.26 | 11.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.
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 162.159.200.1 | 0.632 | 0.852 | 1.045 | 2.658 | 18.909 | 22.484 | 23.779 | 17.864 | 21.631 | 6.010 | 5.928 | ms | 1.212 | 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 162.159.200.123 | 0.147 | 0.504 | 0.842 | 2.605 | 15.861 | 22.235 | 27.315 | 15.019 | 21.731 | 5.050 | 5.090 | ms | 1.552 | 4.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 169.229.128.134 | 0.333 | 0.747 | 1.073 | 2.937 | 18.261 | 24.697 | 33.704 | 17.188 | 23.949 | 5.896 | 5.796 | ms | 1.611 | 5.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 173.11.101.155 | 0.861 | 1.047 | 1.469 | 3.883 | 18.134 | 25.251 | 33.639 | 16.665 | 24.204 | 5.546 | 6.242 | ms | 2.115 | 7.029 |
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
Server Jitter 192.12.19.20 | 0.271 | 0.765 | 1.102 | 3.188 | 16.829 | 20.200 | 29.254 | 15.727 | 19.434 | 5.140 | 5.568 | ms | 1.727 | 4.989 |
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the 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.184.148 | 0.355 | 0.586 | 0.955 | 2.978 | 17.680 | 21.425 | 32.761 | 16.725 | 20.840 | 5.851 | 6.029 | ms | 1.273 | 3.49 |
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
Server Jitter 50.116.42.84 | 0.248 | 0.717 | 1.040 | 2.859 | 16.984 | 22.264 | 29.671 | 15.944 | 21.547 | 5.477 | 5.554 | ms | 1.45 | 4.265 |
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
Server Jitter 52.10.183.132 | 0.151 | 0.561 | 0.880 | 2.703 | 17.229 | 21.877 | 31.451 | 16.349 | 21.316 | 5.495 | 5.438 | ms | 1.418 | 4.261 |
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the 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.122.36 | 0.198 | 0.653 | 1.014 | 3.226 | 17.916 | 22.362 | 26.645 | 16.902 | 21.709 | 5.445 | 5.726 | ms | 1.534 | 4.27 |
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the 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.220.9.122 | 0.377 | 0.711 | 0.975 | 2.711 | 17.007 | 22.390 | 34.030 | 16.032 | 21.678 | 5.520 | 5.428 | ms | 1.566 | 5.248 |
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the 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.032 | 0.075 | 0.110 | 0.323 | 1.013 | 1.436 | 2.732 | 0.903 | 1.361 | 0.300 | 0.414 | ms | 2.802 | 9.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 SHM(1) | 0.161 | 0.330 | 0.444 | 0.851 | 1.642 | 2.117 | 5.532 | 1.198 | 1.787 | 0.379 | 0.923 | µs | 8.571 | 30.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 | ||
Local Clock Frequency Offset | -563.171 | -556.717 | -523.819 | -368.744 | -178.497 | -163.193 | -159.180 | 345.322 | 393.524 | 116.627 | -358.294 | ppb | -79.61 | 374.1 | ||
Local Clock Time Offset | -3.889 | -1.779 | -1.217 | 0.029 | 1.078 | 1.506 | 6.090 | 2.295 | 3.285 | 0.705 | -0.005 | µs | -4.26 | 11.52 | ||
Local RMS Frequency Jitter | 154.000 | 202.000 | 234.000 | 330.000 | 460.000 | 530.000 | 1,821.000 | 226.000 | 328.000 | 74.526 | 336.762 | 10e-12 | 56.75 | 302.7 | ||
Local RMS Time Jitter | 0.361 | 0.507 | 0.604 | 0.877 | 1.254 | 1.446 | 3.126 | 0.650 | 0.939 | 0.202 | 0.897 | µs | 52.02 | 229.3 | ||
Server Jitter 162.159.200.1 | 0.632 | 0.852 | 1.045 | 2.658 | 18.909 | 22.484 | 23.779 | 17.864 | 21.631 | 6.010 | 5.928 | ms | 1.212 | 3.228 | ||
Server Jitter 162.159.200.123 | 0.147 | 0.504 | 0.842 | 2.605 | 15.861 | 22.235 | 27.315 | 15.019 | 21.731 | 5.050 | 5.090 | ms | 1.552 | 4.817 | ||
Server Jitter 169.229.128.134 | 0.333 | 0.747 | 1.073 | 2.937 | 18.261 | 24.697 | 33.704 | 17.188 | 23.949 | 5.896 | 5.796 | ms | 1.611 | 5.186 | ||
Server Jitter 173.11.101.155 | 0.861 | 1.047 | 1.469 | 3.883 | 18.134 | 25.251 | 33.639 | 16.665 | 24.204 | 5.546 | 6.242 | ms | 2.115 | 7.029 | ||
Server Jitter 192.12.19.20 | 0.271 | 0.765 | 1.102 | 3.188 | 16.829 | 20.200 | 29.254 | 15.727 | 19.434 | 5.140 | 5.568 | ms | 1.727 | 4.989 | ||
Server Jitter 5.161.184.148 | 0.355 | 0.586 | 0.955 | 2.978 | 17.680 | 21.425 | 32.761 | 16.725 | 20.840 | 5.851 | 6.029 | ms | 1.273 | 3.49 | ||
Server Jitter 50.116.42.84 | 0.248 | 0.717 | 1.040 | 2.859 | 16.984 | 22.264 | 29.671 | 15.944 | 21.547 | 5.477 | 5.554 | ms | 1.45 | 4.265 | ||
Server Jitter 52.10.183.132 | 0.151 | 0.561 | 0.880 | 2.703 | 17.229 | 21.877 | 31.451 | 16.349 | 21.316 | 5.495 | 5.438 | ms | 1.418 | 4.261 | ||
Server Jitter 64.142.122.36 | 0.198 | 0.653 | 1.014 | 3.226 | 17.916 | 22.362 | 26.645 | 16.902 | 21.709 | 5.445 | 5.726 | ms | 1.534 | 4.27 | ||
Server Jitter 66.220.9.122 | 0.377 | 0.711 | 0.975 | 2.711 | 17.007 | 22.390 | 34.030 | 16.032 | 21.678 | 5.520 | 5.428 | ms | 1.566 | 5.248 | ||
Server Jitter SHM(0) | 0.032 | 0.075 | 0.110 | 0.323 | 1.013 | 1.436 | 2.732 | 0.903 | 1.361 | 0.300 | 0.414 | ms | 2.802 | 9.711 | ||
Server Jitter SHM(1) | 0.161 | 0.330 | 0.444 | 0.851 | 1.642 | 2.117 | 5.532 | 1.198 | 1.787 | 0.379 | 0.923 | µs | 8.571 | 30.86 | ||
Server Offset 162.159.200.1 | -0.081 | 1.389 | 3.658 | 4.759 | 8.742 | 11.357 | 11.587 | 5.084 | 9.968 | 1.528 | 5.143 | ms | 22.1 | 90.15 | ||
Server Offset 162.159.200.123 | 0.587 | 1.920 | 2.847 | 4.694 | 7.867 | 11.027 | 15.425 | 5.020 | 9.107 | 1.501 | 4.776 | ms | 18.9 | 79.29 | ||
Server Offset 169.229.128.134 | -1.963 | -0.106 | 0.790 | 2.877 | 5.945 | 8.274 | 10.057 | 5.155 | 8.380 | 1.580 | 2.759 | ms | 3.926 | 13.68 | ||
Server Offset 173.11.101.155 | -6.106 | -3.056 | -2.144 | 0.709 | 4.273 | 7.288 | 24.939 | 6.417 | 10.344 | 2.169 | 0.900 | ms | 0.4813 | 19.67 | ||
Server Offset 192.12.19.20 | -0.506 | 0.784 | 1.604 | 3.758 | 6.676 | 8.807 | 12.592 | 5.072 | 8.023 | 1.495 | 3.714 | ms | 9.15 | 34.63 | ||
Server Offset 5.161.184.148 | -1.145 | 1.582 | 2.404 | 6.696 | 9.492 | 13.308 | 14.110 | 7.087 | 11.726 | 2.068 | 6.369 | ms | 15.25 | 49.83 | ||
Server Offset 50.116.42.84 | 2.591 | 3.354 | 4.314 | 5.847 | 8.662 | 11.944 | 14.656 | 4.348 | 8.591 | 1.417 | 6.095 | ms | 48.08 | 224.4 | ||
Server Offset 52.10.183.132 | -1.381 | 1.160 | 2.254 | 3.968 | 7.035 | 9.311 | 12.264 | 4.781 | 8.151 | 1.470 | 4.124 | ms | 12.78 | 48.76 | ||
Server Offset 64.142.122.36 | -3.244 | -0.668 | 0.598 | 2.859 | 5.810 | 7.753 | 10.207 | 5.213 | 8.421 | 1.561 | 2.771 | ms | 3.61 | 12.66 | ||
Server Offset 66.220.9.122 | -0.939 | 0.368 | 1.167 | 3.332 | 6.334 | 9.554 | 14.117 | 5.167 | 9.185 | 1.652 | 3.280 | ms | 5.694 | 23.72 | ||
Server Offset SHM(0) | -102.307 | -101.332 | -99.981 | -97.022 | -94.912 | -94.131 | -92.614 | 5.069 | 7.202 | 1.496 | -97.185 | ms | -2.874e+05 | 1.897e+07 | ||
Server Offset SHM(1) | -3.890 | -1.780 | -1.218 | 0.030 | 1.079 | 1.507 | 6.091 | 2.297 | 3.287 | 0.706 | -0.005 | µs | -4.26 | 11.51 | ||
TDOP | 0.490 | 0.520 | 0.560 | 0.800 | 1.240 | 1.400 | 3.120 | 0.680 | 0.880 | 0.210 | 0.846 | 37.98 | 158.6 | |||
Temp ZONE0 | 43.470 | 44.008 | 44.008 | 45.622 | 47.774 | 48.312 | 48.312 | 3.766 | 4.304 | 1.121 | 45.860 | °C | ||||
nSats | 6.000 | 8.000 | 8.000 | 10.000 | 12.000 | 12.000 | 12.000 | 4.000 | 4.000 | 1.083 | 9.739 | nSat | 534.2 | 4467 |