NTPsec

c-ntpsec-72-hour-stats

Report generated: Thu Aug 13 05:02:24 2020 UTC
Start Time: Mon Aug 10 05:02:22 2020 UTC
End Time: Thu Aug 13 05:02:22 2020 UTC
Report published: Wed Aug 12 22:02:39 2020 PDT
Report Period: 3.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 -3,645.000 -836.000 -612.000 -36.000 641.000 939.000 2,268.000 1,253.000 1,775.000 386.837 -17.816 ns -4.167 11.4
Local Clock Frequency Offset -5.418 -5.417 -5.408 -5.265 -5.195 -5.166 -5.157 0.213 0.251 0.071 -5.287 ppm -4.381e+05 3.329e+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 83.000 114.000 134.000 195.000 288.000 381.000 2,139.000 154.000 267.000 87.080 205.113 ns 17.61 264.4

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.025 0.036 0.043 0.079 0.174 0.349 6.337 0.131 0.313 0.165 0.100 ppb 19.75 545.3

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 -3,645.000 -836.000 -612.000 -36.000 641.000 939.000 2,268.000 1,253.000 1,775.000 386.837 -17.816 ns -4.167 11.4

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.418 -5.417 -5.408 -5.265 -5.195 -5.166 -5.157 0.213 0.251 0.071 -5.287 ppm -4.381e+05 3.329e+07
Temp ZONE0 56.920 56.920 57.458 59.072 60.686 61.762 62.300 3.228 4.842 1.118 59.205 °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 6.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.146 9.372 nSat 391.1 2964
TDOP 0.520 0.550 0.610 0.850 1.360 1.560 2.470 0.750 1.010 0.227 0.882 33.69 137.7

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 -1.253 0.255 1.085 1.671 6.745 8.532 21.211 5.660 8.277 1.943 2.284 ms 4.373 29.24

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.131 -1.156 -0.505 0.340 4.636 7.308 41.652 5.141 8.464 2.073 0.837 ms 7.464 149.7

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 -77.431 35.564 61.831 147.037 198.899 218.164 279.069 137.068 182.600 41.804 140.104 µs 19.46 61.41

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.776 2.080 2.549 8.205 11.004 28.077 6.126 9.228 2.420 3.558 ms 4.948 34.12

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 0.684 1.616 1.945 2.402 7.515 11.426 27.832 5.570 9.809 2.507 3.391 ms 5.561 40.81

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 0.990 1.637 2.042 2.455 6.849 8.396 12.623 4.807 6.759 1.524 3.015 ms 6.461 27.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 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 2.528 3.245 3.667 4.824 10.178 11.943 21.645 6.511 8.698 2.057 5.356 ms 11.8 55.24

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) 1.372 2.061 2.373 2.920 8.160 10.729 40.611 5.788 8.668 2.202 3.571 ms 9.091 116.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 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) -16.442 0.268 0.734 1.833 6.534 9.473 34.164 5.800 9.205 2.378 2.559 ms 3.971 50.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 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) -72.876 -66.927 -62.948 -54.554 -46.169 -44.029 -40.355 16.779 22.898 5.139 -54.579 ms -1604 1.906e+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) -3,646.000 -837.000 -613.000 -37.000 644.000 946.000 2,269.000 1,257.000 1,783.000 389.991 -17.051 ns -4.152 11.53

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.266 0.405 2.456 11.089 30.800 186.576 10.683 30.534 8.971 4.803 ms 10.07 182.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 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.366 0.672 2.837 12.858 44.448 121.709 12.186 44.082 8.683 5.340 ms 6.53 75.54

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.023 0.042 0.177 8.691 8.934 268.476 8.649 8.911 7.170 1.469 ms 26.13 958.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 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.195 0.266 0.432 4.231 35.691 174.450 199.649 35.259 174.184 24.661 10.320 ms 3.198 21.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 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.136 0.267 0.401 7.565 167.375 187.252 194.054 166.973 186.985 53.789 34.751 ms 0.4871 2.656

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.269 0.458 2.790 15.299 29.255 69.127 14.840 28.986 6.678 5.128 ms 4.049 35.29

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.456 0.685 4.022 15.300 64.351 83.178 14.615 63.896 9.361 6.284 ms 3.976 27.57

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.235 0.401 2.744 16.038 60.041 116.947 15.637 59.806 10.320 5.820 ms 4.383 38.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 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.260 0.414 3.012 16.005 39.089 73.466 15.591 38.829 7.533 5.628 ms 3.562 26.82

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.211 0.333 0.942 3.127 5.780 9.705 2.794 5.569 1.024 1.228 ms 3.355 15.24

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 81.000 110.000 233.000 521.000 720.000 4,316.000 411.000 639.000 156.703 267.320 ns 7.824 99.32

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.418 -5.417 -5.408 -5.265 -5.195 -5.166 -5.157 0.213 0.251 0.071 -5.287 ppm -4.381e+05 3.329e+07
Local Clock Time Offset -3,645.000 -836.000 -612.000 -36.000 641.000 939.000 2,268.000 1,253.000 1,775.000 386.837 -17.816 ns -4.167 11.4
Local RMS Frequency Jitter 0.025 0.036 0.043 0.079 0.174 0.349 6.337 0.131 0.313 0.165 0.100 ppb 19.75 545.3
Local RMS Time Jitter 83.000 114.000 134.000 195.000 288.000 381.000 2,139.000 154.000 267.000 87.080 205.113 ns 17.61 264.4
Server Jitter 162.159.200.1 0.000 0.266 0.405 2.456 11.089 30.800 186.576 10.683 30.534 8.971 4.803 ms 10.07 182.1
Server Jitter 173.11.101.155 0.000 0.366 0.672 2.837 12.858 44.448 121.709 12.186 44.082 8.683 5.340 ms 6.53 75.54
Server Jitter 192.168.1.10 0.000 0.023 0.042 0.177 8.691 8.934 268.476 8.649 8.911 7.170 1.469 ms 26.13 958.1
Server Jitter 2001:6b0:123::43 0.195 0.266 0.432 4.231 35.691 174.450 199.649 35.259 174.184 24.661 10.320 ms 3.198 21.6
Server Jitter 2001:6b0:123::44 0.136 0.267 0.401 7.565 167.375 187.252 194.054 166.973 186.985 53.789 34.751 ms 0.4871 2.656
Server Jitter 204.123.2.5 0.000 0.269 0.458 2.790 15.299 29.255 69.127 14.840 28.986 6.678 5.128 ms 4.049 35.29
Server Jitter 2405:fc00:0:1::123 0.000 0.456 0.685 4.022 15.300 64.351 83.178 14.615 63.896 9.361 6.284 ms 3.976 27.57
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.235 0.401 2.744 16.038 60.041 116.947 15.637 59.806 10.320 5.820 ms 4.383 38.65
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.000 0.260 0.414 3.012 16.005 39.089 73.466 15.591 38.829 7.533 5.628 ms 3.562 26.82
Server Jitter SHM(0) 0.000 0.211 0.333 0.942 3.127 5.780 9.705 2.794 5.569 1.024 1.228 ms 3.355 15.24
Server Jitter SHM(1) 0.000 81.000 110.000 233.000 521.000 720.000 4,316.000 411.000 639.000 156.703 267.320 ns 7.824 99.32
Server Offset 162.159.200.1 -1.253 0.255 1.085 1.671 6.745 8.532 21.211 5.660 8.277 1.943 2.284 ms 4.373 29.24
Server Offset 173.11.101.155 -2.131 -1.156 -0.505 0.340 4.636 7.308 41.652 5.141 8.464 2.073 0.837 ms 7.464 149.7
Server Offset 192.168.1.10 -77.431 35.564 61.831 147.037 198.899 218.164 279.069 137.068 182.600 41.804 140.104 µs 19.46 61.41
Server Offset 2001:6b0:123::43 -4.940 1.776 2.080 2.549 8.205 11.004 28.077 6.126 9.228 2.420 3.558 ms 4.948 34.12
Server Offset 2001:6b0:123::44 0.684 1.616 1.945 2.402 7.515 11.426 27.832 5.570 9.809 2.507 3.391 ms 5.561 40.81
Server Offset 204.123.2.5 0.990 1.637 2.042 2.455 6.849 8.396 12.623 4.807 6.759 1.524 3.015 ms 6.461 27.03
Server Offset 2405:fc00:0:1::123 2.528 3.245 3.667 4.824 10.178 11.943 21.645 6.511 8.698 2.057 5.356 ms 11.8 55.24
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 1.372 2.061 2.373 2.920 8.160 10.729 40.611 5.788 8.668 2.202 3.571 ms 9.091 116.2
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) -16.442 0.268 0.734 1.833 6.534 9.473 34.164 5.800 9.205 2.378 2.559 ms 3.971 50.2
Server Offset SHM(0) -72.876 -66.927 -62.948 -54.554 -46.169 -44.029 -40.355 16.779 22.898 5.139 -54.579 ms -1604 1.906e+04
Server Offset SHM(1) -3,646.000 -837.000 -613.000 -37.000 644.000 946.000 2,269.000 1,257.000 1,783.000 389.991 -17.051 ns -4.152 11.53
TDOP 0.520 0.550 0.610 0.850 1.360 1.560 2.470 0.750 1.010 0.227 0.882 33.69 137.7
Temp ZONE0 56.920 56.920 57.458 59.072 60.686 61.762 62.300 3.228 4.842 1.118 59.205 °C
nSats 6.000 7.000 8.000 9.000 11.000 12.000 12.000 3.000 5.000 1.146 9.372 nSat 391.1 2964
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!