NTPsec

Kong

Report generated: Tue Oct 8 13:59:01 2024 UTC
Start Time: Tue Oct 1 13:59:00 2024 UTC
End Time: Tue Oct 8 13:59:00 2024 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 -4.810 -0.135 -0.045 -0.002 0.041 0.176 67.418 0.086 0.311 2.112 0.075 ms 24.85 746.1
Local Clock Frequency Offset 12.155 12.397 12.472 12.887 14.032 14.158 14.228 1.560 1.761 0.377 12.921 ppm 3.688e+04 1.23e+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.004 0.009 0.011 0.020 0.053 1.532 23.836 0.041 1.523 1.108 0.116 ms 11.61 201.3

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 4.529 5.633 10.729 54.388 97.448 182.571 48.755 92.919 17.779 16.044 ppb 3.457 18.47

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 -4.810 -0.135 -0.045 -0.002 0.041 0.176 67.418 0.086 0.311 2.112 0.075 ms 24.85 746.1

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.155 12.397 12.472 12.887 14.032 14.158 14.228 1.560 1.761 0.377 12.921 ppm 3.688e+04 1.23e+06
Temp /dev/sda 45.000 46.000 46.000 49.000 51.000 52.000 53.000 5.000 6.000 1.359 48.800 °C
Temp /dev/sdb 35.000 35.000 36.000 38.000 40.000 41.000 42.000 4.000 6.000 1.270 37.629 °C
Temp LM0 47.000 49.000 49.000 53.000 58.000 59.000 60.000 9.000 10.000 2.717 53.499 °C
Temp LM1 40.000 46.500 47.125 49.500 74.500 76.875 85.375 27.375 30.375 6.920 51.591 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 26.000 26.000 0.000 1.000 0.113 25.013 °C
Temp LM11 63.000 63.000 63.000 65.000 66.000 66.000 67.000 3.000 3.000 0.814 64.663 °C
Temp LM12 2.000 3.000 4.000 5.000 9.000 11.000 37.000 5.000 8.000 2.258 5.860 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 26.000 26.000 0.000 1.000 0.134 25.018 °C
Temp LM14 44.000 45.000 45.000 47.000 48.000 48.000 49.000 3.000 3.000 0.965 46.597 °C
Temp LM15 35.000 39.000 39.000 41.000 63.000 65.000 74.000 24.000 26.000 5.994 42.585 °C
Temp LM16 68.500 68.500 68.500 70.000 70.500 71.000 72.000 2.000 2.500 0.622 69.760 °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 39.750 45.750 46.250 48.750 73.000 76.500 85.250 26.750 30.750 6.955 50.995 °C
Temp LM20 40.000 46.500 47.125 49.500 74.500 76.750 85.375 27.375 30.250 6.888 51.531 °C
Temp LM21 68.500 68.750 68.875 70.000 70.750 71.000 72.250 1.875 2.250 0.605 69.902 °C
Temp LM22 0.000 35.000 36.000 38.000 40.000 41.000 42.000 4.000 6.000 1.931 37.663 °C
Temp LM23 63.850 65.850 66.850 70.850 72.850 73.850 74.850 6.000 8.000 1.849 70.450 °C
Temp LM3 45.000 46.000 46.000 49.000 51.000 52.000 53.000 5.000 6.000 1.364 48.798 °C
Temp LM4 48.850 49.850 50.850 51.850 54.850 55.850 58.850 4.000 6.000 1.249 52.233 °C
Temp LM5 48.850 49.850 50.850 51.850 54.850 55.850 58.850 4.000 6.000 1.251 52.235 °C
Temp LM6 55.850 56.850 57.850 59.850 63.850 70.850 76.850 6.000 14.000 2.294 60.421 °C
Temp LM7 48.850 49.850 50.850 51.850 54.850 55.850 58.850 4.000 6.000 1.250 52.252 °C
Temp LM8 45.000 45.000 45.000 47.000 48.000 48.000 49.000 3.000 3.000 0.964 46.597 °C
Temp LM9 35.500 39.000 39.500 41.000 52.500 53.000 54.500 13.000 14.000 3.034 41.833 °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 8.000 9.000 12.000 14.000 15.000 18.000 5.000 7.000 1.503 11.868 nSat 348.7 2550
TDOP 0.660 0.850 0.940 1.310 2.390 3.370 22.360 1.450 2.520 0.489 1.436 15.72 94.88

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) -5.702 -0.120 -0.054 0.011 0.072 0.269 67.680 0.126 0.390 1.511 0.055 ms 33.17 1323

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) -5.708 -0.649 -0.217 -0.017 0.068 0.216 67.420 0.285 0.865 2.756 0.082 ms 19.24 461.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 -5.986 -0.674 -0.368 -0.023 0.266 0.508 67.170 0.634 1.182 1.490 0.002 ms 32.53 1314

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 -5.739 -0.167 -0.054 0.002 0.061 0.206 67.475 0.115 0.373 2.701 0.119 ms 19.82 484.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 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 -4.746 -0.327 -0.088 -0.014 0.034 0.209 67.438 0.122 0.536 1.725 0.031 ms 30.73 1139

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) -8.520 2.670 2.888 3.588 5.097 6.599 72.152 2.209 3.928 2.180 3.859 ms 27.29 799.3

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

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

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

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



Server Offset 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) -11.441 -8.073 -2.097 1.059 1.701 2.047 68.112 3.798 10.120 2.460 0.761 ms 8.616 298.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 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) 0.471 1.424 1.701 2.119 2.537 2.767 69.722 0.836 1.344 2.785 2.249 ms 20.9 472.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 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.129 1.324 1.612 2.159 2.576 2.780 3.535 0.963 1.456 0.295 2.134 ms 260.1 1735

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) -165.881 -138.996 -136.492 -132.008 -128.162 -126.513 -65.026 8.330 12.483 2.792 -132.145 ms -1.13e+05 5.468e+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 0.003 0.005 0.014 0.065 0.110 48.112 0.061 0.107 1.592 0.091 ms 20.9 548.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 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 0.002 0.003 0.008 0.032 0.134 55.727 0.029 0.132 1.769 0.086 ms 22.37 621.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 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 0.002 0.003 0.011 0.038 0.118 47.752 0.034 0.116 1.569 0.084 ms 21.12 559.4

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 0.000 0.003 0.005 0.015 0.050 0.153 55.967 0.044 0.150 1.747 0.096 ms 22.37 627.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 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 0.003 0.005 0.016 0.065 0.200 49.897 0.060 0.197 2.048 0.126 ms 17.27 378.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::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.000 0.284 0.402 1.413 6.141 11.543 55.193 5.740 11.259 2.908 2.197 ms 8.935 150.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 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.215 0.344 1.039 5.938 9.437 50.031 5.594 9.223 2.672 1.832 ms 8.16 127.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 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.172 0.241 0.671 5.209 11.007 52.266 4.969 10.835 3.455 1.549 ms 7.812 100.7

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.120 0.189 0.248 0.631 3.941 7.296 9.529 3.693 7.107 1.306 1.117 ms 2.52 11.58

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.291 0.417 1.011 2.539 6.303 35.300 2.122 6.012 1.187 1.243 ms 9.384 156.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset 12.155 12.397 12.472 12.887 14.032 14.158 14.228 1.560 1.761 0.377 12.921 ppm 3.688e+04 1.23e+06
Local Clock Time Offset -4.810 -0.135 -0.045 -0.002 0.041 0.176 67.418 0.086 0.311 2.112 0.075 ms 24.85 746.1
Local RMS Frequency Jitter 0.000 4.529 5.633 10.729 54.388 97.448 182.571 48.755 92.919 17.779 16.044 ppb 3.457 18.47
Local RMS Time Jitter 0.004 0.009 0.011 0.020 0.053 1.532 23.836 0.041 1.523 1.108 0.116 ms 11.61 201.3
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.000 0.003 0.005 0.014 0.065 0.110 48.112 0.061 0.107 1.592 0.091 ms 20.9 548.3
Server Jitter 2001:470:e815::8 (spidey.rellim.com) 0.000 0.002 0.003 0.008 0.032 0.134 55.727 0.029 0.132 1.769 0.086 ms 22.37 621.2
Server Jitter 204.17.205.1 0.000 0.002 0.003 0.011 0.038 0.118 47.752 0.034 0.116 1.569 0.084 ms 21.12 559.4
Server Jitter 204.17.205.16 0.000 0.003 0.005 0.015 0.050 0.153 55.967 0.044 0.150 1.747 0.096 ms 22.37 627.1
Server Jitter 204.17.205.30 0.000 0.003 0.005 0.016 0.065 0.200 49.897 0.060 0.197 2.048 0.126 ms 17.27 378.8
Server Jitter 2405:fc00::1 (robusta.dcs1.biz) 0.000 0.284 0.402 1.413 6.141 11.543 55.193 5.740 11.259 2.908 2.197 ms 8.935 150.2
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.000 0.215 0.344 1.039 5.938 9.437 50.031 5.594 9.223 2.672 1.832 ms 8.16 127.6
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.000 0.172 0.241 0.671 5.209 11.007 52.266 4.969 10.835 3.455 1.549 ms 7.812 100.7
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.120 0.189 0.248 0.631 3.941 7.296 9.529 3.693 7.107 1.306 1.117 ms 2.52 11.58
Server Jitter SHM(0) 0.000 0.291 0.417 1.011 2.539 6.303 35.300 2.122 6.012 1.187 1.243 ms 9.384 156.2
Server Offset 2001:470:e815::24 (pi4.rellim.com) -5.702 -0.120 -0.054 0.011 0.072 0.269 67.680 0.126 0.390 1.511 0.055 ms 33.17 1323
Server Offset 2001:470:e815::8 (spidey.rellim.com) -5.708 -0.649 -0.217 -0.017 0.068 0.216 67.420 0.285 0.865 2.756 0.082 ms 19.24 461.8
Server Offset 204.17.205.1 -5.986 -0.674 -0.368 -0.023 0.266 0.508 67.170 0.634 1.182 1.490 0.002 ms 32.53 1314
Server Offset 204.17.205.16 -5.739 -0.167 -0.054 0.002 0.061 0.206 67.475 0.115 0.373 2.701 0.119 ms 19.82 484.1
Server Offset 204.17.205.30 -4.746 -0.327 -0.088 -0.014 0.034 0.209 67.438 0.122 0.536 1.725 0.031 ms 30.73 1139
Server Offset 2405:fc00::1 (robusta.dcs1.biz) -8.520 2.670 2.888 3.588 5.097 6.599 72.152 2.209 3.928 2.180 3.859 ms 27.29 799.3
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) -11.441 -8.073 -2.097 1.059 1.701 2.047 68.112 3.798 10.120 2.460 0.761 ms 8.616 298.1
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 0.471 1.424 1.701 2.119 2.537 2.767 69.722 0.836 1.344 2.785 2.249 ms 20.9 472.8
Server Offset 2606:4700:f1::123 (time.cloudflare.com) 1.129 1.324 1.612 2.159 2.576 2.780 3.535 0.963 1.456 0.295 2.134 ms 260.1 1735
Server Offset SHM(0) -165.881 -138.996 -136.492 -132.008 -128.162 -126.513 -65.026 8.330 12.483 2.792 -132.145 ms -1.13e+05 5.468e+06
TDOP 0.660 0.850 0.940 1.310 2.390 3.370 22.360 1.450 2.520 0.489 1.436 15.72 94.88
Temp /dev/sda 45.000 46.000 46.000 49.000 51.000 52.000 53.000 5.000 6.000 1.359 48.800 °C
Temp /dev/sdb 35.000 35.000 36.000 38.000 40.000 41.000 42.000 4.000 6.000 1.270 37.629 °C
Temp LM0 47.000 49.000 49.000 53.000 58.000 59.000 60.000 9.000 10.000 2.717 53.499 °C
Temp LM1 40.000 46.500 47.125 49.500 74.500 76.875 85.375 27.375 30.375 6.920 51.591 °C
Temp LM10 25.000 25.000 25.000 25.000 25.000 26.000 26.000 0.000 1.000 0.113 25.013 °C
Temp LM11 63.000 63.000 63.000 65.000 66.000 66.000 67.000 3.000 3.000 0.814 64.663 °C
Temp LM12 2.000 3.000 4.000 5.000 9.000 11.000 37.000 5.000 8.000 2.258 5.860 °C
Temp LM13 25.000 25.000 25.000 25.000 25.000 26.000 26.000 0.000 1.000 0.134 25.018 °C
Temp LM14 44.000 45.000 45.000 47.000 48.000 48.000 49.000 3.000 3.000 0.965 46.597 °C
Temp LM15 35.000 39.000 39.000 41.000 63.000 65.000 74.000 24.000 26.000 5.994 42.585 °C
Temp LM16 68.500 68.500 68.500 70.000 70.500 71.000 72.000 2.000 2.500 0.622 69.760 °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 39.750 45.750 46.250 48.750 73.000 76.500 85.250 26.750 30.750 6.955 50.995 °C
Temp LM20 40.000 46.500 47.125 49.500 74.500 76.750 85.375 27.375 30.250 6.888 51.531 °C
Temp LM21 68.500 68.750 68.875 70.000 70.750 71.000 72.250 1.875 2.250 0.605 69.902 °C
Temp LM22 0.000 35.000 36.000 38.000 40.000 41.000 42.000 4.000 6.000 1.931 37.663 °C
Temp LM23 63.850 65.850 66.850 70.850 72.850 73.850 74.850 6.000 8.000 1.849 70.450 °C
Temp LM3 45.000 46.000 46.000 49.000 51.000 52.000 53.000 5.000 6.000 1.364 48.798 °C
Temp LM4 48.850 49.850 50.850 51.850 54.850 55.850 58.850 4.000 6.000 1.249 52.233 °C
Temp LM5 48.850 49.850 50.850 51.850 54.850 55.850 58.850 4.000 6.000 1.251 52.235 °C
Temp LM6 55.850 56.850 57.850 59.850 63.850 70.850 76.850 6.000 14.000 2.294 60.421 °C
Temp LM7 48.850 49.850 50.850 51.850 54.850 55.850 58.850 4.000 6.000 1.250 52.252 °C
Temp LM8 45.000 45.000 45.000 47.000 48.000 48.000 49.000 3.000 3.000 0.964 46.597 °C
Temp LM9 35.500 39.000 39.500 41.000 52.500 53.000 54.500 13.000 14.000 3.034 41.833 °C
nSats 6.000 8.000 9.000 12.000 14.000 15.000 18.000 5.000 7.000 1.503 11.868 nSat 348.7 2550
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!