NTPsec

C-ntpsec-3-hour-stats

Report generated: Thu Mar 4 16:01:22 2021 UTC
Start Time: Thu Mar 4 13:01:22 2021 UTC
End Time: Thu Mar 4 16:01:22 2021 UTC
Report published: Thu Mar 04 08:01:27 2021 PST
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.095 -1.014 -0.811 -0.213 0.602 0.940 1.177 1.413 1.954 0.444 -0.167 µs -6.373 15.56
Local Clock Frequency Offset -5.239 -5.239 -5.238 -5.225 -5.189 -5.184 -5.184 0.049 0.055 0.0161 -5.219 ppm -3.413e+07 1.107e+10

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

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



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 101.000 108.000 123.000 193.000 335.000 470.000 595.000 212.000 362.000 68.574 204.882 ns 15.61 61.76

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 43.000 48.000 60.000 115.000 264.000 363.000 456.000 204.000 315.000 64.999 131.516 10e-12 5.725 19.93

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.095 -1.014 -0.811 -0.213 0.602 0.940 1.177 1.413 1.954 0.444 -0.167 µs -6.373 15.56

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.239 -5.238 -5.225 -5.189 -5.184 -5.184 0.049 0.055 0.0161 -5.219 ppm -3.413e+07 1.107e+10
Temp ZONE0 56.920 56.920 56.920 57.458 57.996 57.996 57.996 1.076 1.076 0.400 57.524 °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 8.000 10.000 11.000 11.000 11.000 3.000 3.000 0.812 9.626 nSat 1313 1.461e+04
TDOP 0.590 0.600 0.610 0.770 1.300 1.410 1.410 0.690 0.810 0.194 0.874 54.85 242

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.094 1.094 1.094 1.668 3.218 3.218 3.218 2.124 2.124 0.528 1.870 ms 25.25 97.24

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.961 1.961 2.062 2.332 2.514 2.536 2.536 0.453 0.575 0.149 2.304 ms 3090 4.54e+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 -856.625 -856.625 -377.959 30.968 457.556 654.033 654.033 835.515 1,510.658 291.067 33.852 µs -3.845 11.13

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.716 1.716 1.716 4.408 4.776 4.776 4.776 3.060 3.060 0.896 3.855 ms 44.89 174.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 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 13.433 31.760 79.498 135.685 194.339 232.023 233.533 114.841 200.263 34.524 132.694 µs 31.55 118.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 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 2.033 2.033 2.033 2.138 2.419 2.419 2.419 0.386 0.386 0.122 2.185 ms 4880 8.337e+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 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 2.113 2.113 2.113 2.372 2.586 2.586 2.586 0.473 0.473 0.123 2.350 ms 5992 1.095e+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 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.712 2.712 3.189 3.540 4.269 4.501 4.501 1.079 1.789 0.339 3.551 ms 877 8591

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 -2.046 -2.046 -2.020 2.138 9.198 9.914 9.914 11.218 11.961 3.642 2.757 ms -0.397 1.896

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) -71.438 -68.843 -65.363 -59.356 -49.082 -47.091 -46.131 16.281 21.753 4.605 -59.063 ms -2684 3.767e+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.096 -1.015 -0.812 -0.214 0.603 0.941 1.178 1.415 1.956 0.445 -0.167 µs -6.372 15.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 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 1.004 1.004 1.004 1.892 11.561 11.561 11.561 10.557 10.557 4.474 5.022 ms 0.9036 1.756

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.449 0.449 0.671 1.405 8.880 19.808 19.808 8.209 19.358 3.642 2.649 ms 2.281 10.55

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.959 0.959 1.062 5.714 9.213 9.643 9.643 8.151 8.684 3.525 5.066 ms 1.429 2.37

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 1.288 1.288 1.288 8.220 9.208 9.208 9.208 7.920 7.920 3.565 5.582 ms 1.561 2.435

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.030 0.040 0.054 0.220 8.611 8.842 8.852 8.557 8.802 2.373 1.294 ms 0.6803 3.664

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.791 0.791 0.791 1.307 8.783 8.783 8.783 7.992 7.992 2.388 2.259 ms 2.021 5.781

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.248 0.248 0.248 1.508 13.508 13.508 13.508 13.259 13.259 5.175 4.181 ms 0.4707 1.648

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.382 0.612 2.658 13.085 13.199 13.199 12.473 12.817 4.310 4.653 ms 1.055 2.396

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.986 0.986 1.115 2.977 11.391 11.401 11.401 10.276 10.415 3.076 4.074 ms 2.199 5.257

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.068 0.150 0.330 1.223 5.128 6.939 8.407 4.798 6.789 1.442 1.690 ms 2.457 8.327

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) 60.000 86.000 110.000 243.000 570.000 792.000 1,175.000 460.000 706.000 153.427 282.334 ns 4.569 15.63

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.239 -5.238 -5.225 -5.189 -5.184 -5.184 0.049 0.055 0.0161 -5.219 ppm -3.413e+07 1.107e+10
Local Clock Time Offset -1.095 -1.014 -0.811 -0.213 0.602 0.940 1.177 1.413 1.954 0.444 -0.167 µs -6.373 15.56
Local RMS Frequency Jitter 43.000 48.000 60.000 115.000 264.000 363.000 456.000 204.000 315.000 64.999 131.516 10e-12 5.725 19.93
Local RMS Time Jitter 101.000 108.000 123.000 193.000 335.000 470.000 595.000 212.000 362.000 68.574 204.882 ns 15.61 61.76
Server Jitter 104.131.155.175 1.004 1.004 1.004 1.892 11.561 11.561 11.561 10.557 10.557 4.474 5.022 ms 0.9036 1.756
Server Jitter 162.159.200.1 0.449 0.449 0.671 1.405 8.880 19.808 19.808 8.209 19.358 3.642 2.649 ms 2.281 10.55
Server Jitter 173.11.101.155 0.959 0.959 1.062 5.714 9.213 9.643 9.643 8.151 8.684 3.525 5.066 ms 1.429 2.37
Server Jitter 178.62.68.79 1.288 1.288 1.288 8.220 9.208 9.208 9.208 7.920 7.920 3.565 5.582 ms 1.561 2.435
Server Jitter 192.168.1.10 0.030 0.040 0.054 0.220 8.611 8.842 8.852 8.557 8.802 2.373 1.294 ms 0.6803 3.664
Server Jitter 192.53.103.98 0.791 0.791 0.791 1.307 8.783 8.783 8.783 7.992 7.992 2.388 2.259 ms 2.021 5.781
Server Jitter 204.123.2.5 0.248 0.248 0.248 1.508 13.508 13.508 13.508 13.259 13.259 5.175 4.181 ms 0.4707 1.648
Server Jitter 204.17.205.24 0.382 0.382 0.612 2.658 13.085 13.199 13.199 12.473 12.817 4.310 4.653 ms 1.055 2.396
Server Jitter 47.51.249.154 0.986 0.986 1.115 2.977 11.391 11.401 11.401 10.276 10.415 3.076 4.074 ms 2.199 5.257
Server Jitter SHM(0) 0.068 0.150 0.330 1.223 5.128 6.939 8.407 4.798 6.789 1.442 1.690 ms 2.457 8.327
Server Jitter SHM(1) 60.000 86.000 110.000 243.000 570.000 792.000 1,175.000 460.000 706.000 153.427 282.334 ns 4.569 15.63
Server Offset 104.131.155.175 1.094 1.094 1.094 1.668 3.218 3.218 3.218 2.124 2.124 0.528 1.870 ms 25.25 97.24
Server Offset 162.159.200.1 1.961 1.961 2.062 2.332 2.514 2.536 2.536 0.453 0.575 0.149 2.304 ms 3090 4.54e+04
Server Offset 173.11.101.155 -856.625 -856.625 -377.959 30.968 457.556 654.033 654.033 835.515 1,510.658 291.067 33.852 µs -3.845 11.13
Server Offset 178.62.68.79 1.716 1.716 1.716 4.408 4.776 4.776 4.776 3.060 3.060 0.896 3.855 ms 44.89 174.2
Server Offset 192.168.1.10 13.433 31.760 79.498 135.685 194.339 232.023 233.533 114.841 200.263 34.524 132.694 µs 31.55 118.5
Server Offset 192.53.103.98 2.033 2.033 2.033 2.138 2.419 2.419 2.419 0.386 0.386 0.122 2.185 ms 4880 8.337e+04
Server Offset 204.123.2.5 2.113 2.113 2.113 2.372 2.586 2.586 2.586 0.473 0.473 0.123 2.350 ms 5992 1.095e+05
Server Offset 204.17.205.24 2.712 2.712 3.189 3.540 4.269 4.501 4.501 1.079 1.789 0.339 3.551 ms 877 8591
Server Offset 47.51.249.154 -2.046 -2.046 -2.020 2.138 9.198 9.914 9.914 11.218 11.961 3.642 2.757 ms -0.397 1.896
Server Offset SHM(0) -71.438 -68.843 -65.363 -59.356 -49.082 -47.091 -46.131 16.281 21.753 4.605 -59.063 ms -2684 3.767e+04
Server Offset SHM(1) -1.096 -1.015 -0.812 -0.214 0.603 0.941 1.178 1.415 1.956 0.445 -0.167 µs -6.372 15.55
TDOP 0.590 0.600 0.610 0.770 1.300 1.410 1.410 0.690 0.810 0.194 0.874 54.85 242
Temp ZONE0 56.920 56.920 56.920 57.458 57.996 57.996 57.996 1.076 1.076 0.400 57.524 °C
nSats 8.000 8.000 8.000 10.000 11.000 11.000 11.000 3.000 3.000 0.812 9.626 nSat 1313 1.461e+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!