NTPsec

Kong

Report generated: Sat Jul 27 06:49:00 2024 UTC
Start Time: Fri Jul 26 06:49:00 2024 UTC
End Time: Sat Jul 27 06:49:00 2024 UTC
Report Period: 1.0 days
Warning: plots clipped

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 -81.509 -58.152 -34.309 -2.088 26.716 46.414 291.183 61.025 104.566 26.895 -1.449 µs 0.2207 34.07
Local Clock Frequency Offset 12.508 12.512 12.525 12.792 12.962 13.019 13.037 0.437 0.507 0.146 12.747 ppm 6.464e+05 5.59e+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 6.583 7.625 10.182 18.102 31.991 62.259 84.538 21.809 54.634 9.116 19.623 µs 8.133 41.43

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 3.637 3.983 4.766 8.263 18.252 56.642 79.203 13.486 52.659 8.340 9.983 ppb 5.691 38.39

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 -81.509 -58.152 -34.309 -2.088 26.716 46.414 291.183 61.025 104.566 26.895 -1.449 µs 0.2207 34.07

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 12.508 12.512 12.525 12.792 12.962 13.019 13.037 0.437 0.507 0.146 12.747 ppm 6.464e+05 5.59e+07
Temp /dev/sda 50.000 50.000 51.000 52.000 52.000 53.000 53.000 1.000 3.000 0.629 51.585 °C
Temp /dev/sdb 39.000 39.000 40.000 41.000 42.000 43.000 43.000 2.000 4.000 0.705 40.679 °C
Temp LM0 48.000 49.000 49.000 54.000 58.000 59.000 59.000 9.000 10.000 2.688 53.923 °C
Temp LM1 46.875 47.000 47.375 48.875 53.625 58.750 75.750 6.250 11.750 2.513 49.343 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM11 64.000 64.000 64.000 65.000 66.000 66.000 66.000 2.000 2.000 0.583 65.125 °C
Temp LM12 4.000 5.000 5.000 8.000 12.000 14.000 15.000 7.000 9.000 2.095 8.125 °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 46.000 46.000 47.000 48.000 49.000 49.000 49.000 2.000 3.000 0.697 47.739 °C
Temp LM15 39.000 40.000 40.000 41.000 44.000 47.000 64.000 4.000 7.000 1.720 41.631 °C
Temp LM16 69.000 69.000 69.500 70.000 70.500 71.000 71.000 1.000 2.000 0.465 69.984 °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 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM19 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM2 46.000 46.500 47.000 49.000 52.500 61.000 74.250 5.500 14.500 2.570 49.483 °C
Temp LM20 46.875 47.000 47.375 48.875 53.625 58.875 75.875 6.250 11.875 2.476 49.334 °C
Temp LM21 69.125 69.250 69.500 70.250 70.750 71.000 71.250 1.250 1.750 0.427 70.139 °C
Temp LM22 39.000 39.000 39.000 41.000 42.000 42.000 43.000 3.000 3.000 0.732 40.617 °C
Temp LM23 65.850 66.850 67.850 71.850 74.850 74.850 74.850 7.000 8.000 2.041 71.742 °C
Temp LM3 50.000 50.000 50.000 52.000 52.000 53.000 53.000 2.000 3.000 0.651 51.589 °C
Temp LM4 50.850 50.850 51.850 52.850 54.850 55.850 57.850 3.000 5.000 0.971 53.418 °C
Temp LM5 50.850 50.850 51.850 52.850 54.850 55.850 58.850 3.000 5.000 0.991 53.425 °C
Temp LM6 59.850 59.850 60.850 62.850 64.850 68.850 74.850 4.000 9.000 1.584 62.850 °C
Temp LM7 50.850 50.850 51.850 53.850 54.850 54.850 58.850 3.000 4.000 0.985 53.456 °C
Temp LM8 46.000 46.000 47.000 48.000 49.000 49.000 49.000 2.000 3.000 0.681 47.742 °C
Temp LM9 40.000 40.500 40.500 42.000 43.000 44.500 48.000 2.500 4.000 0.915 41.786 °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 8.000 9.000 12.000 15.000 16.000 16.000 6.000 8.000 1.739 11.828 nSat 212.9 1339
TDOP 0.690 0.850 0.930 1.390 2.510 3.260 16.650 1.580 2.410 0.534 1.488 14.42 102

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) -86.926 -57.205 -37.669 18.421 54.744 77.115 353.737 92.413 134.320 32.546 17.298 µs 1.128 26.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: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) -169.244 -156.123 -108.647 -8.778 72.330 94.349 298.342 180.977 250.472 51.731 -12.104 µs -5.462 17.22

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 -466.901 -427.795 -324.692 -17.340 252.129 286.774 300.591 576.821 714.569 181.350 -41.219 µs -5.682 14.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 204.17.205.16

peer offset 204.17.205.16 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.16 -146.646 -77.952 -50.365 3.074 54.719 193.501 315.234 105.084 271.453 38.726 4.693 µs -1.303 15.29

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 -120.517 -86.545 -56.525 -29.956 1.381 198.710 274.994 57.906 285.255 32.283 -27.523 µs -6.466 39.92

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::1 (robusta.dcs1.biz)

peer offset 2405:fc00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00::1 (robusta.dcs1.biz) 5.720 5.882 6.058 6.550 7.316 7.699 8.442 1.258 1.817 0.397 6.604 ms 3880 6.148e+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 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) 0.160 0.191 0.634 1.701 2.514 2.962 3.079 1.880 2.771 0.572 1.618 ms 11.4 32.58

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) 1.550 1.614 1.753 2.158 2.629 2.900 2.927 0.877 1.286 0.273 2.164 ms 351.1 2578

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) 1.575 1.804 1.925 2.279 2.738 2.969 2.985 0.813 1.165 0.255 2.311 ms 548.9 4631

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) -168.849 -138.980 -136.817 -131.754 -127.061 -125.529 -123.555 9.756 13.451 3.019 -131.913 ms -8.939e+04 4.001e+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) 2.088 2.933 3.916 12.294 62.865 82.606 111.008 58.949 79.673 17.616 17.997 µs 2.358 8.738

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) 1.900 2.181 2.891 7.005 20.285 48.281 125.981 17.394 46.100 10.547 9.676 µs 6.246 57.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 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 1.136 2.268 3.528 10.466 28.531 58.616 127.691 25.003 56.348 12.062 13.200 µs 5.454 44.78

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

peer jitter 204.17.205.16 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.16 2.395 3.503 5.186 13.323 45.441 105.381 231.719 40.255 101.878 17.927 18.265 µs 5.01 44.55

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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 1.838 2.158 3.451 10.506 36.467 142.676 242.975 33.016 140.518 25.082 16.163 µs 5.006 39.15

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::1 (robusta.dcs1.biz)

peer jitter 2405:fc00::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.101 0.353 0.567 1.988 4.951 6.315 9.698 4.384 5.962 1.381 2.255 ms 3.316 11

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.182 0.260 0.339 0.735 1.564 5.728 6.874 1.225 5.468 0.743 0.900 ms 5.594 38.85

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.202 0.214 0.245 0.490 0.935 1.092 1.144 0.690 0.878 0.194 0.501 ms 9.667 30.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 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.119 0.162 0.244 0.465 0.949 1.067 1.126 0.705 0.905 0.220 0.517 ms 7.434 22.23

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.138 0.274 0.394 0.982 2.507 4.397 33.516 2.113 4.123 1.165 1.200 ms 10.5 192

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 12.508 12.512 12.525 12.792 12.962 13.019 13.037 0.437 0.507 0.146 12.747 ppm 6.464e+05 5.59e+07
Local Clock Time Offset -81.509 -58.152 -34.309 -2.088 26.716 46.414 291.183 61.025 104.566 26.895 -1.449 µs 0.2207 34.07
Local RMS Frequency Jitter 3.637 3.983 4.766 8.263 18.252 56.642 79.203 13.486 52.659 8.340 9.983 ppb 5.691 38.39
Local RMS Time Jitter 6.583 7.625 10.182 18.102 31.991 62.259 84.538 21.809 54.634 9.116 19.623 µs 8.133 41.43
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 2.088 2.933 3.916 12.294 62.865 82.606 111.008 58.949 79.673 17.616 17.997 µs 2.358 8.738
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 1.900 2.181 2.891 7.005 20.285 48.281 125.981 17.394 46.100 10.547 9.676 µs 6.246 57.82
Server Jitter 204.17.205.1 1.136 2.268 3.528 10.466 28.531 58.616 127.691 25.003 56.348 12.062 13.200 µs 5.454 44.78
Server Jitter 204.17.205.16 2.395 3.503 5.186 13.323 45.441 105.381 231.719 40.255 101.878 17.927 18.265 µs 5.01 44.55
Server Jitter 204.17.205.30 1.838 2.158 3.451 10.506 36.467 142.676 242.975 33.016 140.518 25.082 16.163 µs 5.006 39.15
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.101 0.353 0.567 1.988 4.951 6.315 9.698 4.384 5.962 1.381 2.255 ms 3.316 11
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.182 0.260 0.339 0.735 1.564 5.728 6.874 1.225 5.468 0.743 0.900 ms 5.594 38.85
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.202 0.214 0.245 0.490 0.935 1.092 1.144 0.690 0.878 0.194 0.501 ms 9.667 30.8
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.119 0.162 0.244 0.465 0.949 1.067 1.126 0.705 0.905 0.220 0.517 ms 7.434 22.23
Server Jitter SHM(0) 0.138 0.274 0.394 0.982 2.507 4.397 33.516 2.113 4.123 1.165 1.200 ms 10.5 192
Server Offset 2001:470:e815::24 (pi4.rellim.com) -86.926 -57.205 -37.669 18.421 54.744 77.115 353.737 92.413 134.320 32.546 17.298 µs 1.128 26.12
Server Offset 2001:470:e815::8 (spidey.rellim.com) -169.244 -156.123 -108.647 -8.778 72.330 94.349 298.342 180.977 250.472 51.731 -12.104 µs -5.462 17.22
Server Offset 204.17.205.1 -466.901 -427.795 -324.692 -17.340 252.129 286.774 300.591 576.821 714.569 181.350 -41.219 µs -5.682 14.12
Server Offset 204.17.205.16 -146.646 -77.952 -50.365 3.074 54.719 193.501 315.234 105.084 271.453 38.726 4.693 µs -1.303 15.29
Server Offset 204.17.205.30 -120.517 -86.545 -56.525 -29.956 1.381 198.710 274.994 57.906 285.255 32.283 -27.523 µs -6.466 39.92
Server Offset 2405:fc00::1 (robusta.dcs1.biz) 5.720 5.882 6.058 6.550 7.316 7.699 8.442 1.258 1.817 0.397 6.604 ms 3880 6.148e+04
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.160 0.191 0.634 1.701 2.514 2.962 3.079 1.880 2.771 0.572 1.618 ms 11.4 32.58
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 1.550 1.614 1.753 2.158 2.629 2.900 2.927 0.877 1.286 0.273 2.164 ms 351.1 2578
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 1.575 1.804 1.925 2.279 2.738 2.969 2.985 0.813 1.165 0.255 2.311 ms 548.9 4631
Server Offset SHM(0) -168.849 -138.980 -136.817 -131.754 -127.061 -125.529 -123.555 9.756 13.451 3.019 -131.913 ms -8.939e+04 4.001e+06
TDOP 0.690 0.850 0.930 1.390 2.510 3.260 16.650 1.580 2.410 0.534 1.488 14.42 102
Temp /dev/sda 50.000 50.000 51.000 52.000 52.000 53.000 53.000 1.000 3.000 0.629 51.585 °C
Temp /dev/sdb 39.000 39.000 40.000 41.000 42.000 43.000 43.000 2.000 4.000 0.705 40.679 °C
Temp LM0 48.000 49.000 49.000 54.000 58.000 59.000 59.000 9.000 10.000 2.688 53.923 °C
Temp LM1 46.875 47.000 47.375 48.875 53.625 58.750 75.750 6.250 11.750 2.513 49.343 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 25.000 25.000 0.000 0.000 0.000 25.000 °C
Temp LM11 64.000 64.000 64.000 65.000 66.000 66.000 66.000 2.000 2.000 0.583 65.125 °C
Temp LM12 4.000 5.000 5.000 8.000 12.000 14.000 15.000 7.000 9.000 2.095 8.125 °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 46.000 46.000 47.000 48.000 49.000 49.000 49.000 2.000 3.000 0.697 47.739 °C
Temp LM15 39.000 40.000 40.000 41.000 44.000 47.000 64.000 4.000 7.000 1.720 41.631 °C
Temp LM16 69.000 69.000 69.500 70.000 70.500 71.000 71.000 1.000 2.000 0.465 69.984 °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 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM19 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 °C
Temp LM2 46.000 46.500 47.000 49.000 52.500 61.000 74.250 5.500 14.500 2.570 49.483 °C
Temp LM20 46.875 47.000 47.375 48.875 53.625 58.875 75.875 6.250 11.875 2.476 49.334 °C
Temp LM21 69.125 69.250 69.500 70.250 70.750 71.000 71.250 1.250 1.750 0.427 70.139 °C
Temp LM22 39.000 39.000 39.000 41.000 42.000 42.000 43.000 3.000 3.000 0.732 40.617 °C
Temp LM23 65.850 66.850 67.850 71.850 74.850 74.850 74.850 7.000 8.000 2.041 71.742 °C
Temp LM3 50.000 50.000 50.000 52.000 52.000 53.000 53.000 2.000 3.000 0.651 51.589 °C
Temp LM4 50.850 50.850 51.850 52.850 54.850 55.850 57.850 3.000 5.000 0.971 53.418 °C
Temp LM5 50.850 50.850 51.850 52.850 54.850 55.850 58.850 3.000 5.000 0.991 53.425 °C
Temp LM6 59.850 59.850 60.850 62.850 64.850 68.850 74.850 4.000 9.000 1.584 62.850 °C
Temp LM7 50.850 50.850 51.850 53.850 54.850 54.850 58.850 3.000 4.000 0.985 53.456 °C
Temp LM8 46.000 46.000 47.000 48.000 49.000 49.000 49.000 2.000 3.000 0.681 47.742 °C
Temp LM9 40.000 40.500 40.500 42.000 43.000 44.500 48.000 2.500 4.000 0.915 41.786 °C
nSats 7.000 8.000 9.000 12.000 15.000 16.000 16.000 6.000 8.000 1.739 11.828 nSat 212.9 1339
Summary as CSV file


This server:

Motherboard:
OS: Gentoo unstable
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!