NTPsec

C-ntpsec-12-hour-stats

Report generated: Thu Aug 5 10:02:21 2021 UTC
Start Time: Wed Aug 4 22:02:20 2021 UTC
End Time: Thu Aug 5 10:02:20 2021 UTC
Report published: Thu Aug 05 03:03:05 2021 PDT
Report Period: 0.5 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.707 -0.679 -0.478 0.059 0.690 1.000 1.940 1.168 1.679 0.366 0.068 µs -2.842 8.52
Local Clock Frequency Offset -4.967 -4.963 -4.952 -4.895 -4.872 -4.869 -4.869 0.080 0.093 0.025 -4.900 ppm -7.633e+06 1.503e+09

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 102.000 116.000 134.000 194.000 317.000 467.000 1,676.000 183.000 351.000 92.411 209.861 ns 13.31 141

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 29.000 36.000 45.000 76.000 164.000 287.000 346.000 119.000 251.000 42.833 86.574 10e-12 6.679 29.91

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.707 -0.679 -0.478 0.059 0.690 1.000 1.940 1.168 1.679 0.366 0.068 µs -2.842 8.52

The clock offsets of the local clock as a histogram.

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



Local Temperatures

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 -4.967 -4.963 -4.952 -4.895 -4.872 -4.869 -4.869 0.080 0.093 0.025 -4.900 ppm -7.633e+06 1.503e+09
Temp ZONE0 57.996 58.534 59.072 60.148 60.686 60.686 60.686 1.614 2.152 0.520 59.788 °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 12.000 13.000 3.000 5.000 1.054 9.344 nSat 510.1 4208
TDOP 0.470 0.530 0.570 0.780 1.230 1.580 1.850 0.660 1.050 0.218 0.847 33.81 137.5

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.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 1.390 1.390 2.516 2.945 3.402 4.070 4.070 0.886 2.680 0.348 2.931 ms 428.1 3321

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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 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 3.692 3.692 3.692 3.692 3.692 3.692 3.692 0.000 0.000 0.000 3.692 ms nan nan

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

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

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

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



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.857 -2.792 -0.494 0.068 2.327 534.687 560.083 2.821 537.479 86.814 14.518 ms 2.771 20.41

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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.168.1.10

peer offset 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.10 -37.454 32.161 78.940 180.907 242.299 271.290 279.530 163.359 239.129 52.302 171.773 µs 18.03 55.39

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

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

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

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



Server Offset 194.58.202.211

peer offset 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.211 3.988 3.988 5.770 6.499 8.161 10.266 10.266 2.391 6.278 0.890 6.744 ms 305.8 2170

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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 194.58.202.219

peer offset 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.219 4.198 4.198 6.107 6.852 9.169 9.309 9.309 3.062 5.111 0.905 7.086 ms 340.6 2493

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 -1.204 -1.204 -0.841 -0.140 6.330 7.171 7.171 7.171 8.375 1.598 0.150 ms 0.3176 7.832

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

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

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

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



Server Offset 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 -1.294 -1.294 -1.294 2.717 4.641 4.641 4.641 5.935 5.935 1.490 2.307 ms 0.6694 3.866

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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 204.17.205.24

peer offset 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.24 2.943 2.943 3.469 3.950 4.277 5.365 5.365 0.808 2.422 0.290 3.946 ms 2049 2.637e+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 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 -1.157 -0.269 1.175 2.774 3.080 3.136 3.210 1.904 3.405 0.609 2.654 ms 43.88 161.5

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

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

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

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



Server Offset 63.145.169.3

peer offset 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 63.145.169.3 -78.676 -75.402 -73.377 -0.091 0.650 1.117 2.765 74.026 76.519 29.758 -22.943 ms -11.53 35.01

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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.62.153.210

peer offset 64.62.153.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.62.153.210 -3.413 -0.027 2.185 2.792 3.102 3.208 3.225 0.917 3.234 0.722 2.676 ms 21.51 78.41

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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.62.194.189

peer offset 64.62.194.189 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 64.62.194.189 2.355 4.127 4.324 5.321 6.829 22.328 539.755 2.506 18.201 50.735 10.395 ms 7.437 79.1

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

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

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

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



Server Offset 73.158.5.1

peer offset 73.158.5.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 73.158.5.1 -3.700 -3.652 -2.115 -0.554 0.427 4.376 20.468 2.542 8.028 2.152 -0.515 ms 2.1 48.97

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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) -68.332 -65.974 -62.934 -54.999 -47.480 -45.218 -42.470 15.454 20.756 4.507 -54.987 ms -2339 3.141e+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 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.708 -0.680 -0.479 0.060 0.691 1.000 1.941 1.170 1.680 0.367 0.068 µs -2.844 8.507

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

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much 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.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.139 0.139 0.209 1.492 6.338 203.797 203.797 6.129 203.658 21.959 4.488 ms 6.009 56.67

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

Closer 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 3.152 3.152 3.152 3.152 3.152 3.152 3.152 0.000 0.000 0.000 3.152 ms nan nan

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

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

RMS Jitter is field 8 in the peerstats log file.



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 0.000 0.000 0.064 2.074 17.946 387.908 550.259 17.882 387.908 70.506 15.012 ms 3.358 25.94

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 192.168.1.10

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 0.025 0.040 0.073 0.275 8.875 10.343 16.417 8.802 10.303 3.159 1.874 ms 0.4832 2.863

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

Closer 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 194.58.202.211

peer jitter 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.211 0.305 0.305 0.397 2.068 11.229 45.495 45.495 10.832 45.190 6.738 4.117 ms 3.636 23.03

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 194.58.202.219

peer jitter 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.219 0.221 0.221 0.317 1.811 11.908 14.280 14.280 11.591 14.059 3.161 2.920 ms 1.812 6.092

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

Closer 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 203.123.48.219

peer jitter 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 203.123.48.219 0.146 0.146 0.420 2.404 11.148 19.467 19.467 10.728 19.321 4.190 4.407 ms 1.477 4.881

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

Closer 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 204.123.2.5

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.045 3.070 3.070 3.070 3.070 3.070 0.950 1.028 ms 0.9938 3.173

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

Closer 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 204.17.205.24

peer jitter 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.24 0.174 0.174 0.401 1.413 9.624 10.741 10.741 9.223 10.566 3.123 3.055 ms 1.097 2.854

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

Closer 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 216.218.192.202

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.000 0.000 0.270 1.415 9.083 19.844 19.903 8.813 19.844 3.952 3.099 ms 1.571 6.527

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

Closer 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 63.145.169.3

peer jitter 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 63.145.169.3 0.000 0.000 3.310 45.431 75.301 82.684 87.622 71.991 82.684 24.420 41.265 ms 2.185 4.247

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 64.62.153.210

peer jitter 64.62.153.210 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.62.153.210 0.000 0.000 0.390 1.663 9.076 13.118 20.921 8.687 13.118 3.895 3.753 ms 1.354 5.004

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

Closer 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.62.194.189

peer jitter 64.62.194.189 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 64.62.194.189 0.000 0.000 0.151 1.178 12.432 380.262 517.428 12.281 380.262 60.463 10.505 ms 4.391 37.63

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 73.158.5.1

peer jitter 73.158.5.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 73.158.5.1 0.000 0.000 0.845 2.408 11.203 55.483 55.774 10.358 55.483 7.560 4.525 ms 4.061 27.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 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.098 0.213 0.352 1.012 3.242 5.878 9.259 2.889 5.664 1.044 1.303 ms 3.383 15.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.



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) 45.000 69.000 99.000 233.000 549.000 801.000 3,082.000 450.000 732.000 175.186 272.088 ns 6.313 60.44

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

Closer 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 -4.967 -4.963 -4.952 -4.895 -4.872 -4.869 -4.869 0.080 0.093 0.025 -4.900 ppm -7.633e+06 1.503e+09
Local Clock Time Offset -2.707 -0.679 -0.478 0.059 0.690 1.000 1.940 1.168 1.679 0.366 0.068 µs -2.842 8.52
Local RMS Frequency Jitter 29.000 36.000 45.000 76.000 164.000 287.000 346.000 119.000 251.000 42.833 86.574 10e-12 6.679 29.91
Local RMS Time Jitter 102.000 116.000 134.000 194.000 317.000 467.000 1,676.000 183.000 351.000 92.411 209.861 ns 13.31 141
Server Jitter 162.159.200.1 0.139 0.139 0.209 1.492 6.338 203.797 203.797 6.129 203.658 21.959 4.488 ms 6.009 56.67
Server Jitter 162.159.200.123 3.152 3.152 3.152 3.152 3.152 3.152 3.152 0.000 0.000 0.000 3.152 ms nan nan
Server Jitter 173.11.101.155 0.000 0.000 0.064 2.074 17.946 387.908 550.259 17.882 387.908 70.506 15.012 ms 3.358 25.94
Server Jitter 192.168.1.10 0.025 0.040 0.073 0.275 8.875 10.343 16.417 8.802 10.303 3.159 1.874 ms 0.4832 2.863
Server Jitter 194.58.202.211 0.305 0.305 0.397 2.068 11.229 45.495 45.495 10.832 45.190 6.738 4.117 ms 3.636 23.03
Server Jitter 194.58.202.219 0.221 0.221 0.317 1.811 11.908 14.280 14.280 11.591 14.059 3.161 2.920 ms 1.812 6.092
Server Jitter 203.123.48.219 0.146 0.146 0.420 2.404 11.148 19.467 19.467 10.728 19.321 4.190 4.407 ms 1.477 4.881
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.045 3.070 3.070 3.070 3.070 3.070 0.950 1.028 ms 0.9938 3.173
Server Jitter 204.17.205.24 0.174 0.174 0.401 1.413 9.624 10.741 10.741 9.223 10.566 3.123 3.055 ms 1.097 2.854
Server Jitter 216.218.192.202 0.000 0.000 0.270 1.415 9.083 19.844 19.903 8.813 19.844 3.952 3.099 ms 1.571 6.527
Server Jitter 63.145.169.3 0.000 0.000 3.310 45.431 75.301 82.684 87.622 71.991 82.684 24.420 41.265 ms 2.185 4.247
Server Jitter 64.62.153.210 0.000 0.000 0.390 1.663 9.076 13.118 20.921 8.687 13.118 3.895 3.753 ms 1.354 5.004
Server Jitter 64.62.194.189 0.000 0.000 0.151 1.178 12.432 380.262 517.428 12.281 380.262 60.463 10.505 ms 4.391 37.63
Server Jitter 73.158.5.1 0.000 0.000 0.845 2.408 11.203 55.483 55.774 10.358 55.483 7.560 4.525 ms 4.061 27.7
Server Jitter SHM(0) 0.098 0.213 0.352 1.012 3.242 5.878 9.259 2.889 5.664 1.044 1.303 ms 3.383 15.35
Server Jitter SHM(1) 45.000 69.000 99.000 233.000 549.000 801.000 3,082.000 450.000 732.000 175.186 272.088 ns 6.313 60.44
Server Offset 162.159.200.1 1.390 1.390 2.516 2.945 3.402 4.070 4.070 0.886 2.680 0.348 2.931 ms 428.1 3321
Server Offset 162.159.200.123 3.692 3.692 3.692 3.692 3.692 3.692 3.692 0.000 0.000 0.000 3.692 ms nan nan
Server Offset 173.11.101.155 -3.857 -2.792 -0.494 0.068 2.327 534.687 560.083 2.821 537.479 86.814 14.518 ms 2.771 20.41
Server Offset 192.168.1.10 -37.454 32.161 78.940 180.907 242.299 271.290 279.530 163.359 239.129 52.302 171.773 µs 18.03 55.39
Server Offset 194.58.202.211 3.988 3.988 5.770 6.499 8.161 10.266 10.266 2.391 6.278 0.890 6.744 ms 305.8 2170
Server Offset 194.58.202.219 4.198 4.198 6.107 6.852 9.169 9.309 9.309 3.062 5.111 0.905 7.086 ms 340.6 2493
Server Offset 203.123.48.219 -1.204 -1.204 -0.841 -0.140 6.330 7.171 7.171 7.171 8.375 1.598 0.150 ms 0.3176 7.832
Server Offset 204.123.2.5 -1.294 -1.294 -1.294 2.717 4.641 4.641 4.641 5.935 5.935 1.490 2.307 ms 0.6694 3.866
Server Offset 204.17.205.24 2.943 2.943 3.469 3.950 4.277 5.365 5.365 0.808 2.422 0.290 3.946 ms 2049 2.637e+04
Server Offset 216.218.192.202 -1.157 -0.269 1.175 2.774 3.080 3.136 3.210 1.904 3.405 0.609 2.654 ms 43.88 161.5
Server Offset 63.145.169.3 -78.676 -75.402 -73.377 -0.091 0.650 1.117 2.765 74.026 76.519 29.758 -22.943 ms -11.53 35.01
Server Offset 64.62.153.210 -3.413 -0.027 2.185 2.792 3.102 3.208 3.225 0.917 3.234 0.722 2.676 ms 21.51 78.41
Server Offset 64.62.194.189 2.355 4.127 4.324 5.321 6.829 22.328 539.755 2.506 18.201 50.735 10.395 ms 7.437 79.1
Server Offset 73.158.5.1 -3.700 -3.652 -2.115 -0.554 0.427 4.376 20.468 2.542 8.028 2.152 -0.515 ms 2.1 48.97
Server Offset SHM(0) -68.332 -65.974 -62.934 -54.999 -47.480 -45.218 -42.470 15.454 20.756 4.507 -54.987 ms -2339 3.141e+04
Server Offset SHM(1) -2.708 -0.680 -0.479 0.060 0.691 1.000 1.941 1.170 1.680 0.367 0.068 µs -2.844 8.507
TDOP 0.470 0.530 0.570 0.780 1.230 1.580 1.850 0.660 1.050 0.218 0.847 33.81 137.5
Temp ZONE0 57.996 58.534 59.072 60.148 60.686 60.686 60.686 1.614 2.152 0.520 59.788 °C
nSats 7.000 7.000 8.000 9.000 11.000 12.000 13.000 3.000 5.000 1.054 9.344 nSat 510.1 4208
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!