NTPsec

C-ntpsec-3-hour-stats

Report generated: Fri Oct 22 17:02:20 2021 UTC
Start Time: Fri Oct 22 14:02:20 2021 UTC
End Time: Fri Oct 22 17:02:20 2021 UTC
Report published: Fri Oct 22 10:02:25 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,147.000 -820.000 -544.000 -120.000 344.000 543.000 735.000 888.000 1,363.000 274.032 -113.531 ns -7.059 19.15
Local Clock Frequency Offset -4.910 -4.909 -4.909 -4.903 -4.889 -4.888 -4.888 0.021 0.022 0.0059 -4.902 ppm -5.828e+08 4.869e+11

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 92.000 110.000 127.000 186.000 266.000 304.000 342.000 139.000 194.000 40.629 190.107 ns 61.46 277.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 31.000 35.000 43.000 65.000 127.000 217.000 257.000 84.000 182.000 31.170 72.334 10e-12 9.044 41.8

The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.

Lower is better. An ideal clock would be a horizontal line at 0ppm.

RMS Frequency Jitter is field 6 in the loopstats log file.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -1,147.000 -820.000 -544.000 -120.000 344.000 543.000 735.000 888.000 1,363.000 274.032 -113.531 ns -7.059 19.15

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -4.910 -4.909 -4.909 -4.903 -4.889 -4.888 -4.888 0.021 0.022 0.0059 -4.902 ppm -5.828e+08 4.869e+11
Temp ZONE0 58.534 58.534 58.534 59.072 59.610 59.610 59.610 1.076 1.076 0.245 59.042 °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 9.000 11.000 12.000 12.000 2.000 4.000 0.752 9.592 nSat 1660 1.996e+04
TDOP 0.510 0.520 0.600 0.790 1.110 1.230 1.460 0.510 0.710 0.163 0.833 81.66 396.7

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 162.159.200.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 2.600 2.600 2.644 2.944 3.224 3.412 3.412 0.580 0.812 0.181 2.947 ms 3585 5.535e+04

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

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

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

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



Server Offset 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 2.159 2.159 2.230 2.457 2.626 3.609 3.609 0.396 1.450 0.215 2.472 ms 1192 1.297e+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.025 -1.025 -0.377 0.040 0.572 0.647 0.647 0.949 1.672 0.309 0.022 ms -4.262 13.56

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 3.137 24.779 60.138 141.080 212.181 238.235 240.352 152.043 213.456 42.164 142.633 µs 20.3 66.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 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 7.230 7.230 7.299 7.459 7.708 7.723 7.723 0.409 0.493 0.124 7.481 ms 2.094e+05 1.244e+07

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

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

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

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



Server Offset 194.58.202.219

peer offset 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.219 10.592 10.592 10.636 10.839 11.052 11.222 11.222 0.417 0.630 0.129 10.847 ms 5.792e+05 4.83e+07

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

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

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

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



Server Offset 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 2.053 2.053 2.231 2.489 2.795 2.896 2.896 0.564 0.842 0.179 2.496 ms 2216 2.923e+04

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

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

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

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



Server Offset 216.218.254.202

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.254.202 2.315 2.315 2.362 2.593 2.773 2.825 2.825 0.411 0.510 0.130 2.558 ms 6594 1.243e+05

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

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

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

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



Server Offset 63.145.169.3

peer offset 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 63.145.169.3 -66.233 -66.233 -61.525 0.043 0.722 2.198 2.198 62.247 68.430 20.467 -8.824 ms -9.248 33.43

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) -65.030 -63.839 -62.792 -55.680 -46.803 -45.772 -44.807 15.989 18.068 4.730 -54.715 ms -2023 2.59e+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,148.000 -821.000 -545.000 -121.000 345.000 544.000 736.000 890.000 1,365.000 274.717 -113.873 ns -7.058 19.12

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

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

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

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



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.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.223 0.223 0.271 0.516 6.704 7.387 7.387 6.432 7.165 2.010 1.516 ms 1.044 3.482

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.185 0.185 0.231 0.778 6.521 6.638 6.638 6.290 6.453 1.607 1.426 ms 1.91 6.623

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.457 0.457 0.527 1.452 5.156 5.443 5.443 4.629 4.986 1.258 2.004 ms 3.418 9.941

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 10.975 25.314 47.278 112.735 456.666 654.928 850.555 409.388 629.614 132.317 151.717 µs 3.071 12.09

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.162 0.162 0.279 0.810 6.285 6.383 6.383 6.007 6.221 1.637 1.388 ms 1.584 4.82

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.174 0.174 0.179 1.371 9.998 10.090 10.090 9.819 9.916 2.703 2.424 ms 1.446 4.689

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.263 0.263 0.343 1.166 9.706 22.998 22.998 9.364 22.736 4.205 2.596 ms 2.01 10.35

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.218.254.202

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.254.202 0.101 0.101 0.160 0.425 1.271 1.399 1.399 1.110 1.298 0.420 0.631 ms 2.083 4.138

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 63.145.169.3

peer jitter 63.145.169.3 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 63.145.169.3 9.249 9.249 13.555 53.011 68.082 70.903 70.903 54.527 61.654 16.903 47.970 ms 10.93 28.27

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.106 0.171 0.270 0.880 3.009 6.066 8.532 2.739 5.894 1.052 1.136 ms 3.395 16.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) 56.000 75.000 111.000 231.000 506.000 715.000 782.000 395.000 640.000 130.635 261.936 ns 5.263 16.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 -4.910 -4.909 -4.909 -4.903 -4.889 -4.888 -4.888 0.021 0.022 0.0059 -4.902 ppm -5.828e+08 4.869e+11
Local Clock Time Offset -1,147.000 -820.000 -544.000 -120.000 344.000 543.000 735.000 888.000 1,363.000 274.032 -113.531 ns -7.059 19.15
Local RMS Frequency Jitter 31.000 35.000 43.000 65.000 127.000 217.000 257.000 84.000 182.000 31.170 72.334 10e-12 9.044 41.8
Local RMS Time Jitter 92.000 110.000 127.000 186.000 266.000 304.000 342.000 139.000 194.000 40.629 190.107 ns 61.46 277.3
Server Jitter 162.159.200.1 0.223 0.223 0.271 0.516 6.704 7.387 7.387 6.432 7.165 2.010 1.516 ms 1.044 3.482
Server Jitter 169.229.128.134 0.185 0.185 0.231 0.778 6.521 6.638 6.638 6.290 6.453 1.607 1.426 ms 1.91 6.623
Server Jitter 173.11.101.155 0.457 0.457 0.527 1.452 5.156 5.443 5.443 4.629 4.986 1.258 2.004 ms 3.418 9.941
Server Jitter 192.168.1.10 10.975 25.314 47.278 112.735 456.666 654.928 850.555 409.388 629.614 132.317 151.717 µs 3.071 12.09
Server Jitter 194.58.202.211 0.162 0.162 0.279 0.810 6.285 6.383 6.383 6.007 6.221 1.637 1.388 ms 1.584 4.82
Server Jitter 194.58.202.219 0.174 0.174 0.179 1.371 9.998 10.090 10.090 9.819 9.916 2.703 2.424 ms 1.446 4.689
Server Jitter 203.123.48.219 0.263 0.263 0.343 1.166 9.706 22.998 22.998 9.364 22.736 4.205 2.596 ms 2.01 10.35
Server Jitter 216.218.254.202 0.101 0.101 0.160 0.425 1.271 1.399 1.399 1.110 1.298 0.420 0.631 ms 2.083 4.138
Server Jitter 63.145.169.3 9.249 9.249 13.555 53.011 68.082 70.903 70.903 54.527 61.654 16.903 47.970 ms 10.93 28.27
Server Jitter SHM(0) 0.106 0.171 0.270 0.880 3.009 6.066 8.532 2.739 5.894 1.052 1.136 ms 3.395 16.85
Server Jitter SHM(1) 56.000 75.000 111.000 231.000 506.000 715.000 782.000 395.000 640.000 130.635 261.936 ns 5.263 16.71
Server Offset 162.159.200.1 2.600 2.600 2.644 2.944 3.224 3.412 3.412 0.580 0.812 0.181 2.947 ms 3585 5.535e+04
Server Offset 169.229.128.134 2.159 2.159 2.230 2.457 2.626 3.609 3.609 0.396 1.450 0.215 2.472 ms 1192 1.297e+04
Server Offset 173.11.101.155 -1.025 -1.025 -0.377 0.040 0.572 0.647 0.647 0.949 1.672 0.309 0.022 ms -4.262 13.56
Server Offset 192.168.1.10 3.137 24.779 60.138 141.080 212.181 238.235 240.352 152.043 213.456 42.164 142.633 µs 20.3 66.55
Server Offset 194.58.202.211 7.230 7.230 7.299 7.459 7.708 7.723 7.723 0.409 0.493 0.124 7.481 ms 2.094e+05 1.244e+07
Server Offset 194.58.202.219 10.592 10.592 10.636 10.839 11.052 11.222 11.222 0.417 0.630 0.129 10.847 ms 5.792e+05 4.83e+07
Server Offset 203.123.48.219 2.053 2.053 2.231 2.489 2.795 2.896 2.896 0.564 0.842 0.179 2.496 ms 2216 2.923e+04
Server Offset 216.218.254.202 2.315 2.315 2.362 2.593 2.773 2.825 2.825 0.411 0.510 0.130 2.558 ms 6594 1.243e+05
Server Offset 63.145.169.3 -66.233 -66.233 -61.525 0.043 0.722 2.198 2.198 62.247 68.430 20.467 -8.824 ms -9.248 33.43
Server Offset SHM(0) -65.030 -63.839 -62.792 -55.680 -46.803 -45.772 -44.807 15.989 18.068 4.730 -54.715 ms -2023 2.59e+04
Server Offset SHM(1) -1,148.000 -821.000 -545.000 -121.000 345.000 544.000 736.000 890.000 1,365.000 274.717 -113.873 ns -7.058 19.12
TDOP 0.510 0.520 0.600 0.790 1.110 1.230 1.460 0.510 0.710 0.163 0.833 81.66 396.7
Temp ZONE0 58.534 58.534 58.534 59.072 59.610 59.610 59.610 1.076 1.076 0.245 59.042 °C
nSats 8.000 8.000 9.000 9.000 11.000 12.000 12.000 2.000 4.000 0.752 9.592 nSat 1660 1.996e+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!