NTPsec

A-ntpsec-6-hour-stats

Report generated: Sun Oct 13 22:04:23 2024 UTC
Start Time: Sun Oct 13 16:04:23 2024 UTC
End Time: Sun Oct 13 22:04:23 2024 UTC
Report published: Tue Oct 15 05:04:03 PM 2024 PDT
Report published: Tue Oct 15 04:04:05 PM 2024 PDT
Report published: Tue Oct 15 03:04:04 PM 2024 PDT
Report published: Tue Oct 15 02:04:04 PM 2024 PDT
Report published: Tue Oct 15 01:04:04 PM 2024 PDT
Report published: Tue Oct 15 12:04:06 PM 2024 PDT
Report published: Tue Oct 15 11:04:06 AM 2024 PDT
Report published: Tue Oct 15 10:04:05 AM 2024 PDT
Report published: Tue Oct 15 09:04:04 AM 2024 PDT
Report published: Tue Oct 15 08:04:04 AM 2024 PDT
Report published: Tue Oct 15 07:04:03 AM 2024 PDT
Report published: Tue Oct 15 06:04:06 AM 2024 PDT
Report published: Tue Oct 15 05:04:03 AM 2024 PDT
Report published: Tue Oct 15 04:04:04 AM 2024 PDT
Report published: Tue Oct 15 03:04:05 AM 2024 PDT
Report published: Tue Oct 15 02:04:05 AM 2024 PDT
Report published: Tue Oct 15 01:04:05 AM 2024 PDT
Report published: Tue Oct 15 12:04:05 AM 2024 PDT
Report published: Mon Oct 14 11:04:04 PM 2024 PDT
Report published: Mon Oct 14 10:04:04 PM 2024 PDT
Report published: Mon Oct 14 09:04:06 PM 2024 PDT
Report published: Mon Oct 14 08:04:03 PM 2024 PDT
Report published: Mon Oct 14 07:04:04 PM 2024 PDT
Report published: Mon Oct 14 06:04:04 PM 2024 PDT
Report published: Mon Oct 14 05:04:04 PM 2024 PDT
Report published: Mon Oct 14 04:04:04 PM 2024 PDT
Report published: Mon Oct 14 03:04:04 PM 2024 PDT
Report published: Mon Oct 14 02:04:04 PM 2024 PDT
Report published: Mon Oct 14 01:04:04 PM 2024 PDT
Report published: Mon Oct 14 12:04:05 PM 2024 PDT
Report published: Mon Oct 14 11:04:05 AM 2024 PDT
Report published: Mon Oct 14 10:04:03 AM 2024 PDT
Report published: Mon Oct 14 09:04:04 AM 2024 PDT
Report published: Mon Oct 14 08:04:04 AM 2024 PDT
Report published: Mon Oct 14 07:04:05 AM 2024 PDT
Report published: Mon Oct 14 06:04:04 AM 2024 PDT
Report published: Mon Oct 14 05:04:04 AM 2024 PDT
Report published: Mon Oct 14 04:04:05 AM 2024 PDT
Report published: Mon Oct 14 03:04:04 AM 2024 PDT
Report published: Mon Oct 14 02:04:03 AM 2024 PDT
Report published: Mon Oct 14 01:04:05 AM 2024 PDT
Report published: Mon Oct 14 12:04:05 AM 2024 PDT
Report published: Sun Oct 13 11:04:04 PM 2024 PDT
Report published: Sun Oct 13 10:04:05 PM 2024 PDT
Report published: Sun Oct 13 09:04:03 PM 2024 PDT
Report published: Sun Oct 13 08:04:05 PM 2024 PDT
Report published: Sun Oct 13 07:04:03 PM 2024 PDT
Report published: Sun Oct 13 06:04:04 PM 2024 PDT
Report published: Sun Oct 13 05:04:05 PM 2024 PDT
Report published: Sun Oct 13 04:04:04 PM 2024 PDT
Report published: Sun Oct 13 03:04:29 PM 2024 PDT
Report Period: 0.2 days

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -2.516 -1.737 -1.238 0.089 1.156 1.585 2.121 2.394 3.322 0.721 0.050 µs -3.846 9.875
Local Clock Frequency Offset -438.095 -436.432 -435.593 -423.859 -379.486 -372.192 -369.751 56.107 64.240 18.929 -416.272 ppb -1.222e+04 2.825e+05

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 0.474 0.559 0.651 0.924 1.310 1.533 1.783 0.659 0.974 0.202 0.946 µs 61.16 275.1

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 182.000 213.000 244.000 341.000 471.000 529.000 604.000 227.000 316.000 68.714 346.821 10e-12 78.89 377

The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.

Lower is better. An ideal clock would be a horizontal line at 0ppm.

RMS Frequency Jitter is field 6 in the loopstats log file.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -2.516 -1.737 -1.238 0.089 1.156 1.585 2.121 2.394 3.322 0.721 0.050 µs -3.846 9.875

The clock offsets of the local clock as a histogram.

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



Local Temperatures

local temps plot

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

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



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -438.095 -436.432 -435.593 -423.859 -379.486 -372.192 -369.751 56.107 64.240 18.929 -416.272 ppb -1.222e+04 2.825e+05
Temp ZONE0 44.546 45.084 45.084 45.084 45.622 46.160 46.160 0.538 1.076 0.288 45.243 °C

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

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



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 7.000 7.000 8.000 9.000 11.000 11.000 11.000 3.000 4.000 0.878 9.212 nSat 884.2 8665
TDOP 0.560 0.620 0.650 0.820 1.260 1.480 1.690 0.610 0.860 0.214 0.915 45.92 192.4

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

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

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



Server Offsets

peer offsets plot

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

Clock Offset is field 5 in the peerstats log file.



Server Offset 162.159.200.123

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 2.010 2.010 3.265 4.676 4.936 5.086 5.086 1.670 3.076 0.574 4.478 ms 333.1 2364

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

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

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

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



Server Offset 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 0.275 0.275 0.957 3.110 3.381 3.598 3.598 2.424 3.323 0.799 2.736 ms 20.04 59.36

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

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

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

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



Server Offset 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -3.339 -3.339 -2.093 0.897 3.248 4.852 4.852 5.341 8.191 1.648 0.819 ms -1.846 4.932

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

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

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

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



Server Offset 192.12.19.20

peer offset 192.12.19.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.12.19.20 1.240 1.240 2.044 3.820 4.119 4.487 4.487 2.075 3.247 0.763 3.445 ms 52.95 215.4

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

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

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

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



Server Offset 5.161.184.148

peer offset 5.161.184.148 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 5.161.184.148 4.103 4.103 5.298 6.218 6.662 6.864 6.864 1.364 2.762 0.452 6.145 ms 2031 2.597e+04

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

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

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

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



Server Offset 50.116.42.84

peer offset 50.116.42.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 50.116.42.84 2.803 2.803 3.803 4.710 6.195 6.692 6.692 2.391 3.890 0.784 4.958 ms 167.2 980.3

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

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

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

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



Server Offset 52.10.183.132

peer offset 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 52.10.183.132 0.520 0.520 2.699 3.639 4.271 4.481 4.481 1.571 3.961 0.584 3.569 ms 146.5 805.4

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

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

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

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



Server Offset 64.142.122.36

peer offset 64.142.122.36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.142.122.36 0.076 0.076 0.593 2.805 3.154 3.460 3.460 2.561 3.384 0.828 2.408 ms 11.58 29.82

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

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

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

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



Server Offset 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 0.932 0.932 1.476 3.505 3.871 3.964 3.964 2.395 3.032 0.770 3.154 ms 37.61 135.9

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

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

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

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



Server Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -99.445 -99.058 -98.333 -96.576 -94.586 -93.822 -92.581 3.747 5.236 1.129 -96.508 ms -6.467e+05 5.593e+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.



Server Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -2.517 -1.738 -1.239 0.090 1.157 1.586 2.122 2.396 3.324 0.722 0.050 µs -3.846 9.869

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

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

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

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



Server Jitters

peer jitters plot

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.123

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.628 0.628 0.868 2.079 6.155 9.496 9.496 5.288 8.868 1.707 2.593 ms 3.449 11.99

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 169.229.128.134 0.314 0.314 0.978 2.451 5.911 8.386 8.386 4.933 8.071 1.525 2.741 ms 4.226 13.42

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 1.445 1.445 1.805 3.346 10.125 11.046 11.046 8.320 9.600 2.111 3.942 ms 5.041 17.09

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 192.12.19.20

peer jitter 192.12.19.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.12.19.20 0.617 0.617 1.003 2.908 10.102 11.159 11.159 9.099 10.543 2.775 3.626 ms 2.237 5.894

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 5.161.184.148

peer jitter 5.161.184.148 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 5.161.184.148 0.533 0.533 1.005 2.289 4.910 6.637 6.637 3.905 6.104 1.172 2.482 ms 5.77 17.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 50.116.42.84

peer jitter 50.116.42.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 50.116.42.84 0.529 0.529 0.672 2.116 9.746 13.972 13.972 9.074 13.443 2.726 3.218 ms 2.567 8.848

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 52.10.183.132

peer jitter 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 52.10.183.132 0.372 0.372 0.981 2.682 9.942 15.636 15.636 8.961 15.265 2.603 3.040 ms 4.041 18.92

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 64.142.122.36

peer jitter 64.142.122.36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.142.122.36 0.875 0.875 0.970 2.518 7.059 10.925 10.925 6.089 10.051 2.065 3.247 ms 3.125 9.181

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 0.860 0.860 0.952 2.161 5.106 7.656 7.656 4.154 6.796 1.371 2.618 ms 4.855 15.96

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.038 0.085 0.121 0.326 1.053 1.588 2.152 0.931 1.503 0.316 0.426 ms 2.89 10.31

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.173 0.340 0.471 0.895 1.745 2.168 2.780 1.274 1.828 0.390 0.969 µs 8.722 28.35

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

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

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -438.095 -436.432 -435.593 -423.859 -379.486 -372.192 -369.751 56.107 64.240 18.929 -416.272 ppb -1.222e+04 2.825e+05
Local Clock Time Offset -2.516 -1.737 -1.238 0.089 1.156 1.585 2.121 2.394 3.322 0.721 0.050 µs -3.846 9.875
Local RMS Frequency Jitter 182.000 213.000 244.000 341.000 471.000 529.000 604.000 227.000 316.000 68.714 346.821 10e-12 78.89 377
Local RMS Time Jitter 0.474 0.559 0.651 0.924 1.310 1.533 1.783 0.659 0.974 0.202 0.946 µs 61.16 275.1
Server Jitter 162.159.200.123 0.628 0.628 0.868 2.079 6.155 9.496 9.496 5.288 8.868 1.707 2.593 ms 3.449 11.99
Server Jitter 169.229.128.134 0.314 0.314 0.978 2.451 5.911 8.386 8.386 4.933 8.071 1.525 2.741 ms 4.226 13.42
Server Jitter 173.11.101.155 1.445 1.445 1.805 3.346 10.125 11.046 11.046 8.320 9.600 2.111 3.942 ms 5.041 17.09
Server Jitter 192.12.19.20 0.617 0.617 1.003 2.908 10.102 11.159 11.159 9.099 10.543 2.775 3.626 ms 2.237 5.894
Server Jitter 5.161.184.148 0.533 0.533 1.005 2.289 4.910 6.637 6.637 3.905 6.104 1.172 2.482 ms 5.77 17.7
Server Jitter 50.116.42.84 0.529 0.529 0.672 2.116 9.746 13.972 13.972 9.074 13.443 2.726 3.218 ms 2.567 8.848
Server Jitter 52.10.183.132 0.372 0.372 0.981 2.682 9.942 15.636 15.636 8.961 15.265 2.603 3.040 ms 4.041 18.92
Server Jitter 64.142.122.36 0.875 0.875 0.970 2.518 7.059 10.925 10.925 6.089 10.051 2.065 3.247 ms 3.125 9.181
Server Jitter 66.220.9.122 0.860 0.860 0.952 2.161 5.106 7.656 7.656 4.154 6.796 1.371 2.618 ms 4.855 15.96
Server Jitter SHM(0) 0.038 0.085 0.121 0.326 1.053 1.588 2.152 0.931 1.503 0.316 0.426 ms 2.89 10.31
Server Jitter SHM(1) 0.173 0.340 0.471 0.895 1.745 2.168 2.780 1.274 1.828 0.390 0.969 µs 8.722 28.35
Server Offset 162.159.200.123 2.010 2.010 3.265 4.676 4.936 5.086 5.086 1.670 3.076 0.574 4.478 ms 333.1 2364
Server Offset 169.229.128.134 0.275 0.275 0.957 3.110 3.381 3.598 3.598 2.424 3.323 0.799 2.736 ms 20.04 59.36
Server Offset 173.11.101.155 -3.339 -3.339 -2.093 0.897 3.248 4.852 4.852 5.341 8.191 1.648 0.819 ms -1.846 4.932
Server Offset 192.12.19.20 1.240 1.240 2.044 3.820 4.119 4.487 4.487 2.075 3.247 0.763 3.445 ms 52.95 215.4
Server Offset 5.161.184.148 4.103 4.103 5.298 6.218 6.662 6.864 6.864 1.364 2.762 0.452 6.145 ms 2031 2.597e+04
Server Offset 50.116.42.84 2.803 2.803 3.803 4.710 6.195 6.692 6.692 2.391 3.890 0.784 4.958 ms 167.2 980.3
Server Offset 52.10.183.132 0.520 0.520 2.699 3.639 4.271 4.481 4.481 1.571 3.961 0.584 3.569 ms 146.5 805.4
Server Offset 64.142.122.36 0.076 0.076 0.593 2.805 3.154 3.460 3.460 2.561 3.384 0.828 2.408 ms 11.58 29.82
Server Offset 66.220.9.122 0.932 0.932 1.476 3.505 3.871 3.964 3.964 2.395 3.032 0.770 3.154 ms 37.61 135.9
Server Offset SHM(0) -99.445 -99.058 -98.333 -96.576 -94.586 -93.822 -92.581 3.747 5.236 1.129 -96.508 ms -6.467e+05 5.593e+07
Server Offset SHM(1) -2.517 -1.738 -1.239 0.090 1.157 1.586 2.122 2.396 3.324 0.722 0.050 µs -3.846 9.869
TDOP 0.560 0.620 0.650 0.820 1.260 1.480 1.690 0.610 0.860 0.214 0.915 45.92 192.4
Temp ZONE0 44.546 45.084 45.084 45.084 45.622 46.160 46.160 0.538 1.076 0.288 45.243 °C
nSats 7.000 7.000 8.000 9.000 11.000 11.000 11.000 3.000 4.000 0.878 9.212 nSat 884.2 8665
Summary as CSV file


Glossary:

frequency offset:
The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
jitter, dispersion:
The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Server Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
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 server or reference clock used as a source of time.
µs, us, microsecond:
One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.



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