NTPsec

B-ntpsec-3-hour-stats

Report generated: Wed Aug 17 20:05:32 2022 UTC
Start Time: Wed Aug 17 17:05:31 2022 UTC
End Time: Wed Aug 17 20:05:31 2022 UTC
Report published: Wed Aug 17 13:05:39 2022 PDT
Report Period: 0.1 days

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -8.023 -1.272 -0.628 0.063 0.600 1.107 2.300 1.228 2.379 0.517 0.011 µs -7.594 66.42
Local Clock Frequency Offset -5.406 -5.398 -5.395 -5.360 -5.315 -5.310 -5.307 0.080 0.088 0.028 -5.357 ppm -7.487e+06 1.465e+09

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 0.178 0.212 0.243 0.361 1.223 2.155 4.249 0.980 1.943 0.370 0.476 µs 4.789 28.3

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 0.205 0.435 0.499 0.696 1.943 3.390 5.684 1.444 2.955 0.542 0.859 ppb 5.642 30.96

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 -8.023 -1.272 -0.628 0.063 0.600 1.107 2.300 1.228 2.379 0.517 0.011 µs -7.594 66.42

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.406 -5.398 -5.395 -5.360 -5.315 -5.310 -5.307 0.080 0.088 0.028 -5.357 ppm -7.487e+06 1.465e+09
Temp ZONE0 45.084 45.084 45.084 46.160 46.160 47.236 47.236 1.076 2.152 0.424 45.958 °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.795 9.634 nSat 1408 1.601e+04
TDOP 0.600 0.610 0.630 0.870 1.180 1.260 1.350 0.550 0.650 0.156 0.891 119.3 637.5

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 3.031 3.031 3.031 3.419 3.684 3.684 3.684 0.653 0.653 0.215 3.387 ms 3276 4.909e+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 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 2.675 2.675 2.836 3.369 4.386 6.749 6.749 1.550 4.074 0.741 3.499 ms 65.48 328.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 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 1.712 1.712 1.956 2.512 2.888 2.948 2.948 0.932 1.236 0.243 2.486 ms 812.5 7733

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 -2.504 -2.504 -1.840 -0.155 1.403 2.718 2.718 3.243 5.221 0.984 -0.237 ms -5.249 13.99

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.506 1.506 1.506 2.812 6.730 6.730 6.730 5.223 5.223 1.657 3.444 ms 5.365 14.57

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 -1,136.417 -171.761 16.216 281.486 595.244 750.176 790.874 579.028 921.937 190.433 287.194 µs 0.2992 12.56

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

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

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

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



Server Offset 204.17.205.23

peer offset 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.23 1.140 1.140 1.140 1.854 4.207 4.207 4.207 3.067 3.067 0.876 1.992 ms 7.754 27.11

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

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 -4.837 -4.837 2.084 2.567 3.576 5.367 5.367 1.492 10.204 1.334 2.487 ms -0.9343 15.77

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.134 2.134 2.312 2.685 3.143 3.174 3.174 0.831 1.040 0.228 2.677 ms 1269 1.397e+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 45.33.37.82

peer offset 45.33.37.82 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 45.33.37.82 2.524 2.524 2.566 3.070 3.499 5.086 5.086 0.933 2.562 0.450 3.070 ms 216.6 1415

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) -412.412 -405.564 -396.874 -374.076 -349.079 -342.272 -320.747 47.795 63.292 14.774 -373.032 ms -1.816e+04 4.789e+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) -8.024 -1.273 -0.629 0.064 0.600 1.108 2.300 1.229 2.381 0.518 0.011 µs -7.582 66.19

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.000 0.000 0.000 1.248 2.288 2.288 2.288 2.288 2.288 0.670 1.143 ms 2.4 5.385

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.000 0.000 0.847 1.435 15.518 15.802 15.802 14.670 15.802 4.238 2.839 ms 1.598 5.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.



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.000 0.000 0.614 1.243 3.027 5.034 5.034 2.413 5.034 0.878 1.417 ms 4.054 15.65

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.000 0.000 0.805 2.378 6.786 7.657 7.657 5.981 7.657 1.637 2.705 ms 3.62 11.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 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.000 0.000 0.000 2.432 5.982 5.982 5.982 5.982 5.982 1.790 2.473 ms 1.841 4.347

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.000 0.184 0.385 0.909 5.141 8.752 20.658 4.756 8.569 2.206 1.612 ms 4.486 36.86

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

peer jitter 204.17.205.23 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.23 0.000 0.000 0.000 1.794 17.929 17.929 17.929 17.929 17.929 5.499 3.514 ms 1.054 3.585

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

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.000 0.000 0.323 1.716 4.199 8.413 8.413 3.876 8.413 1.417 1.889 ms 3.639 16.8

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.000 0.000 0.420 1.475 1.960 1.978 1.978 1.540 1.978 0.518 1.303 ms 7.263 17.03

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 45.33.37.82

peer jitter 45.33.37.82 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 45.33.37.82 0.000 0.000 0.460 1.697 14.237 14.267 14.267 13.777 14.267 2.973 2.447 ms 2.996 11.92

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.000 3.423 4.578 9.385 20.261 28.085 40.581 15.684 24.663 5.047 10.528 ms 5.938 20.4

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) 0.000 0.152 0.217 0.470 1.212 2.809 7.973 0.995 2.657 0.485 0.582 µs 5.783 51.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -5.406 -5.398 -5.395 -5.360 -5.315 -5.310 -5.307 0.080 0.088 0.028 -5.357 ppm -7.487e+06 1.465e+09
Local Clock Time Offset -8.023 -1.272 -0.628 0.063 0.600 1.107 2.300 1.228 2.379 0.517 0.011 µs -7.594 66.42
Local RMS Frequency Jitter 0.205 0.435 0.499 0.696 1.943 3.390 5.684 1.444 2.955 0.542 0.859 ppb 5.642 30.96
Local RMS Time Jitter 0.178 0.212 0.243 0.361 1.223 2.155 4.249 0.980 1.943 0.370 0.476 µs 4.789 28.3
Server Jitter 104.131.155.175 0.000 0.000 0.000 1.248 2.288 2.288 2.288 2.288 2.288 0.670 1.143 ms 2.4 5.385
Server Jitter 162.159.200.1 0.000 0.000 0.847 1.435 15.518 15.802 15.802 14.670 15.802 4.238 2.839 ms 1.598 5.28
Server Jitter 169.229.128.134 0.000 0.000 0.614 1.243 3.027 5.034 5.034 2.413 5.034 0.878 1.417 ms 4.054 15.65
Server Jitter 173.11.101.155 0.000 0.000 0.805 2.378 6.786 7.657 7.657 5.981 7.657 1.637 2.705 ms 3.62 11.31
Server Jitter 178.62.68.79 0.000 0.000 0.000 2.432 5.982 5.982 5.982 5.982 5.982 1.790 2.473 ms 1.841 4.347
Server Jitter 192.168.1.10 0.000 0.184 0.385 0.909 5.141 8.752 20.658 4.756 8.569 2.206 1.612 ms 4.486 36.86
Server Jitter 204.17.205.23 0.000 0.000 0.000 1.794 17.929 17.929 17.929 17.929 17.929 5.499 3.514 ms 1.054 3.585
Server Jitter 216.218.192.202 0.000 0.000 0.323 1.716 4.199 8.413 8.413 3.876 8.413 1.417 1.889 ms 3.639 16.8
Server Jitter 216.218.254.202 0.000 0.000 0.420 1.475 1.960 1.978 1.978 1.540 1.978 0.518 1.303 ms 7.263 17.03
Server Jitter 45.33.37.82 0.000 0.000 0.460 1.697 14.237 14.267 14.267 13.777 14.267 2.973 2.447 ms 2.996 11.92
Server Jitter SHM(0) 0.000 3.423 4.578 9.385 20.261 28.085 40.581 15.684 24.663 5.047 10.528 ms 5.938 20.4
Server Jitter SHM(1) 0.000 0.152 0.217 0.470 1.212 2.809 7.973 0.995 2.657 0.485 0.582 µs 5.783 51.1
Server Offset 104.131.155.175 3.031 3.031 3.031 3.419 3.684 3.684 3.684 0.653 0.653 0.215 3.387 ms 3276 4.909e+04
Server Offset 162.159.200.1 2.675 2.675 2.836 3.369 4.386 6.749 6.749 1.550 4.074 0.741 3.499 ms 65.48 328.5
Server Offset 169.229.128.134 1.712 1.712 1.956 2.512 2.888 2.948 2.948 0.932 1.236 0.243 2.486 ms 812.5 7733
Server Offset 173.11.101.155 -2.504 -2.504 -1.840 -0.155 1.403 2.718 2.718 3.243 5.221 0.984 -0.237 ms -5.249 13.99
Server Offset 178.62.68.79 1.506 1.506 1.506 2.812 6.730 6.730 6.730 5.223 5.223 1.657 3.444 ms 5.365 14.57
Server Offset 192.168.1.10 -1,136.417 -171.761 16.216 281.486 595.244 750.176 790.874 579.028 921.937 190.433 287.194 µs 0.2992 12.56
Server Offset 204.17.205.23 1.140 1.140 1.140 1.854 4.207 4.207 4.207 3.067 3.067 0.876 1.992 ms 7.754 27.11
Server Offset 216.218.192.202 -4.837 -4.837 2.084 2.567 3.576 5.367 5.367 1.492 10.204 1.334 2.487 ms -0.9343 15.77
Server Offset 216.218.254.202 2.134 2.134 2.312 2.685 3.143 3.174 3.174 0.831 1.040 0.228 2.677 ms 1269 1.397e+04
Server Offset 45.33.37.82 2.524 2.524 2.566 3.070 3.499 5.086 5.086 0.933 2.562 0.450 3.070 ms 216.6 1415
Server Offset SHM(0) -412.412 -405.564 -396.874 -374.076 -349.079 -342.272 -320.747 47.795 63.292 14.774 -373.032 ms -1.816e+04 4.789e+05
Server Offset SHM(1) -8.024 -1.273 -0.629 0.064 0.600 1.108 2.300 1.229 2.381 0.518 0.011 µs -7.582 66.19
TDOP 0.600 0.610 0.630 0.870 1.180 1.260 1.350 0.550 0.650 0.156 0.891 119.3 637.5
Temp ZONE0 45.084 45.084 45.084 46.160 46.160 47.236 47.236 1.076 2.152 0.424 45.958 °C
nSats 8.000 8.000 8.000 10.000 11.000 11.000 11.000 3.000 3.000 0.795 9.634 nSat 1408 1.601e+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!