NTPsec

B-ntpsec-1-hour-stats

Report generated: Sat Nov 26 20:03:10 2022 UTC
Start Time: Sat Nov 26 19:02:42 2022 UTC
End Time: Sat Nov 26 20:03:10 2022 UTC
Report published: Sat Nov 26 12:03:16 2022 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 -617.000 -512.000 -318.000 116.000 512.000 680.000 782.000 830.000 1,192.000 264.567 103.969 ns -2.138 5.088
Local Clock Frequency Offset -5.186 -5.185 -5.183 -5.174 -5.164 -5.163 -5.163 0.0193 0.022 0.0064 -5.175 ppm -5.382e+08 4.378e+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 240.000 252.000 268.000 354.000 473.000 504.000 537.000 205.000 252.000 62.731 360.845 ns 121.9 654

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 78.000 87.000 98.000 136.000 179.000 189.000 202.000 81.000 102.000 25.304 137.115 10e-12 99.65 502.7

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 -617.000 -512.000 -318.000 116.000 512.000 680.000 782.000 830.000 1,192.000 264.567 103.969 ns -2.138 5.088

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.186 -5.185 -5.183 -5.174 -5.164 -5.163 -5.163 0.0193 0.022 0.0064 -5.175 ppm -5.382e+08 4.378e+11
Temp ZONE0 47.236 47.236 47.236 47.774 48.312 48.850 48.850 1.076 1.614 0.361 47.997 °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 9.000 9.000 9.000 10.000 11.000 11.000 11.000 2.000 2.000 0.733 9.932 nSat 2012 2.571e+04
TDOP 0.600 0.600 0.600 0.640 0.950 0.950 0.950 0.350 0.350 0.130 0.714 105.7 549.8

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 2.667 2.667 2.667 2.937 2.937 2.937 2.937 0.270 0.270 0.135 2.802 ms 7750 1.541e+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 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.306 2.306 2.306 3.045 3.567 3.567 3.567 1.261 1.261 0.278 3.003 ms 968.8 9765

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.365 2.365 2.365 2.742 2.971 2.971 2.971 0.606 0.606 0.173 2.703 ms 3180 4.716e+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 -516.498 -516.498 -516.498 -206.473 630.232 630.232 630.232 1,146.730 1,146.730 311.095 -109.921 µs -5.351 11.86

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.814 1.814 1.814 2.415 2.574 2.574 2.574 0.760 0.760 0.327 2.268 ms 225.7 1435

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 -297.300 -297.300 -46.100 167.692 324.272 362.224 362.224 370.372 659.524 110.986 155.485 µs 0.404 4.336

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.096 2.096 2.096 2.628 3.084 3.084 3.084 0.987 0.987 0.242 2.639 ms 1002 1.022e+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 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 2.450 2.450 2.450 2.786 3.468 3.468 3.468 1.018 1.018 0.291 2.831 ms 688.3 6242

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) -399.163 -392.203 -387.746 -368.682 -345.441 -334.486 -317.921 42.304 57.717 13.091 -368.134 ms -2.478e+04 7.242e+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) -618.000 -513.000 -319.000 117.000 513.000 681.000 783.000 832.000 1,194.000 265.334 104.236 ns -2.141 5.088

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 305.464 305.464 305.464 445.110 445.110 445.110 445.110 139.646 139.646 69.823 375.287 µs 96.86 482.1

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.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.352 0.352 0.352 0.782 13.654 13.654 13.654 13.302 13.302 4.807 2.880 ms 0.5101 2.319

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.355 0.355 0.355 0.746 1.561 1.561 1.561 1.206 1.206 0.337 0.815 ms 7.985 23.72

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 1.061 1.061 1.061 1.249 3.029 3.029 3.029 1.968 1.968 0.610 1.553 ms 9.799 33.07

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.837 0.837 0.837 0.858 1.017 1.017 1.017 0.180 0.180 0.080 0.904 ms 1110 1.172e+04

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.130 0.130 0.158 0.309 0.730 1.327 1.327 0.571 1.197 0.175 0.341 ms 6.068 27.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 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.174 0.174 0.174 1.181 2.017 2.017 2.017 1.843 1.843 0.615 0.955 ms 2.058 4.129

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 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 0.343 0.343 0.343 1.168 1.854 1.854 1.854 1.511 1.511 0.529 1.087 ms 4.243 9.113

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) 2.671 3.584 4.431 9.765 29.258 37.146 40.692 24.827 33.563 7.792 12.433 ms 3.349 9.938

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) 115.000 143.000 174.000 319.000 573.000 714.000 894.000 399.000 571.000 125.848 342.831 ns 11.3 38.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -5.186 -5.185 -5.183 -5.174 -5.164 -5.163 -5.163 0.0193 0.022 0.0064 -5.175 ppm -5.382e+08 4.378e+11
Local Clock Time Offset -617.000 -512.000 -318.000 116.000 512.000 680.000 782.000 830.000 1,192.000 264.567 103.969 ns -2.138 5.088
Local RMS Frequency Jitter 78.000 87.000 98.000 136.000 179.000 189.000 202.000 81.000 102.000 25.304 137.115 10e-12 99.65 502.7
Local RMS Time Jitter 240.000 252.000 268.000 354.000 473.000 504.000 537.000 205.000 252.000 62.731 360.845 ns 121.9 654
Server Jitter 104.131.155.175 305.464 305.464 305.464 445.110 445.110 445.110 445.110 139.646 139.646 69.823 375.287 µs 96.86 482.1
Server Jitter 162.159.200.123 0.352 0.352 0.352 0.782 13.654 13.654 13.654 13.302 13.302 4.807 2.880 ms 0.5101 2.319
Server Jitter 169.229.128.134 0.355 0.355 0.355 0.746 1.561 1.561 1.561 1.206 1.206 0.337 0.815 ms 7.985 23.72
Server Jitter 173.11.101.155 1.061 1.061 1.061 1.249 3.029 3.029 3.029 1.968 1.968 0.610 1.553 ms 9.799 33.07
Server Jitter 178.62.68.79 0.837 0.837 0.837 0.858 1.017 1.017 1.017 0.180 0.180 0.080 0.904 ms 1110 1.172e+04
Server Jitter 192.168.1.10 0.130 0.130 0.158 0.309 0.730 1.327 1.327 0.571 1.197 0.175 0.341 ms 6.068 27.27
Server Jitter 216.218.254.202 0.174 0.174 0.174 1.181 2.017 2.017 2.017 1.843 1.843 0.615 0.955 ms 2.058 4.129
Server Jitter 66.220.9.122 0.343 0.343 0.343 1.168 1.854 1.854 1.854 1.511 1.511 0.529 1.087 ms 4.243 9.113
Server Jitter SHM(0) 2.671 3.584 4.431 9.765 29.258 37.146 40.692 24.827 33.563 7.792 12.433 ms 3.349 9.938
Server Jitter SHM(1) 115.000 143.000 174.000 319.000 573.000 714.000 894.000 399.000 571.000 125.848 342.831 ns 11.3 38.09
Server Offset 104.131.155.175 2.667 2.667 2.667 2.937 2.937 2.937 2.937 0.270 0.270 0.135 2.802 ms 7750 1.541e+05
Server Offset 162.159.200.123 2.306 2.306 2.306 3.045 3.567 3.567 3.567 1.261 1.261 0.278 3.003 ms 968.8 9765
Server Offset 169.229.128.134 2.365 2.365 2.365 2.742 2.971 2.971 2.971 0.606 0.606 0.173 2.703 ms 3180 4.716e+04
Server Offset 173.11.101.155 -516.498 -516.498 -516.498 -206.473 630.232 630.232 630.232 1,146.730 1,146.730 311.095 -109.921 µs -5.351 11.86
Server Offset 178.62.68.79 1.814 1.814 1.814 2.415 2.574 2.574 2.574 0.760 0.760 0.327 2.268 ms 225.7 1435
Server Offset 192.168.1.10 -297.300 -297.300 -46.100 167.692 324.272 362.224 362.224 370.372 659.524 110.986 155.485 µs 0.404 4.336
Server Offset 216.218.254.202 2.096 2.096 2.096 2.628 3.084 3.084 3.084 0.987 0.987 0.242 2.639 ms 1002 1.022e+04
Server Offset 66.220.9.122 2.450 2.450 2.450 2.786 3.468 3.468 3.468 1.018 1.018 0.291 2.831 ms 688.3 6242
Server Offset SHM(0) -399.163 -392.203 -387.746 -368.682 -345.441 -334.486 -317.921 42.304 57.717 13.091 -368.134 ms -2.478e+04 7.242e+05
Server Offset SHM(1) -618.000 -513.000 -319.000 117.000 513.000 681.000 783.000 832.000 1,194.000 265.334 104.236 ns -2.141 5.088
TDOP 0.600 0.600 0.600 0.640 0.950 0.950 0.950 0.350 0.350 0.130 0.714 105.7 549.8
Temp ZONE0 47.236 47.236 47.236 47.774 48.312 48.850 48.850 1.076 1.614 0.361 47.997 °C
nSats 9.000 9.000 9.000 10.000 11.000 11.000 11.000 2.000 2.000 0.733 9.932 nSat 2012 2.571e+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!