NTPsec

C-ntpsec-1-hour-stats

Report generated: Fri Oct 22 17:02:10 2021 UTC
Start Time: Fri Oct 22 16:01:42 2021 UTC
End Time: Fri Oct 22 17:02:10 2021 UTC
Report published: Fri Oct 22 10:02:15 2021 PDT
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 -1,147.000 -627.000 -420.000 -75.000 363.000 540.000 697.000 783.000 1,167.000 250.451 -67.749 ns -6.059 17.67
Local Clock Frequency Offset -4.910 -4.909 -4.909 -4.908 -4.906 -4.906 -4.905 0.0035 0.0039 0.0012 -4.908 ppm -7.525e+10 3.177e+14

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 92.000 100.000 118.000 183.000 251.000 319.000 342.000 133.000 219.000 42.177 186.493 ns 51.02 221.5

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 31.000 33.000 39.000 57.000 96.000 145.000 151.000 57.000 112.000 20.022 61.855 10e-12 17.33 69.72

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,147.000 -627.000 -420.000 -75.000 363.000 540.000 697.000 783.000 1,167.000 250.451 -67.749 ns -6.059 17.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.910 -4.909 -4.909 -4.908 -4.906 -4.906 -4.905 0.0035 0.0039 0.0012 -4.908 ppm -7.525e+10 3.177e+14
Temp ZONE0 58.534 58.534 58.534 59.072 59.610 59.610 59.610 1.076 1.076 0.268 59.000 °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 9.000 9.000 11.000 12.000 12.000 2.000 4.000 0.937 9.567 nSat 808.5 7729
TDOP 0.510 0.510 0.600 0.760 0.780 1.180 1.180 0.180 0.670 0.097 0.725 291.8 2045

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.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.644 2.644 2.644 2.994 3.340 3.340 3.340 0.696 0.696 0.158 2.999 ms 5823 1.054e+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.212 2.212 2.212 2.429 2.633 2.633 2.633 0.421 0.421 0.120 2.425 ms 7120 1.377e+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 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -1.025 -1.025 -1.025 0.167 0.572 0.572 0.572 1.597 1.597 0.392 0.045 ms -4.534 14.03

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 91.978 91.978 107.227 155.317 233.894 240.352 240.352 126.667 148.374 34.800 157.619 µs 55.06 240

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.380 7.380 7.380 7.515 7.675 7.675 7.675 0.295 0.295 0.091 7.495 ms 5.333e+05 4.326e+07

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 10.754 10.754 10.754 10.848 11.026 11.026 11.026 0.272 0.272 0.084 10.857 ms 2.092e+06 2.676e+08

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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 2.284 2.284 2.284 2.492 2.795 2.795 2.795 0.512 0.512 0.152 2.507 ms 3728 5.829e+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 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.315 2.315 2.315 2.593 2.773 2.773 2.773 0.458 0.458 0.160 2.540 ms 3352 5.061e+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 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 -1.674 -1.674 -1.674 0.140 2.198 2.198 2.198 3.872 3.872 0.837 0.158 ms -2.606 8.513

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) -64.743 -63.857 -63.181 -54.713 -46.598 -46.219 -45.709 16.583 17.638 5.391 -55.169 ms -1452 1.669e+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,148.000 -628.000 -421.000 -76.000 364.000 541.000 698.000 785.000 1,169.000 251.155 -67.960 ns -6.056 17.63

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.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.279 0.279 0.279 1.174 7.387 7.387 7.387 7.109 7.109 2.565 2.792 ms 0.8313 1.977

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.185 0.185 0.185 0.408 1.252 1.252 1.252 1.066 1.066 0.392 0.620 ms 2.423 4.816

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.821 0.821 0.821 1.831 4.018 4.018 4.018 3.197 3.197 0.925 1.960 ms 5.62 15.68

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 10.975 10.975 42.219 134.090 646.245 850.555 850.555 604.026 839.580 171.970 186.992 µs 2.473 8.077

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.162 0.162 0.162 0.362 4.436 4.436 4.436 4.274 4.274 1.605 1.307 ms 0.7019 1.995

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 0.174 0.174 0.174 1.443 5.254 5.254 5.254 5.080 5.080 1.818 2.127 ms 1.315 2.786

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 203.123.48.219

peer jitter 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 203.123.48.219 0.343 0.343 0.343 2.311 9.800 9.800 9.800 9.458 9.458 3.710 3.431 ms 0.784 1.947

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.101 0.101 0.101 0.389 1.204 1.204 1.204 1.103 1.103 0.328 0.411 ms 2.337 6.429

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 32.505 32.505 32.505 58.410 70.903 70.903 70.903 38.398 38.398 11.601 54.692 ms 61.97 269.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 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.140 0.164 0.267 0.870 2.730 5.997 6.777 2.464 5.833 0.951 1.091 ms 3.427 16.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 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) 56.000 76.000 100.000 218.000 524.000 717.000 763.000 424.000 641.000 134.746 247.696 ns 4.703 15.84

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.910 -4.909 -4.909 -4.908 -4.906 -4.906 -4.905 0.0035 0.0039 0.0012 -4.908 ppm -7.525e+10 3.177e+14
Local Clock Time Offset -1,147.000 -627.000 -420.000 -75.000 363.000 540.000 697.000 783.000 1,167.000 250.451 -67.749 ns -6.059 17.67
Local RMS Frequency Jitter 31.000 33.000 39.000 57.000 96.000 145.000 151.000 57.000 112.000 20.022 61.855 10e-12 17.33 69.72
Local RMS Time Jitter 92.000 100.000 118.000 183.000 251.000 319.000 342.000 133.000 219.000 42.177 186.493 ns 51.02 221.5
Server Jitter 162.159.200.1 0.279 0.279 0.279 1.174 7.387 7.387 7.387 7.109 7.109 2.565 2.792 ms 0.8313 1.977
Server Jitter 169.229.128.134 0.185 0.185 0.185 0.408 1.252 1.252 1.252 1.066 1.066 0.392 0.620 ms 2.423 4.816
Server Jitter 173.11.101.155 0.821 0.821 0.821 1.831 4.018 4.018 4.018 3.197 3.197 0.925 1.960 ms 5.62 15.68
Server Jitter 192.168.1.10 10.975 10.975 42.219 134.090 646.245 850.555 850.555 604.026 839.580 171.970 186.992 µs 2.473 8.077
Server Jitter 194.58.202.211 0.162 0.162 0.162 0.362 4.436 4.436 4.436 4.274 4.274 1.605 1.307 ms 0.7019 1.995
Server Jitter 194.58.202.219 0.174 0.174 0.174 1.443 5.254 5.254 5.254 5.080 5.080 1.818 2.127 ms 1.315 2.786
Server Jitter 203.123.48.219 0.343 0.343 0.343 2.311 9.800 9.800 9.800 9.458 9.458 3.710 3.431 ms 0.784 1.947
Server Jitter 216.218.254.202 0.101 0.101 0.101 0.389 1.204 1.204 1.204 1.103 1.103 0.328 0.411 ms 2.337 6.429
Server Jitter 63.145.169.3 32.505 32.505 32.505 58.410 70.903 70.903 70.903 38.398 38.398 11.601 54.692 ms 61.97 269.1
Server Jitter SHM(0) 0.140 0.164 0.267 0.870 2.730 5.997 6.777 2.464 5.833 0.951 1.091 ms 3.427 16.55
Server Jitter SHM(1) 56.000 76.000 100.000 218.000 524.000 717.000 763.000 424.000 641.000 134.746 247.696 ns 4.703 15.84
Server Offset 162.159.200.1 2.644 2.644 2.644 2.994 3.340 3.340 3.340 0.696 0.696 0.158 2.999 ms 5823 1.054e+05
Server Offset 169.229.128.134 2.212 2.212 2.212 2.429 2.633 2.633 2.633 0.421 0.421 0.120 2.425 ms 7120 1.377e+05
Server Offset 173.11.101.155 -1.025 -1.025 -1.025 0.167 0.572 0.572 0.572 1.597 1.597 0.392 0.045 ms -4.534 14.03
Server Offset 192.168.1.10 91.978 91.978 107.227 155.317 233.894 240.352 240.352 126.667 148.374 34.800 157.619 µs 55.06 240
Server Offset 194.58.202.211 7.380 7.380 7.380 7.515 7.675 7.675 7.675 0.295 0.295 0.091 7.495 ms 5.333e+05 4.326e+07
Server Offset 194.58.202.219 10.754 10.754 10.754 10.848 11.026 11.026 11.026 0.272 0.272 0.084 10.857 ms 2.092e+06 2.676e+08
Server Offset 203.123.48.219 2.284 2.284 2.284 2.492 2.795 2.795 2.795 0.512 0.512 0.152 2.507 ms 3728 5.829e+04
Server Offset 216.218.254.202 2.315 2.315 2.315 2.593 2.773 2.773 2.773 0.458 0.458 0.160 2.540 ms 3352 5.061e+04
Server Offset 63.145.169.3 -1.674 -1.674 -1.674 0.140 2.198 2.198 2.198 3.872 3.872 0.837 0.158 ms -2.606 8.513
Server Offset SHM(0) -64.743 -63.857 -63.181 -54.713 -46.598 -46.219 -45.709 16.583 17.638 5.391 -55.169 ms -1452 1.669e+04
Server Offset SHM(1) -1,148.000 -628.000 -421.000 -76.000 364.000 541.000 698.000 785.000 1,169.000 251.155 -67.960 ns -6.056 17.63
TDOP 0.510 0.510 0.600 0.760 0.780 1.180 1.180 0.180 0.670 0.097 0.725 291.8 2045
Temp ZONE0 58.534 58.534 58.534 59.072 59.610 59.610 59.610 1.076 1.076 0.268 59.000 °C
nSats 8.000 8.000 9.000 9.000 11.000 12.000 12.000 2.000 4.000 0.937 9.567 nSat 808.5 7729
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!