NTPsec

C-ntpsec-1-hour-stats

Report generated: Fri May 29 08:01:17 2020 UTC
Start Time: Fri May 29 07:00:49 2020 UTC
End Time: Fri May 29 08:01:17 2020 UTC
Report published: Fri May 29 01:01:21 2020 PDT
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 -221.000 -104.000 28.000 389.000 773.000 985.000 1,079.000 745.000 1,089.000 228.614 392.965 ns 2.678 6.89
Local Clock Frequency Offset -5.330 -5.330 -5.330 -5.320 -5.310 -5.309 -5.309 0.020 0.021 0.0066 -5.319 ppm -5.225e+08 4.208e+11

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 102.000 107.000 119.000 177.000 237.000 256.000 263.000 118.000 149.000 35.869 177.124 ns 72.97 337.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 46.000 48.000 60.000 110.000 166.000 174.000 178.000 106.000 126.000 31.376 109.226 10e-12 22.78 77.81

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 -221.000 -104.000 28.000 389.000 773.000 985.000 1,079.000 745.000 1,089.000 228.614 392.965 ns 2.678 6.89

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.330 -5.330 -5.330 -5.320 -5.310 -5.309 -5.309 0.020 0.021 0.0066 -5.319 ppm -5.225e+08 4.208e+11
Temp ZONE0 64.990 64.990 64.990 65.528 66.066 66.066 66.066 1.076 1.076 0.259 65.510 °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 9.000 9.000 9.000 10.000 11.000 11.000 11.000 2.000 2.000 0.622 10.250 nSat 3746 5.864e+04
TDOP 0.630 0.630 0.630 0.730 1.050 1.080 1.080 0.420 0.450 0.116 0.776 203 1280

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 1.117 1.117 1.117 1.559 1.811 1.811 1.811 0.695 0.695 0.189 1.535 ms 385.4 2896

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 1.244 1.244 1.244 1.923 2.156 2.156 2.156 0.911 0.911 0.256 1.813 ms 243.1 1582

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 164.67.62.194

peer offset 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 164.67.62.194 2.449 2.449 2.449 2.586 2.913 2.913 2.913 0.464 0.464 0.120 2.607 ms 8933 1.863e+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 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 -350.088 -350.088 -350.088 279.620 426.478 426.478 426.478 776.566 776.566 244.511 173.513 µs -2.081 4.864

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.191 -7.191 -7.191 -1.636 11.982 11.982 11.982 19.174 19.174 8.055 1.052 ms -2.802 4.996

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 -30.069 -30.069 -17.247 52.799 94.010 94.177 94.177 111.257 124.246 31.809 51.186 µs 1.345 3.459

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 203.123.48.219

peer offset 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 203.123.48.219 2.974 2.974 2.974 3.441 4.193 4.193 4.193 1.219 1.219 0.324 3.417 ms 897.5 8852

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 0.376 0.376 0.376 1.844 2.180 2.180 2.180 1.804 1.804 0.475 1.715 ms 23.68 73.17

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 0.948 0.948 0.948 3.253 4.254 4.254 4.254 3.306 3.306 0.823 3.068 ms 27.49 93.22

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

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

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

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



Server Offset 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.799 -64.799 -64.034 -58.895 -53.474 -53.010 -53.010 10.559 11.789 3.770 -58.724 ms -4604 7.714e+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) -222.000 -105.000 29.000 390.000 774.000 986.000 1,080.000 745.000 1,091.000 228.740 393.858 ns 2.688 6.918

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.363 0.363 0.363 1.945 9.591 9.591 9.591 9.229 9.229 2.413 2.746 ms 2.393 7.251

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 1.260 1.260 1.260 3.825 4.682 4.682 4.682 3.422 3.422 1.100 3.006 ms 10.28 27.62

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 164.67.62.194

peer jitter 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 164.67.62.194 0.535 0.535 0.535 2.072 5.435 5.435 5.435 4.900 4.900 1.546 2.486 ms 2.813 6.575

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.383 0.383 0.383 2.778 9.016 9.016 9.016 8.633 8.633 3.007 3.772 ms 1.397 2.927

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 5.906 5.906 5.906 7.007 13.439 13.439 13.439 7.534 7.534 3.322 8.784 ms 10.02 29.28

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.062 0.062 0.063 0.155 8.692 8.712 8.712 8.629 8.651 3.101 1.700 ms 0.2491 2.222

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 203.123.48.219

peer jitter 203.123.48.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 203.123.48.219 1.690 1.690 1.690 8.883 12.666 12.666 12.666 10.976 10.976 4.334 7.649 ms 2.696 5.048

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.197 0.197 0.197 1.271 2.722 2.722 2.722 2.525 2.525 0.753 1.287 ms 2.776 6.119

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 1.146 1.146 1.146 6.195 10.263 10.263 10.263 9.117 9.117 3.148 6.339 ms 3.94 8.202

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.405 0.405 0.469 1.646 8.589 9.314 9.314 8.121 8.909 2.298 2.795 ms 1.806 4.837

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) 62.000 72.000 100.000 203.000 431.000 526.000 576.000 331.000 454.000 97.502 225.872 ns 7.284 22.95

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.330 -5.330 -5.330 -5.320 -5.310 -5.309 -5.309 0.020 0.021 0.0066 -5.319 ppm -5.225e+08 4.208e+11
Local Clock Time Offset -221.000 -104.000 28.000 389.000 773.000 985.000 1,079.000 745.000 1,089.000 228.614 392.965 ns 2.678 6.89
Local RMS Frequency Jitter 46.000 48.000 60.000 110.000 166.000 174.000 178.000 106.000 126.000 31.376 109.226 10e-12 22.78 77.81
Local RMS Time Jitter 102.000 107.000 119.000 177.000 237.000 256.000 263.000 118.000 149.000 35.869 177.124 ns 72.97 337.3
Server Jitter 104.131.155.175 0.363 0.363 0.363 1.945 9.591 9.591 9.591 9.229 9.229 2.413 2.746 ms 2.393 7.251
Server Jitter 162.159.200.1 1.260 1.260 1.260 3.825 4.682 4.682 4.682 3.422 3.422 1.100 3.006 ms 10.28 27.62
Server Jitter 164.67.62.194 0.535 0.535 0.535 2.072 5.435 5.435 5.435 4.900 4.900 1.546 2.486 ms 2.813 6.575
Server Jitter 173.11.101.155 0.383 0.383 0.383 2.778 9.016 9.016 9.016 8.633 8.633 3.007 3.772 ms 1.397 2.927
Server Jitter 178.62.68.79 5.906 5.906 5.906 7.007 13.439 13.439 13.439 7.534 7.534 3.322 8.784 ms 10.02 29.28
Server Jitter 192.168.1.10 0.062 0.062 0.063 0.155 8.692 8.712 8.712 8.629 8.651 3.101 1.700 ms 0.2491 2.222
Server Jitter 203.123.48.219 1.690 1.690 1.690 8.883 12.666 12.666 12.666 10.976 10.976 4.334 7.649 ms 2.696 5.048
Server Jitter 204.17.205.24 0.197 0.197 0.197 1.271 2.722 2.722 2.722 2.525 2.525 0.753 1.287 ms 2.776 6.119
Server Jitter 47.51.249.154 1.146 1.146 1.146 6.195 10.263 10.263 10.263 9.117 9.117 3.148 6.339 ms 3.94 8.202
Server Jitter SHM(0) 0.405 0.405 0.469 1.646 8.589 9.314 9.314 8.121 8.909 2.298 2.795 ms 1.806 4.837
Server Jitter SHM(1) 62.000 72.000 100.000 203.000 431.000 526.000 576.000 331.000 454.000 97.502 225.872 ns 7.284 22.95
Server Offset 104.131.155.175 1.117 1.117 1.117 1.559 1.811 1.811 1.811 0.695 0.695 0.189 1.535 ms 385.4 2896
Server Offset 162.159.200.1 1.244 1.244 1.244 1.923 2.156 2.156 2.156 0.911 0.911 0.256 1.813 ms 243.1 1582
Server Offset 164.67.62.194 2.449 2.449 2.449 2.586 2.913 2.913 2.913 0.464 0.464 0.120 2.607 ms 8933 1.863e+05
Server Offset 173.11.101.155 -350.088 -350.088 -350.088 279.620 426.478 426.478 426.478 776.566 776.566 244.511 173.513 µs -2.081 4.864
Server Offset 178.62.68.79 -7.191 -7.191 -7.191 -1.636 11.982 11.982 11.982 19.174 19.174 8.055 1.052 ms -2.802 4.996
Server Offset 192.168.1.10 -30.069 -30.069 -17.247 52.799 94.010 94.177 94.177 111.257 124.246 31.809 51.186 µs 1.345 3.459
Server Offset 203.123.48.219 2.974 2.974 2.974 3.441 4.193 4.193 4.193 1.219 1.219 0.324 3.417 ms 897.5 8852
Server Offset 204.17.205.24 0.376 0.376 0.376 1.844 2.180 2.180 2.180 1.804 1.804 0.475 1.715 ms 23.68 73.17
Server Offset 47.51.249.154 0.948 0.948 0.948 3.253 4.254 4.254 4.254 3.306 3.306 0.823 3.068 ms 27.49 93.22
Server Offset SHM(0) -64.799 -64.799 -64.034 -58.895 -53.474 -53.010 -53.010 10.559 11.789 3.770 -58.724 ms -4604 7.714e+04
Server Offset SHM(1) -222.000 -105.000 29.000 390.000 774.000 986.000 1,080.000 745.000 1,091.000 228.740 393.858 ns 2.688 6.918
TDOP 0.630 0.630 0.630 0.730 1.050 1.080 1.080 0.420 0.450 0.116 0.776 203 1280
Temp ZONE0 64.990 64.990 64.990 65.528 66.066 66.066 66.066 1.076 1.076 0.259 65.510 °C
nSats 9.000 9.000 9.000 10.000 11.000 11.000 11.000 2.000 2.000 0.622 10.250 nSat 3746 5.864e+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!