NTPsec

ntp1.wiktel.com

Report generated: Mon Apr 7 14:53:02 2025 UTC
Start Time: Sun Apr 6 14:53:01 2025 UTC
End Time: Mon Apr 7 14:53:01 2025 UTC
Report Period: 1.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 -7.597 -1.755 -1.105 0.018 1.033 1.475 3.133 2.138 3.230 0.733 -0.021 µs -5.612 25.19
Local Clock Frequency Offset 17.714 17.721 17.738 17.768 17.799 17.816 17.823 0.060 0.095 0.0171 17.769 ppm 1.114e+09 1.155e+12

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.311 0.370 0.423 0.590 1.561 2.380 3.614 1.138 2.010 0.379 0.700 µs 6.269 29.65

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 135.000 165.000 193.000 295.000 608.000 864.000 1,354.000 415.000 699.000 136.910 331.634 10e-12 9.243 37.21

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 -7.597 -1.755 -1.105 0.018 1.033 1.475 3.133 2.138 3.230 0.733 -0.021 µs -5.612 25.19

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats 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 128.101.101.101

peer offset 128.101.101.101 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 128.101.101.101 -89.913 -80.106 -34.322 49.620 126.453 144.451 287.224 160.775 224.557 49.038 49.501 µs 0.257 5.211

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 128.138.141.177

peer offset 128.138.141.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 128.138.141.177 -328.138 -213.883 -91.738 98.412 595.361 791.766 966.045 687.099 1,005.649 224.952 162.489 µs 0.1017 2.918

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:470:0:2c8::2 (clock.nyc.he.net)

peer offset 2001:470:0:2c8::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2001:470:0:2c8::2 (clock.nyc.he.net) -1.430 -1.423 -1.247 -0.893 -0.511 0.503 0.529 0.736 1.926 0.300 -0.831 ms -62.94 267.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 209.87.233.53

peer offset 209.87.233.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 209.87.233.53 -4.800 -2.298 -0.691 1.538 3.306 4.173 4.451 3.997 6.471 1.278 1.439 ms -0.5277 5.41

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:fd53:11e:123::2 (time2.mbix.ca)

peer offset 2602:fd53:11e:123::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -96.132 -78.461 -64.623 -35.040 -11.529 -3.952 2.166 53.094 74.509 15.711 -35.227 µs -44.52 187

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) -677.150 -674.780 -533.994 -358.163 -220.973 -168.807 -166.733 313.021 505.973 98.880 -381.373 µs -129.7 711.3

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::123 (time.cloudflare.com)

peer offset 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -438.038 -429.546 -408.563 -341.604 -284.241 -271.921 -271.900 124.322 157.625 37.126 -343.129 µs -1105 1.165e+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 2607:f128:1:3::dd1 (dns1.steadfast.net)

peer offset 2607:f128:1:3::dd1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) -309.459 -293.750 -280.052 -243.344 -203.740 -192.377 -190.536 76.312 101.373 22.703 -243.304 µs -1644 1.967e+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 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) -88.643 -71.072 -50.681 -10.157 30.282 43.106 61.615 80.963 114.178 23.528 -10.317 µs -7.449 21.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) -7.598 -1.756 -1.106 0.019 1.034 1.476 3.134 2.140 3.232 0.734 -0.021 µs -5.608 25.14

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 128.101.101.101

peer jitter 128.101.101.101 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 128.101.101.101 5.882 6.897 9.510 22.648 60.246 87.178 100.747 50.736 80.281 17.076 27.635 µs 3.482 10.96

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 128.138.141.177

peer jitter 128.138.141.177 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 128.138.141.177 0.243 0.277 0.387 0.605 0.844 1.012 1.234 0.457 0.736 0.151 0.611 ms 38.01 151.8

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:470:0:2c8::2 (clock.nyc.he.net)

peer jitter 2001:470:0:2c8::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2001:470:0:2c8::2 (clock.nyc.he.net) 0.006 0.008 0.011 0.022 0.167 0.679 5.927 0.157 0.671 0.354 0.062 ms 12.49 209.2

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 209.87.233.53

peer jitter 209.87.233.53 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 209.87.233.53 1.595 1.646 2.946 8.746 16.117 48.249 163.600 13.171 46.603 10.662 10.035 ms 10.67 149.4

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:fd53:11e:123::2 (time2.mbix.ca)

peer jitter 2602:fd53:11e:123::2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 7.755 8.395 9.943 20.675 43.782 888.865 1,151.569 33.839 880.470 129.377 38.441 µs 5.391 44.9

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) 8.474 8.970 11.152 24.012 85.292 112.996 126.993 74.140 104.026 20.783 30.253 µs 3.868 15.39

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::123 (time.cloudflare.com)

peer jitter 2606:4700:f1::123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.005 0.008 0.011 0.022 0.093 2.161 2.167 0.081 2.154 0.254 0.062 ms 5.183 45.02

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:f128:1:3::dd1 (dns1.steadfast.net)

peer jitter 2607:f128:1:3::dd1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 10.618 12.582 16.649 32.457 75.660 321.946 338.065 59.011 309.364 45.130 42.772 µs 4.914 29.73

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) 7.536 8.621 12.940 22.396 45.902 60.234 71.168 32.962 51.613 10.528 25.153 µs 8.036 26.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 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) 0.105 0.236 0.309 0.567 1.526 2.857 6.888 1.217 2.621 0.500 0.694 µs 5.518 38.06

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 17.714 17.721 17.738 17.768 17.799 17.816 17.823 0.060 0.095 0.0171 17.769 ppm 1.114e+09 1.155e+12
Local Clock Time Offset -7.597 -1.755 -1.105 0.018 1.033 1.475 3.133 2.138 3.230 0.733 -0.021 µs -5.612 25.19
Local RMS Frequency Jitter 135.000 165.000 193.000 295.000 608.000 864.000 1,354.000 415.000 699.000 136.910 331.634 10e-12 9.243 37.21
Local RMS Time Jitter 0.311 0.370 0.423 0.590 1.561 2.380 3.614 1.138 2.010 0.379 0.700 µs 6.269 29.65
Server Jitter 128.101.101.101 5.882 6.897 9.510 22.648 60.246 87.178 100.747 50.736 80.281 17.076 27.635 µs 3.482 10.96
Server Jitter 128.138.141.177 0.243 0.277 0.387 0.605 0.844 1.012 1.234 0.457 0.736 0.151 0.611 ms 38.01 151.8
Server Jitter 2001:470:0:2c8::2 (clock.nyc.he.net) 0.006 0.008 0.011 0.022 0.167 0.679 5.927 0.157 0.671 0.354 0.062 ms 12.49 209.2
Server Jitter 209.87.233.53 1.595 1.646 2.946 8.746 16.117 48.249 163.600 13.171 46.603 10.662 10.035 ms 10.67 149.4
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 7.755 8.395 9.943 20.675 43.782 888.865 1,151.569 33.839 880.470 129.377 38.441 µs 5.391 44.9
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 8.474 8.970 11.152 24.012 85.292 112.996 126.993 74.140 104.026 20.783 30.253 µs 3.868 15.39
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 0.005 0.008 0.011 0.022 0.093 2.161 2.167 0.081 2.154 0.254 0.062 ms 5.183 45.02
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 10.618 12.582 16.649 32.457 75.660 321.946 338.065 59.011 309.364 45.130 42.772 µs 4.914 29.73
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 7.536 8.621 12.940 22.396 45.902 60.234 71.168 32.962 51.613 10.528 25.153 µs 8.036 26.5
Server Jitter PPS(0) 0.105 0.236 0.309 0.567 1.526 2.857 6.888 1.217 2.621 0.500 0.694 µs 5.518 38.06
Server Offset 128.101.101.101 -89.913 -80.106 -34.322 49.620 126.453 144.451 287.224 160.775 224.557 49.038 49.501 µs 0.257 5.211
Server Offset 128.138.141.177 -328.138 -213.883 -91.738 98.412 595.361 791.766 966.045 687.099 1,005.649 224.952 162.489 µs 0.1017 2.918
Server Offset 2001:470:0:2c8::2 (clock.nyc.he.net) -1.430 -1.423 -1.247 -0.893 -0.511 0.503 0.529 0.736 1.926 0.300 -0.831 ms -62.94 267.5
Server Offset 209.87.233.53 -4.800 -2.298 -0.691 1.538 3.306 4.173 4.451 3.997 6.471 1.278 1.439 ms -0.5277 5.41
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -96.132 -78.461 -64.623 -35.040 -11.529 -3.952 2.166 53.094 74.509 15.711 -35.227 µs -44.52 187
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -677.150 -674.780 -533.994 -358.163 -220.973 -168.807 -166.733 313.021 505.973 98.880 -381.373 µs -129.7 711.3
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -438.038 -429.546 -408.563 -341.604 -284.241 -271.921 -271.900 124.322 157.625 37.126 -343.129 µs -1105 1.165e+04
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) -309.459 -293.750 -280.052 -243.344 -203.740 -192.377 -190.536 76.312 101.373 22.703 -243.304 µs -1644 1.967e+04
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -88.643 -71.072 -50.681 -10.157 30.282 43.106 61.615 80.963 114.178 23.528 -10.317 µs -7.449 21.04
Server Offset PPS(0) -7.598 -1.756 -1.106 0.019 1.034 1.476 3.134 2.140 3.232 0.734 -0.021 µs -5.608 25.14
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!