NTPsec

C-ntpsec-24-hour-stats

Report generated: Thu Jul 18 02:08:18 2019 UTC
Start Time: Wed Jul 17 02:08:11 2019 UTC
End Time: Thu Jul 18 02:08:11 2019 UTC
Report published: Wed Jul 17 19:09:19 2019 PDT
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 -3.032 -1.823 -1.217 -0.159 1.084 1.626 2.619 2.301 3.449 0.726 -0.104 µs -4.857 12.58
Local Clock Frequency Offset -8.535 -8.534 -8.523 -8.404 -8.283 -8.273 -8.272 0.241 0.261 0.067 -8.411 ppm -2.051e+06 2.606e+08

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 93.000 124.000 145.000 224.000 494.000 677.000 962.000 349.000 553.000 111.747 255.632 ns 8.074 31.83

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 24.000 31.000 41.000 112.000 363.000 485.000 719.000 322.000 454.000 105.659 148.148 10e-12 2.699 8.351

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 -3.032 -1.823 -1.217 -0.159 1.084 1.626 2.619 2.301 3.449 0.726 -0.104 µs -4.857 12.58

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 -8.535 -8.534 -8.523 -8.404 -8.283 -8.273 -8.272 0.241 0.261 0.067 -8.411 ppm -2.051e+06 2.606e+08
Temp ZONE0 57.458 57.996 57.996 59.610 61.762 62.300 62.300 3.766 4.304 0.941 59.567 °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 7.000 10.000 12.000 12.000 12.000 5.000 5.000 1.435 9.679 nSat 206.5 1285
TDOP 0.490 0.580 0.610 0.800 1.350 1.760 2.480 0.740 1.180 0.249 0.873 24.81 100.3

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -5.028 -4.335 -3.925 -2.262 0.324 1.560 1.855 4.249 5.895 1.193 -2.185 ms -30.32 106.6

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.677 -2.459 -2.223 -1.760 -1.275 -1.084 -0.006 0.948 1.375 0.302 -1.772 ms -343.5 2494

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 -7.130 -6.533 -6.081 -5.271 -4.631 -4.122 -3.887 1.450 2.411 0.470 -5.311 ms -1895 2.376e+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 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 -180.562 -98.972 -48.193 17.756 109.968 187.797 271.351 158.161 286.769 48.603 20.252 µs -1.017 7.416

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

peer offset 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.11 -271.437 -68.760 -41.604 29.818 106.360 153.680 295.490 147.964 222.440 46.739 30.084 µs -1.009 7.048

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 -1.921 -1.810 -1.731 -1.231 -0.866 -0.704 -0.614 0.865 1.106 0.264 -1.265 ms -211.4 1330

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) -87.412 -72.405 -69.552 -59.433 -50.123 -46.777 -42.734 19.429 25.628 5.991 -59.485 ms -1339 1.499e+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) -3.033 -1.824 -1.218 -0.160 1.085 1.627 2.620 2.303 3.451 0.726 -0.104 µs -4.857 12.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 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.359 0.470 0.566 1.369 7.944 56.105 56.174 7.378 55.634 6.190 2.772 ms 5.635 47.61

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.191 0.311 0.547 1.237 8.265 21.706 21.732 7.719 21.395 3.267 2.266 ms 3.17 18

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.360 0.534 0.754 1.823 6.904 14.475 57.141 6.150 13.941 4.728 2.881 ms 7.675 83.21

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.009 0.025 0.062 0.540 5.948 10.204 56.661 5.886 10.179 4.364 1.483 ms 8.029 102.6

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

peer jitter 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.11 0.022 0.039 0.075 0.628 6.133 56.430 57.005 6.058 56.391 6.444 2.063 ms 5.269 46.47

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.240 0.258 0.397 1.202 7.176 15.278 57.617 6.779 15.020 5.326 2.541 ms 6.3 65.11

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.119 0.402 0.572 1.393 3.882 6.621 16.912 3.310 6.219 1.208 1.731 ms 3.8 17.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.



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.037 0.086 0.127 0.326 0.808 1.127 1.900 0.681 1.041 0.226 0.381 µs 3.812 13

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 -8.535 -8.534 -8.523 -8.404 -8.283 -8.273 -8.272 0.241 0.261 0.067 -8.411 ppm -2.051e+06 2.606e+08
Local Clock Time Offset -3.032 -1.823 -1.217 -0.159 1.084 1.626 2.619 2.301 3.449 0.726 -0.104 µs -4.857 12.58
Local RMS Frequency Jitter 24.000 31.000 41.000 112.000 363.000 485.000 719.000 322.000 454.000 105.659 148.148 10e-12 2.699 8.351
Local RMS Time Jitter 93.000 124.000 145.000 224.000 494.000 677.000 962.000 349.000 553.000 111.747 255.632 ns 8.074 31.83
Server Jitter 162.159.200.1 0.359 0.470 0.566 1.369 7.944 56.105 56.174 7.378 55.634 6.190 2.772 ms 5.635 47.61
Server Jitter 164.67.62.194 0.191 0.311 0.547 1.237 8.265 21.706 21.732 7.719 21.395 3.267 2.266 ms 3.17 18
Server Jitter 173.11.101.155 0.360 0.534 0.754 1.823 6.904 14.475 57.141 6.150 13.941 4.728 2.881 ms 7.675 83.21
Server Jitter 192.168.1.10 0.009 0.025 0.062 0.540 5.948 10.204 56.661 5.886 10.179 4.364 1.483 ms 8.029 102.6
Server Jitter 192.168.1.11 0.022 0.039 0.075 0.628 6.133 56.430 57.005 6.058 56.391 6.444 2.063 ms 5.269 46.47
Server Jitter 204.123.2.5 0.240 0.258 0.397 1.202 7.176 15.278 57.617 6.779 15.020 5.326 2.541 ms 6.3 65.11
Server Jitter SHM(0) 0.119 0.402 0.572 1.393 3.882 6.621 16.912 3.310 6.219 1.208 1.731 ms 3.8 17.88
Server Jitter SHM(1) 0.037 0.086 0.127 0.326 0.808 1.127 1.900 0.681 1.041 0.226 0.381 µs 3.812 13
Server Offset 162.159.200.1 -5.028 -4.335 -3.925 -2.262 0.324 1.560 1.855 4.249 5.895 1.193 -2.185 ms -30.32 106.6
Server Offset 164.67.62.194 -2.677 -2.459 -2.223 -1.760 -1.275 -1.084 -0.006 0.948 1.375 0.302 -1.772 ms -343.5 2494
Server Offset 173.11.101.155 -7.130 -6.533 -6.081 -5.271 -4.631 -4.122 -3.887 1.450 2.411 0.470 -5.311 ms -1895 2.376e+04
Server Offset 192.168.1.10 -180.562 -98.972 -48.193 17.756 109.968 187.797 271.351 158.161 286.769 48.603 20.252 µs -1.017 7.416
Server Offset 192.168.1.11 -271.437 -68.760 -41.604 29.818 106.360 153.680 295.490 147.964 222.440 46.739 30.084 µs -1.009 7.048
Server Offset 204.123.2.5 -1.921 -1.810 -1.731 -1.231 -0.866 -0.704 -0.614 0.865 1.106 0.264 -1.265 ms -211.4 1330
Server Offset SHM(0) -87.412 -72.405 -69.552 -59.433 -50.123 -46.777 -42.734 19.429 25.628 5.991 -59.485 ms -1339 1.499e+04
Server Offset SHM(1) -3.033 -1.824 -1.218 -0.160 1.085 1.627 2.620 2.303 3.451 0.726 -0.104 µs -4.857 12.58
TDOP 0.490 0.580 0.610 0.800 1.350 1.760 2.480 0.740 1.180 0.249 0.873 24.81 100.3
Temp ZONE0 57.458 57.996 57.996 59.610 61.762 62.300 62.300 3.766 4.304 0.941 59.567 °C
nSats 6.000 7.000 7.000 10.000 12.000 12.000 12.000 5.000 5.000 1.435 9.679 nSat 206.5 1285
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!