NTPsec

C-ntpsec-12-hour-stats

Report generated: Thu Mar 4 15:01:42 2021 UTC
Start Time: Thu Mar 4 03:01:42 2021 UTC
End Time: Thu Mar 4 15:01:42 2021 UTC
Report published: Thu Mar 04 07:01:47 2021 PST
Report Period: 0.5 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,642.000 -975.000 -752.000 -266.000 291.000 541.000 1,273.000 1,043.000 1,516.000 317.324 -258.244 ns -11.15 32.54
Local Clock Frequency Offset -5.239 -5.238 -5.228 -5.109 -5.052 -5.051 -5.050 0.176 0.187 0.057 -5.121 ppm -7.589e+05 6.924e+07

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 77.000 100.000 115.000 171.000 299.000 421.000 668.000 184.000 321.000 63.191 184.761 ns 14.91 61.66

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 34.000 44.000 91.000 194.000 299.000 456.000 150.000 265.000 50.797 100.769 10e-12 5.858 23.84

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

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

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



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -1,642.000 -975.000 -752.000 -266.000 291.000 541.000 1,273.000 1,043.000 1,516.000 317.324 -258.244 ns -11.15 32.54

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.239 -5.238 -5.228 -5.109 -5.052 -5.051 -5.050 0.176 0.187 0.057 -5.121 ppm -7.589e+05 6.924e+07
Temp ZONE0 56.920 56.920 57.458 58.534 59.610 60.148 60.148 2.152 3.228 0.726 58.546 °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 10.000 12.000 12.000 12.000 5.000 5.000 1.266 9.852 nSat 332.1 2384
TDOP 0.520 0.540 0.590 0.790 1.300 1.340 1.590 0.710 0.800 0.202 0.860 44.74 187.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 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 0.912 0.912 1.094 1.689 2.691 3.022 3.022 1.597 2.109 0.386 1.728 ms 53.7 240.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 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 1.224 1.415 1.931 2.329 2.827 3.310 3.344 0.896 1.895 0.287 2.333 ms 382.1 2878

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.517 -1.235 -0.767 0.165 1.267 2.751 2.892 2.034 3.985 0.606 0.201 ms -1.23 7.274

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 1.419 1.419 1.716 3.677 4.776 4.797 4.797 3.060 3.378 0.909 3.482 ms 30.68 109.3

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 -5.709 31.171 49.706 127.959 185.126 228.877 254.845 135.420 197.706 40.676 124.850 µs 14.95 46.44

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

peer offset 192.53.103.98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.53.103.98 -0.438 -0.438 -0.177 2.144 2.471 2.640 2.640 2.648 3.077 1.087 1.439 ms 0.4684 1.378

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.684 1.684 1.975 2.249 2.720 2.923 2.923 0.745 1.239 0.219 2.298 ms 883.4 8667

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 2.485 2.790 3.059 3.595 4.149 4.609 4.824 1.090 1.819 0.330 3.605 ms 1006 1.029e+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 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 -8.470 -7.858 -6.203 3.412 8.897 11.224 11.397 15.100 19.082 3.956 2.183 ms -1.806 5.076

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

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

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

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



Server Offset SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -72.581 -69.411 -67.486 -59.248 -50.077 -46.027 -44.856 17.409 23.384 5.124 -59.278 ms -2023 2.589e+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,643.000 -976.000 -753.000 -267.000 292.000 542.000 1,274.000 1,045.000 1,518.000 317.850 -258.839 ns -11.15 32.53

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.721 0.721 0.856 2.132 9.619 12.015 12.015 8.763 11.294 3.372 3.984 ms 1.385 2.983

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.162 0.439 0.671 1.814 9.297 25.511 25.656 8.626 25.072 3.920 3.300 ms 2.696 14.31

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.538 0.734 0.993 2.396 10.028 14.441 14.986 9.035 13.707 3.470 4.044 ms 1.706 4.337

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.869 0.869 0.884 2.069 10.733 18.382 18.382 9.849 17.513 3.945 4.238 ms 1.752 5.799

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.022 0.040 0.069 0.236 8.667 8.890 9.600 8.597 8.850 2.429 1.360 ms 0.7708 3.857

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

peer jitter 192.53.103.98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.53.103.98 0.755 0.755 0.791 1.572 8.584 8.586 8.586 7.793 7.831 2.629 2.922 ms 1.582 3.479

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.447 0.447 0.680 1.767 12.861 13.992 13.992 12.181 13.545 3.597 3.620 ms 1.53 4.121

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.382 0.463 0.612 1.798 10.566 13.009 13.199 9.955 12.546 3.605 3.750 ms 1.13 2.709

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.406 0.591 0.941 2.648 11.779 15.307 15.736 10.838 14.716 3.528 4.039 ms 1.883 5.199

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.070 0.165 0.271 0.944 3.211 5.856 8.194 2.940 5.692 1.062 1.234 ms 3.032 13.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 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) 28.000 67.000 95.000 213.000 525.000 736.000 1,269.000 430.000 669.000 142.557 248.069 ns 4.431 17.28

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.239 -5.238 -5.228 -5.109 -5.052 -5.051 -5.050 0.176 0.187 0.057 -5.121 ppm -7.589e+05 6.924e+07
Local Clock Time Offset -1,642.000 -975.000 -752.000 -266.000 291.000 541.000 1,273.000 1,043.000 1,516.000 317.324 -258.244 ns -11.15 32.54
Local RMS Frequency Jitter 23.000 34.000 44.000 91.000 194.000 299.000 456.000 150.000 265.000 50.797 100.769 10e-12 5.858 23.84
Local RMS Time Jitter 77.000 100.000 115.000 171.000 299.000 421.000 668.000 184.000 321.000 63.191 184.761 ns 14.91 61.66
Server Jitter 104.131.155.175 0.721 0.721 0.856 2.132 9.619 12.015 12.015 8.763 11.294 3.372 3.984 ms 1.385 2.983
Server Jitter 162.159.200.1 0.162 0.439 0.671 1.814 9.297 25.511 25.656 8.626 25.072 3.920 3.300 ms 2.696 14.31
Server Jitter 173.11.101.155 0.538 0.734 0.993 2.396 10.028 14.441 14.986 9.035 13.707 3.470 4.044 ms 1.706 4.337
Server Jitter 178.62.68.79 0.869 0.869 0.884 2.069 10.733 18.382 18.382 9.849 17.513 3.945 4.238 ms 1.752 5.799
Server Jitter 192.168.1.10 0.022 0.040 0.069 0.236 8.667 8.890 9.600 8.597 8.850 2.429 1.360 ms 0.7708 3.857
Server Jitter 192.53.103.98 0.755 0.755 0.791 1.572 8.584 8.586 8.586 7.793 7.831 2.629 2.922 ms 1.582 3.479
Server Jitter 204.123.2.5 0.447 0.447 0.680 1.767 12.861 13.992 13.992 12.181 13.545 3.597 3.620 ms 1.53 4.121
Server Jitter 204.17.205.24 0.382 0.463 0.612 1.798 10.566 13.009 13.199 9.955 12.546 3.605 3.750 ms 1.13 2.709
Server Jitter 47.51.249.154 0.406 0.591 0.941 2.648 11.779 15.307 15.736 10.838 14.716 3.528 4.039 ms 1.883 5.199
Server Jitter SHM(0) 0.070 0.165 0.271 0.944 3.211 5.856 8.194 2.940 5.692 1.062 1.234 ms 3.032 13.2
Server Jitter SHM(1) 28.000 67.000 95.000 213.000 525.000 736.000 1,269.000 430.000 669.000 142.557 248.069 ns 4.431 17.28
Server Offset 104.131.155.175 0.912 0.912 1.094 1.689 2.691 3.022 3.022 1.597 2.109 0.386 1.728 ms 53.7 240.2
Server Offset 162.159.200.1 1.224 1.415 1.931 2.329 2.827 3.310 3.344 0.896 1.895 0.287 2.333 ms 382.1 2878
Server Offset 173.11.101.155 -1.517 -1.235 -0.767 0.165 1.267 2.751 2.892 2.034 3.985 0.606 0.201 ms -1.23 7.274
Server Offset 178.62.68.79 1.419 1.419 1.716 3.677 4.776 4.797 4.797 3.060 3.378 0.909 3.482 ms 30.68 109.3
Server Offset 192.168.1.10 -5.709 31.171 49.706 127.959 185.126 228.877 254.845 135.420 197.706 40.676 124.850 µs 14.95 46.44
Server Offset 192.53.103.98 -0.438 -0.438 -0.177 2.144 2.471 2.640 2.640 2.648 3.077 1.087 1.439 ms 0.4684 1.378
Server Offset 204.123.2.5 1.684 1.684 1.975 2.249 2.720 2.923 2.923 0.745 1.239 0.219 2.298 ms 883.4 8667
Server Offset 204.17.205.24 2.485 2.790 3.059 3.595 4.149 4.609 4.824 1.090 1.819 0.330 3.605 ms 1006 1.029e+04
Server Offset 47.51.249.154 -8.470 -7.858 -6.203 3.412 8.897 11.224 11.397 15.100 19.082 3.956 2.183 ms -1.806 5.076
Server Offset SHM(0) -72.581 -69.411 -67.486 -59.248 -50.077 -46.027 -44.856 17.409 23.384 5.124 -59.278 ms -2023 2.589e+04
Server Offset SHM(1) -1,643.000 -976.000 -753.000 -267.000 292.000 542.000 1,274.000 1,045.000 1,518.000 317.850 -258.839 ns -11.15 32.53
TDOP 0.520 0.540 0.590 0.790 1.300 1.340 1.590 0.710 0.800 0.202 0.860 44.74 187.7
Temp ZONE0 56.920 56.920 57.458 58.534 59.610 60.148 60.148 2.152 3.228 0.726 58.546 °C
nSats 6.000 7.000 7.000 10.000 12.000 12.000 12.000 5.000 5.000 1.266 9.852 nSat 332.1 2384
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!