NTPsec

C-ntpsec-3-hour-stats

Report generated: Sun Sep 26 13:02:21 2021 UTC
Start Time: Sun Sep 26 10:02:21 2021 UTC
End Time: Sun Sep 26 13:02:21 2021 UTC
Report published: Sun Sep 26 06:02:27 2021 PDT
Report Period: 0.1 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 -829.000 -709.000 -561.000 -200.000 294.000 509.000 651.000 855.000 1,218.000 263.115 -172.467 ns -9.124 24.45
Local Clock Frequency Offset -4.974 -4.974 -4.972 -4.960 -4.948 -4.946 -4.946 0.025 0.028 0.0081 -4.959 ppm -2.285e+08 1.397e+11

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 87.000 106.000 123.000 179.000 268.000 308.000 372.000 145.000 202.000 41.990 184.561 ns 50.19 218.3

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

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

RMS jitter is field 5 in the loopstats log file.



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 32.000 37.000 48.000 74.000 111.000 121.000 129.000 63.000 84.000 19.160 75.616 10e-12 34.79 134.4

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 -829.000 -709.000 -561.000 -200.000 294.000 509.000 651.000 855.000 1,218.000 263.115 -172.467 ns -9.124 24.45

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.974 -4.974 -4.972 -4.960 -4.948 -4.946 -4.946 0.025 0.028 0.0081 -4.959 ppm -2.285e+08 1.397e+11
Temp ZONE0 57.996 57.996 57.996 58.534 59.072 59.610 59.610 1.076 1.614 0.393 58.546 °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 7.000 9.000 9.000 10.000 10.000 2.000 3.000 0.645 8.536 nSat 1866 2.326e+04
TDOP 0.650 0.650 0.680 0.860 1.400 1.420 1.420 0.720 0.770 0.154 0.871 116.3 641

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.378 2.378 2.532 2.894 3.223 3.682 3.682 0.691 1.304 0.242 2.911 ms 1382 1.566e+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 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 -5.843 -5.843 -5.788 -5.690 -5.512 -5.185 -5.185 0.276 0.658 0.112 -5.660 ms -1.358e+05 6.985e+06

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 -940.560 -940.560 -669.994 -4.211 349.091 457.060 457.060 1,019.085 1,397.620 301.849 -42.746 µs -5.817 17.19

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 -119.745 -118.515 -60.502 76.805 210.221 276.042 328.205 270.723 394.557 82.493 75.780 µs -0.05885 3.138

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 8.421 8.421 8.540 8.690 8.869 8.938 8.938 0.329 0.517 0.104 8.691 ms 5.697e+05 4.724e+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 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 6.334 6.334 6.360 6.572 6.672 6.705 6.705 0.312 0.371 0.096 6.561 ms 3.086e+05 2.087e+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 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 2.524 2.524 2.543 2.768 3.030 3.148 3.148 0.487 0.623 0.140 2.769 ms 6733 1.279e+05

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 3.166 3.166 3.373 3.677 3.950 4.022 4.022 0.577 0.857 0.156 3.659 ms 1.145e+04 2.592e+05

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

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.254.202 2.407 2.407 2.423 2.547 2.714 2.784 2.784 0.291 0.377 0.102 2.565 ms 1.436e+04 3.503e+05

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 -86.430 -86.430 -73.159 -57.298 1.079 3.689 3.689 74.238 90.120 30.212 -42.952 ms -20.96 66.28

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) -61.866 -61.230 -60.361 -54.182 -50.619 -48.264 -46.848 9.742 12.966 3.447 -55.252 ms -4988 8.58e+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) -830.000 -710.000 -562.000 -201.000 295.000 510.000 652.000 857.000 1,220.000 263.749 -172.957 ns -9.124 24.43

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.257 0.257 0.323 1.274 21.832 22.822 22.822 21.509 22.564 8.122 5.954 ms 0.394 1.878

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.218 0.218 0.223 1.609 23.089 24.432 24.432 22.866 24.214 6.363 4.514 ms 0.9535 3.757

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.326 0.326 0.682 1.487 18.381 20.219 20.219 17.699 19.893 6.838 5.414 ms 0.4905 1.743

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.078 0.085 0.149 3.229 21.508 22.842 24.729 21.360 22.757 7.393 6.405 ms 0.5655 2.239

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.201 0.201 0.249 1.083 21.523 21.534 21.534 21.274 21.333 6.070 4.134 ms 0.7849 3.374

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.164 0.164 0.185 0.895 15.055 21.805 21.805 14.869 21.642 5.170 3.083 ms 0.8746 4.348

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.153 0.153 0.160 1.085 15.710 15.736 15.736 15.550 15.582 4.709 4.165 ms 0.6629 2.339

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.127 0.127 0.298 0.720 23.682 23.721 23.721 23.384 23.594 7.485 5.463 ms 0.5146 2.436

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

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.254.202 0.152 0.152 0.161 1.345 18.659 18.682 18.682 18.498 18.530 6.561 4.543 ms 0.5703 2.258

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 2.512 2.512 4.362 24.307 87.512 94.401 94.401 83.150 91.888 25.391 34.644 ms 1.889 4.198

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.133 0.244 0.360 0.958 3.018 5.966 7.880 2.658 5.722 1.022 1.236 ms 3.587 16.89

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) 53.000 72.000 100.000 228.000 518.000 654.000 972.000 418.000 582.000 128.416 251.184 ns 5.025 16.52

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.974 -4.974 -4.972 -4.960 -4.948 -4.946 -4.946 0.025 0.028 0.0081 -4.959 ppm -2.285e+08 1.397e+11
Local Clock Time Offset -829.000 -709.000 -561.000 -200.000 294.000 509.000 651.000 855.000 1,218.000 263.115 -172.467 ns -9.124 24.45
Local RMS Frequency Jitter 32.000 37.000 48.000 74.000 111.000 121.000 129.000 63.000 84.000 19.160 75.616 10e-12 34.79 134.4
Local RMS Time Jitter 87.000 106.000 123.000 179.000 268.000 308.000 372.000 145.000 202.000 41.990 184.561 ns 50.19 218.3
Server Jitter 162.159.200.123 0.257 0.257 0.323 1.274 21.832 22.822 22.822 21.509 22.564 8.122 5.954 ms 0.394 1.878
Server Jitter 169.229.128.134 0.218 0.218 0.223 1.609 23.089 24.432 24.432 22.866 24.214 6.363 4.514 ms 0.9535 3.757
Server Jitter 173.11.101.155 0.326 0.326 0.682 1.487 18.381 20.219 20.219 17.699 19.893 6.838 5.414 ms 0.4905 1.743
Server Jitter 192.168.1.10 0.078 0.085 0.149 3.229 21.508 22.842 24.729 21.360 22.757 7.393 6.405 ms 0.5655 2.239
Server Jitter 194.58.202.211 0.201 0.201 0.249 1.083 21.523 21.534 21.534 21.274 21.333 6.070 4.134 ms 0.7849 3.374
Server Jitter 194.58.202.219 0.164 0.164 0.185 0.895 15.055 21.805 21.805 14.869 21.642 5.170 3.083 ms 0.8746 4.348
Server Jitter 203.123.48.219 0.153 0.153 0.160 1.085 15.710 15.736 15.736 15.550 15.582 4.709 4.165 ms 0.6629 2.339
Server Jitter 204.17.205.24 0.127 0.127 0.298 0.720 23.682 23.721 23.721 23.384 23.594 7.485 5.463 ms 0.5146 2.436
Server Jitter 216.218.254.202 0.152 0.152 0.161 1.345 18.659 18.682 18.682 18.498 18.530 6.561 4.543 ms 0.5703 2.258
Server Jitter 63.145.169.3 2.512 2.512 4.362 24.307 87.512 94.401 94.401 83.150 91.888 25.391 34.644 ms 1.889 4.198
Server Jitter SHM(0) 0.133 0.244 0.360 0.958 3.018 5.966 7.880 2.658 5.722 1.022 1.236 ms 3.587 16.89
Server Jitter SHM(1) 53.000 72.000 100.000 228.000 518.000 654.000 972.000 418.000 582.000 128.416 251.184 ns 5.025 16.52
Server Offset 162.159.200.123 2.378 2.378 2.532 2.894 3.223 3.682 3.682 0.691 1.304 0.242 2.911 ms 1382 1.566e+04
Server Offset 169.229.128.134 -5.843 -5.843 -5.788 -5.690 -5.512 -5.185 -5.185 0.276 0.658 0.112 -5.660 ms -1.358e+05 6.985e+06
Server Offset 173.11.101.155 -940.560 -940.560 -669.994 -4.211 349.091 457.060 457.060 1,019.085 1,397.620 301.849 -42.746 µs -5.817 17.19
Server Offset 192.168.1.10 -119.745 -118.515 -60.502 76.805 210.221 276.042 328.205 270.723 394.557 82.493 75.780 µs -0.05885 3.138
Server Offset 194.58.202.211 8.421 8.421 8.540 8.690 8.869 8.938 8.938 0.329 0.517 0.104 8.691 ms 5.697e+05 4.724e+07
Server Offset 194.58.202.219 6.334 6.334 6.360 6.572 6.672 6.705 6.705 0.312 0.371 0.096 6.561 ms 3.086e+05 2.087e+07
Server Offset 203.123.48.219 2.524 2.524 2.543 2.768 3.030 3.148 3.148 0.487 0.623 0.140 2.769 ms 6733 1.279e+05
Server Offset 204.17.205.24 3.166 3.166 3.373 3.677 3.950 4.022 4.022 0.577 0.857 0.156 3.659 ms 1.145e+04 2.592e+05
Server Offset 216.218.254.202 2.407 2.407 2.423 2.547 2.714 2.784 2.784 0.291 0.377 0.102 2.565 ms 1.436e+04 3.503e+05
Server Offset 63.145.169.3 -86.430 -86.430 -73.159 -57.298 1.079 3.689 3.689 74.238 90.120 30.212 -42.952 ms -20.96 66.28
Server Offset SHM(0) -61.866 -61.230 -60.361 -54.182 -50.619 -48.264 -46.848 9.742 12.966 3.447 -55.252 ms -4988 8.58e+04
Server Offset SHM(1) -830.000 -710.000 -562.000 -201.000 295.000 510.000 652.000 857.000 1,220.000 263.749 -172.957 ns -9.124 24.43
TDOP 0.650 0.650 0.680 0.860 1.400 1.420 1.420 0.720 0.770 0.154 0.871 116.3 641
Temp ZONE0 57.996 57.996 57.996 58.534 59.072 59.610 59.610 1.076 1.614 0.393 58.546 °C
nSats 7.000 7.000 7.000 9.000 9.000 10.000 10.000 2.000 3.000 0.645 8.536 nSat 1866 2.326e+04
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!