NTPsec

A-ntpsec-6-hour-stats

Report generated: Sun Mar 3 05:04:22 2024 UTC
Start Time: Sat Mar 2 23:04:22 2024 UTC
End Time: Sun Mar 3 05:04:22 2024 UTC
Report published: Sat Mar 02 09:04:27 PM 2024 PST
Report Period: 0.2 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.582 -1.173 -0.885 0.031 0.750 1.015 1.674 1.635 2.188 0.488 -0.001 µs -4.274 11.01
Local Clock Frequency Offset -321.289 -320.236 -319.290 -309.219 -304.672 -303.284 -302.261 14.618 16.952 4.216 -309.928 ppb -4.138e+05 3.085e+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 0.301 0.391 0.447 0.640 0.894 1.000 1.235 0.447 0.609 0.136 0.648 µs 65.79 300.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 118.000 143.000 167.000 231.000 316.000 353.000 410.000 149.000 210.000 44.969 234.472 10e-12 87.89 431.9

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.582 -1.173 -0.885 0.031 0.750 1.015 1.674 1.635 2.188 0.488 -0.001 µs -4.274 11.01

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 -321.289 -320.236 -319.290 -309.219 -304.672 -303.284 -302.261 14.618 16.952 4.216 -309.928 ppb -4.138e+05 3.085e+07
Temp ZONE0 46.160 46.160 46.160 47.236 47.236 47.774 47.774 1.076 1.614 0.305 47.113 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 7.000 8.000 9.000 10.000 12.000 12.000 12.000 3.000 4.000 0.925 9.874 nSat 935.7 9356
TDOP 0.500 0.510 0.550 0.800 1.200 1.230 1.490 0.650 0.720 0.188 0.832 51.07 219.2

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 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 3.367 3.367 3.930 4.873 310.304 441.556 441.556 306.374 438.189 125.540 88.440 ms 0.1287 1.84

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 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 1.366 1.366 1.451 2.116 432.660 493.512 493.512 431.209 492.145 134.067 86.639 ms 0.2936 2.728

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 -12.470 -12.470 -8.938 0.208 314.540 498.796 498.796 323.479 511.265 131.900 78.395 ms 0.1298 2.693

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

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

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

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



Server Offset 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 1.895 1.895 2.153 2.836 311.096 494.682 494.682 308.942 492.787 119.226 80.772 ms 0.2054 2.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 216.218.254.202

peer offset 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.254.202 1.882 1.882 2.130 2.759 334.370 493.213 493.213 332.240 491.331 134.211 94.760 ms 0.1725 2.062

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 52.10.183.132

peer offset 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 52.10.183.132 4.477 4.477 4.670 5.521 317.178 463.434 463.434 312.508 458.957 118.663 77.503 ms 0.2573 2.404

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) -101.678 -101.055 -100.589 -96.791 -95.256 -94.610 -93.893 5.333 6.445 1.465 -97.083 ms -3.044e+05 2.049e+07

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.583 -1.174 -0.886 0.032 0.750 1.016 1.675 1.636 2.190 0.489 -0.001 µs -4.273 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 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.301 0.301 0.423 3.023 324.909 476.014 476.014 324.486 475.713 115.137 78.854 ms 0.5169 3.405

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 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 169.229.128.134 0.573 0.573 0.628 1.891 339.017 448.298 448.298 338.390 447.725 111.851 70.686 ms 0.3829 3.051

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 2.322 2.322 3.151 7.309 293.269 473.820 473.820 290.118 471.498 109.620 72.551 ms 0.6041 3.764

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.218.192.202

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.687 0.687 0.892 3.120 247.182 463.980 463.980 246.290 463.293 108.462 75.063 ms 0.4687 3.408

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 216.218.254.202

peer jitter 216.218.254.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.254.202 0.679 0.679 0.823 1.653 298.591 471.381 471.381 297.768 470.701 109.802 76.502 ms 0.4976 3.413

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 52.10.183.132

peer jitter 52.10.183.132 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 52.10.183.132 0.568 0.568 0.944 3.626 253.807 466.569 466.569 252.863 466.001 108.673 69.778 ms 0.5308 3.686

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.036 0.067 0.094 0.275 0.931 1.343 2.372 0.837 1.275 0.287 0.372 ms 2.572 9.155

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) 0.105 0.237 0.320 0.607 1.155 1.403 1.819 0.835 1.166 0.255 0.653 µs 9.484 30.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 -321.289 -320.236 -319.290 -309.219 -304.672 -303.284 -302.261 14.618 16.952 4.216 -309.928 ppb -4.138e+05 3.085e+07
Local Clock Time Offset -1.582 -1.173 -0.885 0.031 0.750 1.015 1.674 1.635 2.188 0.488 -0.001 µs -4.274 11.01
Local RMS Frequency Jitter 118.000 143.000 167.000 231.000 316.000 353.000 410.000 149.000 210.000 44.969 234.472 10e-12 87.89 431.9
Local RMS Time Jitter 0.301 0.391 0.447 0.640 0.894 1.000 1.235 0.447 0.609 0.136 0.648 µs 65.79 300.3
Server Jitter 162.159.200.1 0.301 0.301 0.423 3.023 324.909 476.014 476.014 324.486 475.713 115.137 78.854 ms 0.5169 3.405
Server Jitter 169.229.128.134 0.573 0.573 0.628 1.891 339.017 448.298 448.298 338.390 447.725 111.851 70.686 ms 0.3829 3.051
Server Jitter 173.11.101.155 2.322 2.322 3.151 7.309 293.269 473.820 473.820 290.118 471.498 109.620 72.551 ms 0.6041 3.764
Server Jitter 216.218.192.202 0.687 0.687 0.892 3.120 247.182 463.980 463.980 246.290 463.293 108.462 75.063 ms 0.4687 3.408
Server Jitter 216.218.254.202 0.679 0.679 0.823 1.653 298.591 471.381 471.381 297.768 470.701 109.802 76.502 ms 0.4976 3.413
Server Jitter 52.10.183.132 0.568 0.568 0.944 3.626 253.807 466.569 466.569 252.863 466.001 108.673 69.778 ms 0.5308 3.686
Server Jitter SHM(0) 0.036 0.067 0.094 0.275 0.931 1.343 2.372 0.837 1.275 0.287 0.372 ms 2.572 9.155
Server Jitter SHM(1) 0.105 0.237 0.320 0.607 1.155 1.403 1.819 0.835 1.166 0.255 0.653 µs 9.484 30.88
Server Offset 162.159.200.1 3.367 3.367 3.930 4.873 310.304 441.556 441.556 306.374 438.189 125.540 88.440 ms 0.1287 1.84
Server Offset 169.229.128.134 1.366 1.366 1.451 2.116 432.660 493.512 493.512 431.209 492.145 134.067 86.639 ms 0.2936 2.728
Server Offset 173.11.101.155 -12.470 -12.470 -8.938 0.208 314.540 498.796 498.796 323.479 511.265 131.900 78.395 ms 0.1298 2.693
Server Offset 216.218.192.202 1.895 1.895 2.153 2.836 311.096 494.682 494.682 308.942 492.787 119.226 80.772 ms 0.2054 2.5
Server Offset 216.218.254.202 1.882 1.882 2.130 2.759 334.370 493.213 493.213 332.240 491.331 134.211 94.760 ms 0.1725 2.062
Server Offset 52.10.183.132 4.477 4.477 4.670 5.521 317.178 463.434 463.434 312.508 458.957 118.663 77.503 ms 0.2573 2.404
Server Offset SHM(0) -101.678 -101.055 -100.589 -96.791 -95.256 -94.610 -93.893 5.333 6.445 1.465 -97.083 ms -3.044e+05 2.049e+07
Server Offset SHM(1) -1.583 -1.174 -0.886 0.032 0.750 1.016 1.675 1.636 2.190 0.489 -0.001 µs -4.273 11
TDOP 0.500 0.510 0.550 0.800 1.200 1.230 1.490 0.650 0.720 0.188 0.832 51.07 219.2
Temp ZONE0 46.160 46.160 46.160 47.236 47.236 47.774 47.774 1.076 1.614 0.305 47.113 °C
nSats 7.000 8.000 9.000 10.000 12.000 12.000 12.000 3.000 4.000 0.925 9.874 nSat 935.7 9356
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!