NTPsec

B-ntpsec-24-hour-stats

Report generated: Mon Sep 16 01:04:12 2019 UTC
Start Time: Sun Sep 15 01:04:09 2019 UTC
End Time: Mon Sep 16 01:04:09 2019 UTC
Report published: Sun Sep 15 18:04:34 2019 PDT
Report Period: 1.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 -956.000 -612.000 -409.000 25.000 428.000 578.000 813.000 837.000 1,190.000 252.986 20.572 ns -3.698 9.354
Local Clock Frequency Offset -5.731 -5.730 -5.729 -5.659 -5.636 -5.635 -5.634 0.093 0.095 0.035 -5.673 ppm -4.399e+06 7.208e+08

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 107.000 124.000 144.000 208.000 331.000 393.000 496.000 187.000 269.000 57.883 218.500 ns 30.69 120.8

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 24.000 29.000 33.000 54.000 101.000 121.000 137.000 68.000 92.000 20.831 59.081 10e-12 12.68 42.39

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 -956.000 -612.000 -409.000 25.000 428.000 578.000 813.000 837.000 1,190.000 252.986 20.572 ns -3.698 9.354

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.731 -5.730 -5.729 -5.659 -5.636 -5.635 -5.634 0.093 0.095 0.035 -5.673 ppm -4.399e+06 7.208e+08
Temp ZONE0 55.844 55.844 56.382 57.996 59.610 60.148 60.148 3.228 4.304 1.105 58.004 °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 7.000 9.000 12.000 12.000 12.000 5.000 5.000 1.417 9.395 nSat 195.2 1196
TDOP 0.550 0.570 0.610 0.850 1.450 1.700 2.500 0.840 1.130 0.267 0.913 22.84 88.76

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. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



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 -19.940 -19.940 0.743 3.159 4.807 5.711 5.711 4.064 25.652 3.906 2.315 ms -5.722 32.34

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

peer offset 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.213.2.253 1.231 1.742 1.883 2.233 2.623 2.917 2.973 0.740 1.175 0.227 2.239 ms 717.3 6579

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 1.872 2.016 2.116 2.360 2.707 3.094 3.681 0.591 1.078 0.206 2.384 ms 1221 1.333e+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 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 -5.556 -5.556 -2.859 2.911 6.500 7.935 7.935 9.359 13.491 2.688 2.650 ms -0.837 3.887

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 -65.337 -8.999 14.898 51.111 84.260 107.066 226.166 69.362 116.065 23.201 50.826 µs 5.297 17.21

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 -0.706 -0.645 -0.304 0.089 7.094 7.452 8.493 7.398 8.097 3.306 2.392 ms -0.2322 1.189

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.099 1.193 1.367 1.701 2.115 2.496 3.436 0.748 1.303 0.284 1.726 ms 147.1 851.4

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

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

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

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



Server Offset 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 -0.428 1.894 2.162 2.460 2.872 3.289 3.641 0.710 1.394 0.299 2.469 ms 399.2 3022

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 76.14.161.109

peer offset 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 76.14.161.109 -4.877 -2.818 -1.839 -0.693 0.643 2.015 2.268 2.482 4.832 0.815 -0.698 ms -12 38.93

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) -490.485 -438.494 -413.385 -367.651 -325.361 -310.784 -273.285 88.024 127.711 27.673 -368.755 ms -2983 4.336e+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) -957.000 -613.000 -410.000 26.000 429.000 579.000 814.000 839.000 1,192.000 253.744 20.652 ns -3.697 9.342

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.000 0.000 0.808 13.050 25.291 25.291 13.050 25.291 5.050 3.021 ms 1.275 6.792

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

peer jitter 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.213.2.253 0.192 0.196 0.292 2.181 8.919 15.072 15.978 8.627 14.876 3.116 3.323 ms 1.869 6.385

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.109 0.231 0.399 1.940 10.350 13.078 13.520 9.951 12.847 3.367 3.706 ms 1.333 3.372

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.990 3.862 10.314 21.341 21.341 9.324 21.341 3.554 4.631 ms 2.895 11.76

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.011 0.019 0.031 0.162 8.706 12.272 38.863 8.675 12.253 3.207 1.880 ms 1.653 16.86

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.272 0.526 3.457 10.741 13.347 13.791 10.215 13.074 3.470 4.388 ms 1.605 3.847

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.000 0.376 2.637 11.705 21.685 27.916 11.328 21.685 4.299 4.339 ms 2.014 9.119

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.218.192.202

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.202 0.277 0.442 2.260 11.635 20.413 133.691 11.192 20.136 8.894 3.980 ms 10.63 154.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 76.14.161.109

peer jitter 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 76.14.161.109 0.682 0.898 1.712 14.146 97.549 108.045 123.964 95.837 107.147 28.532 25.417 ms 1.263 3.888

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) 1.803 4.621 6.216 11.771 23.599 31.785 65.853 17.384 27.164 5.621 12.953 ms 7.692 28.85

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

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

RMS Jitter is field 8 in the peerstats log file.



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) 34.000 81.000 106.000 203.000 397.000 517.000 767.000 291.000 436.000 93.518 220.380 ns 7.83 26.71

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.731 -5.730 -5.729 -5.659 -5.636 -5.635 -5.634 0.093 0.095 0.035 -5.673 ppm -4.399e+06 7.208e+08
Local Clock Time Offset -956.000 -612.000 -409.000 25.000 428.000 578.000 813.000 837.000 1,190.000 252.986 20.572 ns -3.698 9.354
Local RMS Frequency Jitter 24.000 29.000 33.000 54.000 101.000 121.000 137.000 68.000 92.000 20.831 59.081 10e-12 12.68 42.39
Local RMS Time Jitter 107.000 124.000 144.000 208.000 331.000 393.000 496.000 187.000 269.000 57.883 218.500 ns 30.69 120.8
Server Jitter 104.131.155.175 0.000 0.000 0.000 0.808 13.050 25.291 25.291 13.050 25.291 5.050 3.021 ms 1.275 6.792
Server Jitter 162.213.2.253 0.192 0.196 0.292 2.181 8.919 15.072 15.978 8.627 14.876 3.116 3.323 ms 1.869 6.385
Server Jitter 169.229.128.134 0.109 0.231 0.399 1.940 10.350 13.078 13.520 9.951 12.847 3.367 3.706 ms 1.333 3.372
Server Jitter 178.62.68.79 0.000 0.000 0.990 3.862 10.314 21.341 21.341 9.324 21.341 3.554 4.631 ms 2.895 11.76
Server Jitter 192.168.1.10 0.011 0.019 0.031 0.162 8.706 12.272 38.863 8.675 12.253 3.207 1.880 ms 1.653 16.86
Server Jitter 203.123.48.219 0.000 0.272 0.526 3.457 10.741 13.347 13.791 10.215 13.074 3.470 4.388 ms 1.605 3.847
Server Jitter 204.17.205.24 0.000 0.000 0.376 2.637 11.705 21.685 27.916 11.328 21.685 4.299 4.339 ms 2.014 9.119
Server Jitter 216.218.192.202 0.202 0.277 0.442 2.260 11.635 20.413 133.691 11.192 20.136 8.894 3.980 ms 10.63 154.8
Server Jitter 76.14.161.109 0.682 0.898 1.712 14.146 97.549 108.045 123.964 95.837 107.147 28.532 25.417 ms 1.263 3.888
Server Jitter SHM(0) 1.803 4.621 6.216 11.771 23.599 31.785 65.853 17.384 27.164 5.621 12.953 ms 7.692 28.85
Server Jitter SHM(1) 34.000 81.000 106.000 203.000 397.000 517.000 767.000 291.000 436.000 93.518 220.380 ns 7.83 26.71
Server Offset 104.131.155.175 -19.940 -19.940 0.743 3.159 4.807 5.711 5.711 4.064 25.652 3.906 2.315 ms -5.722 32.34
Server Offset 162.213.2.253 1.231 1.742 1.883 2.233 2.623 2.917 2.973 0.740 1.175 0.227 2.239 ms 717.3 6579
Server Offset 169.229.128.134 1.872 2.016 2.116 2.360 2.707 3.094 3.681 0.591 1.078 0.206 2.384 ms 1221 1.333e+04
Server Offset 178.62.68.79 -5.556 -5.556 -2.859 2.911 6.500 7.935 7.935 9.359 13.491 2.688 2.650 ms -0.837 3.887
Server Offset 192.168.1.10 -65.337 -8.999 14.898 51.111 84.260 107.066 226.166 69.362 116.065 23.201 50.826 µs 5.297 17.21
Server Offset 203.123.48.219 -0.706 -0.645 -0.304 0.089 7.094 7.452 8.493 7.398 8.097 3.306 2.392 ms -0.2322 1.189
Server Offset 204.17.205.24 -0.099 1.193 1.367 1.701 2.115 2.496 3.436 0.748 1.303 0.284 1.726 ms 147.1 851.4
Server Offset 216.218.192.202 -0.428 1.894 2.162 2.460 2.872 3.289 3.641 0.710 1.394 0.299 2.469 ms 399.2 3022
Server Offset 76.14.161.109 -4.877 -2.818 -1.839 -0.693 0.643 2.015 2.268 2.482 4.832 0.815 -0.698 ms -12 38.93
Server Offset SHM(0) -490.485 -438.494 -413.385 -367.651 -325.361 -310.784 -273.285 88.024 127.711 27.673 -368.755 ms -2983 4.336e+04
Server Offset SHM(1) -957.000 -613.000 -410.000 26.000 429.000 579.000 814.000 839.000 1,192.000 253.744 20.652 ns -3.697 9.342
TDOP 0.550 0.570 0.610 0.850 1.450 1.700 2.500 0.840 1.130 0.267 0.913 22.84 88.76
Temp ZONE0 55.844 55.844 56.382 57.996 59.610 60.148 60.148 3.228 4.304 1.105 58.004 °C
nSats 6.000 7.000 7.000 9.000 12.000 12.000 12.000 5.000 5.000 1.417 9.395 nSat 195.2 1196
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!