NTPsec

A-ntpsec-3-hour-stats

Report generated: Mon Nov 9 21:01:32 2026 UTC
Start Time: Mon Nov 9 18:01:32 2026 UTC
End Time: Mon Nov 9 21:01:32 2026 UTC
Report published: Mon Nov 09 01:01:54 PM 2026 PST
Report Period: 0.1 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 -2.324 -1.395 -0.898 0.014 0.836 1.157 1.645 1.734 2.552 0.532 -0.005 µs -0.2369 3.334
Local Clock Frequency Offset 147.491 147.873 148.315 149.948 151.871 152.267 152.679 3.556 4.394 1.085 150.025 ppb 0.1305 2.236

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.382 0.436 0.500 0.723 1.058 1.254 1.404 0.558 0.818 0.166 0.743 µs 0.7891 3.943

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 134.000 158.000 182.000 249.000 351.000 390.000 456.000 169.000 232.000 49.970 255.613 10e-12 0.6084 3.468

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 -2.324 -1.395 -0.898 0.014 0.836 1.157 1.645 1.734 2.552 0.532 -0.005 µs -0.2369 3.334

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 147.491 147.873 148.315 149.948 151.871 152.267 152.679 3.556 4.394 1.085 150.025 ppb 0.1305 2.236
Temp ZONE0 54.768 54.768 54.768 55.844 55.844 55.844 56.382 1.076 1.076 0.418 55.510 °C

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

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



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 173.8.172.33

peer offset 173.8.172.33 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.8.172.33 -2.431 -2.431 -1.381 1.134 4.178 6.389 6.389 5.558 8.820 2.036 1.374 ms 0.48 2.757

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 2001:5a8:601:4005::36

peer offset 2001:5a8:601:4005::36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:5a8:601:4005::36 2.534 2.534 2.635 3.607 5.383 5.430 5.430 2.749 2.896 0.913 3.891 ms 0.6654 1.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 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com)

peer offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.871 0.871 1.675 4.707 5.667 6.151 6.151 3.991 5.279 1.411 4.100 ms -0.6598 2.293

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 2600:3c02::f03c:93ff:fecf:972e (time.cifelli.xyz)

peer offset 2600:3c02::f03c:93ff:fecf:972e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:3c02::f03c:93ff:fecf:972e (time.cifelli.xyz) 0.863 0.863 1.859 3.774 5.940 6.610 6.610 4.081 5.747 1.313 3.476 ms 0.1892 2.269

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 2606:4700:f1::1 (time.cloudflare.com)

peer offset 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 2.199 2.199 2.887 5.282 5.547 5.708 5.708 2.660 3.510 1.067 4.638 ms -0.8476 2.069

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 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu)

peer offset 2607:f140:ffff:8000:0:8006:0:a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 1.649 1.649 2.458 3.727 5.543 5.657 5.657 3.085 4.008 0.956 3.823 ms 0.1928 2.664

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 66.220.9.122

peer offset 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 66.220.9.122 1.906 1.906 2.969 3.440 5.367 5.435 5.435 2.398 3.529 0.819 3.723 ms 0.687 2.866

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) -132.359 -132.351 -132.180 -130.812 -129.586 -129.254 -128.929 2.594 3.098 0.794 -130.767 ms -0.168 2.292

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) -2.325 -1.396 -0.899 0.015 0.837 1.158 1.646 1.736 2.554 0.533 -0.005 µs -0.2362 3.326

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 173.8.172.33

peer jitter 173.8.172.33 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.8.172.33 0.000 0.000 0.000 2.563 12.276 14.180 14.180 12.276 14.180 4.041 4.374 ms 1.006 2.896

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 2001:5a8:601:4005::36

peer jitter 2001:5a8:601:4005::36 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:5a8:601:4005::36 0.384 0.384 0.589 2.073 19.397 19.443 19.443 18.808 19.058 5.328 4.572 ms 1.77 4.936

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 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com)

peer jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.933 0.933 1.221 3.666 12.156 18.387 18.387 10.935 17.454 3.744 4.659 ms 1.365 5.342

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 2600:3c02::f03c:93ff:fecf:972e (time.cifelli.xyz)

peer jitter 2600:3c02::f03c:93ff:fecf:972e plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:3c02::f03c:93ff:fecf:972e (time.cifelli.xyz) 0.445 0.445 0.622 2.232 12.412 12.418 12.418 11.790 11.973 3.403 3.494 ms 1.751 4.827

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 2606:4700:f1::1 (time.cloudflare.com)

peer jitter 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.322 0.322 0.337 4.961 14.898 15.771 15.771 14.561 15.449 5.186 6.233 ms 0.4064 1.541

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 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu)

peer jitter 2607:f140:ffff:8000:0:8006:0:a plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.543 0.543 0.552 2.342 9.655 10.694 10.694 9.103 10.152 2.738 3.255 ms 1.338 3.827

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 66.220.9.122

peer jitter 66.220.9.122 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 66.220.9.122 0.523 0.523 0.890 2.089 12.430 12.594 12.594 11.540 12.072 2.658 2.803 ms 2.859 10.32

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.044 0.053 0.112 0.393 1.076 1.515 1.637 0.964 1.462 0.299 0.461 ms 1.324 4.853

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.156 0.269 0.349 0.658 1.264 1.688 2.369 0.915 1.419 0.285 0.716 µs 1.294 5.756

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 147.491 147.873 148.315 149.948 151.871 152.267 152.679 3.556 4.394 1.085 150.025 ppb 0.1305 2.236
Local Clock Time Offset -2.324 -1.395 -0.898 0.014 0.836 1.157 1.645 1.734 2.552 0.532 -0.005 µs -0.2369 3.334
Local RMS Frequency Jitter 134.000 158.000 182.000 249.000 351.000 390.000 456.000 169.000 232.000 49.970 255.613 10e-12 0.6084 3.468
Local RMS Time Jitter 0.382 0.436 0.500 0.723 1.058 1.254 1.404 0.558 0.818 0.166 0.743 µs 0.7891 3.943
Server Jitter 173.8.172.33 0.000 0.000 0.000 2.563 12.276 14.180 14.180 12.276 14.180 4.041 4.374 ms 1.006 2.896
Server Jitter 2001:5a8:601:4005::36 0.384 0.384 0.589 2.073 19.397 19.443 19.443 18.808 19.058 5.328 4.572 ms 1.77 4.936
Server Jitter 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.933 0.933 1.221 3.666 12.156 18.387 18.387 10.935 17.454 3.744 4.659 ms 1.365 5.342
Server Jitter 2600:3c02::f03c:93ff:fecf:972e (time.cifelli.xyz) 0.445 0.445 0.622 2.232 12.412 12.418 12.418 11.790 11.973 3.403 3.494 ms 1.751 4.827
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 0.322 0.322 0.337 4.961 14.898 15.771 15.771 14.561 15.449 5.186 6.233 ms 0.4064 1.541
Server Jitter 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 0.543 0.543 0.552 2.342 9.655 10.694 10.694 9.103 10.152 2.738 3.255 ms 1.338 3.827
Server Jitter 66.220.9.122 0.523 0.523 0.890 2.089 12.430 12.594 12.594 11.540 12.072 2.658 2.803 ms 2.859 10.32
Server Jitter SHM(0) 0.044 0.053 0.112 0.393 1.076 1.515 1.637 0.964 1.462 0.299 0.461 ms 1.324 4.853
Server Jitter SHM(1) 0.156 0.269 0.349 0.658 1.264 1.688 2.369 0.915 1.419 0.285 0.716 µs 1.294 5.756
Server Offset 173.8.172.33 -2.431 -2.431 -1.381 1.134 4.178 6.389 6.389 5.558 8.820 2.036 1.374 ms 0.48 2.757
Server Offset 2001:5a8:601:4005::36 2.534 2.534 2.635 3.607 5.383 5.430 5.430 2.749 2.896 0.913 3.891 ms 0.6654 1.974
Server Offset 2600:1f13:eda:9800:bcd8:839c:9b40:25b2 (oregon.time.system76.com) 0.871 0.871 1.675 4.707 5.667 6.151 6.151 3.991 5.279 1.411 4.100 ms -0.6598 2.293
Server Offset 2600:3c02::f03c:93ff:fecf:972e (time.cifelli.xyz) 0.863 0.863 1.859 3.774 5.940 6.610 6.610 4.081 5.747 1.313 3.476 ms 0.1892 2.269
Server Offset 2606:4700:f1::1 (time.cloudflare.com) 2.199 2.199 2.887 5.282 5.547 5.708 5.708 2.660 3.510 1.067 4.638 ms -0.8476 2.069
Server Offset 2607:f140:ffff:8000:0:8006:0:a (ntp1.net.berkeley.edu) 1.649 1.649 2.458 3.727 5.543 5.657 5.657 3.085 4.008 0.956 3.823 ms 0.1928 2.664
Server Offset 66.220.9.122 1.906 1.906 2.969 3.440 5.367 5.435 5.435 2.398 3.529 0.819 3.723 ms 0.687 2.866
Server Offset SHM(0) -132.359 -132.351 -132.180 -130.812 -129.586 -129.254 -128.929 2.594 3.098 0.794 -130.767 ms -0.168 2.292
Server Offset SHM(1) -2.325 -1.396 -0.899 0.015 0.837 1.158 1.646 1.736 2.554 0.533 -0.005 µs -0.2362 3.326
Temp ZONE0 54.768 54.768 54.768 55.844 55.844 55.844 56.382 1.076 1.076 0.418 55.510 °C
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.
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 FIsher-Pearson moment of skewness. There are other different ways to calculate Skewness Wikipedia describes Skewness best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
Kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses standard Kurtosis. There are other different ways to calculate 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".
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!