NTPsec

Kong

Report generated: Mon May 29 13:59:02 2023 UTC
Start Time: Mon May 22 13:59:01 2023 UTC
End Time: Mon May 29 13:59:01 2023 UTC
Report Period: 7.0 days

Daily stats   Weekly stats   Live GNSS Data   24 Hour Scatter Plots: ( )

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 -379.210 -96.862 -57.287 -1.767 54.550 115.160 674.819 111.837 212.022 41.093 -1.032 µs -1.518 44.28
Local Clock Frequency Offset 11.342 11.429 11.637 12.120 12.527 13.049 13.147 0.890 1.620 0.281 12.090 ppm 7.472e+04 3.151e+06

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.060 15.078 18.489 34.196 56.492 108.375 322.422 38.003 93.297 20.670 36.511 µs 9.479 94.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 0.000 6.833 8.678 16.839 41.646 61.097 85.916 32.968 54.264 10.673 19.576 ppb 5.133 20.04

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 -379.210 -96.862 -57.287 -1.767 54.550 115.160 674.819 111.837 212.022 41.093 -1.032 µs -1.518 44.28

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 11.342 11.429 11.637 12.120 12.527 13.049 13.147 0.890 1.620 0.281 12.090 ppm 7.472e+04 3.151e+06
Temp /dev/sda 45.000 46.000 46.000 48.000 50.000 51.000 51.000 4.000 5.000 0.932 47.768 °C
Temp /dev/sdb 34.000 35.000 35.000 36.000 38.000 40.000 41.000 3.000 5.000 0.991 36.501 °C
Temp LM0 47.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.859 53.753 °C
Temp LM1 72.625 74.000 74.500 76.750 85.375 87.875 88.500 10.875 13.875 2.803 77.309 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.089 25.008 °C
Temp LM11 60.000 60.000 60.000 61.000 62.000 62.000 62.000 2.000 2.000 0.394 61.002 °C
Temp LM12 4.000 6.000 7.000 8.000 9.000 10.000 11.000 2.000 4.000 0.623 8.159 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM14 61.500 63.000 63.500 65.500 74.000 76.500 77.500 10.500 13.500 2.809 66.114 °C
Temp LM15 64.500 65.000 65.500 66.000 66.500 67.000 67.000 1.000 2.000 0.397 65.923 °C
Temp LM16 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM17 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM18 72.375 74.000 74.500 76.750 85.375 87.750 88.500 10.875 13.750 2.797 77.306 °C
Temp LM19 64.750 65.000 65.500 66.000 66.750 67.250 67.375 1.250 2.250 0.377 66.063 °C
Temp LM2 64.000 73.250 74.250 76.500 84.750 87.500 88.750 10.500 14.250 2.853 76.964 °C
Temp LM20 34.000 35.000 35.000 36.000 38.000 40.000 41.000 3.000 5.000 0.957 36.558 °C
Temp LM21 63.850 63.850 64.850 66.850 68.850 69.850 70.850 4.000 6.000 1.411 67.007 °C
Temp LM3 45.000 46.000 46.000 48.000 50.000 51.000 51.000 4.000 5.000 0.934 47.772 °C
Temp LM4 46.850 47.850 48.850 48.850 50.850 51.850 54.850 2.000 4.000 0.808 49.256 °C
Temp LM5 46.850 47.850 48.850 48.850 50.850 51.850 54.850 2.000 4.000 0.809 49.279 °C
Temp LM6 54.850 55.850 55.850 56.850 59.850 66.850 70.850 4.000 11.000 1.776 57.578 °C
Temp LM7 46.850 47.850 48.850 48.850 50.850 51.850 54.850 2.000 4.000 0.808 49.297 °C
Temp LM8 42.000 43.000 43.000 44.000 45.000 45.000 45.000 2.000 2.000 0.486 44.086 °C
Temp LM9 42.000 42.500 42.500 44.000 51.000 53.500 54.500 8.500 11.000 2.214 44.530 °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 7.000 10.000 11.000 13.000 16.000 17.000 18.000 5.000 7.000 1.494 13.225 nSat 507.7 4175
TDOP 0.530 0.710 0.790 1.100 1.770 2.350 7.720 0.980 1.640 0.326 1.172 27.08 115.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 2001:470:e815::24 (pi4.rellim.com)

peer offset 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e815::24 (pi4.rellim.com) -0.449 -0.117 -0.075 -0.006 0.061 0.126 212.558 0.136 0.243 3.312 0.046 ms 60.23 3870

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:470:e815::8 (spidey.rellim.com)

peer offset 2001:470:e815::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:e815::8 (spidey.rellim.com) -1.709 -1.265 -0.727 0.074 0.552 0.901 212.539 1.279 2.165 6.587 0.233 ms 28.29 916.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 204.17.205.1

peer offset 204.17.205.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.1 -1.293 -0.904 -0.443 0.069 0.357 0.454 212.455 0.800 1.358 3.300 0.068 ms 60.06 3871

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

peer offset 204.17.205.30 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.30 -0.285 -0.103 -0.049 0.011 0.073 0.118 212.354 0.122 0.221 4.634 0.113 ms 41.92 1925

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 (ntpmon.dcs1.biz)

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 (ntpmon.dcs1.biz) 2.386 2.386 2.386 2.803 3.382 3.382 3.382 0.996 0.996 0.409 2.857 ms 233.4 1512

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) -4.092 -2.732 -2.091 -0.813 0.385 0.885 211.471 2.476 3.617 4.688 -0.723 ms 39.05 1800

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 2606:4700:f1::1 (time.cloudflare.com)

peer offset 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -3.821 -1.433 -0.730 0.631 1.758 2.265 214.418 2.488 3.698 4.716 0.688 ms 40.92 1853

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 2606:4700:f1::123 (time.cloudflare.com)

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -2.658 -2.658 -1.610 0.808 1.440 1.511 1.511 3.050 4.170 0.889 0.533 ms -3.08 10.55

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) -160.266 -138.530 -136.739 -132.422 -128.779 -127.479 80.520 7.959 11.051 2.784 -132.560 ms -1.15e+05 5.596e+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 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 2001:470:e815::24 (pi4.rellim.com)

peer jitter 2001:470:e815::24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 5.072 7.470 18.114 69.833 95.444 386.491 62.363 90.372 21.767 25.694 µs 3.867 33.66

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:470:e815::8 (spidey.rellim.com)

peer jitter 2001:470:e815::8 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 4.200 6.174 14.971 47.441 75.716 403.352 41.267 71.516 16.142 19.663 µs 6.155 94.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 204.17.205.1

peer jitter 204.17.205.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.1 0.000 4.444 6.599 16.944 49.735 73.208 793.162 43.136 68.764 25.673 21.427 µs 18.66 518.9

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

peer jitter 204.17.205.30 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.30 0.000 4.695 7.915 26.961 77.809 110.582 266.700 69.894 105.887 23.885 32.371 µs 3.706 20.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 2405:fc00:0:1::123 (ntpmon.dcs1.biz)

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 (ntpmon.dcs1.biz) 0.000 0.000 0.000 1.913 2.067 2.067 2.067 2.067 2.067 0.940 1.327 ms 0.6097 1.403

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.493 0.701 2.141 24.585 30.034 40.099 23.885 29.541 8.771 7.952 ms 0.6859 2.359

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 2606:4700:f1::1 (time.cloudflare.com)

peer jitter 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.456 0.660 2.144 24.615 34.193 86.212 23.955 33.737 9.174 7.628 ms 1.344 9.035

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 2606:4700:f1::123 (time.cloudflare.com)

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.775 0.775 0.899 1.372 19.297 20.344 20.344 18.398 19.569 5.988 4.044 ms 0.9362 3.222

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.264 0.388 0.943 2.333 3.908 213.958 1.945 3.644 2.051 1.160 ms 58.03 4787

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 11.342 11.429 11.637 12.120 12.527 13.049 13.147 0.890 1.620 0.281 12.090 ppm 7.472e+04 3.151e+06
Local Clock Time Offset -379.210 -96.862 -57.287 -1.767 54.550 115.160 674.819 111.837 212.022 41.093 -1.032 µs -1.518 44.28
Local RMS Frequency Jitter 0.000 6.833 8.678 16.839 41.646 61.097 85.916 32.968 54.264 10.673 19.576 ppb 5.133 20.04
Local RMS Time Jitter 0.060 15.078 18.489 34.196 56.492 108.375 322.422 38.003 93.297 20.670 36.511 µs 9.479 94.05
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 5.072 7.470 18.114 69.833 95.444 386.491 62.363 90.372 21.767 25.694 µs 3.867 33.66
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 4.200 6.174 14.971 47.441 75.716 403.352 41.267 71.516 16.142 19.663 µs 6.155 94.68
Server Jitter 204.17.205.1 0.000 4.444 6.599 16.944 49.735 73.208 793.162 43.136 68.764 25.673 21.427 µs 18.66 518.9
Server Jitter 204.17.205.30 0.000 4.695 7.915 26.961 77.809 110.582 266.700 69.894 105.887 23.885 32.371 µs 3.706 20.65
Server Jitter 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 0.000 0.000 0.000 1.913 2.067 2.067 2.067 2.067 2.067 0.940 1.327 ms 0.6097 1.403
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.493 0.701 2.141 24.585 30.034 40.099 23.885 29.541 8.771 7.952 ms 0.6859 2.359
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.456 0.660 2.144 24.615 34.193 86.212 23.955 33.737 9.174 7.628 ms 1.344 9.035
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.775 0.775 0.899 1.372 19.297 20.344 20.344 18.398 19.569 5.988 4.044 ms 0.9362 3.222
Server Jitter SHM(0) 0.000 0.264 0.388 0.943 2.333 3.908 213.958 1.945 3.644 2.051 1.160 ms 58.03 4787
Server Offset 2001:470:e815::24 (pi4.rellim.com) -0.449 -0.117 -0.075 -0.006 0.061 0.126 212.558 0.136 0.243 3.312 0.046 ms 60.23 3870
Server Offset 2001:470:e815::8 (spidey.rellim.com) -1.709 -1.265 -0.727 0.074 0.552 0.901 212.539 1.279 2.165 6.587 0.233 ms 28.29 916.8
Server Offset 204.17.205.1 -1.293 -0.904 -0.443 0.069 0.357 0.454 212.455 0.800 1.358 3.300 0.068 ms 60.06 3871
Server Offset 204.17.205.30 -0.285 -0.103 -0.049 0.011 0.073 0.118 212.354 0.122 0.221 4.634 0.113 ms 41.92 1925
Server Offset 2405:fc00:0:1::123 (ntpmon.dcs1.biz) 2.386 2.386 2.386 2.803 3.382 3.382 3.382 0.996 0.996 0.409 2.857 ms 233.4 1512
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -4.092 -2.732 -2.091 -0.813 0.385 0.885 211.471 2.476 3.617 4.688 -0.723 ms 39.05 1800
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -3.821 -1.433 -0.730 0.631 1.758 2.265 214.418 2.488 3.698 4.716 0.688 ms 40.92 1853
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -2.658 -2.658 -1.610 0.808 1.440 1.511 1.511 3.050 4.170 0.889 0.533 ms -3.08 10.55
Server Offset SHM(0) -160.266 -138.530 -136.739 -132.422 -128.779 -127.479 80.520 7.959 11.051 2.784 -132.560 ms -1.15e+05 5.596e+06
TDOP 0.530 0.710 0.790 1.100 1.770 2.350 7.720 0.980 1.640 0.326 1.172 27.08 115.7
Temp /dev/sda 45.000 46.000 46.000 48.000 50.000 51.000 51.000 4.000 5.000 0.932 47.768 °C
Temp /dev/sdb 34.000 35.000 35.000 36.000 38.000 40.000 41.000 3.000 5.000 0.991 36.501 °C
Temp LM0 47.000 49.000 50.000 54.000 58.000 59.000 59.000 8.000 10.000 2.859 53.753 °C
Temp LM1 72.625 74.000 74.500 76.750 85.375 87.875 88.500 10.875 13.875 2.803 77.309 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 26.000 0.000 0.000 0.089 25.008 °C
Temp LM11 60.000 60.000 60.000 61.000 62.000 62.000 62.000 2.000 2.000 0.394 61.002 °C
Temp LM12 4.000 6.000 7.000 8.000 9.000 10.000 11.000 2.000 4.000 0.623 8.159 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM14 61.500 63.000 63.500 65.500 74.000 76.500 77.500 10.500 13.500 2.809 66.114 °C
Temp LM15 64.500 65.000 65.500 66.000 66.500 67.000 67.000 1.000 2.000 0.397 65.923 °C
Temp LM16 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM17 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM18 72.375 74.000 74.500 76.750 85.375 87.750 88.500 10.875 13.750 2.797 77.306 °C
Temp LM19 64.750 65.000 65.500 66.000 66.750 67.250 67.375 1.250 2.250 0.377 66.063 °C
Temp LM2 64.000 73.250 74.250 76.500 84.750 87.500 88.750 10.500 14.250 2.853 76.964 °C
Temp LM20 34.000 35.000 35.000 36.000 38.000 40.000 41.000 3.000 5.000 0.957 36.558 °C
Temp LM21 63.850 63.850 64.850 66.850 68.850 69.850 70.850 4.000 6.000 1.411 67.007 °C
Temp LM3 45.000 46.000 46.000 48.000 50.000 51.000 51.000 4.000 5.000 0.934 47.772 °C
Temp LM4 46.850 47.850 48.850 48.850 50.850 51.850 54.850 2.000 4.000 0.808 49.256 °C
Temp LM5 46.850 47.850 48.850 48.850 50.850 51.850 54.850 2.000 4.000 0.809 49.279 °C
Temp LM6 54.850 55.850 55.850 56.850 59.850 66.850 70.850 4.000 11.000 1.776 57.578 °C
Temp LM7 46.850 47.850 48.850 48.850 50.850 51.850 54.850 2.000 4.000 0.808 49.297 °C
Temp LM8 42.000 43.000 43.000 44.000 45.000 45.000 45.000 2.000 2.000 0.486 44.086 °C
Temp LM9 42.000 42.500 42.500 44.000 51.000 53.500 54.500 8.500 11.000 2.214 44.530 °C
nSats 7.000 10.000 11.000 13.000 16.000 17.000 18.000 5.000 7.000 1.494 13.225 nSat 507.7 4175
Summary as CSV file


This server:

Motherboard:
OS: Gentoo unstable
GPS:
GPS/PPS server: gpsd
NTP server: NTPsec
../ntp.conf

Notes:

Feb 21 03:28:57 UTC 2019: New install

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!