NTPsec

C-ntpsec-3-hour-stats

Report generated: Tue Jun 15 17:01:17 2021 UTC
Start Time: Tue Jun 15 14:01:17 2021 UTC
End Time: Tue Jun 15 17:01:17 2021 UTC
Report published: Tue Jun 15 10:01:23 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 -1,203.000 -990.000 -791.000 -270.000 336.000 597.000 822.000 1,127.000 1,587.000 336.553 -265.591 ns -10.87 30.87
Local Clock Frequency Offset -5.094 -5.094 -5.094 -5.077 -5.052 -5.048 -5.047 0.042 0.046 0.0139 -5.077 ppm -4.96e+07 1.822e+10

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 112.000 123.000 134.000 193.000 292.000 337.000 362.000 158.000 214.000 47.024 198.301 ns 43.73 182.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 23.000 26.000 39.000 95.000 178.000 225.000 267.000 139.000 199.000 43.899 102.003 10e-12 6.988 20.61

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,203.000 -990.000 -791.000 -270.000 336.000 597.000 822.000 1,127.000 1,587.000 336.553 -265.591 ns -10.87 30.87

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.094 -5.094 -5.094 -5.077 -5.052 -5.048 -5.047 0.042 0.046 0.0139 -5.077 ppm -4.96e+07 1.822e+10
Temp ZONE0 57.458 57.458 57.458 57.996 58.534 59.072 59.072 1.076 1.614 0.232 58.026 °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 9.000 10.000 10.000 12.000 12.000 12.000 2.000 3.000 0.879 10.600 nSat 1384 1.568e+04
TDOP 0.600 0.600 0.650 0.900 1.060 1.110 1.470 0.410 0.510 0.160 0.870 99.78 502.8

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 2.210 2.210 2.210 2.548 3.053 3.053 3.053 0.843 0.843 0.285 2.540 ms 517.8 4293

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

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

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

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



Server Offset 162.159.200.123

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 2.332 2.332 2.417 2.715 3.047 3.187 3.187 0.630 0.856 0.195 2.726 ms 2242 2.97e+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 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 -1.092 -1.092 -1.069 0.215 0.557 0.652 0.652 1.626 1.744 0.440 0.061 ms -4.47 12.97

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

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

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

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



Server Offset 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 502.072 502.072 502.072 626.880 765.265 765.265 765.265 263.193 263.193 90.051 617.106 µs 218.3 1386

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 71.965 92.392 107.347 167.570 265.191 366.808 371.659 157.844 274.416 48.074 172.795 µs 26.35 102.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 194.58.202.211

peer offset 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.211 3.496 3.496 3.571 3.838 4.115 4.307 4.307 0.544 0.811 0.169 3.831 ms 1.016e+04 2.209e+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 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 3.455 3.455 3.461 3.750 4.099 4.107 4.107 0.638 0.653 0.156 3.770 ms 1.256e+04 2.93e+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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 -1.379 -1.379 4.158 4.906 5.285 5.395 5.395 1.127 6.773 1.153 4.715 ms 33.89 113.9

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

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

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

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



Server Offset 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 1.949 1.949 1.949 2.225 2.529 2.529 2.529 0.579 0.579 0.149 2.211 ms 2697 3.793e+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) -66.650 -65.896 -64.148 -57.881 -50.381 -47.883 -46.915 13.767 18.013 4.338 -57.280 ms -2908 4.19e+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,204.000 -991.000 -792.000 -271.000 337.000 598.000 823.000 1,129.000 1,589.000 337.123 -266.172 ns -10.87 30.86

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.323 0.323 0.323 1.005 9.184 9.184 9.184 8.861 8.861 3.487 3.351 ms 0.4914 1.439

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.123

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.206 0.206 0.272 0.707 9.620 12.594 12.594 9.349 12.388 3.511 2.248 ms 0.7655 3.2

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.616 0.616 0.673 1.777 11.434 11.862 11.862 10.762 11.246 3.011 3.040 ms 1.734 4.986

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.276 0.276 0.276 8.579 10.636 10.636 10.636 10.360 10.360 3.939 6.979 ms 1.8 3.144

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.040 0.051 0.072 0.172 8.699 8.929 8.943 8.627 8.879 2.735 1.572 ms 0.4072 2.711

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.173 0.173 0.234 0.948 8.867 11.024 11.024 8.632 10.852 2.940 2.481 ms 0.9753 3.183

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.198 0.198 0.245 1.063 12.038 12.170 12.170 11.793 11.971 3.337 2.784 ms 0.9441 3.205

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.194 0.194 0.204 0.746 7.221 13.254 13.254 7.017 13.060 2.852 2.099 ms 1.547 6.561

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.278 0.278 0.278 1.566 8.764 8.764 8.764 8.485 8.485 2.983 2.976 ms 1.333 2.913

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.144 0.206 0.314 0.951 3.313 6.023 7.492 3.000 5.816 1.068 1.253 ms 3.051 12.97

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) 64.000 85.000 111.000 236.000 556.000 693.000 905.000 445.000 608.000 137.990 269.801 ns 4.989 15.77

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.094 -5.094 -5.094 -5.077 -5.052 -5.048 -5.047 0.042 0.046 0.0139 -5.077 ppm -4.96e+07 1.822e+10
Local Clock Time Offset -1,203.000 -990.000 -791.000 -270.000 336.000 597.000 822.000 1,127.000 1,587.000 336.553 -265.591 ns -10.87 30.87
Local RMS Frequency Jitter 23.000 26.000 39.000 95.000 178.000 225.000 267.000 139.000 199.000 43.899 102.003 10e-12 6.988 20.61
Local RMS Time Jitter 112.000 123.000 134.000 193.000 292.000 337.000 362.000 158.000 214.000 47.024 198.301 ns 43.73 182.7
Server Jitter 104.131.155.175 0.323 0.323 0.323 1.005 9.184 9.184 9.184 8.861 8.861 3.487 3.351 ms 0.4914 1.439
Server Jitter 162.159.200.123 0.206 0.206 0.272 0.707 9.620 12.594 12.594 9.349 12.388 3.511 2.248 ms 0.7655 3.2
Server Jitter 173.11.101.155 0.616 0.616 0.673 1.777 11.434 11.862 11.862 10.762 11.246 3.011 3.040 ms 1.734 4.986
Server Jitter 178.62.68.79 0.276 0.276 0.276 8.579 10.636 10.636 10.636 10.360 10.360 3.939 6.979 ms 1.8 3.144
Server Jitter 192.168.1.10 0.040 0.051 0.072 0.172 8.699 8.929 8.943 8.627 8.879 2.735 1.572 ms 0.4072 2.711
Server Jitter 194.58.202.211 0.173 0.173 0.234 0.948 8.867 11.024 11.024 8.632 10.852 2.940 2.481 ms 0.9753 3.183
Server Jitter 194.58.202.219 0.198 0.198 0.245 1.063 12.038 12.170 12.170 11.793 11.971 3.337 2.784 ms 0.9441 3.205
Server Jitter 203.123.48.219 0.194 0.194 0.204 0.746 7.221 13.254 13.254 7.017 13.060 2.852 2.099 ms 1.547 6.561
Server Jitter 204.123.2.5 0.278 0.278 0.278 1.566 8.764 8.764 8.764 8.485 8.485 2.983 2.976 ms 1.333 2.913
Server Jitter SHM(0) 0.144 0.206 0.314 0.951 3.313 6.023 7.492 3.000 5.816 1.068 1.253 ms 3.051 12.97
Server Jitter SHM(1) 64.000 85.000 111.000 236.000 556.000 693.000 905.000 445.000 608.000 137.990 269.801 ns 4.989 15.77
Server Offset 104.131.155.175 2.210 2.210 2.210 2.548 3.053 3.053 3.053 0.843 0.843 0.285 2.540 ms 517.8 4293
Server Offset 162.159.200.123 2.332 2.332 2.417 2.715 3.047 3.187 3.187 0.630 0.856 0.195 2.726 ms 2242 2.97e+04
Server Offset 173.11.101.155 -1.092 -1.092 -1.069 0.215 0.557 0.652 0.652 1.626 1.744 0.440 0.061 ms -4.47 12.97
Server Offset 178.62.68.79 502.072 502.072 502.072 626.880 765.265 765.265 765.265 263.193 263.193 90.051 617.106 µs 218.3 1386
Server Offset 192.168.1.10 71.965 92.392 107.347 167.570 265.191 366.808 371.659 157.844 274.416 48.074 172.795 µs 26.35 102.7
Server Offset 194.58.202.211 3.496 3.496 3.571 3.838 4.115 4.307 4.307 0.544 0.811 0.169 3.831 ms 1.016e+04 2.209e+05
Server Offset 194.58.202.219 3.455 3.455 3.461 3.750 4.099 4.107 4.107 0.638 0.653 0.156 3.770 ms 1.256e+04 2.93e+05
Server Offset 203.123.48.219 -1.379 -1.379 4.158 4.906 5.285 5.395 5.395 1.127 6.773 1.153 4.715 ms 33.89 113.9
Server Offset 204.123.2.5 1.949 1.949 1.949 2.225 2.529 2.529 2.529 0.579 0.579 0.149 2.211 ms 2697 3.793e+04
Server Offset SHM(0) -66.650 -65.896 -64.148 -57.881 -50.381 -47.883 -46.915 13.767 18.013 4.338 -57.280 ms -2908 4.19e+04
Server Offset SHM(1) -1,204.000 -991.000 -792.000 -271.000 337.000 598.000 823.000 1,129.000 1,589.000 337.123 -266.172 ns -10.87 30.86
TDOP 0.600 0.600 0.650 0.900 1.060 1.110 1.470 0.410 0.510 0.160 0.870 99.78 502.8
Temp ZONE0 57.458 57.458 57.458 57.996 58.534 59.072 59.072 1.076 1.614 0.232 58.026 °C
nSats 8.000 9.000 10.000 10.000 12.000 12.000 12.000 2.000 3.000 0.879 10.600 nSat 1384 1.568e+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!