NTPsec

C-ntpsec-3-hour-stats

Report generated: Fri May 29 08:01:31 2020 UTC
Start Time: Fri May 29 05:01:31 2020 UTC
End Time: Fri May 29 08:01:31 2020 UTC
Report published: Fri May 29 01:01:35 2020 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 -0.221 -0.075 0.082 0.479 0.901 1.033 1.212 0.819 1.108 0.247 0.480 µs 3.732 9.098
Local Clock Frequency Offset -5.405 -5.405 -5.400 -5.350 -5.310 -5.309 -5.309 0.090 0.095 0.028 -5.351 ppm -6.922e+06 1.319e+09

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 102.000 113.000 134.000 191.000 262.000 306.000 337.000 128.000 193.000 39.423 193.168 ns 71.54 334.3

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

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

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 46.000 52.000 74.000 142.000 246.000 275.000 314.000 172.000 223.000 50.951 147.534 10e-12 13.1 42.13

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.221 -0.075 0.082 0.479 0.901 1.033 1.212 0.819 1.108 0.247 0.480 µs 3.732 9.098

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.405 -5.405 -5.400 -5.350 -5.310 -5.309 -5.309 0.090 0.095 0.028 -5.351 ppm -6.922e+06 1.319e+09
Temp ZONE0 64.990 64.990 65.528 66.066 66.604 67.142 67.142 1.076 2.152 0.550 66.054 °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 9.000 11.000 12.000 12.000 13.000 3.000 4.000 1.037 10.609 nSat 812.9 7751
TDOP 0.550 0.600 0.620 0.730 1.150 1.450 1.480 0.530 0.850 0.195 0.807 41.91 178

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 1.117 1.117 1.344 1.859 2.470 2.577 2.577 1.125 1.460 0.329 1.849 ms 113.3 594.5

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 0.046 0.046 0.939 1.580 2.156 2.382 2.382 1.217 2.337 0.424 1.562 ms 26.62 91.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 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 0.627 0.627 2.449 2.706 3.125 3.401 3.401 0.676 2.774 0.402 2.696 ms 200.1 1201

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 -0.854 -0.854 -0.645 0.282 0.877 1.340 1.340 1.521 2.194 0.466 0.243 ms -1.735 4.733

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 -7.191 -7.191 -7.191 4.582 13.056 13.056 13.056 20.247 20.247 6.460 4.576 ms -1.214 2.889

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 -131.680 -102.859 -30.069 52.874 156.080 207.311 225.148 186.149 310.170 51.607 56.091 µs 0.4494 4.853

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.831 2.831 2.835 3.387 4.193 4.674 4.674 1.358 1.843 0.378 3.419 ms 547.9 4638

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 0.376 0.376 1.377 1.969 2.466 2.514 2.514 1.088 2.138 0.363 1.935 ms 92.16 440.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 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 0.948 0.948 2.406 3.201 4.254 4.305 4.305 1.848 3.357 0.603 3.169 ms 88.84 426.1

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) -67.027 -66.819 -64.721 -58.552 -53.010 -51.539 -51.349 11.711 15.280 3.920 -58.495 ms -4085 6.581e+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) -0.222 -0.076 0.083 0.480 0.902 1.034 1.213 0.819 1.110 0.247 0.481 µs 3.746 9.138

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

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

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

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



Server 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.363 0.363 0.411 2.769 11.434 11.669 11.669 11.023 11.306 3.116 3.980 ms 2.046 5.266

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.419 0.419 0.549 2.802 10.128 10.160 10.160 9.580 9.741 2.603 3.452 ms 2.165 5.858

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.535 0.535 0.912 1.787 7.247 10.442 10.442 6.335 9.907 2.064 2.631 ms 2.766 9.351

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.383 0.383 0.468 2.329 8.962 9.016 9.016 8.494 8.633 2.101 2.888 ms 2.675 7.874

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 5.906 5.906 5.906 8.415 13.729 13.729 13.729 7.824 7.824 2.636 9.180 ms 23.24 81.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.



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.014 0.028 0.056 0.153 8.684 8.721 9.306 8.627 8.693 2.433 1.122 ms 0.7091 4.137

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.376 0.376 0.534 3.921 12.638 12.666 12.666 12.105 12.290 4.018 4.781 ms 1.516 3.45

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.197 0.197 0.502 2.722 11.278 11.489 11.489 10.776 11.292 3.304 4.021 ms 1.637 3.899

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.678 0.678 0.967 5.361 11.010 11.047 11.047 10.043 10.369 3.468 5.691 ms 2.368 4.656

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.405 0.432 0.683 2.416 7.390 9.314 9.416 6.707 8.881 2.078 3.033 ms 2.589 7.036

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) 62.000 75.000 104.000 215.000 427.000 576.000 771.000 323.000 501.000 104.547 234.984 ns 6.963 23.67

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.405 -5.405 -5.400 -5.350 -5.310 -5.309 -5.309 0.090 0.095 0.028 -5.351 ppm -6.922e+06 1.319e+09
Local Clock Time Offset -0.221 -0.075 0.082 0.479 0.901 1.033 1.212 0.819 1.108 0.247 0.480 µs 3.732 9.098
Local RMS Frequency Jitter 46.000 52.000 74.000 142.000 246.000 275.000 314.000 172.000 223.000 50.951 147.534 10e-12 13.1 42.13
Local RMS Time Jitter 102.000 113.000 134.000 191.000 262.000 306.000 337.000 128.000 193.000 39.423 193.168 ns 71.54 334.3
Server Jitter 104.131.155.175 0.363 0.363 0.411 2.769 11.434 11.669 11.669 11.023 11.306 3.116 3.980 ms 2.046 5.266
Server Jitter 162.159.200.1 0.419 0.419 0.549 2.802 10.128 10.160 10.160 9.580 9.741 2.603 3.452 ms 2.165 5.858
Server Jitter 164.67.62.194 0.535 0.535 0.912 1.787 7.247 10.442 10.442 6.335 9.907 2.064 2.631 ms 2.766 9.351
Server Jitter 173.11.101.155 0.383 0.383 0.468 2.329 8.962 9.016 9.016 8.494 8.633 2.101 2.888 ms 2.675 7.874
Server Jitter 178.62.68.79 5.906 5.906 5.906 8.415 13.729 13.729 13.729 7.824 7.824 2.636 9.180 ms 23.24 81.79
Server Jitter 192.168.1.10 0.014 0.028 0.056 0.153 8.684 8.721 9.306 8.627 8.693 2.433 1.122 ms 0.7091 4.137
Server Jitter 203.123.48.219 0.376 0.376 0.534 3.921 12.638 12.666 12.666 12.105 12.290 4.018 4.781 ms 1.516 3.45
Server Jitter 204.17.205.24 0.197 0.197 0.502 2.722 11.278 11.489 11.489 10.776 11.292 3.304 4.021 ms 1.637 3.899
Server Jitter 47.51.249.154 0.678 0.678 0.967 5.361 11.010 11.047 11.047 10.043 10.369 3.468 5.691 ms 2.368 4.656
Server Jitter SHM(0) 0.405 0.432 0.683 2.416 7.390 9.314 9.416 6.707 8.881 2.078 3.033 ms 2.589 7.036
Server Jitter SHM(1) 62.000 75.000 104.000 215.000 427.000 576.000 771.000 323.000 501.000 104.547 234.984 ns 6.963 23.67
Server Offset 104.131.155.175 1.117 1.117 1.344 1.859 2.470 2.577 2.577 1.125 1.460 0.329 1.849 ms 113.3 594.5
Server Offset 162.159.200.1 0.046 0.046 0.939 1.580 2.156 2.382 2.382 1.217 2.337 0.424 1.562 ms 26.62 91.55
Server Offset 164.67.62.194 0.627 0.627 2.449 2.706 3.125 3.401 3.401 0.676 2.774 0.402 2.696 ms 200.1 1201
Server Offset 173.11.101.155 -0.854 -0.854 -0.645 0.282 0.877 1.340 1.340 1.521 2.194 0.466 0.243 ms -1.735 4.733
Server Offset 178.62.68.79 -7.191 -7.191 -7.191 4.582 13.056 13.056 13.056 20.247 20.247 6.460 4.576 ms -1.214 2.889
Server Offset 192.168.1.10 -131.680 -102.859 -30.069 52.874 156.080 207.311 225.148 186.149 310.170 51.607 56.091 µs 0.4494 4.853
Server Offset 203.123.48.219 2.831 2.831 2.835 3.387 4.193 4.674 4.674 1.358 1.843 0.378 3.419 ms 547.9 4638
Server Offset 204.17.205.24 0.376 0.376 1.377 1.969 2.466 2.514 2.514 1.088 2.138 0.363 1.935 ms 92.16 440.2
Server Offset 47.51.249.154 0.948 0.948 2.406 3.201 4.254 4.305 4.305 1.848 3.357 0.603 3.169 ms 88.84 426.1
Server Offset SHM(0) -67.027 -66.819 -64.721 -58.552 -53.010 -51.539 -51.349 11.711 15.280 3.920 -58.495 ms -4085 6.581e+04
Server Offset SHM(1) -0.222 -0.076 0.083 0.480 0.902 1.034 1.213 0.819 1.110 0.247 0.481 µs 3.746 9.138
TDOP 0.550 0.600 0.620 0.730 1.150 1.450 1.480 0.530 0.850 0.195 0.807 41.91 178
Temp ZONE0 64.990 64.990 65.528 66.066 66.604 67.142 67.142 1.076 2.152 0.550 66.054 °C
nSats 8.000 8.000 9.000 11.000 12.000 12.000 13.000 3.000 4.000 1.037 10.609 nSat 812.9 7751
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!