NTPsec

B-ntpsec-1-hour-stats

Report generated: Sun Jan 26 15:01:11 2020 UTC
Start Time: Sun Jan 26 14:00:42 2020 UTC
End Time: Sun Jan 26 15:01:10 2020 UTC
Report published: Sun Jan 26 07:01:15 2020 PST
Report Period: 0.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 -525.000 -337.000 -233.000 129.000 571.000 745.000 993.000 804.000 1,082.000 247.780 164.513 ns -0.7569 3.359
Local Clock Frequency Offset -5.723 -5.722 -5.722 -5.716 -5.714 -5.714 -5.714 0.0084 0.0088 0.0027 -5.717 ppm -9.755e+09 2.084e+13

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 167.000 174.000 199.000 301.000 394.000 426.000 445.000 195.000 252.000 58.971 300.553 ns 81 384.2

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 35.000 36.000 39.000 67.000 110.000 127.000 129.000 71.000 91.000 23.187 70.473 10e-12 15.09 48.64

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 -525.000 -337.000 -233.000 129.000 571.000 745.000 993.000 804.000 1,082.000 247.780 164.513 ns -0.7569 3.359

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.723 -5.722 -5.722 -5.716 -5.714 -5.714 -5.714 0.0084 0.0088 0.0027 -5.717 ppm -9.755e+09 2.084e+13
Temp ZONE0 61.224 61.224 61.224 61.762 62.300 62.300 62.300 1.076 1.076 0.377 61.708 °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 7.000 8.000 9.000 10.000 10.000 10.000 2.000 3.000 0.685 8.883 nSat 1747 2.132e+04
TDOP 0.620 0.620 0.630 0.880 1.020 1.210 1.210 0.390 0.590 0.124 0.841 209.6 1308

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. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



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 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 58.873 58.873 69.124 97.675 123.037 126.766 126.766 53.913 67.893 16.616 96.036 µs 123.3 657.6

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:0:50::2 (clock.fmt.he.net)

peer offset 2001:470:0:50::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 2.402 2.402 2.402 2.455 2.723 2.723 2.723 0.322 0.322 0.110 2.499 ms 1.04e+04 2.281e+05

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::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) 3.974 3.974 3.974 4.300 4.692 4.692 4.692 0.718 0.718 0.190 4.251 ms 9754 2.093e+05

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 216.218.254.202

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.254.202 2.476 2.476 2.476 2.614 3.228 3.228 3.228 0.753 0.753 0.272 2.697 ms 739.2 6876

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 9.147 9.147 9.147 9.455 9.868 9.868 9.868 0.721 0.721 0.170 9.456 ms 1.625e+05 8.877e+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 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.380 1.380 1.380 1.925 2.946 2.946 2.946 1.566 1.566 0.464 1.935 ms 42.36 176.5

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 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu)

peer offset 2607:f140:ffff:8000:0:8006:0:a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.000 0.000 0.000 2.456 2.666 2.666 2.666 2.666 2.666 0.667 2.290 ms 18.66 51.44

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) 2.828 2.828 2.828 3.083 3.340 3.340 3.340 0.512 0.512 0.158 3.084 ms 6361 1.185e+05

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 76.14.161.109

peer offset 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 76.14.161.109 -1.659 -1.659 -1.659 -0.924 1.052 1.052 1.052 2.711 2.711 0.915 -0.495 ms -7.991 19.68

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) -394.882 -378.739 -373.646 -352.278 -330.530 -319.862 -298.667 43.117 58.877 13.145 -352.016 ms -2.152e+04 6.002e+05

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) -525.000 -338.000 -234.000 130.000 572.000 746.000 994.000 806.000 1,084.000 248.315 165.031 ns -0.7601 3.357

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 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.030 0.030 0.053 0.183 8.685 8.697 8.697 8.632 8.667 2.571 1.141 ms 0.6814 3.88

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:0:50::2 (clock.fmt.he.net)

peer jitter 2001:470:0:50::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.445 0.445 0.445 0.676 2.068 2.068 2.068 1.623 1.623 0.617 0.968 ms 2.735 5.958

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::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.564 0.564 0.564 8.148 9.709 9.709 9.709 9.145 9.145 3.543 5.861 ms 1.691 2.874

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 216.218.254.202

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.254.202 5.698 5.698 5.698 6.913 7.488 7.488 7.488 1.791 1.791 0.667 6.801 ms 805.1 7646

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.370 0.370 0.370 2.827 3.365 3.365 3.365 2.994 2.994 1.088 2.364 ms 4.186 7.903

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.342 0.342 0.342 0.995 9.295 9.295 9.295 8.953 8.953 2.711 2.427 ms 1.048 3.235

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 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu)

peer jitter 2607:f140:ffff:8000:0:8006:0:a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.312 0.312 0.312 1.518 9.299 9.299 9.299 8.987 8.987 2.914 2.786 ms 1.449 3.662

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.383 0.383 0.383 1.171 9.395 9.395 9.395 9.012 9.012 3.573 3.035 ms 0.546 1.598

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 76.14.161.109

peer jitter 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 76.14.161.109 4.998 4.998 4.998 9.801 32.697 32.697 32.697 27.699 27.699 6.942 12.627 ms 5.022 17.59

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) 2.688 3.769 5.076 9.740 20.712 28.007 36.536 15.635 24.237 5.039 10.994 ms 6.601 22.67

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) 99.000 112.000 142.000 275.000 496.000 646.000 694.000 354.000 534.000 107.602 289.814 ns 10.96 36.84

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.723 -5.722 -5.722 -5.716 -5.714 -5.714 -5.714 0.0084 0.0088 0.0027 -5.717 ppm -9.755e+09 2.084e+13
Local Clock Time Offset -525.000 -337.000 -233.000 129.000 571.000 745.000 993.000 804.000 1,082.000 247.780 164.513 ns -0.7569 3.359
Local RMS Frequency Jitter 35.000 36.000 39.000 67.000 110.000 127.000 129.000 71.000 91.000 23.187 70.473 10e-12 15.09 48.64
Local RMS Time Jitter 167.000 174.000 199.000 301.000 394.000 426.000 445.000 195.000 252.000 58.971 300.553 ns 81 384.2
Server Jitter 192.168.1.10 0.030 0.030 0.053 0.183 8.685 8.697 8.697 8.632 8.667 2.571 1.141 ms 0.6814 3.88
Server Jitter 2001:470:0:50::2 (clock.fmt.he.net) 0.445 0.445 0.445 0.676 2.068 2.068 2.068 1.623 1.623 0.617 0.968 ms 2.735 5.958
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.564 0.564 0.564 8.148 9.709 9.709 9.709 9.145 9.145 3.543 5.861 ms 1.691 2.874
Server Jitter 216.218.254.202 5.698 5.698 5.698 6.913 7.488 7.488 7.488 1.791 1.791 0.667 6.801 ms 805.1 7646
Server Jitter 2405:fc00:0:1::123 0.370 0.370 0.370 2.827 3.365 3.365 3.365 2.994 2.994 1.088 2.364 ms 4.186 7.903
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.342 0.342 0.342 0.995 9.295 9.295 9.295 8.953 8.953 2.711 2.427 ms 1.048 3.235
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.312 0.312 0.312 1.518 9.299 9.299 9.299 8.987 8.987 2.914 2.786 ms 1.449 3.662
Server Jitter 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 0.383 0.383 0.383 1.171 9.395 9.395 9.395 9.012 9.012 3.573 3.035 ms 0.546 1.598
Server Jitter 76.14.161.109 4.998 4.998 4.998 9.801 32.697 32.697 32.697 27.699 27.699 6.942 12.627 ms 5.022 17.59
Server Jitter SHM(0) 2.688 3.769 5.076 9.740 20.712 28.007 36.536 15.635 24.237 5.039 10.994 ms 6.601 22.67
Server Jitter SHM(1) 99.000 112.000 142.000 275.000 496.000 646.000 694.000 354.000 534.000 107.602 289.814 ns 10.96 36.84
Server Offset 192.168.1.10 58.873 58.873 69.124 97.675 123.037 126.766 126.766 53.913 67.893 16.616 96.036 µs 123.3 657.6
Server Offset 2001:470:0:50::2 (clock.fmt.he.net) 2.402 2.402 2.402 2.455 2.723 2.723 2.723 0.322 0.322 0.110 2.499 ms 1.04e+04 2.281e+05
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.974 3.974 3.974 4.300 4.692 4.692 4.692 0.718 0.718 0.190 4.251 ms 9754 2.093e+05
Server Offset 216.218.254.202 2.476 2.476 2.476 2.614 3.228 3.228 3.228 0.753 0.753 0.272 2.697 ms 739.2 6876
Server Offset 2405:fc00:0:1::123 9.147 9.147 9.147 9.455 9.868 9.868 9.868 0.721 0.721 0.170 9.456 ms 1.625e+05 8.877e+06
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 1.380 1.380 1.380 1.925 2.946 2.946 2.946 1.566 1.566 0.464 1.935 ms 42.36 176.5
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.000 0.000 0.000 2.456 2.666 2.666 2.666 2.666 2.666 0.667 2.290 ms 18.66 51.44
Server Offset 2a03:b0c0:1:d0::1f9:f001 (ntp2.glypnod.com) 2.828 2.828 2.828 3.083 3.340 3.340 3.340 0.512 0.512 0.158 3.084 ms 6361 1.185e+05
Server Offset 76.14.161.109 -1.659 -1.659 -1.659 -0.924 1.052 1.052 1.052 2.711 2.711 0.915 -0.495 ms -7.991 19.68
Server Offset SHM(0) -394.882 -378.739 -373.646 -352.278 -330.530 -319.862 -298.667 43.117 58.877 13.145 -352.016 ms -2.152e+04 6.002e+05
Server Offset SHM(1) -525.000 -338.000 -234.000 130.000 572.000 746.000 994.000 806.000 1,084.000 248.315 165.031 ns -0.7601 3.357
TDOP 0.620 0.620 0.630 0.880 1.020 1.210 1.210 0.390 0.590 0.124 0.841 209.6 1308
Temp ZONE0 61.224 61.224 61.224 61.762 62.300 62.300 62.300 1.076 1.076 0.377 61.708 °C
nSats 7.000 7.000 8.000 9.000 10.000 10.000 10.000 2.000 3.000 0.685 8.883 nSat 1747 2.132e+04
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!