About this server | other servers
UTC (according to your browser):
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Local Clock Time Offset | -492.702 | -453.802 | -437.895 | -13.687 | 378.888 | 462.469 | 509.922 | 816.783 | 916.271 | 289.351 | 0.008 | µs | -4.141 | 9.209 | |||
Local Clock Frequency Offset | 115.436 | 115.555 | 115.640 | 115.847 | 116.022 | 116.080 | 116.161 | 0.382 | 0.526 | 0.114 | 115.843 | ppm | 1.034e+09 | 1.045e+12 |
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% | 95% | StdDev | Mean | Units | ness | osis | |||
Local RMS Time Jitter | 395.627 | 416.156 | 430.078 | 468.081 | 502.945 | 513.436 | 529.557 | 72.867 | 97.280 | 22.400 | 467.355 | µs | 7898 | 1.581e+05 |
This shows 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% | 95% | StdDev | Mean | Units | ness | osis | |||
Local RMS Frequency Jitter | 60.043 | 63.941 | 65.844 | 70.330 | 75.820 | 77.098 | 79.517 | 9.976 | 13.157 | 3.021 | 70.577 | ppb | 1.125e+04 | 2.531e+05 |
This shows 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% | 95% | StdDev | Mean | Units | ness | osis | |||
Local Clock Offset | -492.702 | -453.802 | -437.895 | -13.687 | 378.888 | 462.469 | 509.922 | 816.783 | 916.271 | 289.351 | 0.008 | µs | -4.141 | 9.209 |
This shows the clock offsets of the local clock as a histogram.
The Local Clock Offset is field 3 from the loopstats log file.
This shows the offset of all refclocks, peers 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% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 13.65.88.161 | -12.049 | -2.453 | 0.009 | 2.476 | 4.600 | 5.672 | 22.847 | 4.590 | 8.125 | 1.657 | 2.422 | ms | 0.8654 | 24.52 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 133.243.238.243 | -25.877 | -4.741 | -2.836 | 1.269 | 5.502 | 5.847 | 6.383 | 8.338 | 10.588 | 2.440 | 1.061 | ms | -4.723 | 36.84 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 166.70.136.35 | -21.265 | -1.493 | 0.219 | 6.258 | 7.775 | 9.030 | 10.343 | 7.556 | 10.523 | 2.811 | 5.195 | ms | 0.8537 | 11.73 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 17.253.2.125 | -26.294 | -3.956 | -3.294 | 0.868 | 2.159 | 2.577 | 7.127 | 5.453 | 6.533 | 2.461 | -0.330 | ms | -7.389 | 41.7 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 17.254.0.49 | -34.356 | -1.169 | 0.922 | 1.651 | 2.433 | 2.710 | 13.262 | 1.511 | 3.879 | 1.629 | 1.553 | ms | -13.47 | 244 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 192.168.254.55 | 1.283 | 1.306 | 1.334 | 1.408 | 1.500 | 1.527 | 1.561 | 0.167 | 0.221 | 0.050 | 1.411 | ms | 2.033e+04 | 5.563e+05 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 194.58.200.20 | -27.806 | -1.521 | -1.061 | -0.586 | 3.363 | 5.414 | 6.832 | 4.424 | 6.935 | 1.768 | -0.304 | ms | -8.276 | 82.5 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 199.102.46.72 | -70.950 | -19.959 | -1.953 | -1.207 | -0.581 | -0.324 | 0.163 | 1.371 | 19.634 | 3.947 | -1.705 | ms | -17.57 | 204.8 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 209.165.131.20 | -26.639 | -11.163 | -4.852 | -0.558 | 2.107 | 3.559 | 4.884 | 6.959 | 14.722 | 2.734 | -0.992 | ms | -9.046 | 43.79 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 209.193.63.10 | -23.112 | -1.785 | -0.047 | 1.624 | 3.116 | 6.744 | 12.924 | 3.163 | 8.530 | 1.632 | 1.576 | ms | -4.773 | 72.06 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 209.193.63.100 | -27.470 | -0.209 | 0.524 | 1.372 | 2.148 | 2.428 | 12.891 | 1.624 | 2.637 | 1.241 | 1.314 | ms | -15.51 | 335.5 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 209.193.63.123 | -21.224 | -0.466 | 0.361 | 1.449 | 2.453 | 2.936 | 3.526 | 2.092 | 3.402 | 1.330 | 1.395 | ms | -11.38 | 167.9 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 216.218.254.202 | -21.954 | 0.468 | 0.984 | 2.589 | 3.097 | 3.387 | 5.038 | 2.113 | 2.919 | 1.183 | 2.368 | ms | -6.636 | 137.6 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 31.207.56.54 | -20.153 | -0.759 | 0.112 | 0.718 | 1.325 | 1.829 | 9.731 | 1.212 | 2.588 | 1.090 | 0.654 | ms | -11.14 | 167.4 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Offset 31.207.56.55 | -23.838 | -3.322 | -0.042 | 0.650 | 1.216 | 1.472 | 4.635 | 1.258 | 4.795 | 1.424 | 0.515 | ms | -13.59 | 189 |
This shows the offset of a peer or server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt. Where rtt is the round trip time to the remote. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN peer 80µs; 90% ranges for WAN servers may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Refclock Offset SHM(0) | -22.349 | -16.866 | -12.794 | -2.738 | 7.390 | 10.171 | 18.665 | 20.184 | 27.037 | 6.206 | -2.701 | ms | -7.325 | 19.46 |
This shows the offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90%% ranges may be: local serial GPS 200 ms; local PPS 20µs.
Clock Offset is field 5 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Refclock Offset SHM(1) | -492.703 | -453.803 | -437.896 | -13.688 | 378.889 | 462.470 | 509.923 | 816.785 | 916.273 | 289.352 | 0.008 | µs | -4.141 | 9.209 |
This shows the offset of a local refclock in seconds. This is useful to see how the measured offset is behaving.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90%% ranges may be: local serial GPS 200 ms; local PPS 20µs.
Clock Offset is field 5 in the peerstats log file.
This shows the RMS Jitter of all refclocks, peers and servers. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 13.65.88.161 | 0.561 | 0.969 | 1.326 | 16.562 | 73.188 | 96.928 | 166.758 | 71.862 | 95.959 | 25.442 | 24.285 | ms | 1.239 | 5.113 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 133.243.238.243 | 0.249 | 1.632 | 2.188 | 3.568 | 48.664 | 71.919 | 158.836 | 46.477 | 70.288 | 15.868 | 9.807 | ms | 2.146 | 13.16 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 166.70.136.35 | 0.141 | 0.211 | 0.313 | 0.629 | 46.815 | 77.434 | 159.793 | 46.503 | 77.223 | 17.163 | 7.442 | ms | 1.662 | 13.57 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 17.253.2.125 | 0.179 | 0.357 | 0.456 | 0.983 | 55.711 | 77.631 | 156.764 | 55.255 | 77.274 | 18.668 | 9.144 | ms | 1.164 | 8.199 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 17.254.0.49 | 0.154 | 0.253 | 0.346 | 0.722 | 51.935 | 70.654 | 175.340 | 51.589 | 70.401 | 17.199 | 7.888 | ms | 1.344 | 10.18 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 192.168.254.55 | 7.835 | 22.553 | 33.293 | 62.696 | 115.770 | 138.626 | 1,506.659 | 82.477 | 116.073 | 89.128 | 72.346 | µs | 13.89 | 216.6 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 194.58.200.20 | 0.078 | 0.172 | 0.249 | 0.578 | 58.430 | 74.629 | 163.847 | 58.181 | 74.457 | 19.328 | 8.944 | ms | 1.233 | 9.449 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 199.102.46.72 | 0.135 | 0.245 | 0.350 | 4.984 | 63.173 | 84.155 | 161.388 | 62.823 | 83.910 | 22.871 | 18.231 | ms | 0.7667 | 4.186 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 209.165.131.20 | 0.133 | 0.303 | 0.544 | 2.452 | 55.267 | 79.475 | 157.070 | 54.723 | 79.172 | 19.028 | 9.477 | ms | 1.79 | 12.27 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 209.193.63.10 | 0.074 | 0.163 | 0.251 | 0.555 | 54.888 | 86.536 | 175.845 | 54.637 | 86.373 | 20.103 | 8.446 | ms | 1.696 | 14.38 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 209.193.63.100 | 0.061 | 0.153 | 0.227 | 0.541 | 50.261 | 70.670 | 153.513 | 50.034 | 70.516 | 16.543 | 7.394 | ms | 1.28 | 10.11 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 209.193.63.123 | 0.075 | 0.127 | 0.179 | 0.427 | 50.215 | 71.129 | 117.622 | 50.036 | 71.002 | 16.165 | 6.611 | ms | 1.228 | 8.707 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 216.218.254.202 | 0.086 | 0.200 | 0.287 | 0.578 | 53.076 | 72.103 | 160.830 | 52.788 | 71.903 | 17.318 | 8.185 | ms | 0.9405 | 7.204 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 31.207.56.54 | 0.117 | 0.290 | 0.395 | 0.780 | 51.109 | 71.424 | 137.438 | 50.713 | 71.134 | 16.090 | 7.176 | ms | 1.137 | 7.599 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Peer Jitter 31.207.56.55 | 0.183 | 0.322 | 0.424 | 0.750 | 54.058 | 68.998 | 161.468 | 53.634 | 68.677 | 17.618 | 7.907 | ms | 1.426 | 11.45 |
This shows the RMS Jitter of a remote peer or server. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Refclock RMS Jitter SHM(0) | 0.159 | 0.427 | 0.637 | 1.783 | 4.489 | 6.311 | 22.320 | 3.852 | 5.884 | 1.278 | 2.074 | ms | 3.974 | 18.31 |
This shows the RMS Jitter of a local refclock. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Refclock RMS Jitter SHM(1) | 234.331 | 258.091 | 276.703 | 400.769 | 570.929 | 592.647 | 629.195 | 294.226 | 334.556 | 97.681 | 403.694 | µs | 40.45 | 161 |
This shows the RMS Jitter of a local refclock. Jitter is the current estimated dispersion; the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Percentiles...... | Ranges...... | Skew- | Kurt- | ||||||||||||||
Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 95% | StdDev | Mean | Units | ness | osis | |||
Local Clock Frequency Offset | 115.436 | 115.555 | 115.640 | 115.847 | 116.022 | 116.080 | 116.161 | 0.382 | 0.526 | 0.114 | 115.843 | ppm | 1.034e+09 | 1.045e+12 | |||
Local Clock Time Offset | -492.702 | -453.802 | -437.895 | -13.687 | 378.888 | 462.469 | 509.922 | 816.783 | 916.271 | 289.351 | 0.008 | µs | -4.141 | 9.209 | |||
Local RMS Frequency Jitter | 60.043 | 63.941 | 65.844 | 70.330 | 75.820 | 77.098 | 79.517 | 9.976 | 13.157 | 3.021 | 70.577 | ppb | 1.125e+04 | 2.531e+05 | |||
Local RMS Time Jitter | 395.627 | 416.156 | 430.078 | 468.081 | 502.945 | 513.436 | 529.557 | 72.867 | 97.280 | 22.400 | 467.355 | µs | 7898 | 1.581e+05 | |||
Peer Jitter 13.65.88.161 | 0.561 | 0.969 | 1.326 | 16.562 | 73.188 | 96.928 | 166.758 | 71.862 | 95.959 | 25.442 | 24.285 | ms | 1.239 | 5.113 | |||
Peer Jitter 133.243.238.243 | 0.249 | 1.632 | 2.188 | 3.568 | 48.664 | 71.919 | 158.836 | 46.477 | 70.288 | 15.868 | 9.807 | ms | 2.146 | 13.16 | |||
Peer Jitter 166.70.136.35 | 0.141 | 0.211 | 0.313 | 0.629 | 46.815 | 77.434 | 159.793 | 46.503 | 77.223 | 17.163 | 7.442 | ms | 1.662 | 13.57 | |||
Peer Jitter 17.253.2.125 | 0.179 | 0.357 | 0.456 | 0.983 | 55.711 | 77.631 | 156.764 | 55.255 | 77.274 | 18.668 | 9.144 | ms | 1.164 | 8.199 | |||
Peer Jitter 17.254.0.49 | 0.154 | 0.253 | 0.346 | 0.722 | 51.935 | 70.654 | 175.340 | 51.589 | 70.401 | 17.199 | 7.888 | ms | 1.344 | 10.18 | |||
Peer Jitter 192.168.254.55 | 7.835 | 22.553 | 33.293 | 62.696 | 115.770 | 138.626 | 1,506.659 | 82.477 | 116.073 | 89.128 | 72.346 | µs | 13.89 | 216.6 | |||
Peer Jitter 194.58.200.20 | 0.078 | 0.172 | 0.249 | 0.578 | 58.430 | 74.629 | 163.847 | 58.181 | 74.457 | 19.328 | 8.944 | ms | 1.233 | 9.449 | |||
Peer Jitter 199.102.46.72 | 0.135 | 0.245 | 0.350 | 4.984 | 63.173 | 84.155 | 161.388 | 62.823 | 83.910 | 22.871 | 18.231 | ms | 0.7667 | 4.186 | |||
Peer Jitter 209.165.131.20 | 0.133 | 0.303 | 0.544 | 2.452 | 55.267 | 79.475 | 157.070 | 54.723 | 79.172 | 19.028 | 9.477 | ms | 1.79 | 12.27 | |||
Peer Jitter 209.193.63.10 | 0.074 | 0.163 | 0.251 | 0.555 | 54.888 | 86.536 | 175.845 | 54.637 | 86.373 | 20.103 | 8.446 | ms | 1.696 | 14.38 | |||
Peer Jitter 209.193.63.100 | 0.061 | 0.153 | 0.227 | 0.541 | 50.261 | 70.670 | 153.513 | 50.034 | 70.516 | 16.543 | 7.394 | ms | 1.28 | 10.11 | |||
Peer Jitter 209.193.63.123 | 0.075 | 0.127 | 0.179 | 0.427 | 50.215 | 71.129 | 117.622 | 50.036 | 71.002 | 16.165 | 6.611 | ms | 1.228 | 8.707 | |||
Peer Jitter 216.218.254.202 | 0.086 | 0.200 | 0.287 | 0.578 | 53.076 | 72.103 | 160.830 | 52.788 | 71.903 | 17.318 | 8.185 | ms | 0.9405 | 7.204 | |||
Peer Jitter 31.207.56.54 | 0.117 | 0.290 | 0.395 | 0.780 | 51.109 | 71.424 | 137.438 | 50.713 | 71.134 | 16.090 | 7.176 | ms | 1.137 | 7.599 | |||
Peer Jitter 31.207.56.55 | 0.183 | 0.322 | 0.424 | 0.750 | 54.058 | 68.998 | 161.468 | 53.634 | 68.677 | 17.618 | 7.907 | ms | 1.426 | 11.45 | |||
Peer Offset 13.65.88.161 | -12.049 | -2.453 | 0.009 | 2.476 | 4.600 | 5.672 | 22.847 | 4.590 | 8.125 | 1.657 | 2.422 | ms | 0.8654 | 24.52 | |||
Peer Offset 133.243.238.243 | -25.877 | -4.741 | -2.836 | 1.269 | 5.502 | 5.847 | 6.383 | 8.338 | 10.588 | 2.440 | 1.061 | ms | -4.723 | 36.84 | |||
Peer Offset 166.70.136.35 | -21.265 | -1.493 | 0.219 | 6.258 | 7.775 | 9.030 | 10.343 | 7.556 | 10.523 | 2.811 | 5.195 | ms | 0.8537 | 11.73 | |||
Peer Offset 17.253.2.125 | -26.294 | -3.956 | -3.294 | 0.868 | 2.159 | 2.577 | 7.127 | 5.453 | 6.533 | 2.461 | -0.330 | ms | -7.389 | 41.7 | |||
Peer Offset 17.254.0.49 | -34.356 | -1.169 | 0.922 | 1.651 | 2.433 | 2.710 | 13.262 | 1.511 | 3.879 | 1.629 | 1.553 | ms | -13.47 | 244 | |||
Peer Offset 192.168.254.55 | 1.283 | 1.306 | 1.334 | 1.408 | 1.500 | 1.527 | 1.561 | 0.167 | 0.221 | 0.050 | 1.411 | ms | 2.033e+04 | 5.563e+05 | |||
Peer Offset 194.58.200.20 | -27.806 | -1.521 | -1.061 | -0.586 | 3.363 | 5.414 | 6.832 | 4.424 | 6.935 | 1.768 | -0.304 | ms | -8.276 | 82.5 | |||
Peer Offset 199.102.46.72 | -70.950 | -19.959 | -1.953 | -1.207 | -0.581 | -0.324 | 0.163 | 1.371 | 19.634 | 3.947 | -1.705 | ms | -17.57 | 204.8 | |||
Peer Offset 209.165.131.20 | -26.639 | -11.163 | -4.852 | -0.558 | 2.107 | 3.559 | 4.884 | 6.959 | 14.722 | 2.734 | -0.992 | ms | -9.046 | 43.79 | |||
Peer Offset 209.193.63.10 | -23.112 | -1.785 | -0.047 | 1.624 | 3.116 | 6.744 | 12.924 | 3.163 | 8.530 | 1.632 | 1.576 | ms | -4.773 | 72.06 | |||
Peer Offset 209.193.63.100 | -27.470 | -0.209 | 0.524 | 1.372 | 2.148 | 2.428 | 12.891 | 1.624 | 2.637 | 1.241 | 1.314 | ms | -15.51 | 335.5 | |||
Peer Offset 209.193.63.123 | -21.224 | -0.466 | 0.361 | 1.449 | 2.453 | 2.936 | 3.526 | 2.092 | 3.402 | 1.330 | 1.395 | ms | -11.38 | 167.9 | |||
Peer Offset 216.218.254.202 | -21.954 | 0.468 | 0.984 | 2.589 | 3.097 | 3.387 | 5.038 | 2.113 | 2.919 | 1.183 | 2.368 | ms | -6.636 | 137.6 | |||
Peer Offset 31.207.56.54 | -20.153 | -0.759 | 0.112 | 0.718 | 1.325 | 1.829 | 9.731 | 1.212 | 2.588 | 1.090 | 0.654 | ms | -11.14 | 167.4 | |||
Peer Offset 31.207.56.55 | -23.838 | -3.322 | -0.042 | 0.650 | 1.216 | 1.472 | 4.635 | 1.258 | 4.795 | 1.424 | 0.515 | ms | -13.59 | 189 | |||
Refclock Offset SHM(0) | -22.349 | -16.866 | -12.794 | -2.738 | 7.390 | 10.171 | 18.665 | 20.184 | 27.037 | 6.206 | -2.701 | ms | -7.325 | 19.46 | |||
Refclock Offset SHM(1) | -492.703 | -453.803 | -437.896 | -13.688 | 378.889 | 462.470 | 509.923 | 816.785 | 916.273 | 289.352 | 0.008 | µs | -4.141 | 9.209 | |||
Refclock RMS Jitter SHM(0) | 0.159 | 0.427 | 0.637 | 1.783 | 4.489 | 6.311 | 22.320 | 3.852 | 5.884 | 1.278 | 2.074 | ms | 3.974 | 18.31 | |||
Refclock RMS Jitter SHM(1) | 234.331 | 258.091 | 276.703 | 400.769 | 570.929 | 592.647 | 629.195 | 294.226 | 334.556 | 97.681 | 403.694 | µs | 40.45 | 161 |
Back to Tech Solvency