NTPsec

C-ntpsec-1-hour-stats

Report generated: Mon Oct 19 16:01:08 2020 UTC
Start Time: Mon Oct 19 15:00:40 2020 UTC
End Time: Mon Oct 19 16:01:08 2020 UTC
Report published: Mon Oct 19 09:01:13 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 -906.000 -847.000 -751.000 -313.000 205.000 314.000 362.000 956.000 1,161.000 263.614 -317.029 ns -16.98 52.69
Local Clock Frequency Offset -5.314 -5.314 -5.313 -5.306 -5.295 -5.294 -5.293 0.0183 0.0199 0.0061 -5.305 ppm -6.619e+08 5.768e+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 122.000 127.000 134.000 166.000 215.000 231.000 234.000 81.000 104.000 23.969 169.429 ns 242.2 1592

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 57.000 105.000 197.000 264.000 273.000 140.000 216.000 43.257 107.891 10e-12 9.155 31.84

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 -906.000 -847.000 -751.000 -313.000 205.000 314.000 362.000 956.000 1,161.000 263.614 -317.029 ns -16.98 52.69

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.314 -5.314 -5.313 -5.306 -5.295 -5.294 -5.293 0.0183 0.0199 0.0061 -5.305 ppm -6.619e+08 5.768e+11
Temp ZONE0 57.458 57.458 57.996 57.996 57.996 58.534 58.534 0.000 1.076 0.139 57.996 °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 11.000 11.000 11.000 11.000 2.000 2.000 0.719 10.500 nSat 2560 3.534e+04
TDOP 0.680 0.680 0.690 0.740 1.210 1.220 1.220 0.520 0.540 0.185 0.856 58.96 263.6

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.524 1.524 1.524 3.232 3.602 3.602 3.602 2.078 2.078 0.825 2.638 ms 17.07 52.36

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.833 1.833 1.833 2.235 2.444 2.444 2.444 0.611 0.611 0.205 2.152 ms 882.3 8637

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 -533.693 -533.693 -533.693 181.169 994.583 994.583 994.583 1,528.276 1,528.276 427.354 268.754 µs -1.163 3.001

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 1.951 1.951 1.951 2.134 2.134 2.134 2.134 0.182 0.182 0.091 2.042 ms 9865 2.125e+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 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 -26.661 -26.661 -19.224 43.070 107.759 121.507 121.507 126.983 148.168 34.249 40.583 µs 0.6521 2.974

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 2.092 2.092 2.092 2.539 2.837 2.837 2.837 0.745 0.745 0.214 2.536 ms 1304 1.447e+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(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) -62.881 -62.024 -61.490 -55.422 -50.702 -49.684 -49.495 10.788 12.340 3.275 -55.889 ms -5952 1.085e+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 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) -907.000 -848.000 -752.000 -314.000 206.000 315.000 363.000 958.000 1,163.000 264.027 -317.735 ns -16.99 52.71

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.000 0.000 0.000 0.369 16.546 16.546 16.546 16.546 16.546 7.113 4.229 ms -0.1299 1.475

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.256 0.256 0.256 1.935 8.733 8.733 8.733 8.477 8.477 3.028 2.915 ms 1.053 2.582

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.883 0.883 0.883 2.546 9.697 9.697 9.697 8.814 8.814 2.911 3.510 ms 1.895 4.537

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 1.175 1.175 1.175 2.990 2.990 2.990 2.990 1.815 1.815 0.908 2.083 ms 6.051 13.86

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 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.031 0.031 0.052 0.239 8.671 9.166 9.166 8.620 9.135 2.566 1.566 ms 0.6886 3.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.573 0.573 0.573 1.958 8.214 8.214 8.214 7.641 7.641 2.203 2.552 ms 2.482 6.962

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.184 0.223 0.311 0.943 3.090 5.558 6.214 2.780 5.335 0.958 1.217 ms 3.247 13.41

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) 82.000 85.000 105.000 215.000 442.000 609.000 704.000 337.000 524.000 108.219 238.307 ns 6.422 20.43

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.314 -5.314 -5.313 -5.306 -5.295 -5.294 -5.293 0.0183 0.0199 0.0061 -5.305 ppm -6.619e+08 5.768e+11
Local Clock Time Offset -906.000 -847.000 -751.000 -313.000 205.000 314.000 362.000 956.000 1,161.000 263.614 -317.029 ns -16.98 52.69
Local RMS Frequency Jitter 46.000 48.000 57.000 105.000 197.000 264.000 273.000 140.000 216.000 43.257 107.891 10e-12 9.155 31.84
Local RMS Time Jitter 122.000 127.000 134.000 166.000 215.000 231.000 234.000 81.000 104.000 23.969 169.429 ns 242.2 1592
Server Jitter 104.131.155.175 0.000 0.000 0.000 0.369 16.546 16.546 16.546 16.546 16.546 7.113 4.229 ms -0.1299 1.475
Server Jitter 162.159.200.1 0.256 0.256 0.256 1.935 8.733 8.733 8.733 8.477 8.477 3.028 2.915 ms 1.053 2.582
Server Jitter 173.11.101.155 0.883 0.883 0.883 2.546 9.697 9.697 9.697 8.814 8.814 2.911 3.510 ms 1.895 4.537
Server Jitter 178.62.68.79 1.175 1.175 1.175 2.990 2.990 2.990 2.990 1.815 1.815 0.908 2.083 ms 6.051 13.86
Server Jitter 192.168.1.10 0.031 0.031 0.052 0.239 8.671 9.166 9.166 8.620 9.135 2.566 1.566 ms 0.6886 3.47
Server Jitter 204.123.2.5 0.573 0.573 0.573 1.958 8.214 8.214 8.214 7.641 7.641 2.203 2.552 ms 2.482 6.962
Server Jitter SHM(0) 0.184 0.223 0.311 0.943 3.090 5.558 6.214 2.780 5.335 0.958 1.217 ms 3.247 13.41
Server Jitter SHM(1) 82.000 85.000 105.000 215.000 442.000 609.000 704.000 337.000 524.000 108.219 238.307 ns 6.422 20.43
Server Offset 104.131.155.175 1.524 1.524 1.524 3.232 3.602 3.602 3.602 2.078 2.078 0.825 2.638 ms 17.07 52.36
Server Offset 162.159.200.1 1.833 1.833 1.833 2.235 2.444 2.444 2.444 0.611 0.611 0.205 2.152 ms 882.3 8637
Server Offset 173.11.101.155 -533.693 -533.693 -533.693 181.169 994.583 994.583 994.583 1,528.276 1,528.276 427.354 268.754 µs -1.163 3.001
Server Offset 178.62.68.79 1.951 1.951 1.951 2.134 2.134 2.134 2.134 0.182 0.182 0.091 2.042 ms 9865 2.125e+05
Server Offset 192.168.1.10 -26.661 -26.661 -19.224 43.070 107.759 121.507 121.507 126.983 148.168 34.249 40.583 µs 0.6521 2.974
Server Offset 204.123.2.5 2.092 2.092 2.092 2.539 2.837 2.837 2.837 0.745 0.745 0.214 2.536 ms 1304 1.447e+04
Server Offset SHM(0) -62.881 -62.024 -61.490 -55.422 -50.702 -49.684 -49.495 10.788 12.340 3.275 -55.889 ms -5952 1.085e+05
Server Offset SHM(1) -907.000 -848.000 -752.000 -314.000 206.000 315.000 363.000 958.000 1,163.000 264.027 -317.735 ns -16.99 52.71
TDOP 0.680 0.680 0.690 0.740 1.210 1.220 1.220 0.520 0.540 0.185 0.856 58.96 263.6
Temp ZONE0 57.458 57.458 57.996 57.996 57.996 58.534 58.534 0.000 1.076 0.139 57.996 °C
nSats 9.000 9.000 9.000 11.000 11.000 11.000 11.000 2.000 2.000 0.719 10.500 nSat 2560 3.534e+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!