NTPsec

C-ntpsec-24-hour-stats

Report generated: Thu Mar 4 15:01:57 2021 UTC
Start Time: Wed Mar 3 15:01:57 2021 UTC
End Time: Thu Mar 4 15:01:57 2021 UTC
Report published: Thu Mar 04 07:02:04 2021 PST
Report Period: 1.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 -1.642 -0.871 -0.641 0.037 0.748 1.041 1.550 1.389 1.912 0.431 0.039 µs -3.404 8.091
Local Clock Frequency Offset -5.319 -5.311 -5.272 -5.116 -5.052 -5.051 -5.050 0.220 0.260 0.072 -5.134 ppm -3.72e+05 2.677e+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 77.000 103.000 118.000 177.000 290.000 387.000 668.000 172.000 284.000 56.450 186.767 ns 20.98 85.85

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 23.000 35.000 44.000 96.000 231.000 359.000 485.000 187.000 324.000 62.793 110.314 10e-12 4.701 18.49

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 -1.642 -0.871 -0.641 0.037 0.748 1.041 1.550 1.389 1.912 0.431 0.039 µs -3.404 8.091

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.319 -5.311 -5.272 -5.116 -5.052 -5.051 -5.050 0.220 0.260 0.072 -5.134 ppm -3.72e+05 2.677e+07
Temp ZONE0 56.382 56.920 56.920 58.534 59.610 60.148 60.148 2.690 3.228 0.844 58.524 °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 7.000 8.000 10.000 12.000 12.000 12.000 4.000 5.000 1.300 9.733 nSat 292.5 2023
TDOP 0.520 0.550 0.600 0.800 1.300 1.400 1.590 0.700 0.850 0.198 0.850 46.59 199.4

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 104.131.155.175

peer offset 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 104.131.155.175 0.747 0.747 0.912 1.689 2.703 3.268 3.268 1.791 2.520 0.473 1.735 ms 27.76 106.2

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 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 0.932 1.559 1.961 2.357 2.865 3.310 3.896 0.904 1.751 0.297 2.365 ms 358.4 2653

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 -2.653 -1.984 -1.044 0.153 1.169 2.162 2.892 2.213 4.146 0.669 0.166 ms -2.821 10.54

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 -3.262 -3.262 0.319 3.077 4.768 8.289 8.289 4.449 11.551 1.531 2.998 ms 2.929 10.67

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 -5.709 24.962 42.484 110.184 177.625 223.783 254.845 135.141 198.821 41.040 112.311 µs 10.61 31.39

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

peer offset 192.53.103.98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.53.103.98 -0.438 -0.438 -0.242 0.327 2.419 2.640 2.640 2.661 3.077 0.990 0.829 ms 0.1248 1.468

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 -5.929 -4.346 1.223 2.257 2.998 3.991 4.188 1.774 8.336 1.106 2.130 ms -1.247 19.11

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

peer offset 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.17.205.24 2.485 2.826 3.056 3.593 4.108 4.609 5.335 1.052 1.783 0.327 3.606 ms 1038 1.072e+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 47.51.249.154

peer offset 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 47.51.249.154 -8.470 -7.061 -2.675 3.047 6.177 10.211 11.397 8.852 17.272 2.934 2.587 ms -1.189 6.249

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) -72.581 -69.625 -67.372 -58.618 -50.021 -46.305 -44.856 17.351 23.319 5.249 -58.782 ms -1852 2.303e+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) -1.643 -0.872 -0.642 0.038 0.749 1.042 1.550 1.391 1.914 0.432 0.039 µs -3.404 8.087

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 104.131.155.175

peer jitter 104.131.155.175 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 104.131.155.175 0.703 0.703 0.879 1.753 9.231 12.015 12.015 8.352 11.311 2.945 3.213 ms 1.631 3.961

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 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.162 0.463 0.749 1.943 9.297 19.808 25.656 8.548 19.345 3.362 3.232 ms 2.845 15.86

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.538 0.734 1.086 2.407 9.718 14.259 14.986 8.632 13.525 2.982 3.663 ms 2.203 6.149

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.784 0.784 1.082 2.551 26.788 39.997 39.997 25.706 39.213 8.643 6.638 ms 1.573 5.981

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.022 0.038 0.062 0.207 8.466 8.894 22.128 8.404 8.856 2.327 1.189 ms 1.19 8.103

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

peer jitter 192.53.103.98 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.53.103.98 0.556 0.556 0.791 1.971 8.907 13.095 13.095 8.116 12.539 2.969 3.293 ms 1.859 5.217

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.447 0.644 1.069 2.089 10.616 13.508 13.992 9.547 12.864 3.295 3.771 ms 1.863 4.935

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

peer jitter 204.17.205.24 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.17.205.24 0.344 0.473 0.662 1.735 10.566 14.107 15.224 9.904 13.634 3.520 3.462 ms 1.39 3.848

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 47.51.249.154

peer jitter 47.51.249.154 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 47.51.249.154 0.406 0.689 1.038 2.752 9.903 13.643 15.736 8.864 12.954 3.045 3.845 ms 2.384 7.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 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.053 0.169 0.291 0.939 3.143 5.676 8.301 2.852 5.507 1.022 1.224 ms 3.167 14.05

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) 28.000 69.000 96.000 215.000 505.000 696.000 1,386.000 409.000 627.000 136.164 246.693 ns 4.836 19.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -5.319 -5.311 -5.272 -5.116 -5.052 -5.051 -5.050 0.220 0.260 0.072 -5.134 ppm -3.72e+05 2.677e+07
Local Clock Time Offset -1.642 -0.871 -0.641 0.037 0.748 1.041 1.550 1.389 1.912 0.431 0.039 µs -3.404 8.091
Local RMS Frequency Jitter 23.000 35.000 44.000 96.000 231.000 359.000 485.000 187.000 324.000 62.793 110.314 10e-12 4.701 18.49
Local RMS Time Jitter 77.000 103.000 118.000 177.000 290.000 387.000 668.000 172.000 284.000 56.450 186.767 ns 20.98 85.85
Server Jitter 104.131.155.175 0.703 0.703 0.879 1.753 9.231 12.015 12.015 8.352 11.311 2.945 3.213 ms 1.631 3.961
Server Jitter 162.159.200.1 0.162 0.463 0.749 1.943 9.297 19.808 25.656 8.548 19.345 3.362 3.232 ms 2.845 15.86
Server Jitter 173.11.101.155 0.538 0.734 1.086 2.407 9.718 14.259 14.986 8.632 13.525 2.982 3.663 ms 2.203 6.149
Server Jitter 178.62.68.79 0.784 0.784 1.082 2.551 26.788 39.997 39.997 25.706 39.213 8.643 6.638 ms 1.573 5.981
Server Jitter 192.168.1.10 0.022 0.038 0.062 0.207 8.466 8.894 22.128 8.404 8.856 2.327 1.189 ms 1.19 8.103
Server Jitter 192.53.103.98 0.556 0.556 0.791 1.971 8.907 13.095 13.095 8.116 12.539 2.969 3.293 ms 1.859 5.217
Server Jitter 204.123.2.5 0.447 0.644 1.069 2.089 10.616 13.508 13.992 9.547 12.864 3.295 3.771 ms 1.863 4.935
Server Jitter 204.17.205.24 0.344 0.473 0.662 1.735 10.566 14.107 15.224 9.904 13.634 3.520 3.462 ms 1.39 3.848
Server Jitter 47.51.249.154 0.406 0.689 1.038 2.752 9.903 13.643 15.736 8.864 12.954 3.045 3.845 ms 2.384 7.1
Server Jitter SHM(0) 0.053 0.169 0.291 0.939 3.143 5.676 8.301 2.852 5.507 1.022 1.224 ms 3.167 14.05
Server Jitter SHM(1) 28.000 69.000 96.000 215.000 505.000 696.000 1,386.000 409.000 627.000 136.164 246.693 ns 4.836 19.8
Server Offset 104.131.155.175 0.747 0.747 0.912 1.689 2.703 3.268 3.268 1.791 2.520 0.473 1.735 ms 27.76 106.2
Server Offset 162.159.200.1 0.932 1.559 1.961 2.357 2.865 3.310 3.896 0.904 1.751 0.297 2.365 ms 358.4 2653
Server Offset 173.11.101.155 -2.653 -1.984 -1.044 0.153 1.169 2.162 2.892 2.213 4.146 0.669 0.166 ms -2.821 10.54
Server Offset 178.62.68.79 -3.262 -3.262 0.319 3.077 4.768 8.289 8.289 4.449 11.551 1.531 2.998 ms 2.929 10.67
Server Offset 192.168.1.10 -5.709 24.962 42.484 110.184 177.625 223.783 254.845 135.141 198.821 41.040 112.311 µs 10.61 31.39
Server Offset 192.53.103.98 -0.438 -0.438 -0.242 0.327 2.419 2.640 2.640 2.661 3.077 0.990 0.829 ms 0.1248 1.468
Server Offset 204.123.2.5 -5.929 -4.346 1.223 2.257 2.998 3.991 4.188 1.774 8.336 1.106 2.130 ms -1.247 19.11
Server Offset 204.17.205.24 2.485 2.826 3.056 3.593 4.108 4.609 5.335 1.052 1.783 0.327 3.606 ms 1038 1.072e+04
Server Offset 47.51.249.154 -8.470 -7.061 -2.675 3.047 6.177 10.211 11.397 8.852 17.272 2.934 2.587 ms -1.189 6.249
Server Offset SHM(0) -72.581 -69.625 -67.372 -58.618 -50.021 -46.305 -44.856 17.351 23.319 5.249 -58.782 ms -1852 2.303e+04
Server Offset SHM(1) -1.643 -0.872 -0.642 0.038 0.749 1.042 1.550 1.391 1.914 0.432 0.039 µs -3.404 8.087
TDOP 0.520 0.550 0.600 0.800 1.300 1.400 1.590 0.700 0.850 0.198 0.850 46.59 199.4
Temp ZONE0 56.382 56.920 56.920 58.534 59.610 60.148 60.148 2.690 3.228 0.844 58.524 °C
nSats 6.000 7.000 8.000 10.000 12.000 12.000 12.000 4.000 5.000 1.300 9.733 nSat 292.5 2023
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!