NTPsec

C-ntpsec-1-hour-stats

Report generated: Sun Sep 26 13:02:10 2021 UTC
Start Time: Sun Sep 26 12:01:42 2021 UTC
End Time: Sun Sep 26 13:02:10 2021 UTC
Report published: Sun Sep 26 06:02:16 2021 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 -829.000 -761.000 -535.000 -208.000 275.000 509.000 580.000 810.000 1,270.000 248.364 -187.319 ns -10.08 27.74
Local Clock Frequency Offset -4.974 -4.974 -4.974 -4.967 -4.964 -4.964 -4.964 0.0096 0.0103 0.0033 -4.968 ppm -3.513e+09 5.341e+12

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

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



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 104.000 107.000 116.000 158.000 215.000 276.000 297.000 99.000 169.000 32.794 161.575 ns 73.48 353.7

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 42.000 45.000 49.000 74.000 109.000 123.000 129.000 60.000 78.000 17.880 75.106 10e-12 42.97 176.8

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 -761.000 -535.000 -208.000 275.000 509.000 580.000 810.000 1,270.000 248.364 -187.319 ns -10.08 27.74

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.974 -4.967 -4.964 -4.964 -4.964 0.0096 0.0103 0.0033 -4.968 ppm -3.513e+09 5.341e+12
Temp ZONE0 57.996 57.996 57.996 58.534 59.072 59.072 59.072 1.076 1.076 0.338 58.391 °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 8.000 8.000 8.000 9.000 10.000 10.000 10.000 2.000 2.000 0.447 9.000 nSat 7052 1.36e+05
TDOP 0.650 0.650 0.660 0.780 1.070 1.140 1.140 0.410 0.490 0.106 0.814 317.6 2280

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.532 2.532 2.532 3.137 3.682 3.682 3.682 1.150 1.150 0.281 3.076 ms 1014 1.038e+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.770 -5.770 -5.770 -5.692 -5.512 -5.512 -5.512 0.259 0.259 0.069 -5.674 ms -5.701e+05 4.728e+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 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 -488.434 -488.434 -488.434 151.524 278.969 278.969 278.969 767.403 767.403 245.187 2.292 µs -4.609 11.68

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 -119.745 -116.478 49.595 224.511 328.205 328.205 340.989 447.950 91.601 56.310 µs -0.7223 4.077

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.540 8.540 8.540 8.664 8.938 8.938 8.938 0.398 0.398 0.102 8.675 ms 5.994e+05 5.055e+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.360 6.360 6.360 6.507 6.598 6.598 6.598 0.238 0.238 0.070 6.491 ms 7.667e+05 7.019e+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.524 2.812 3.148 3.148 3.148 0.623 0.623 0.165 2.826 ms 4216 6.862e+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 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.166 3.698 4.022 4.022 4.022 0.857 0.857 0.220 3.658 ms 3868 6.12e+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.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.490 2.490 2.490 2.564 2.784 2.784 2.784 0.294 0.294 0.090 2.612 ms 2.246e+04 6.352e+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 -69.116 -69.116 -69.116 -40.213 3.689 3.689 3.689 72.805 72.805 28.195 -36.068 ms -18.41 57.2

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.783 -61.574 -60.881 -53.703 -50.678 -49.121 -48.877 10.204 12.453 3.603 -55.281 ms -4413 7.293e+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 -762.000 -536.000 -209.000 276.000 510.000 581.000 812.000 1,272.000 248.954 -187.920 ns -10.09 27.73

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.363 0.363 0.363 1.274 22.822 22.822 22.822 22.459 22.459 8.323 5.674 ms 0.3073 1.838

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.218 1.695 16.360 16.360 16.360 16.142 16.142 5.017 4.379 ms 0.9242 2.645

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.326 1.175 20.219 20.219 20.219 19.893 19.893 5.282 2.748 ms 1.437 5.691

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.116 0.116 0.193 3.206 21.409 21.480 21.480 21.216 21.364 6.817 6.237 ms 0.629 2.343

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.201 7.494 16.298 16.298 16.298 16.097 16.097 5.316 6.531 ms 0.966 2.524

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.185 0.185 0.185 1.730 15.055 15.055 15.055 14.869 14.869 5.816 5.485 ms 0.3031 1.3

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.180 0.180 0.180 3.065 10.525 10.525 10.525 10.346 10.346 4.342 4.691 ms 0.6018 1.518

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.350 0.350 0.350 0.667 11.239 11.239 11.239 10.889 10.889 4.269 3.572 ms 0.3565 1.629

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.271 0.271 0.271 0.877 18.659 18.659 18.659 18.389 18.389 7.480 4.667 ms 0.1467 1.648

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 9.587 9.587 9.587 30.523 87.512 87.512 87.512 77.925 77.925 25.746 38.325 ms 2.1 4.354

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.234 0.337 0.892 2.896 5.903 7.880 2.559 5.668 1.002 1.197 ms 3.506 17.14

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 65.000 90.000 192.000 454.000 619.000 720.000 364.000 554.000 124.768 228.858 ns 4.246 12.79

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.974 -4.967 -4.964 -4.964 -4.964 0.0096 0.0103 0.0033 -4.968 ppm -3.513e+09 5.341e+12
Local Clock Time Offset -829.000 -761.000 -535.000 -208.000 275.000 509.000 580.000 810.000 1,270.000 248.364 -187.319 ns -10.08 27.74
Local RMS Frequency Jitter 42.000 45.000 49.000 74.000 109.000 123.000 129.000 60.000 78.000 17.880 75.106 10e-12 42.97 176.8
Local RMS Time Jitter 104.000 107.000 116.000 158.000 215.000 276.000 297.000 99.000 169.000 32.794 161.575 ns 73.48 353.7
Server Jitter 162.159.200.123 0.363 0.363 0.363 1.274 22.822 22.822 22.822 22.459 22.459 8.323 5.674 ms 0.3073 1.838
Server Jitter 169.229.128.134 0.218 0.218 0.218 1.695 16.360 16.360 16.360 16.142 16.142 5.017 4.379 ms 0.9242 2.645
Server Jitter 173.11.101.155 0.326 0.326 0.326 1.175 20.219 20.219 20.219 19.893 19.893 5.282 2.748 ms 1.437 5.691
Server Jitter 192.168.1.10 0.116 0.116 0.193 3.206 21.409 21.480 21.480 21.216 21.364 6.817 6.237 ms 0.629 2.343
Server Jitter 194.58.202.211 0.201 0.201 0.201 7.494 16.298 16.298 16.298 16.097 16.097 5.316 6.531 ms 0.966 2.524
Server Jitter 194.58.202.219 0.185 0.185 0.185 1.730 15.055 15.055 15.055 14.869 14.869 5.816 5.485 ms 0.3031 1.3
Server Jitter 203.123.48.219 0.180 0.180 0.180 3.065 10.525 10.525 10.525 10.346 10.346 4.342 4.691 ms 0.6018 1.518
Server Jitter 204.17.205.24 0.350 0.350 0.350 0.667 11.239 11.239 11.239 10.889 10.889 4.269 3.572 ms 0.3565 1.629
Server Jitter 216.218.254.202 0.271 0.271 0.271 0.877 18.659 18.659 18.659 18.389 18.389 7.480 4.667 ms 0.1467 1.648
Server Jitter 63.145.169.3 9.587 9.587 9.587 30.523 87.512 87.512 87.512 77.925 77.925 25.746 38.325 ms 2.1 4.354
Server Jitter SHM(0) 0.133 0.234 0.337 0.892 2.896 5.903 7.880 2.559 5.668 1.002 1.197 ms 3.506 17.14
Server Jitter SHM(1) 53.000 65.000 90.000 192.000 454.000 619.000 720.000 364.000 554.000 124.768 228.858 ns 4.246 12.79
Server Offset 162.159.200.123 2.532 2.532 2.532 3.137 3.682 3.682 3.682 1.150 1.150 0.281 3.076 ms 1014 1.038e+04
Server Offset 169.229.128.134 -5.770 -5.770 -5.770 -5.692 -5.512 -5.512 -5.512 0.259 0.259 0.069 -5.674 ms -5.701e+05 4.728e+07
Server Offset 173.11.101.155 -488.434 -488.434 -488.434 151.524 278.969 278.969 278.969 767.403 767.403 245.187 2.292 µs -4.609 11.68
Server Offset 192.168.1.10 -119.745 -119.745 -116.478 49.595 224.511 328.205 328.205 340.989 447.950 91.601 56.310 µs -0.7223 4.077
Server Offset 194.58.202.211 8.540 8.540 8.540 8.664 8.938 8.938 8.938 0.398 0.398 0.102 8.675 ms 5.994e+05 5.055e+07
Server Offset 194.58.202.219 6.360 6.360 6.360 6.507 6.598 6.598 6.598 0.238 0.238 0.070 6.491 ms 7.667e+05 7.019e+07
Server Offset 203.123.48.219 2.524 2.524 2.524 2.812 3.148 3.148 3.148 0.623 0.623 0.165 2.826 ms 4216 6.862e+04
Server Offset 204.17.205.24 3.166 3.166 3.166 3.698 4.022 4.022 4.022 0.857 0.857 0.220 3.658 ms 3868 6.12e+04
Server Offset 216.218.254.202 2.490 2.490 2.490 2.564 2.784 2.784 2.784 0.294 0.294 0.090 2.612 ms 2.246e+04 6.352e+05
Server Offset 63.145.169.3 -69.116 -69.116 -69.116 -40.213 3.689 3.689 3.689 72.805 72.805 28.195 -36.068 ms -18.41 57.2
Server Offset SHM(0) -61.783 -61.574 -60.881 -53.703 -50.678 -49.121 -48.877 10.204 12.453 3.603 -55.281 ms -4413 7.293e+04
Server Offset SHM(1) -830.000 -762.000 -536.000 -209.000 276.000 510.000 581.000 812.000 1,272.000 248.954 -187.920 ns -10.09 27.73
TDOP 0.650 0.650 0.660 0.780 1.070 1.140 1.140 0.410 0.490 0.106 0.814 317.6 2280
Temp ZONE0 57.996 57.996 57.996 58.534 59.072 59.072 59.072 1.076 1.076 0.338 58.391 °C
nSats 8.000 8.000 8.000 9.000 10.000 10.000 10.000 2.000 2.000 0.447 9.000 nSat 7052 1.36e+05
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!