NTPsec

C-ntpsec-1-hour-stats

Report generated: Sat May 28 17:02:16 2022 UTC
Start Time: Sat May 28 16:01:48 2022 UTC
End Time: Sat May 28 17:02:16 2022 UTC
Report published: Sat May 28 10:02:21 2022 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 -0.408 -0.338 -0.128 0.479 1.085 1.296 1.354 1.213 1.634 0.366 0.475 µs 0.9286 3.078
Local Clock Frequency Offset -6.535 -6.535 -6.533 -6.515 -6.499 -6.498 -6.498 0.034 0.037 0.0119 -6.515 ppm -1.645e+08 9.015e+10

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

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



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 131.000 138.000 147.000 238.000 379.000 477.000 522.000 232.000 339.000 77.676 246.727 ns 17.62 61.05

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 58.000 61.000 67.000 167.000 357.000 396.000 435.000 290.000 335.000 79.469 180.543 10e-12 6.953 21.66

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 -0.408 -0.338 -0.128 0.479 1.085 1.296 1.354 1.213 1.634 0.366 0.475 µs 0.9286 3.078

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 -6.535 -6.535 -6.533 -6.515 -6.499 -6.498 -6.498 0.034 0.037 0.0119 -6.515 ppm -1.645e+08 9.015e+10
Temp ZONE0 47.774 47.774 47.774 48.312 48.312 48.312 48.312 0.538 0.538 0.201 48.222 °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 10.000 10.000 10.000 10.000 12.000 12.000 12.000 2.000 2.000 0.883 10.767 nSat 1439 1.651e+04
TDOP 0.610 0.610 0.620 0.750 1.220 1.240 1.240 0.600 0.630 0.245 0.888 26.11 91.49

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 5.133 5.133 5.133 5.315 5.543 5.543 5.543 0.409 0.409 0.134 5.332 ms 5.875e+04 2.287e+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 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.371 2.371 2.371 2.648 2.761 2.761 2.761 0.390 0.390 0.124 2.617 ms 8113 1.638e+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 -172.221 -172.221 -172.221 330.977 577.005 577.005 577.005 749.226 749.226 231.667 273.737 µs 0.1304 1.848

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 143.803 143.803 177.694 227.427 299.026 308.803 308.803 121.332 165.000 39.618 236.920 µs 138.6 769.2

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

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

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

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



Server Offset 194.58.207.79

peer offset 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.79 7.719 7.719 7.719 8.014 8.268 8.268 8.268 0.549 0.549 0.144 8.002 ms 1.636e+05 8.95e+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.207.80

peer offset 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.207.80 7.562 7.562 7.562 7.940 8.231 8.231 8.231 0.669 0.669 0.140 7.940 ms 1.714e+05 9.525e+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.974 1.974 1.974 2.042 2.067 2.067 2.067 0.093 0.093 0.041 2.015 ms 1.148e+05 5.583e+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 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 2.074 2.074 2.074 2.904 4.390 4.390 4.390 2.317 2.317 0.593 2.937 ms 74.7 359.3

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.511 2.511 2.511 2.736 2.805 2.805 2.805 0.293 0.293 0.092 2.690 ms 2.237e+04 6.317e+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(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) -68.468 -68.375 -67.036 -59.111 -53.898 -53.725 -52.876 13.138 14.650 4.280 -60.066 ms -3444 5.248e+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) -0.409 -0.339 -0.129 0.480 1.086 1.297 1.355 1.215 1.636 0.366 0.476 µs 0.928 3.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 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.357 0.357 0.357 15.550 41.782 41.782 41.782 41.425 41.425 13.813 13.841 ms 0.9526 2.852

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.345 0.345 0.345 1.579 9.276 9.276 9.276 8.931 8.931 2.361 2.361 ms 1.874 5.878

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.338 1.338 1.338 1.927 18.926 18.926 18.926 17.588 17.588 5.328 4.867 ms 1.387 4.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 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.033 0.033 0.047 0.125 2.528 5.523 5.523 2.481 5.489 1.080 0.429 ms 2.126 11.6

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

peer jitter 194.58.207.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.79 0.343 0.343 0.343 17.428 33.355 33.355 33.355 33.012 33.012 10.705 14.753 ms 1.455 3.336

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

peer jitter 194.58.207.80 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.207.80 158.207 158.207 158.207 371.237 987.664 987.664 987.664 829.457 829.457 248.143 452.893 µs 3.756 9.219

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.663 0.663 0.663 17.709 17.743 17.743 17.743 17.081 17.081 8.474 9.253 ms 0.2765 1.051

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.999 0.999 0.999 32.830 201.973 201.973 201.973 200.974 200.974 71.949 59.623 ms 0.8817 2.34

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.379 0.379 0.379 1.079 29.682 29.682 29.682 29.303 29.303 9.355 5.591 ms 0.7728 3.251

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.493 0.539 0.739 1.626 4.705 5.965 5.975 3.966 5.426 1.116 1.951 ms 4.432 15.35

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.079 0.098 0.120 0.296 0.700 1.177 1.572 0.580 1.079 0.196 0.338 µs 4.67 20.3

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 -6.535 -6.535 -6.533 -6.515 -6.499 -6.498 -6.498 0.034 0.037 0.0119 -6.515 ppm -1.645e+08 9.015e+10
Local Clock Time Offset -0.408 -0.338 -0.128 0.479 1.085 1.296 1.354 1.213 1.634 0.366 0.475 µs 0.9286 3.078
Local RMS Frequency Jitter 58.000 61.000 67.000 167.000 357.000 396.000 435.000 290.000 335.000 79.469 180.543 10e-12 6.953 21.66
Local RMS Time Jitter 131.000 138.000 147.000 238.000 379.000 477.000 522.000 232.000 339.000 77.676 246.727 ns 17.62 61.05
Server Jitter 162.159.200.123 0.357 0.357 0.357 15.550 41.782 41.782 41.782 41.425 41.425 13.813 13.841 ms 0.9526 2.852
Server Jitter 169.229.128.134 0.345 0.345 0.345 1.579 9.276 9.276 9.276 8.931 8.931 2.361 2.361 ms 1.874 5.878
Server Jitter 173.11.101.155 1.338 1.338 1.338 1.927 18.926 18.926 18.926 17.588 17.588 5.328 4.867 ms 1.387 4.08
Server Jitter 192.168.1.10 0.033 0.033 0.047 0.125 2.528 5.523 5.523 2.481 5.489 1.080 0.429 ms 2.126 11.6
Server Jitter 194.58.207.79 0.343 0.343 0.343 17.428 33.355 33.355 33.355 33.012 33.012 10.705 14.753 ms 1.455 3.336
Server Jitter 194.58.207.80 158.207 158.207 158.207 371.237 987.664 987.664 987.664 829.457 829.457 248.143 452.893 µs 3.756 9.219
Server Jitter 204.17.205.24 0.663 0.663 0.663 17.709 17.743 17.743 17.743 17.081 17.081 8.474 9.253 ms 0.2765 1.051
Server Jitter 216.218.192.202 0.999 0.999 0.999 32.830 201.973 201.973 201.973 200.974 200.974 71.949 59.623 ms 0.8817 2.34
Server Jitter 216.218.254.202 0.379 0.379 0.379 1.079 29.682 29.682 29.682 29.303 29.303 9.355 5.591 ms 0.7728 3.251
Server Jitter SHM(0) 0.493 0.539 0.739 1.626 4.705 5.965 5.975 3.966 5.426 1.116 1.951 ms 4.432 15.35
Server Jitter SHM(1) 0.079 0.098 0.120 0.296 0.700 1.177 1.572 0.580 1.079 0.196 0.338 µs 4.67 20.3
Server Offset 162.159.200.123 5.133 5.133 5.133 5.315 5.543 5.543 5.543 0.409 0.409 0.134 5.332 ms 5.875e+04 2.287e+06
Server Offset 169.229.128.134 2.371 2.371 2.371 2.648 2.761 2.761 2.761 0.390 0.390 0.124 2.617 ms 8113 1.638e+05
Server Offset 173.11.101.155 -172.221 -172.221 -172.221 330.977 577.005 577.005 577.005 749.226 749.226 231.667 273.737 µs 0.1304 1.848
Server Offset 192.168.1.10 143.803 143.803 177.694 227.427 299.026 308.803 308.803 121.332 165.000 39.618 236.920 µs 138.6 769.2
Server Offset 194.58.207.79 7.719 7.719 7.719 8.014 8.268 8.268 8.268 0.549 0.549 0.144 8.002 ms 1.636e+05 8.95e+06
Server Offset 194.58.207.80 7.562 7.562 7.562 7.940 8.231 8.231 8.231 0.669 0.669 0.140 7.940 ms 1.714e+05 9.525e+06
Server Offset 204.17.205.24 1.974 1.974 1.974 2.042 2.067 2.067 2.067 0.093 0.093 0.041 2.015 ms 1.148e+05 5.583e+06
Server Offset 216.218.192.202 2.074 2.074 2.074 2.904 4.390 4.390 4.390 2.317 2.317 0.593 2.937 ms 74.7 359.3
Server Offset 216.218.254.202 2.511 2.511 2.511 2.736 2.805 2.805 2.805 0.293 0.293 0.092 2.690 ms 2.237e+04 6.317e+05
Server Offset SHM(0) -68.468 -68.375 -67.036 -59.111 -53.898 -53.725 -52.876 13.138 14.650 4.280 -60.066 ms -3444 5.248e+04
Server Offset SHM(1) -0.409 -0.339 -0.129 0.480 1.086 1.297 1.355 1.215 1.636 0.366 0.476 µs 0.928 3.08
TDOP 0.610 0.610 0.620 0.750 1.220 1.240 1.240 0.600 0.630 0.245 0.888 26.11 91.49
Temp ZONE0 47.774 47.774 47.774 48.312 48.312 48.312 48.312 0.538 0.538 0.201 48.222 °C
nSats 10.000 10.000 10.000 10.000 12.000 12.000 12.000 2.000 2.000 0.883 10.767 nSat 1439 1.651e+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!