NTPsec

interval - ALIX + Navisys GR-701W (USB)

Report generated: Fri Nov 30 17:00:30 2018 UTC
Start Time: Fri Nov 23 17:00:02 2018 UTC
End Time: Fri Nov 30 17:00:02 2018 UTC
Report Period: 7.0 days
Warning: plots clipped



Tech Solvency / NTP / Servers / interval / all graphs

About this server | other servers

UTC (according to your browser):

loading time widget ...


Day stats | Week stats


Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Local Clock Time Offset-492.702-453.802-437.895-13.687378.888 462.469509.922816.783916.271289.3510.008µs-4.141 9.209
Local Clock Frequency Offset115.436115.555115.640115.847116.022 116.080116.1610.3820.5260.114115.843ppm1.034e+091.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.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Local RMS Time Jitter395.627416.156430.078468.081502.945 513.436529.55772.86797.28022.400467.355µs 78981.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.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter60.04363.94165.84470.33075.820 77.09879.5179.97613.1573.02170.577ppb1.125e+042.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.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Local Clock Offset-492.702-453.802-437.895-13.687378.888 462.469509.922816.783916.271289.3510.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.



Peer Offsets

peer offsets plot

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.



Peer Offset 13.65.88.161

peer offset 13.65.88.161 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 13.65.88.161-12.049-2.4530.0092.4764.600 5.67222.8474.5908.1251.6572.422ms0.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.



Peer Offset 133.243.238.243

peer offset 133.243.238.243 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 133.243.238.243-25.877-4.741-2.8361.2695.502 5.8476.3838.33810.5882.4401.061ms-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.



Peer Offset 166.70.136.35

peer offset 166.70.136.35 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 166.70.136.35-21.265-1.4930.2196.2587.775 9.03010.3437.55610.5232.8115.195ms0.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.



Peer Offset 17.253.2.125

peer offset 17.253.2.125 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 17.253.2.125-26.294-3.956-3.2940.8682.159 2.5777.1275.4536.5332.461-0.330ms-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.



Peer Offset 17.254.0.49

peer offset 17.254.0.49 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 17.254.0.49-34.356-1.1690.9221.6512.433 2.71013.2621.5113.8791.6291.553ms-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.



Peer Offset 192.168.254.55

peer offset 192.168.254.55 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 192.168.254.551.2831.3061.3341.4081.500 1.5271.5610.1670.2210.0501.411ms2.033e+045.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.



Peer Offset 194.58.200.20

peer offset 194.58.200.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 194.58.200.20-27.806-1.521-1.061-0.5863.363 5.4146.8324.4246.9351.768-0.304ms-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.



Peer Offset 199.102.46.72

peer offset 199.102.46.72 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 199.102.46.72-70.950-19.959-1.953-1.207-0.581 -0.3240.1631.37119.6343.947-1.705ms-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.



Peer Offset 209.165.131.20

peer offset 209.165.131.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 209.165.131.20-26.639-11.163-4.852-0.5582.107 3.5594.8846.95914.7222.734-0.992ms-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.



Peer Offset 209.193.63.10

peer offset 209.193.63.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 209.193.63.10-23.112-1.785-0.0471.6243.116 6.74412.9243.1638.5301.6321.576ms-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.



Peer Offset 209.193.63.100

peer offset 209.193.63.100 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 209.193.63.100-27.470-0.2090.5241.3722.148 2.42812.8911.6242.6371.2411.314ms-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.



Peer Offset 209.193.63.123

peer offset 209.193.63.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 209.193.63.123-21.224-0.4660.3611.4492.453 2.9363.5262.0923.4021.3301.395ms-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.



Peer Offset 216.218.254.202

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 216.218.254.202-21.9540.4680.9842.5893.097 3.3875.0382.1132.9191.1832.368ms-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.



Peer Offset 31.207.56.54

peer offset 31.207.56.54 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 31.207.56.54-20.153-0.7590.1120.7181.325 1.8299.7311.2122.5881.0900.654ms-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.



Peer Offset 31.207.56.55

peer offset 31.207.56.55 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Offset 31.207.56.55-23.838-3.322-0.0420.6501.216 1.4724.6351.2584.7951.4240.515ms-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.



Refclock Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Refclock Offset SHM(0)-22.349-16.866-12.794-2.7387.390 10.17118.66520.18427.0376.206-2.701ms-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.



Refclock Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Refclock Offset SHM(1)-492.703-453.803-437.896-13.688378.889 462.470509.923816.785916.273289.3520.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.



Peer Jitters

peer jitters plot

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.



Peer Jitter 13.65.88.161

peer jitter 13.65.88.161 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 13.65.88.1610.5610.9691.32616.56273.188 96.928166.75871.86295.95925.44224.285ms 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.



Peer Jitter 133.243.238.243

peer jitter 133.243.238.243 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 133.243.238.2430.2491.6322.1883.56848.664 71.919158.83646.47770.28815.8689.807ms 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.



Peer Jitter 166.70.136.35

peer jitter 166.70.136.35 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 166.70.136.350.1410.2110.3130.62946.815 77.434159.79346.50377.22317.1637.442ms 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.



Peer Jitter 17.253.2.125

peer jitter 17.253.2.125 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 17.253.2.1250.1790.3570.4560.98355.711 77.631156.76455.25577.27418.6689.144ms 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.



Peer Jitter 17.254.0.49

peer jitter 17.254.0.49 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 17.254.0.490.1540.2530.3460.72251.935 70.654175.34051.58970.40117.1997.888ms 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.



Peer Jitter 192.168.254.55

peer jitter 192.168.254.55 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 192.168.254.557.83522.55333.29362.696115.770 138.6261,506.65982.477116.07389.12872.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.



Peer Jitter 194.58.200.20

peer jitter 194.58.200.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 194.58.200.200.0780.1720.2490.57858.430 74.629163.84758.18174.45719.3288.944ms 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.



Peer Jitter 199.102.46.72

peer jitter 199.102.46.72 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 199.102.46.720.1350.2450.3504.98463.173 84.155161.38862.82383.91022.87118.231ms0.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.



Peer Jitter 209.165.131.20

peer jitter 209.165.131.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 209.165.131.200.1330.3030.5442.45255.267 79.475157.07054.72379.17219.0289.477ms 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.



Peer Jitter 209.193.63.10

peer jitter 209.193.63.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 209.193.63.100.0740.1630.2510.55554.888 86.536175.84554.63786.37320.1038.446ms 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.



Peer Jitter 209.193.63.100

peer jitter 209.193.63.100 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 209.193.63.1000.0610.1530.2270.54150.261 70.670153.51350.03470.51616.5437.394ms 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.



Peer Jitter 209.193.63.123

peer jitter 209.193.63.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 209.193.63.1230.0750.1270.1790.42750.215 71.129117.62250.03671.00216.1656.611ms 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.



Peer Jitter 216.218.254.202

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 216.218.254.2020.0860.2000.2870.57853.076 72.103160.83052.78871.90317.3188.185ms0.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.



Peer Jitter 31.207.56.54

peer jitter 31.207.56.54 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 31.207.56.540.1170.2900.3950.78051.109 71.424137.43850.71371.13416.0907.176ms 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.



Peer Jitter 31.207.56.55

peer jitter 31.207.56.55 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Peer Jitter 31.207.56.550.1830.3220.4240.75054.058 68.998161.46853.63468.67717.6187.907ms 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.



Refclock RMS Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(0)0.1590.4270.6371.7834.489 6.31122.3203.8525.8841.2782.074ms 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.



Refclock RMS Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Refclock RMS Jitter SHM(1)234.331258.091276.703400.769570.929 592.647629.195294.226334.55697.681403.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%95%StdDev  MeanUnits nessosis
Local Clock Frequency Offset115.436115.555115.640115.847116.022 116.080116.1610.3820.5260.114115.843ppm1.034e+091.045e+12
Local Clock Time Offset-492.702-453.802-437.895-13.687378.888 462.469509.922816.783916.271289.3510.008µs-4.141 9.209
Local RMS Frequency Jitter60.04363.94165.84470.33075.820 77.09879.5179.97613.1573.02170.577ppb1.125e+042.531e+05
Local RMS Time Jitter395.627416.156430.078468.081502.945 513.436529.55772.86797.28022.400467.355µs 78981.581e+05
Peer Jitter 13.65.88.1610.5610.9691.32616.56273.188 96.928166.75871.86295.95925.44224.285ms 1.239 5.113
Peer Jitter 133.243.238.2430.2491.6322.1883.56848.664 71.919158.83646.47770.28815.8689.807ms 2.146 13.16
Peer Jitter 166.70.136.350.1410.2110.3130.62946.815 77.434159.79346.50377.22317.1637.442ms 1.662 13.57
Peer Jitter 17.253.2.1250.1790.3570.4560.98355.711 77.631156.76455.25577.27418.6689.144ms 1.164 8.199
Peer Jitter 17.254.0.490.1540.2530.3460.72251.935 70.654175.34051.58970.40117.1997.888ms 1.344 10.18
Peer Jitter 192.168.254.557.83522.55333.29362.696115.770 138.6261,506.65982.477116.07389.12872.346µs 13.89 216.6
Peer Jitter 194.58.200.200.0780.1720.2490.57858.430 74.629163.84758.18174.45719.3288.944ms 1.233 9.449
Peer Jitter 199.102.46.720.1350.2450.3504.98463.173 84.155161.38862.82383.91022.87118.231ms0.7667 4.186
Peer Jitter 209.165.131.200.1330.3030.5442.45255.267 79.475157.07054.72379.17219.0289.477ms 1.79 12.27
Peer Jitter 209.193.63.100.0740.1630.2510.55554.888 86.536175.84554.63786.37320.1038.446ms 1.696 14.38
Peer Jitter 209.193.63.1000.0610.1530.2270.54150.261 70.670153.51350.03470.51616.5437.394ms 1.28 10.11
Peer Jitter 209.193.63.1230.0750.1270.1790.42750.215 71.129117.62250.03671.00216.1656.611ms 1.228 8.707
Peer Jitter 216.218.254.2020.0860.2000.2870.57853.076 72.103160.83052.78871.90317.3188.185ms0.9405 7.204
Peer Jitter 31.207.56.540.1170.2900.3950.78051.109 71.424137.43850.71371.13416.0907.176ms 1.137 7.599
Peer Jitter 31.207.56.550.1830.3220.4240.75054.058 68.998161.46853.63468.67717.6187.907ms 1.426 11.45
Peer Offset 13.65.88.161-12.049-2.4530.0092.4764.600 5.67222.8474.5908.1251.6572.422ms0.8654 24.52
Peer Offset 133.243.238.243-25.877-4.741-2.8361.2695.502 5.8476.3838.33810.5882.4401.061ms-4.723 36.84
Peer Offset 166.70.136.35-21.265-1.4930.2196.2587.775 9.03010.3437.55610.5232.8115.195ms0.8537 11.73
Peer Offset 17.253.2.125-26.294-3.956-3.2940.8682.159 2.5777.1275.4536.5332.461-0.330ms-7.389 41.7
Peer Offset 17.254.0.49-34.356-1.1690.9221.6512.433 2.71013.2621.5113.8791.6291.553ms-13.47 244
Peer Offset 192.168.254.551.2831.3061.3341.4081.500 1.5271.5610.1670.2210.0501.411ms2.033e+045.563e+05
Peer Offset 194.58.200.20-27.806-1.521-1.061-0.5863.363 5.4146.8324.4246.9351.768-0.304ms-8.276 82.5
Peer Offset 199.102.46.72-70.950-19.959-1.953-1.207-0.581 -0.3240.1631.37119.6343.947-1.705ms-17.57 204.8
Peer Offset 209.165.131.20-26.639-11.163-4.852-0.5582.107 3.5594.8846.95914.7222.734-0.992ms-9.046 43.79
Peer Offset 209.193.63.10-23.112-1.785-0.0471.6243.116 6.74412.9243.1638.5301.6321.576ms-4.773 72.06
Peer Offset 209.193.63.100-27.470-0.2090.5241.3722.148 2.42812.8911.6242.6371.2411.314ms-15.51 335.5
Peer Offset 209.193.63.123-21.224-0.4660.3611.4492.453 2.9363.5262.0923.4021.3301.395ms-11.38 167.9
Peer Offset 216.218.254.202-21.9540.4680.9842.5893.097 3.3875.0382.1132.9191.1832.368ms-6.636 137.6
Peer Offset 31.207.56.54-20.153-0.7590.1120.7181.325 1.8299.7311.2122.5881.0900.654ms-11.14 167.4
Peer Offset 31.207.56.55-23.838-3.322-0.0420.6501.216 1.4724.6351.2584.7951.4240.515ms-13.59 189
Refclock Offset SHM(0)-22.349-16.866-12.794-2.7387.390 10.17118.66520.18427.0376.206-2.701ms-7.325 19.46
Refclock Offset SHM(1)-492.703-453.803-437.896-13.688378.889 462.470509.923816.785916.273289.3520.008µs-4.141 9.209
Refclock RMS Jitter SHM(0)0.1590.4270.6371.7834.489 6.31122.3203.8525.8841.2782.074ms 3.974 18.31
Refclock RMS Jitter SHM(1)234.331258.091276.703400.769570.929 592.647629.195294.226334.55697.681403.694µs 40.45 161
Summary as CSV file


Back to Tech Solvency

Glossary:

frequency offset:
The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
jitter, dispersion:
The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Peer Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of kurtosis. A normal distribution has a kurtosis of three. NIST describes a kurtosis over three as "heavy tailed" and one under three as "light tailed".
ms, millisecond:
One thousandth of a second = 0.001 seconds, 1e-3 seconds
mu, mean:
The arithmetic mean: the sum of all the values divided by the number of values. The formula for mu is: "mu = (∑xi) / N". Where xi denotes the data points and N is the number of data points.
ns, nanosecond:
One billionth of a second, also one thousandth of a microsecond, 0.000000001 seconds and 1e-9 seconds.
percentile:
The value below which a given percentage of values fall.
ppb, parts per billion:
Ratio between two values. These following are all the same: 1 ppb, one in one billion, 1/1,000,000,000, 0.000,000,001, 1e-9 and 0.000,000,1%
ppm, parts per million:
Ratio between two values. These following are all the same: 1 ppm, one in one million, 1/1,000,000, 0.000,001, and 0.000,1%
‰, parts per thousand:
Ratio between two values. These following are all the same: 1 ‰. one in one thousand, 1/1,000, 0.001, and 0.1%
refclock:
Reference clock, a local GPS module or other local source of time.
remote clock:
Any clock reached over the network, LAN or WAN. Also called a peer or server.
time offset:
The difference between the ntpd calculated time and the local system clock's time. Also called phase offset.
σ, sigma:
Sigma denotes the standard deviation (SD) and is centered on the arithmetic mean of the data set. The SD is simply the square root of the variance of the data set. Two sigma is simply twice the standard deviation. Three sigma is three times sigma. Smaller is better.
The formula for sigma is: "σ = √[ ∑(xi-mu)^2 / N ]". Where xi denotes the data points and N is the number of data points.
skewness, Skew:
The skewness of a random variable X is the third standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
upstream clock:
Any remote clock or reference clock used as a source of time.
µs, us, microsecond:
One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.



This page autogenerated by ntpviz, part of the NTPsec project
html 5    Valid CSS!