NTPsec

C-ntpsec-3-hour-stats

Report generated: Wed Nov 20 18:04:12 2019 UTC
Start Time: Wed Nov 20 15:04:11 2019 UTC
End Time: Wed Nov 20 18:04:11 2019 UTC
Report published: Wed Nov 20 10:05:22 2019 PST
Report Period: 0.1 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 -664.000 -597.000 -434.000 -61.000 393.000 608.000 804.000 827.000 1,205.000 252.816 -52.867 ns -5.007 12.14
Local Clock Frequency Offset -6.791 -6.790 -6.789 -6.782 -6.780 -6.780 -6.780 0.0089 0.0106 0.0027 -6.783 ppm -1.652e+10 4.209e+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 104.000 113.000 135.000 195.000 263.000 280.000 292.000 128.000 167.000 39.324 196.486 ns 75.88 354.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 26.000 31.000 37.000 59.000 94.000 105.000 119.000 57.000 74.000 16.700 61.183 10e-12 27.51 102.8

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 -664.000 -597.000 -434.000 -61.000 393.000 608.000 804.000 827.000 1,205.000 252.816 -52.867 ns -5.007 12.14

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 -6.791 -6.790 -6.789 -6.782 -6.780 -6.780 -6.780 0.0089 0.0106 0.0027 -6.783 ppm -1.652e+10 4.209e+13
Temp ZONE0 63.376 63.376 63.376 63.914 64.452 64.452 64.452 1.076 1.076 0.455 63.848 °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 8.000 8.000 8.000 10.000 11.000 12.000 12.000 3.000 4.000 1.064 9.371 nSat 499.4 4090
TDOP 0.500 0.500 0.600 0.830 1.460 1.480 1.490 0.860 0.980 0.314 0.937 14.31 45.25

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 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -8.367 -8.367 -8.288 -2.278 -1.682 -1.583 -1.583 6.605 6.785 3.014 -4.603 ms -24 83

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

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

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

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



Server Offset 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -977.032 -977.032 -491.546 336.155 702.563 754.332 754.332 1,194.109 1,731.364 378.508 194.261 µs -2.524 7.004

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 178.62.68.79

peer offset 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 178.62.68.79 -7.406 -7.406 -7.406 2.058 2.590 2.590 2.590 9.997 9.997 3.537 -0.275 ms -5.549 15.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 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 -25.931 24.132 60.123 98.001 126.419 143.056 149.153 66.296 118.924 23.346 94.696 µs 36.43 135

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.473 3.473 3.887 4.200 4.684 4.821 4.821 0.797 1.348 0.273 4.230 ms 3084 4.531e+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 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 2.130 2.130 2.130 2.475 2.852 2.852 2.852 0.722 0.722 0.209 2.495 ms 1345 1.508e+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 2405:fc00:0:1::123

peer offset 2405:fc00:0:1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2405:fc00:0:1::123 -2.473 -2.473 -2.459 -2.154 -1.872 -1.759 -1.759 0.587 0.714 0.153 -2.165 ms -3532 5.424e+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) 1.793 1.793 1.840 2.388 3.520 3.620 3.620 1.680 1.827 0.497 2.486 ms 76.89 369.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 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) -64.928 -64.797 -62.764 -54.943 -46.103 -45.469 -45.465 16.661 19.328 4.607 -54.371 ms -2136 2.784e+04

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

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

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

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



Server Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -665.000 -598.000 -435.000 -62.000 394.000 609.000 805.000 829.000 1,207.000 253.562 -53.076 ns -5.008 12.13

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

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

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

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



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.138 0.138 0.204 1.430 8.770 8.801 8.801 8.566 8.663 1.839 1.903 ms 2.93 11.21

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.239 0.239 0.612 1.512 6.947 9.215 9.215 6.335 8.976 1.918 2.218 ms 2.599 8.437

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 178.62.68.79

peer jitter 178.62.68.79 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 178.62.68.79 0.590 0.590 0.590 2.091 15.922 15.922 15.922 15.333 15.333 5.684 4.986 ms 0.6455 1.923

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 192.168.1.10

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 0.020 0.021 0.033 0.128 8.664 8.710 10.108 8.631 8.689 2.722 1.538 ms 0.4022 2.864

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.138 0.138 0.297 1.532 6.731 7.476 7.476 6.435 7.337 2.158 2.429 ms 1.197 2.933

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 204.123.2.5

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.276 0.276 0.276 1.408 10.826 10.826 10.826 10.550 10.550 2.607 2.520 ms 1.829 6.112

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.392 0.392 0.411 1.946 12.184 12.195 12.195 11.773 11.803 4.257 4.271 ms 0.6974 1.828

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.277 0.277 0.356 1.830 12.318 12.339 12.339 11.962 12.062 4.174 4.238 ms 0.8185 2.146

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.368 0.389 0.485 2.273 6.234 8.049 8.656 5.748 7.659 1.911 2.709 ms 2.087 5.105

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) 72.000 83.000 107.000 216.000 450.000 589.000 757.000 343.000 506.000 110.856 241.327 ns 6.372 20.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -6.791 -6.790 -6.789 -6.782 -6.780 -6.780 -6.780 0.0089 0.0106 0.0027 -6.783 ppm -1.652e+10 4.209e+13
Local Clock Time Offset -664.000 -597.000 -434.000 -61.000 393.000 608.000 804.000 827.000 1,205.000 252.816 -52.867 ns -5.007 12.14
Local RMS Frequency Jitter 26.000 31.000 37.000 59.000 94.000 105.000 119.000 57.000 74.000 16.700 61.183 10e-12 27.51 102.8
Local RMS Time Jitter 104.000 113.000 135.000 195.000 263.000 280.000 292.000 128.000 167.000 39.324 196.486 ns 75.88 354.2
Server Jitter 162.159.200.1 0.138 0.138 0.204 1.430 8.770 8.801 8.801 8.566 8.663 1.839 1.903 ms 2.93 11.21
Server Jitter 173.11.101.155 0.239 0.239 0.612 1.512 6.947 9.215 9.215 6.335 8.976 1.918 2.218 ms 2.599 8.437
Server Jitter 178.62.68.79 0.590 0.590 0.590 2.091 15.922 15.922 15.922 15.333 15.333 5.684 4.986 ms 0.6455 1.923
Server Jitter 192.168.1.10 0.020 0.021 0.033 0.128 8.664 8.710 10.108 8.631 8.689 2.722 1.538 ms 0.4022 2.864
Server Jitter 2001:470:e815::24 (pi4.rellim.com) 0.138 0.138 0.297 1.532 6.731 7.476 7.476 6.435 7.337 2.158 2.429 ms 1.197 2.933
Server Jitter 204.123.2.5 0.276 0.276 0.276 1.408 10.826 10.826 10.826 10.550 10.550 2.607 2.520 ms 1.829 6.112
Server Jitter 2405:fc00:0:1::123 0.392 0.392 0.411 1.946 12.184 12.195 12.195 11.773 11.803 4.257 4.271 ms 0.6974 1.828
Server Jitter 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 0.277 0.277 0.356 1.830 12.318 12.339 12.339 11.962 12.062 4.174 4.238 ms 0.8185 2.146
Server Jitter SHM(0) 0.368 0.389 0.485 2.273 6.234 8.049 8.656 5.748 7.659 1.911 2.709 ms 2.087 5.105
Server Jitter SHM(1) 72.000 83.000 107.000 216.000 450.000 589.000 757.000 343.000 506.000 110.856 241.327 ns 6.372 20.88
Server Offset 162.159.200.1 -8.367 -8.367 -8.288 -2.278 -1.682 -1.583 -1.583 6.605 6.785 3.014 -4.603 ms -24 83
Server Offset 173.11.101.155 -977.032 -977.032 -491.546 336.155 702.563 754.332 754.332 1,194.109 1,731.364 378.508 194.261 µs -2.524 7.004
Server Offset 178.62.68.79 -7.406 -7.406 -7.406 2.058 2.590 2.590 2.590 9.997 9.997 3.537 -0.275 ms -5.549 15.44
Server Offset 192.168.1.10 -25.931 24.132 60.123 98.001 126.419 143.056 149.153 66.296 118.924 23.346 94.696 µs 36.43 135
Server Offset 2001:470:e815::24 (pi4.rellim.com) 3.473 3.473 3.887 4.200 4.684 4.821 4.821 0.797 1.348 0.273 4.230 ms 3084 4.531e+04
Server Offset 204.123.2.5 2.130 2.130 2.130 2.475 2.852 2.852 2.852 0.722 0.722 0.209 2.495 ms 1345 1.508e+04
Server Offset 2405:fc00:0:1::123 -2.473 -2.473 -2.459 -2.154 -1.872 -1.759 -1.759 0.587 0.714 0.153 -2.165 ms -3532 5.424e+04
Server Offset 2604:a880:1:20::17:5001 (ntp1.glypnod.com) 1.793 1.793 1.840 2.388 3.520 3.620 3.620 1.680 1.827 0.497 2.486 ms 76.89 369.1
Server Offset SHM(0) -64.928 -64.797 -62.764 -54.943 -46.103 -45.469 -45.465 16.661 19.328 4.607 -54.371 ms -2136 2.784e+04
Server Offset SHM(1) -665.000 -598.000 -435.000 -62.000 394.000 609.000 805.000 829.000 1,207.000 253.562 -53.076 ns -5.008 12.13
TDOP 0.500 0.500 0.600 0.830 1.460 1.480 1.490 0.860 0.980 0.314 0.937 14.31 45.25
Temp ZONE0 63.376 63.376 63.376 63.914 64.452 64.452 64.452 1.076 1.076 0.455 63.848 °C
nSats 8.000 8.000 8.000 10.000 11.000 12.000 12.000 3.000 4.000 1.064 9.371 nSat 499.4 4090
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!