NTPsec

A-ntpsec-1-hour-stats

Report generated: Sat May 28 17:02:08 2022 UTC
Start Time: Sat May 28 16:01:39 2022 UTC
End Time: Sat May 28 17:02:07 2022 UTC
Report published: Sat May 28 10:02:13 2022 PDT
Report Period: 0.0 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 -0.919 -0.725 -0.456 0.062 0.852 1.066 1.419 1.308 1.791 0.390 0.095 µs -2.315 5.949
Local Clock Frequency Offset -65.018 -64.987 -64.178 -61.813 -59.250 -59.097 -59.021 4.928 5.890 1.495 -61.640 ppb -7.55e+04 3.194e+06

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 306.000 322.000 353.000 517.000 677.000 724.000 777.000 324.000 402.000 89.891 518.498 ns 122.7 656.6

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 53.000 58.000 64.000 96.000 125.000 150.000 170.000 61.000 92.000 18.985 96.189 10e-12 79.91 384.1

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 -0.919 -0.725 -0.456 0.062 0.852 1.066 1.419 1.308 1.791 0.390 0.095 µs -2.315 5.949

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 -65.018 -64.987 -64.178 -61.813 -59.250 -59.097 -59.021 4.928 5.890 1.495 -61.640 ppb -7.55e+04 3.194e+06
Temp ZONE0 52.616 52.616 52.616 53.154 53.692 53.692 53.692 1.076 1.076 0.393 53.154 °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 10.000 10.000 10.000 10.000 12.000 12.000 12.000 2.000 2.000 0.854 10.733 nSat 1585 1.876e+04
TDOP 0.610 0.610 0.620 1.020 1.230 1.240 1.240 0.610 0.630 0.245 0.897 26.9 94.75

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 4.779 4.779 4.779 5.132 5.319 5.319 5.319 0.541 0.541 0.166 5.092 ms 2.616e+04 7.781e+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 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 2.291 2.291 2.291 2.455 2.545 2.545 2.545 0.254 0.254 0.066 2.456 ms 4.78e+04 1.737e+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 -372.525 -372.525 -372.525 -78.491 662.523 662.523 662.523 1,035.048 1,035.048 296.687 -21.985 µs -3.117 6.09

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

peer offset 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.11 -137.958 -137.958 -108.666 -48.421 8.627 35.428 35.428 117.293 173.386 40.057 -46.618 µs -16.67 52.55

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

peer offset 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.12 -182.622 -182.622 -169.796 -75.456 19.996 45.069 45.069 189.792 227.691 53.174 -71.746 µs -19.89 65.09

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

peer offset 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.79 5.557 5.557 5.557 5.785 5.888 5.888 5.888 0.331 0.331 0.109 5.760 ms 1.403e+05 7.297e+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 194.58.207.80

peer offset 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.80 7.013 7.013 7.013 7.637 8.048 8.048 8.048 1.036 1.036 0.263 7.628 ms 2.196e+04 6.166e+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 1.844 1.844 1.844 1.845 1.884 1.884 1.884 0.040 0.040 0.019 1.858 ms 9.649e+05 9.537e+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 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 2.468 2.468 2.468 2.566 2.727 2.727 2.727 0.259 0.259 0.089 2.593 ms 2.246e+04 6.353e+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.297 2.297 2.297 2.508 3.094 3.094 3.094 0.797 0.797 0.207 2.567 ms 1523 1.782e+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(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) -56.562 -56.119 -55.639 -52.167 -48.850 -48.177 -47.045 6.789 7.941 2.256 -52.329 ms -1.423e+04 3.46e+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 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) -0.920 -0.726 -0.457 0.063 0.853 1.067 1.420 1.310 1.793 0.391 0.095 µs -2.318 5.948

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 164.400 164.400 164.400 627.747 880.715 880.715 880.715 716.315 716.315 223.546 527.969 µs 6.453 15.5

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.101 0.101 0.101 0.405 10.325 10.325 10.325 10.224 10.224 3.662 2.207 ms 0.4655 2.309

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.001 1.001 1.001 1.957 2.465 2.465 2.465 1.464 1.464 0.407 1.792 ms 49.3 201

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

peer jitter 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.11 22.434 22.434 38.703 92.583 398.279 837.667 837.667 359.576 815.233 162.482 143.442 µs 2.815 11.82

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

peer jitter 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.12 32.880 32.880 38.319 141.532 651.373 869.862 869.862 613.054 836.982 224.838 240.068 µs 1.513 3.782

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

peer jitter 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.79 0.201 0.201 0.201 0.485 15.824 15.824 15.824 15.622 15.622 4.373 2.281 ms 1.101 4.751

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

peer jitter 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.80 0.221 0.221 0.221 0.429 20.148 20.148 20.148 19.926 19.926 8.642 5.727 ms 0.001304 1.388

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 318.520 318.520 318.520 490.390 525.317 525.317 525.317 206.797 206.797 90.384 444.742 µs 71.4 320.1

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.273 0.273 0.273 0.385 1.260 1.260 1.260 0.987 0.987 0.265 0.462 ms 5.002 18.13

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.236 0.236 0.236 1.504 2.019 2.019 2.019 1.783 1.783 0.648 1.225 ms 2.972 5.575

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.122 0.196 0.292 0.863 2.251 2.961 3.628 1.960 2.764 0.623 0.994 ms 3.19 9.462

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.184 0.189 0.227 0.465 0.917 1.186 1.323 0.690 0.997 0.202 0.505 µs 8.98 29.85

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 -65.018 -64.987 -64.178 -61.813 -59.250 -59.097 -59.021 4.928 5.890 1.495 -61.640 ppb -7.55e+04 3.194e+06
Local Clock Time Offset -0.919 -0.725 -0.456 0.062 0.852 1.066 1.419 1.308 1.791 0.390 0.095 µs -2.315 5.949
Local RMS Frequency Jitter 53.000 58.000 64.000 96.000 125.000 150.000 170.000 61.000 92.000 18.985 96.189 10e-12 79.91 384.1
Local RMS Time Jitter 306.000 322.000 353.000 517.000 677.000 724.000 777.000 324.000 402.000 89.891 518.498 ns 122.7 656.6
Server Jitter 162.159.200.1 164.400 164.400 164.400 627.747 880.715 880.715 880.715 716.315 716.315 223.546 527.969 µs 6.453 15.5
Server Jitter 169.229.128.134 0.101 0.101 0.101 0.405 10.325 10.325 10.325 10.224 10.224 3.662 2.207 ms 0.4655 2.309
Server Jitter 173.11.101.155 1.001 1.001 1.001 1.957 2.465 2.465 2.465 1.464 1.464 0.407 1.792 ms 49.3 201
Server Jitter 192.168.1.11 22.434 22.434 38.703 92.583 398.279 837.667 837.667 359.576 815.233 162.482 143.442 µs 2.815 11.82
Server Jitter 192.168.1.12 32.880 32.880 38.319 141.532 651.373 869.862 869.862 613.054 836.982 224.838 240.068 µs 1.513 3.782
Server Jitter 194.58.207.79 0.201 0.201 0.201 0.485 15.824 15.824 15.824 15.622 15.622 4.373 2.281 ms 1.101 4.751
Server Jitter 194.58.207.80 0.221 0.221 0.221 0.429 20.148 20.148 20.148 19.926 19.926 8.642 5.727 ms 0.001304 1.388
Server Jitter 204.17.205.24 318.520 318.520 318.520 490.390 525.317 525.317 525.317 206.797 206.797 90.384 444.742 µs 71.4 320.1
Server Jitter 216.218.192.202 0.273 0.273 0.273 0.385 1.260 1.260 1.260 0.987 0.987 0.265 0.462 ms 5.002 18.13
Server Jitter 216.218.254.202 0.236 0.236 0.236 1.504 2.019 2.019 2.019 1.783 1.783 0.648 1.225 ms 2.972 5.575
Server Jitter SHM(0) 0.122 0.196 0.292 0.863 2.251 2.961 3.628 1.960 2.764 0.623 0.994 ms 3.19 9.462
Server Jitter SHM(1) 0.184 0.189 0.227 0.465 0.917 1.186 1.323 0.690 0.997 0.202 0.505 µs 8.98 29.85
Server Offset 162.159.200.1 4.779 4.779 4.779 5.132 5.319 5.319 5.319 0.541 0.541 0.166 5.092 ms 2.616e+04 7.781e+05
Server Offset 169.229.128.134 2.291 2.291 2.291 2.455 2.545 2.545 2.545 0.254 0.254 0.066 2.456 ms 4.78e+04 1.737e+06
Server Offset 173.11.101.155 -372.525 -372.525 -372.525 -78.491 662.523 662.523 662.523 1,035.048 1,035.048 296.687 -21.985 µs -3.117 6.09
Server Offset 192.168.1.11 -137.958 -137.958 -108.666 -48.421 8.627 35.428 35.428 117.293 173.386 40.057 -46.618 µs -16.67 52.55
Server Offset 192.168.1.12 -182.622 -182.622 -169.796 -75.456 19.996 45.069 45.069 189.792 227.691 53.174 -71.746 µs -19.89 65.09
Server Offset 194.58.207.79 5.557 5.557 5.557 5.785 5.888 5.888 5.888 0.331 0.331 0.109 5.760 ms 1.403e+05 7.297e+06
Server Offset 194.58.207.80 7.013 7.013 7.013 7.637 8.048 8.048 8.048 1.036 1.036 0.263 7.628 ms 2.196e+04 6.166e+05
Server Offset 204.17.205.24 1.844 1.844 1.844 1.845 1.884 1.884 1.884 0.040 0.040 0.019 1.858 ms 9.649e+05 9.537e+07
Server Offset 216.218.192.202 2.468 2.468 2.468 2.566 2.727 2.727 2.727 0.259 0.259 0.089 2.593 ms 2.246e+04 6.353e+05
Server Offset 216.218.254.202 2.297 2.297 2.297 2.508 3.094 3.094 3.094 0.797 0.797 0.207 2.567 ms 1523 1.782e+04
Server Offset SHM(0) -56.562 -56.119 -55.639 -52.167 -48.850 -48.177 -47.045 6.789 7.941 2.256 -52.329 ms -1.423e+04 3.46e+05
Server Offset SHM(1) -0.920 -0.726 -0.457 0.063 0.853 1.067 1.420 1.310 1.793 0.391 0.095 µs -2.318 5.948
TDOP 0.610 0.610 0.620 1.020 1.230 1.240 1.240 0.610 0.630 0.245 0.897 26.9 94.75
Temp ZONE0 52.616 52.616 52.616 53.154 53.692 53.692 53.692 1.076 1.076 0.393 53.154 °C
nSats 10.000 10.000 10.000 10.000 12.000 12.000 12.000 2.000 2.000 0.854 10.733 nSat 1585 1.876e+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!