NTPsec

crane3.services.mbix.ca

Report generated: Sun Nov 8 05:45:06 2026 UTC
Start Time: Sun Nov 1 05:45:04 2026 UTC
End Time: Sun Nov 8 05:45:04 2026 UTC
Report Period: 7.0 days

Top   Daily Stats   Weekly Stats  

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 -44.311 -23.260 -17.697 -3.286 28.594 39.611 72.272 46.291 62.871 14.018 0.001 µs -3.036 6.927
Local Clock Frequency Offset 78.274 78.319 78.383 78.572 78.648 78.668 78.720 0.265 0.349 0.086 78.546 ppm 7.544e+08 6.867e+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 5.149 9.091 11.234 18.301 26.882 30.790 42.304 15.648 21.699 4.779 18.573 µs 33.07 126.7

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 2.001 3.383 4.182 6.605 9.347 10.689 16.417 5.165 7.306 1.592 6.657 ppb 42.17 171.8

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 -44.311 -23.260 -17.697 -3.286 28.594 39.611 72.272 46.291 62.871 14.018 0.001 µs -3.036 6.927

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 78.274 78.319 78.383 78.572 78.648 78.668 78.720 0.265 0.349 0.086 78.546 ppm 7.544e+08 6.867e+11
Temp LM0 35.000 36.000 37.000 39.000 40.000 41.000 42.000 3.000 5.000 1.221 38.456 °C
Temp LM1 32.000 33.000 33.000 35.000 37.000 37.000 38.000 4.000 4.000 0.997 34.947 °C
Temp LM10 33.000 33.000 34.000 35.000 37.000 37.000 39.000 3.000 4.000 0.928 35.256 °C
Temp LM2 31.000 31.000 32.000 33.000 34.000 35.000 36.000 2.000 4.000 0.866 33.015 °C
Temp LM3 35.000 36.000 37.000 39.000 40.000 41.000 42.000 3.000 5.000 1.218 38.436 °C
Temp LM4 33.000 34.000 34.000 35.000 36.000 37.000 38.000 2.000 3.000 0.725 35.334 °C
Temp LM5 62.000 62.000 62.000 63.000 63.000 64.000 64.000 1.000 2.000 0.425 62.817 °C
Temp LM6 39.000 41.000 41.000 42.000 43.000 44.000 44.000 2.000 3.000 0.700 42.053 °C
Temp LM7 38.000 39.000 40.000 41.000 42.000 43.000 44.000 2.000 4.000 0.794 40.859 °C
Temp LM8 38.000 39.000 40.000 41.000 42.000 42.000 43.000 2.000 3.000 0.775 40.806 °C
Temp LM9 37.000 38.000 39.000 40.000 41.000 42.000 44.000 2.000 4.000 0.811 39.802 °C
Temp ZONE0 40.000 40.000 41.000 42.000 43.000 44.000 45.000 2.000 4.000 0.759 42.147 °C
Temp ZONE1 35.000 36.000 37.000 39.000 40.000 41.000 42.000 3.000 5.000 1.271 38.546 °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 132.246.11.227

peer offset 132.246.11.227 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.227 1.933 1.992 2.022 2.087 2.163 2.209 17.955 0.141 0.217 1.038 2.157 ms 19.58 302.4

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 142.3.100.2

peer offset 142.3.100.2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 142.3.100.2 -69.379 -53.262 -38.791 2.314 47.842 68.633 93.386 86.633 121.895 26.173 3.419 µs -3.09 7.458

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:2600::199 (ntp2.wiktel.com)

peer offset 2600:2600::199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:2600::199 (ntp2.wiktel.com) 319.765 329.881 341.690 372.209 400.812 411.841 450.256 59.122 81.960 17.700 371.999 µs 8080 1.629e+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 2602:fde5:2a::13 (ntp3.torix.ca)

peer offset 2602:fde5:2a::13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fde5:2a::13 (ntp3.torix.ca) 8.328 8.343 8.353 8.378 8.410 8.424 8.435 0.057 0.081 0.018 8.380 ms 1.072e+08 5.091e+10

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) -1.509 -1.189 -0.877 -0.353 0.236 0.388 0.718 1.113 1.577 0.320 -0.329 ms -14.47 45.66

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:f388::123:1 (ntp1.doit.wisc.edu)

peer offset 2607:f388::123:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -743.493 -551.191 -516.986 -470.754 -402.870 -257.958 282.185 114.116 293.233 50.656 -465.277 µs -1083 1.126e+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 PPS(0)

peer offset PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset PPS(0) -44.312 -23.261 -17.698 -3.287 28.595 39.612 72.273 46.293 62.873 14.018 0.001 µs -3.036 6.927

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 132.246.11.227

peer jitter 132.246.11.227 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.227 0.022 0.041 0.063 0.286 1.482 3.679 29.056 1.419 3.638 1.219 0.486 ms 13.28 283.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 142.3.100.2

peer jitter 142.3.100.2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 142.3.100.2 0.007 0.016 0.021 0.042 0.217 0.883 219.377 0.197 0.867 6.954 0.377 ms 23.39 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 2600:2600::199 (ntp2.wiktel.com)

peer jitter 2600:2600::199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:2600::199 (ntp2.wiktel.com) 4.249 8.284 11.152 20.751 40.828 57.139 1,005.539 29.676 48.855 38.590 24.171 µs 22.43 561.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 2602:fde5:2a::13 (ntp3.torix.ca)

peer jitter 2602:fde5:2a::13 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fde5:2a::13 (ntp3.torix.ca) 4.204 7.262 10.495 20.889 40.614 53.627 420.710 30.119 46.365 13.962 23.061 µs 15.17 375.3

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) 5.168 13.568 19.597 105.219 574.344 773.410 1,128.518 554.747 759.842 189.050 185.759 µs 1.398 4.927

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:f388::123:1 (ntp1.doit.wisc.edu)

peer jitter 2607:f388::123:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 4.669 9.223 12.136 23.916 51.098 103.474 378.223 38.962 94.251 21.610 27.963 µs 8.727 106.7

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 PPS(0)

peer jitter PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter PPS(0) 1.641 5.060 7.358 17.123 34.768 44.505 76.834 27.410 39.445 8.505 18.516 µs 6.228 20

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 78.274 78.319 78.383 78.572 78.648 78.668 78.720 0.265 0.349 0.086 78.546 ppm 7.544e+08 6.867e+11
Local Clock Time Offset -44.311 -23.260 -17.697 -3.286 28.594 39.611 72.272 46.291 62.871 14.018 0.001 µs -3.036 6.927
Local RMS Frequency Jitter 2.001 3.383 4.182 6.605 9.347 10.689 16.417 5.165 7.306 1.592 6.657 ppb 42.17 171.8
Local RMS Time Jitter 5.149 9.091 11.234 18.301 26.882 30.790 42.304 15.648 21.699 4.779 18.573 µs 33.07 126.7
Server Jitter 132.246.11.227 0.022 0.041 0.063 0.286 1.482 3.679 29.056 1.419 3.638 1.219 0.486 ms 13.28 283.5
Server Jitter 142.3.100.2 0.007 0.016 0.021 0.042 0.217 0.883 219.377 0.197 0.867 6.954 0.377 ms 23.39 686
Server Jitter 2600:2600::199 (ntp2.wiktel.com) 4.249 8.284 11.152 20.751 40.828 57.139 1,005.539 29.676 48.855 38.590 24.171 µs 22.43 561.5
Server Jitter 2602:fde5:2a::13 (ntp3.torix.ca) 4.204 7.262 10.495 20.889 40.614 53.627 420.710 30.119 46.365 13.962 23.061 µs 15.17 375.3
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 5.168 13.568 19.597 105.219 574.344 773.410 1,128.518 554.747 759.842 189.050 185.759 µs 1.398 4.927
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 4.669 9.223 12.136 23.916 51.098 103.474 378.223 38.962 94.251 21.610 27.963 µs 8.727 106.7
Server Jitter PPS(0) 1.641 5.060 7.358 17.123 34.768 44.505 76.834 27.410 39.445 8.505 18.516 µs 6.228 20
Server Offset 132.246.11.227 1.933 1.992 2.022 2.087 2.163 2.209 17.955 0.141 0.217 1.038 2.157 ms 19.58 302.4
Server Offset 142.3.100.2 -69.379 -53.262 -38.791 2.314 47.842 68.633 93.386 86.633 121.895 26.173 3.419 µs -3.09 7.458
Server Offset 2600:2600::199 (ntp2.wiktel.com) 319.765 329.881 341.690 372.209 400.812 411.841 450.256 59.122 81.960 17.700 371.999 µs 8080 1.629e+05
Server Offset 2602:fde5:2a::13 (ntp3.torix.ca) 8.328 8.343 8.353 8.378 8.410 8.424 8.435 0.057 0.081 0.018 8.380 ms 1.072e+08 5.091e+10
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1.509 -1.189 -0.877 -0.353 0.236 0.388 0.718 1.113 1.577 0.320 -0.329 ms -14.47 45.66
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -743.493 -551.191 -516.986 -470.754 -402.870 -257.958 282.185 114.116 293.233 50.656 -465.277 µs -1083 1.126e+04
Server Offset PPS(0) -44.312 -23.261 -17.698 -3.287 28.595 39.612 72.273 46.293 62.873 14.018 0.001 µs -3.036 6.927
Temp LM0 35.000 36.000 37.000 39.000 40.000 41.000 42.000 3.000 5.000 1.221 38.456 °C
Temp LM1 32.000 33.000 33.000 35.000 37.000 37.000 38.000 4.000 4.000 0.997 34.947 °C
Temp LM10 33.000 33.000 34.000 35.000 37.000 37.000 39.000 3.000 4.000 0.928 35.256 °C
Temp LM2 31.000 31.000 32.000 33.000 34.000 35.000 36.000 2.000 4.000 0.866 33.015 °C
Temp LM3 35.000 36.000 37.000 39.000 40.000 41.000 42.000 3.000 5.000 1.218 38.436 °C
Temp LM4 33.000 34.000 34.000 35.000 36.000 37.000 38.000 2.000 3.000 0.725 35.334 °C
Temp LM5 62.000 62.000 62.000 63.000 63.000 64.000 64.000 1.000 2.000 0.425 62.817 °C
Temp LM6 39.000 41.000 41.000 42.000 43.000 44.000 44.000 2.000 3.000 0.700 42.053 °C
Temp LM7 38.000 39.000 40.000 41.000 42.000 43.000 44.000 2.000 4.000 0.794 40.859 °C
Temp LM8 38.000 39.000 40.000 41.000 42.000 42.000 43.000 2.000 3.000 0.775 40.806 °C
Temp LM9 37.000 38.000 39.000 40.000 41.000 42.000 44.000 2.000 4.000 0.811 39.802 °C
Temp ZONE0 40.000 40.000 41.000 42.000 43.000 44.000 45.000 2.000 4.000 0.759 42.147 °C
Temp ZONE1 35.000 36.000 37.000 39.000 40.000 41.000 42.000 3.000 5.000 1.271 38.546 °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.
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!