NTPsec

c-ntpsec-7-day-stats

Report generated: Tue Jun 15 16:03:29 2021 UTC
Start Time: Tue Jun 8 16:03:25 2021 UTC
End Time: Tue Jun 15 16:03:25 2021 UTC
Report published: Tue Jun 15 09:03:49 2021 PDT
Report Period: 7.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.522 -0.869 -0.615 0.000 0.597 0.869 5.131 1.212 1.738 0.376 -0.001 µs -3.674 12.6
Local Clock Frequency Offset -5.172 -5.164 -5.121 -4.937 -4.840 -4.833 -4.831 0.282 0.331 0.087 -4.955 ppm -1.921e+05 1.109e+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 61.000 95.000 111.000 166.000 257.000 325.000 623.000 146.000 230.000 47.585 173.104 ns 27.74 113.8

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 19.000 31.000 38.000 76.000 179.000 264.000 1,591.000 141.000 233.000 56.304 89.539 10e-12 9.45 170

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.522 -0.869 -0.615 0.000 0.597 0.869 5.131 1.212 1.738 0.376 -0.001 µs -3.674 12.6

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.172 -5.164 -5.121 -4.937 -4.840 -4.833 -4.831 0.282 0.331 0.087 -4.955 ppm -1.921e+05 1.109e+07
Temp ZONE0 56.920 56.920 57.996 60.148 62.300 62.838 63.376 4.304 5.918 1.346 59.968 °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 13.000 4.000 5.000 1.233 9.623 nSat 336.1 2434
TDOP 0.490 0.550 0.590 0.820 1.270 1.540 2.440 0.680 0.990 0.215 0.868 38.56 161.5

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.746 1.981 2.155 2.566 3.065 330.012 533.426 0.910 328.031 47.696 8.551 ms 5.401 52.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 Offset 162.159.200.123

peer offset 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.123 1.713 2.056 2.361 2.699 3.064 3.714 417.139 0.703 1.657 20.934 4.347 ms 11.67 189.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 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 -4.304 -1.040 -0.461 0.149 0.622 2.832 512.484 1.084 3.871 23.610 2.076 ms 10.02 162.8

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

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

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

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



Server Offset 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.180 -0.569 0.295 0.799 1.835 5.397 665.396 1.539 5.966 39.408 4.444 ms 9.492 144.8

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

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

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

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



Server Offset 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 -118.427 28.341 78.685 167.313 257.096 384.670 541.314 178.411 356.329 59.594 168.771 µs 12.47 44.58

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 194.58.202.211

peer offset 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.211 1.763 3.360 3.491 3.787 4.105 4.467 293.512 0.614 1.107 16.274 4.995 ms 11.65 168.7

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 194.58.202.219

peer offset 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.58.202.219 1.610 3.340 3.504 3.796 4.109 4.836 423.431 0.605 1.496 22.905 5.772 ms 9.964 138.7

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 4.273 4.539 4.707 5.004 5.336 5.595 531.493 0.629 1.056 29.120 7.057 ms 12.58 202.9

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 0.469 1.824 1.934 2.183 2.485 2.939 314.952 0.552 1.115 22.750 4.105 ms 9.137 115.3

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

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

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

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



Server Offset 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) -71.554 -66.151 -62.963 -54.921 -47.109 -45.525 -42.746 15.854 20.626 4.781 -55.125 ms -2005 2.56e+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.523 -0.870 -0.616 0.001 0.598 0.870 5.132 1.214 1.740 0.377 -0.001 µs -3.676 12.57

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.068 0.262 0.331 1.234 134.431 329.246 526.921 134.099 328.984 64.266 17.889 ms 2.326 18.33

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

peer jitter 162.159.200.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.123 0.082 0.174 0.246 1.049 12.867 444.952 547.555 12.621 444.778 65.003 13.828 ms 3.29 25.8

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.106 0.332 0.564 1.773 12.632 362.650 628.132 12.068 362.318 54.676 12.285 ms 3.895 33.76

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.000 0.188 0.309 1.193 30.594 401.978 500.365 30.285 401.790 60.803 14.883 ms 2.84 21.52

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.016 0.038 0.063 0.178 8.648 8.997 18.782 8.585 8.959 2.658 1.290 ms 0.6277 3.878

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 194.58.202.211

peer jitter 194.58.202.211 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.211 0.089 0.184 0.290 1.308 11.441 284.206 542.124 11.151 284.023 50.576 10.418 ms 4.703 44.71

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 194.58.202.219

peer jitter 194.58.202.219 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.58.202.219 0.078 0.174 0.261 1.188 11.222 294.947 539.552 10.961 294.774 46.616 9.685 ms 4.414 41.07

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 0.000 0.181 0.259 1.207 11.850 293.471 597.684 11.591 293.290 48.819 9.917 ms 4.993 49.8

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.117 0.159 0.281 1.355 10.008 378.272 547.106 9.727 378.113 60.053 13.291 ms 3.375 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 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.062 0.223 0.345 0.981 3.126 5.776 10.243 2.781 5.553 1.014 1.258 ms 3.415 15.5

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) 19.000 67.000 95.000 210.000 497.000 677.000 2,674.000 402.000 610.000 136.351 242.783 ns 5.256 31.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -5.172 -5.164 -5.121 -4.937 -4.840 -4.833 -4.831 0.282 0.331 0.087 -4.955 ppm -1.921e+05 1.109e+07
Local Clock Time Offset -1.522 -0.869 -0.615 0.000 0.597 0.869 5.131 1.212 1.738 0.376 -0.001 µs -3.674 12.6
Local RMS Frequency Jitter 19.000 31.000 38.000 76.000 179.000 264.000 1,591.000 141.000 233.000 56.304 89.539 10e-12 9.45 170
Local RMS Time Jitter 61.000 95.000 111.000 166.000 257.000 325.000 623.000 146.000 230.000 47.585 173.104 ns 27.74 113.8
Server Jitter 104.131.155.175 0.068 0.262 0.331 1.234 134.431 329.246 526.921 134.099 328.984 64.266 17.889 ms 2.326 18.33
Server Jitter 162.159.200.123 0.082 0.174 0.246 1.049 12.867 444.952 547.555 12.621 444.778 65.003 13.828 ms 3.29 25.8
Server Jitter 173.11.101.155 0.106 0.332 0.564 1.773 12.632 362.650 628.132 12.068 362.318 54.676 12.285 ms 3.895 33.76
Server Jitter 178.62.68.79 0.000 0.188 0.309 1.193 30.594 401.978 500.365 30.285 401.790 60.803 14.883 ms 2.84 21.52
Server Jitter 192.168.1.10 0.016 0.038 0.063 0.178 8.648 8.997 18.782 8.585 8.959 2.658 1.290 ms 0.6277 3.878
Server Jitter 194.58.202.211 0.089 0.184 0.290 1.308 11.441 284.206 542.124 11.151 284.023 50.576 10.418 ms 4.703 44.71
Server Jitter 194.58.202.219 0.078 0.174 0.261 1.188 11.222 294.947 539.552 10.961 294.774 46.616 9.685 ms 4.414 41.07
Server Jitter 203.123.48.219 0.000 0.181 0.259 1.207 11.850 293.471 597.684 11.591 293.290 48.819 9.917 ms 4.993 49.8
Server Jitter 204.123.2.5 0.117 0.159 0.281 1.355 10.008 378.272 547.106 9.727 378.113 60.053 13.291 ms 3.375 28
Server Jitter SHM(0) 0.062 0.223 0.345 0.981 3.126 5.776 10.243 2.781 5.553 1.014 1.258 ms 3.415 15.5
Server Jitter SHM(1) 19.000 67.000 95.000 210.000 497.000 677.000 2,674.000 402.000 610.000 136.351 242.783 ns 5.256 31.67
Server Offset 104.131.155.175 1.746 1.981 2.155 2.566 3.065 330.012 533.426 0.910 328.031 47.696 8.551 ms 5.401 52.13
Server Offset 162.159.200.123 1.713 2.056 2.361 2.699 3.064 3.714 417.139 0.703 1.657 20.934 4.347 ms 11.67 189.5
Server Offset 173.11.101.155 -4.304 -1.040 -0.461 0.149 0.622 2.832 512.484 1.084 3.871 23.610 2.076 ms 10.02 162.8
Server Offset 178.62.68.79 -3.180 -0.569 0.295 0.799 1.835 5.397 665.396 1.539 5.966 39.408 4.444 ms 9.492 144.8
Server Offset 192.168.1.10 -118.427 28.341 78.685 167.313 257.096 384.670 541.314 178.411 356.329 59.594 168.771 µs 12.47 44.58
Server Offset 194.58.202.211 1.763 3.360 3.491 3.787 4.105 4.467 293.512 0.614 1.107 16.274 4.995 ms 11.65 168.7
Server Offset 194.58.202.219 1.610 3.340 3.504 3.796 4.109 4.836 423.431 0.605 1.496 22.905 5.772 ms 9.964 138.7
Server Offset 203.123.48.219 4.273 4.539 4.707 5.004 5.336 5.595 531.493 0.629 1.056 29.120 7.057 ms 12.58 202.9
Server Offset 204.123.2.5 0.469 1.824 1.934 2.183 2.485 2.939 314.952 0.552 1.115 22.750 4.105 ms 9.137 115.3
Server Offset SHM(0) -71.554 -66.151 -62.963 -54.921 -47.109 -45.525 -42.746 15.854 20.626 4.781 -55.125 ms -2005 2.56e+04
Server Offset SHM(1) -1.523 -0.870 -0.616 0.001 0.598 0.870 5.132 1.214 1.740 0.377 -0.001 µs -3.676 12.57
TDOP 0.490 0.550 0.590 0.820 1.270 1.540 2.440 0.680 0.990 0.215 0.868 38.56 161.5
Temp ZONE0 56.920 56.920 57.996 60.148 62.300 62.838 63.376 4.304 5.918 1.346 59.968 °C
nSats 6.000 7.000 8.000 10.000 12.000 12.000 13.000 4.000 5.000 1.233 9.623 nSat 336.1 2434
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!