NTPsec

C-ntpsec-1-hour-stats

Report generated: Mon Dec 6 21:02:15 2021 UTC
Start Time: Mon Dec 6 20:01:47 2021 UTC
End Time: Mon Dec 6 21:02:15 2021 UTC
Report published: Mon Dec 06 13:02:20 2021 PST
Report Period: 0.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 -775.000 -650.000 -227.000 203.000 783.000 978.000 1,047.000 1,010.000 1,628.000 333.898 238.704 ns -0.9368 3.67
Local Clock Frequency Offset -4.987 -4.986 -4.986 -4.979 -4.974 -4.974 -4.973 0.0122 0.0128 0.0045 -4.980 ppm -1.324e+09 1.453e+12

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 140.000 143.000 156.000 205.000 335.000 406.000 455.000 179.000 263.000 54.146 217.854 ns 38.24 162.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 35.000 37.000 41.000 80.000 163.000 191.000 201.000 122.000 154.000 40.053 90.000 10e-12 6.395 17.94

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 -775.000 -650.000 -227.000 203.000 783.000 978.000 1,047.000 1,010.000 1,628.000 333.898 238.704 ns -0.9368 3.67

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.987 -4.986 -4.986 -4.979 -4.974 -4.974 -4.973 0.0122 0.0128 0.0045 -4.980 ppm -1.324e+09 1.453e+12
Temp ZONE0 57.996 57.996 57.996 57.996 58.534 58.534 58.534 0.538 0.538 0.161 58.050 °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 6.000 6.000 8.000 9.000 9.000 9.000 3.000 3.000 1.024 8.033 nSat 341 2468
TDOP 0.660 0.660 0.670 1.130 1.700 1.790 1.790 1.030 1.130 0.357 1.054 13.61 41.61

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

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 2.685 2.685 2.685 2.884 3.132 3.132 3.132 0.446 0.446 0.132 2.904 ms 9261 1.954e+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 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.315 2.315 2.315 2.504 2.780 2.780 2.780 0.465 0.465 0.148 2.493 ms 4047 6.502e+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 -947.377 -947.377 -947.377 31.228 333.028 333.028 333.028 1,280.405 1,280.405 336.435 -62.707 µs -6.41 20.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 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 78.863 78.863 114.330 160.075 212.625 228.906 228.906 98.295 150.043 30.256 156.946 µs 86.05 416.8

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.180 7.180 7.180 7.387 7.595 7.595 7.595 0.414 0.414 0.136 7.366 ms 1.492e+05 7.917e+06

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 5.268 5.268 5.268 5.339 5.644 5.644 5.644 0.376 0.376 0.096 5.371 ms 1.646e+05 9.024e+06

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 1.291 1.291 1.291 1.719 1.998 1.998 1.998 0.707 0.707 0.239 1.658 ms 226.8 1449

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.515 2.515 2.515 2.713 2.788 2.788 2.788 0.272 0.272 0.089 2.681 ms 2.44e+04 7.094e+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 -38.386 -38.386 -38.386 0.714 1.150 1.150 1.150 39.536 39.536 10.420 -3.503 ms -8.904 35.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 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) -61.020 -60.644 -58.415 -52.579 -48.141 -46.092 -45.524 10.273 14.553 3.123 -52.741 ms -5779 1.044e+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 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) -776.000 -650.000 -228.000 204.000 784.000 979.000 1,048.000 1,012.000 1,629.000 334.428 239.212 ns -0.9387 3.67

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

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.160 0.160 0.160 1.058 45.099 45.099 45.099 44.938 44.938 15.915 7.752 ms 0.24 2.393

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.558 0.558 0.558 1.309 1.611 1.611 1.611 1.052 1.052 0.322 1.181 ms 26.23 88.36

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.687 0.687 0.687 1.255 1.960 1.960 1.960 1.273 1.273 0.412 1.333 ms 17.97 57.47

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 39.223 39.223 67.878 150.335 261.827 288.907 288.907 193.949 249.684 60.540 152.404 µs 8.3 22.83

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.211 0.211 0.211 1.074 1.468 1.468 1.468 1.257 1.257 0.385 0.961 ms 7.175 16.75

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 228.130 228.130 228.130 685.264 921.425 921.425 921.425 693.295 693.295 247.588 610.517 µs 7.39 18.08

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.390 0.390 0.390 0.881 24.782 24.782 24.782 24.393 24.393 7.521 3.523 ms 0.7244 3.634

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.538 0.538 0.538 1.386 2.612 2.612 2.612 2.074 2.074 0.682 1.491 ms 5.734 14.96

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 1.012 1.012 1.012 26.014 52.267 52.267 52.267 51.256 51.256 16.635 26.692 ms 1.887 3.833

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.114 0.237 0.320 1.023 3.178 5.059 6.885 2.858 4.822 0.915 1.293 ms 3.592 14.78

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) 61.000 70.000 104.000 241.000 522.000 754.000 1,225.000 418.000 684.000 156.752 276.403 ns 4.917 22.64

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.987 -4.986 -4.986 -4.979 -4.974 -4.974 -4.973 0.0122 0.0128 0.0045 -4.980 ppm -1.324e+09 1.453e+12
Local Clock Time Offset -775.000 -650.000 -227.000 203.000 783.000 978.000 1,047.000 1,010.000 1,628.000 333.898 238.704 ns -0.9368 3.67
Local RMS Frequency Jitter 35.000 37.000 41.000 80.000 163.000 191.000 201.000 122.000 154.000 40.053 90.000 10e-12 6.395 17.94
Local RMS Time Jitter 140.000 143.000 156.000 205.000 335.000 406.000 455.000 179.000 263.000 54.146 217.854 ns 38.24 162.8
Server Jitter 162.159.200.123 0.160 0.160 0.160 1.058 45.099 45.099 45.099 44.938 44.938 15.915 7.752 ms 0.24 2.393
Server Jitter 169.229.128.134 0.558 0.558 0.558 1.309 1.611 1.611 1.611 1.052 1.052 0.322 1.181 ms 26.23 88.36
Server Jitter 173.11.101.155 0.687 0.687 0.687 1.255 1.960 1.960 1.960 1.273 1.273 0.412 1.333 ms 17.97 57.47
Server Jitter 192.168.1.10 39.223 39.223 67.878 150.335 261.827 288.907 288.907 193.949 249.684 60.540 152.404 µs 8.3 22.83
Server Jitter 194.58.202.211 0.211 0.211 0.211 1.074 1.468 1.468 1.468 1.257 1.257 0.385 0.961 ms 7.175 16.75
Server Jitter 194.58.202.219 228.130 228.130 228.130 685.264 921.425 921.425 921.425 693.295 693.295 247.588 610.517 µs 7.39 18.08
Server Jitter 204.17.205.24 0.390 0.390 0.390 0.881 24.782 24.782 24.782 24.393 24.393 7.521 3.523 ms 0.7244 3.634
Server Jitter 216.218.254.202 0.538 0.538 0.538 1.386 2.612 2.612 2.612 2.074 2.074 0.682 1.491 ms 5.734 14.96
Server Jitter 63.145.169.3 1.012 1.012 1.012 26.014 52.267 52.267 52.267 51.256 51.256 16.635 26.692 ms 1.887 3.833
Server Jitter SHM(0) 0.114 0.237 0.320 1.023 3.178 5.059 6.885 2.858 4.822 0.915 1.293 ms 3.592 14.78
Server Jitter SHM(1) 61.000 70.000 104.000 241.000 522.000 754.000 1,225.000 418.000 684.000 156.752 276.403 ns 4.917 22.64
Server Offset 162.159.200.123 2.685 2.685 2.685 2.884 3.132 3.132 3.132 0.446 0.446 0.132 2.904 ms 9261 1.954e+05
Server Offset 169.229.128.134 2.315 2.315 2.315 2.504 2.780 2.780 2.780 0.465 0.465 0.148 2.493 ms 4047 6.502e+04
Server Offset 173.11.101.155 -947.377 -947.377 -947.377 31.228 333.028 333.028 333.028 1,280.405 1,280.405 336.435 -62.707 µs -6.41 20.13
Server Offset 192.168.1.10 78.863 78.863 114.330 160.075 212.625 228.906 228.906 98.295 150.043 30.256 156.946 µs 86.05 416.8
Server Offset 194.58.202.211 7.180 7.180 7.180 7.387 7.595 7.595 7.595 0.414 0.414 0.136 7.366 ms 1.492e+05 7.917e+06
Server Offset 194.58.202.219 5.268 5.268 5.268 5.339 5.644 5.644 5.644 0.376 0.376 0.096 5.371 ms 1.646e+05 9.024e+06
Server Offset 204.17.205.24 1.291 1.291 1.291 1.719 1.998 1.998 1.998 0.707 0.707 0.239 1.658 ms 226.8 1449
Server Offset 216.218.254.202 2.515 2.515 2.515 2.713 2.788 2.788 2.788 0.272 0.272 0.089 2.681 ms 2.44e+04 7.094e+05
Server Offset 63.145.169.3 -38.386 -38.386 -38.386 0.714 1.150 1.150 1.150 39.536 39.536 10.420 -3.503 ms -8.904 35.24
Server Offset SHM(0) -61.020 -60.644 -58.415 -52.579 -48.141 -46.092 -45.524 10.273 14.553 3.123 -52.741 ms -5779 1.044e+05
Server Offset SHM(1) -776.000 -650.000 -228.000 204.000 784.000 979.000 1,048.000 1,012.000 1,629.000 334.428 239.212 ns -0.9387 3.67
TDOP 0.660 0.660 0.670 1.130 1.700 1.790 1.790 1.030 1.130 0.357 1.054 13.61 41.61
Temp ZONE0 57.996 57.996 57.996 57.996 58.534 58.534 58.534 0.538 0.538 0.161 58.050 °C
nSats 6.000 6.000 6.000 8.000 9.000 9.000 9.000 3.000 3.000 1.024 8.033 nSat 341 2468
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!