NTPsec

c-ntpsec-14-day-stats

Report generated: Fri May 29 06:12:59 2020 UTC
Start Time: Fri May 15 06:12:54 2020 UTC
End Time: Fri May 29 06:12:54 2020 UTC
Report published: Thu May 28 23:13:24 2020 PDT
Report Period: 14.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 -1,865.000 -848.000 -575.000 -9.000 588.000 884.000 1,731.000 1,163.000 1,732.000 349.228 -3.160 ns -3.964 10.27
Local Clock Frequency Offset -5.747 -5.709 -5.582 -5.324 -5.290 -5.288 -5.285 0.292 0.421 0.090 -5.357 ppm -2.205e+05 1.333e+07

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 72.000 106.000 123.000 180.000 266.000 319.000 676.000 143.000 213.000 44.885 185.465 ns 41.11 173.1

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

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

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 21.000 30.000 36.000 63.000 189.000 275.000 494.000 153.000 245.000 50.792 80.823 10e-12 4.12 15.84

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 -1,865.000 -848.000 -575.000 -9.000 588.000 884.000 1,731.000 1,163.000 1,732.000 349.228 -3.160 ns -3.964 10.27

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 -5.747 -5.709 -5.582 -5.324 -5.290 -5.288 -5.285 0.292 0.421 0.090 -5.357 ppm -2.205e+05 1.333e+07
Temp ZONE0 61.762 62.838 63.376 65.528 68.756 69.832 70.908 5.380 6.994 1.637 65.463 °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 6.000 7.000 8.000 10.000 12.000 12.000 13.000 4.000 5.000 1.207 9.675 nSat 366.6 2726
TDOP 0.530 0.550 0.600 0.810 1.220 1.580 2.180 0.620 1.030 0.211 0.853 38.13 158

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 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 -49.239 1.224 1.642 2.535 3.508 3.913 588.588 1.866 2.688 11.070 2.653 ms 48.14 2548

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.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 -60.421 -4.842 0.066 1.652 2.758 4.366 6.824 2.692 9.208 2.264 1.465 ms -17.56 401

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 164.67.62.194

peer offset 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 164.67.62.194 -46.481 2.022 2.333 2.684 3.135 3.487 7.823 0.802 1.464 1.499 2.647 ms -24.54 729.8

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 -62.054 -1.547 -0.608 0.224 0.972 1.549 26.284 1.580 3.096 1.570 0.180 ms -25.5 945.8

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 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 -16.339 -10.199 -4.937 4.308 11.921 15.162 35.235 16.858 25.361 4.885 3.926 ms -0.8335 5.66

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 -288.893 -81.289 -24.363 38.413 111.043 157.153 389.957 135.406 238.442 45.987 39.598 µs -0.5981 6.432

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 -58.523 -5.472 -0.111 3.929 26.657 31.382 51.426 26.768 36.854 7.209 5.235 ms 1.476 11.7

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 -12.959 1.705 2.031 2.449 3.120 5.277 9.609 1.088 3.572 0.908 2.520 ms 4.909 119.7

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 -54.265 1.253 1.479 1.915 2.419 2.742 5.176 0.940 1.489 1.439 1.885 ms -30.94 1096

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 47.51.249.154

peer offset 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 47.51.249.154 -47.258 0.506 1.498 3.198 4.277 5.126 7.827 2.779 4.620 1.570 3.073 ms -16.64 531.6

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) -72.471 -66.819 -63.996 -55.792 -47.054 -45.130 -42.830 16.942 21.690 5.076 -55.694 ms -1752 2.142e+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) -1,866.000 -849.000 -576.000 -10.000 589.000 885.000 1,732.000 1,165.000 1,734.000 349.972 -3.184 ns -3.965 10.26

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 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.000 0.053 0.373 1.821 11.251 22.343 198.591 10.878 22.290 7.132 3.863 ms 10.51 225

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.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.000 0.224 0.387 1.984 10.422 20.265 180.758 10.035 20.040 6.843 3.872 ms 12.31 272.4

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 164.67.62.194

peer jitter 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 164.67.62.194 0.000 0.227 0.409 2.059 11.706 22.787 271.498 11.297 22.561 10.180 4.389 ms 14.16 313.4

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.437 0.784 2.368 13.006 32.646 334.336 12.222 32.209 10.813 4.897 ms 16.63 454.9

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 178.62.68.79

peer jitter 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.62.68.79 0.000 0.000 0.494 3.345 12.421 40.950 81.708 11.927 40.950 7.545 5.068 ms 5.709 52.54

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.000 0.024 0.045 0.155 8.720 13.299 245.955 8.675 13.275 5.484 1.729 ms 23.89 982

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.000 0.279 0.529 2.633 14.453 26.212 223.129 13.924 25.934 7.784 5.029 ms 12.46 324.6

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.591 9.623 18.921 88.402 9.623 18.921 7.575 3.313 ms 6.959 76.4

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.000 0.246 0.409 1.936 11.929 22.441 211.374 11.521 22.196 6.486 4.053 ms 10.93 282.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 47.51.249.154

peer jitter 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 47.51.249.154 0.000 0.594 1.190 3.563 13.013 39.333 316.521 11.823 38.738 14.744 6.082 ms 11.45 185.8

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.089 0.297 0.533 2.373 6.760 8.481 13.389 6.228 8.184 2.017 2.891 ms 2.296 6.025

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) 22.000 73.000 100.000 206.000 443.000 575.000 1,078.000 343.000 502.000 108.563 229.999 ns 6.017 19.93

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 -5.747 -5.709 -5.582 -5.324 -5.290 -5.288 -5.285 0.292 0.421 0.090 -5.357 ppm -2.205e+05 1.333e+07
Local Clock Time Offset -1,865.000 -848.000 -575.000 -9.000 588.000 884.000 1,731.000 1,163.000 1,732.000 349.228 -3.160 ns -3.964 10.27
Local RMS Frequency Jitter 21.000 30.000 36.000 63.000 189.000 275.000 494.000 153.000 245.000 50.792 80.823 10e-12 4.12 15.84
Local RMS Time Jitter 72.000 106.000 123.000 180.000 266.000 319.000 676.000 143.000 213.000 44.885 185.465 ns 41.11 173.1
Server Jitter 104.131.155.175 0.000 0.053 0.373 1.821 11.251 22.343 198.591 10.878 22.290 7.132 3.863 ms 10.51 225
Server Jitter 162.159.200.1 0.000 0.224 0.387 1.984 10.422 20.265 180.758 10.035 20.040 6.843 3.872 ms 12.31 272.4
Server Jitter 164.67.62.194 0.000 0.227 0.409 2.059 11.706 22.787 271.498 11.297 22.561 10.180 4.389 ms 14.16 313.4
Server Jitter 173.11.101.155 0.000 0.437 0.784 2.368 13.006 32.646 334.336 12.222 32.209 10.813 4.897 ms 16.63 454.9
Server Jitter 178.62.68.79 0.000 0.000 0.494 3.345 12.421 40.950 81.708 11.927 40.950 7.545 5.068 ms 5.709 52.54
Server Jitter 192.168.1.10 0.000 0.024 0.045 0.155 8.720 13.299 245.955 8.675 13.275 5.484 1.729 ms 23.89 982
Server Jitter 203.123.48.219 0.000 0.279 0.529 2.633 14.453 26.212 223.129 13.924 25.934 7.784 5.029 ms 12.46 324.6
Server Jitter 204.123.2.5 0.000 0.000 0.000 1.591 9.623 18.921 88.402 9.623 18.921 7.575 3.313 ms 6.959 76.4
Server Jitter 204.17.205.24 0.000 0.246 0.409 1.936 11.929 22.441 211.374 11.521 22.196 6.486 4.053 ms 10.93 282.3
Server Jitter 47.51.249.154 0.000 0.594 1.190 3.563 13.013 39.333 316.521 11.823 38.738 14.744 6.082 ms 11.45 185.8
Server Jitter SHM(0) 0.089 0.297 0.533 2.373 6.760 8.481 13.389 6.228 8.184 2.017 2.891 ms 2.296 6.025
Server Jitter SHM(1) 22.000 73.000 100.000 206.000 443.000 575.000 1,078.000 343.000 502.000 108.563 229.999 ns 6.017 19.93
Server Offset 104.131.155.175 -49.239 1.224 1.642 2.535 3.508 3.913 588.588 1.866 2.688 11.070 2.653 ms 48.14 2548
Server Offset 162.159.200.1 -60.421 -4.842 0.066 1.652 2.758 4.366 6.824 2.692 9.208 2.264 1.465 ms -17.56 401
Server Offset 164.67.62.194 -46.481 2.022 2.333 2.684 3.135 3.487 7.823 0.802 1.464 1.499 2.647 ms -24.54 729.8
Server Offset 173.11.101.155 -62.054 -1.547 -0.608 0.224 0.972 1.549 26.284 1.580 3.096 1.570 0.180 ms -25.5 945.8
Server Offset 178.62.68.79 -16.339 -10.199 -4.937 4.308 11.921 15.162 35.235 16.858 25.361 4.885 3.926 ms -0.8335 5.66
Server Offset 192.168.1.10 -288.893 -81.289 -24.363 38.413 111.043 157.153 389.957 135.406 238.442 45.987 39.598 µs -0.5981 6.432
Server Offset 203.123.48.219 -58.523 -5.472 -0.111 3.929 26.657 31.382 51.426 26.768 36.854 7.209 5.235 ms 1.476 11.7
Server Offset 204.123.2.5 -12.959 1.705 2.031 2.449 3.120 5.277 9.609 1.088 3.572 0.908 2.520 ms 4.909 119.7
Server Offset 204.17.205.24 -54.265 1.253 1.479 1.915 2.419 2.742 5.176 0.940 1.489 1.439 1.885 ms -30.94 1096
Server Offset 47.51.249.154 -47.258 0.506 1.498 3.198 4.277 5.126 7.827 2.779 4.620 1.570 3.073 ms -16.64 531.6
Server Offset SHM(0) -72.471 -66.819 -63.996 -55.792 -47.054 -45.130 -42.830 16.942 21.690 5.076 -55.694 ms -1752 2.142e+04
Server Offset SHM(1) -1,866.000 -849.000 -576.000 -10.000 589.000 885.000 1,732.000 1,165.000 1,734.000 349.972 -3.184 ns -3.965 10.26
TDOP 0.530 0.550 0.600 0.810 1.220 1.580 2.180 0.620 1.030 0.211 0.853 38.13 158
Temp ZONE0 61.762 62.838 63.376 65.528 68.756 69.832 70.908 5.380 6.994 1.637 65.463 °C
nSats 6.000 7.000 8.000 10.000 12.000 12.000 13.000 4.000 5.000 1.207 9.675 nSat 366.6 2726
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!