NTPsec

c-ntpsec-14-day-stats

Report generated: Thu Aug 13 05:09:33 2020 UTC
Start Time: Thu Jul 30 05:09:25 2020 UTC
End Time: Thu Aug 13 05:09:25 2020 UTC
Report published: Wed Aug 12 22:10:05 2020 PDT
Report Period: 14.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 -29.736 -0.789 -0.525 -0.020 0.567 0.846 885.021 1.092 1.635 3.725 0.006 µs 202 4.488e+04
Local Clock Frequency Offset -5.842 -5.410 -5.357 -5.232 -5.160 -5.152 -4.355 0.197 0.258 0.060 -5.234 ppm -7.042e+05 6.267e+07

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.069 0.097 0.114 0.174 0.285 0.521 323.292 0.171 0.424 1.652 0.207 µs 182.8 3.514e+04

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.000 0.032 0.039 0.069 0.146 0.572 361.736 0.107 0.540 4.241 0.226 ppb 47.5 3015

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 -29.736 -0.789 -0.525 -0.020 0.567 0.846 885.021 1.092 1.635 3.725 0.006 µs 202 4.488e+04

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.842 -5.410 -5.357 -5.232 -5.160 -5.152 -4.355 0.197 0.258 0.060 -5.234 ppm -7.042e+05 6.267e+07
Temp ZONE0 56.920 57.458 57.996 60.148 62.300 62.838 69.294 4.304 5.380 1.177 60.503 °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 0.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.156 9.357 nSat 378.7 2841
TDOP 0.000 0.550 0.610 0.850 1.370 1.560 2.470 0.760 1.010 0.229 0.883 32.89 133.4

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 -0.044 -0.000 0.001 0.001 0.004 0.009 11.076 0.004 0.009 0.242 0.007 s 41.78 1911

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 164.67.62.194

peer offset 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 164.67.62.194 0.735 1.914 2.120 2.459 2.915 3.403 8.624 0.795 1.489 0.376 2.494 ms 201.9 1427

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 -0.018 -0.002 -0.001 0.000 0.003 0.007 11.064 0.003 0.009 0.241 0.006 s 41.88 1921

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 -233.580 -6.952 29.520 128.062 191.276 211.419 3,544.312 161.756 218.371 55.922 122.402 µs 18.25 885.8

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

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

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

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



Server Offset 2001:6b0:123::43

peer offset 2001:6b0:123::43 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:6b0:123::43 -4.940 1.702 2.079 2.666 7.358 12.287 28.077 5.279 10.585 2.132 3.444 ms 5.76 36.89

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 2001:6b0:123::44

peer offset 2001:6b0:123::44 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:6b0:123::44 -1.692 1.545 1.907 2.435 6.984 11.186 27.832 5.078 9.641 2.068 3.149 ms 5.853 40.25

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

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 -5.836 1.645 2.077 2.482 4.681 8.500 24.730 2.604 6.855 1.384 2.747 ms 9.668 90.42

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 2405:fc00:0:1::123

peer offset 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00:0:1::123 -16.298 -10.335 3.520 4.780 9.488 13.137 21.645 5.968 23.473 2.960 4.910 ms 0.4166 17.97

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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer offset 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -2.871 1.694 2.227 2.890 7.266 11.026 52.134 5.039 9.331 2.173 3.393 ms 11.05 185.1

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 2a01:3f7:2:202::202

peer offset 2a01:3f7:2:202::202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a01:3f7:2:202::202 1.199 1.199 1.199 4.431 6.261 6.261 6.261 5.063 5.063 1.565 3.501 ms 5.582 13.35

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 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com)

peer offset 2a03:b0c0:1:d0::1f9:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -111.706 -0.098 0.790 1.929 6.485 10.944 34.164 5.695 11.042 4.592 2.345 ms -16.22 354

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 47.51.249.154

peer offset 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 47.51.249.154 1.198 1.198 1.198 1.865 3.884 3.884 3.884 2.685 2.685 1.142 2.316 ms 4.702 11.14

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) -73.074 -67.629 -63.761 -54.944 -46.471 -44.214 -35.885 17.290 23.415 5.298 -55.045 ms -1512 1.762e+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.000 -0.000 -0.000 -0.000 0.000 0.000 11.065 0.000 0.000 0.056 0.000 s 192.4 3.779e+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 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.000 0.182 0.317 1.878 10.692 29.600 277.775 10.375 29.418 12.002 4.314 ms 13.99 280.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.



Server Jitter 164.67.62.194

peer jitter 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 164.67.62.194 0.000 0.221 0.338 1.541 9.267 13.455 67.158 8.929 13.234 4.585 3.142 ms 5.371 66.94

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.354 0.657 2.326 12.457 26.510 195.854 11.800 26.156 8.614 4.687 ms 11.07 204.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.



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.021 0.042 0.157 8.690 9.168 281.999 8.648 9.147 8.930 1.578 ms 19.88 532.5

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 2001:6b0:123::43

peer jitter 2001:6b0:123::43 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:6b0:123::43 0.000 0.253 0.428 2.700 16.019 121.596 234.542 15.590 121.343 20.120 7.233 ms 5.446 51.94

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 2001:6b0:123::44

peer jitter 2001:6b0:123::44 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:6b0:123::44 0.000 0.316 0.519 7.011 167.815 187.244 194.054 167.296 186.928 55.176 37.227 ms 0.4408 2.455

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

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.000 0.113 0.331 1.926 12.097 22.660 277.882 11.766 22.547 8.223 4.087 ms 18.13 569.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 2405:fc00:0:1::123

peer jitter 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2405:fc00:0:1::123 0.000 0.392 0.632 3.738 14.957 53.914 118.262 14.325 53.521 8.765 6.076 ms 4.685 40.01

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 2604:a880:1:20::17:5001 (ntp1.glypnod.com)

peer jitter 2604:a880:1:20::17:5001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.250 0.400 2.612 14.146 56.961 430.663 13.746 56.711 13.889 5.481 ms 16.4 446.2

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 2a01:3f7:2:202::202

peer jitter 2a01:3f7:2:202::202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a01:3f7:2:202::202 0.000 0.000 0.000 3.247 36.406 36.406 36.406 36.406 36.406 12.658 9.425 ms 0.3568 1.913

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 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com)

peer jitter 2a03:b0c0:1:d0::1f9:f001 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.000 0.278 0.429 2.804 14.572 37.258 93.120 14.144 36.980 7.514 5.305 ms 4.527 41.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 47.51.249.154

peer jitter 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 47.51.249.154 0.000 0.000 0.000 2.019 4.800 4.800 4.800 4.800 4.800 1.968 2.273 ms 0.6604 1.764

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 0.201 0.331 1.002 4.363 6.540 27.296 4.032 6.339 1.294 1.411 ms 2.863 14

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.069 0.097 0.219 0.519 1.007 46.676 0.422 0.938 0.512 0.275 µs 47.59 3509

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.842 -5.410 -5.357 -5.232 -5.160 -5.152 -4.355 0.197 0.258 0.060 -5.234 ppm -7.042e+05 6.267e+07
Local Clock Time Offset -29.736 -0.789 -0.525 -0.020 0.567 0.846 885.021 1.092 1.635 3.725 0.006 µs 202 4.488e+04
Local RMS Frequency Jitter 0.000 0.032 0.039 0.069 0.146 0.572 361.736 0.107 0.540 4.241 0.226 ppb 47.5 3015
Local RMS Time Jitter 0.069 0.097 0.114 0.174 0.285 0.521 323.292 0.171 0.424 1.652 0.207 µs 182.8 3.514e+04
Server Jitter 162.159.200.1 0.000 0.182 0.317 1.878 10.692 29.600 277.775 10.375 29.418 12.002 4.314 ms 13.99 280.3
Server Jitter 164.67.62.194 0.000 0.221 0.338 1.541 9.267 13.455 67.158 8.929 13.234 4.585 3.142 ms 5.371 66.94
Server Jitter 173.11.101.155 0.000 0.354 0.657 2.326 12.457 26.510 195.854 11.800 26.156 8.614 4.687 ms 11.07 204.3
Server Jitter 192.168.1.10 0.000 0.021 0.042 0.157 8.690 9.168 281.999 8.648 9.147 8.930 1.578 ms 19.88 532.5
Server Jitter 2001:6b0:123::43 0.000 0.253 0.428 2.700 16.019 121.596 234.542 15.590 121.343 20.120 7.233 ms 5.446 51.94
Server Jitter 2001:6b0:123::44 0.000 0.316 0.519 7.011 167.815 187.244 194.054 167.296 186.928 55.176 37.227 ms 0.4408 2.455
Server Jitter 204.123.2.5 0.000 0.113 0.331 1.926 12.097 22.660 277.882 11.766 22.547 8.223 4.087 ms 18.13 569.8
Server Jitter 2405:fc00:0:1::123 0.000 0.392 0.632 3.738 14.957 53.914 118.262 14.325 53.521 8.765 6.076 ms 4.685 40.01
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.250 0.400 2.612 14.146 56.961 430.663 13.746 56.711 13.889 5.481 ms 16.4 446.2
Server Jitter 2a01:3f7:2:202::202 0.000 0.000 0.000 3.247 36.406 36.406 36.406 36.406 36.406 12.658 9.425 ms 0.3568 1.913
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.000 0.278 0.429 2.804 14.572 37.258 93.120 14.144 36.980 7.514 5.305 ms 4.527 41.65
Server Jitter 47.51.249.154 0.000 0.000 0.000 2.019 4.800 4.800 4.800 4.800 4.800 1.968 2.273 ms 0.6604 1.764
Server Jitter SHM(0) 0.000 0.201 0.331 1.002 4.363 6.540 27.296 4.032 6.339 1.294 1.411 ms 2.863 14
Server Jitter SHM(1) 0.000 0.069 0.097 0.219 0.519 1.007 46.676 0.422 0.938 0.512 0.275 µs 47.59 3509
Server Offset 162.159.200.1 -0.044 -0.000 0.001 0.001 0.004 0.009 11.076 0.004 0.009 0.242 0.007 s 41.78 1911
Server Offset 164.67.62.194 0.735 1.914 2.120 2.459 2.915 3.403 8.624 0.795 1.489 0.376 2.494 ms 201.9 1427
Server Offset 173.11.101.155 -0.018 -0.002 -0.001 0.000 0.003 0.007 11.064 0.003 0.009 0.241 0.006 s 41.88 1921
Server Offset 192.168.1.10 -233.580 -6.952 29.520 128.062 191.276 211.419 3,544.312 161.756 218.371 55.922 122.402 µs 18.25 885.8
Server Offset 2001:6b0:123::43 -4.940 1.702 2.079 2.666 7.358 12.287 28.077 5.279 10.585 2.132 3.444 ms 5.76 36.89
Server Offset 2001:6b0:123::44 -1.692 1.545 1.907 2.435 6.984 11.186 27.832 5.078 9.641 2.068 3.149 ms 5.853 40.25
Server Offset 204.123.2.5 -5.836 1.645 2.077 2.482 4.681 8.500 24.730 2.604 6.855 1.384 2.747 ms 9.668 90.42
Server Offset 2405:fc00:0:1::123 -16.298 -10.335 3.520 4.780 9.488 13.137 21.645 5.968 23.473 2.960 4.910 ms 0.4166 17.97
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -2.871 1.694 2.227 2.890 7.266 11.026 52.134 5.039 9.331 2.173 3.393 ms 11.05 185.1
Server Offset 2a01:3f7:2:202::202 1.199 1.199 1.199 4.431 6.261 6.261 6.261 5.063 5.063 1.565 3.501 ms 5.582 13.35
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -111.706 -0.098 0.790 1.929 6.485 10.944 34.164 5.695 11.042 4.592 2.345 ms -16.22 354
Server Offset 47.51.249.154 1.198 1.198 1.198 1.865 3.884 3.884 3.884 2.685 2.685 1.142 2.316 ms 4.702 11.14
Server Offset SHM(0) -73.074 -67.629 -63.761 -54.944 -46.471 -44.214 -35.885 17.290 23.415 5.298 -55.045 ms -1512 1.762e+04
Server Offset SHM(1) -0.000 -0.000 -0.000 -0.000 0.000 0.000 11.065 0.000 0.000 0.056 0.000 s 192.4 3.779e+04
TDOP 0.000 0.550 0.610 0.850 1.370 1.560 2.470 0.760 1.010 0.229 0.883 32.89 133.4
Temp ZONE0 56.920 57.458 57.996 60.148 62.300 62.838 69.294 4.304 5.380 1.177 60.503 °C
nSats 0.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.156 9.357 nSat 378.7 2841
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!