NTPsec

ntp1.wiktel.com

Report generated: Sat Apr 26 02:53:00 2025 UTC
Start Time: Fri Apr 25 02:53:00 2025 UTC
End Time: Sat Apr 26 02:53:00 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 -9.656 -5.110 -3.626 0.041 3.304 4.602 5.745 6.930 9.712 1.929 0.002 µs -4.227 11.75
Local Clock Frequency Offset 17.779 17.785 17.796 17.922 18.113 18.132 18.140 0.317 0.347 0.097 17.939 ppm 6.169e+06 1.131e+09

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.293 0.367 0.414 0.599 1.324 1.843 2.703 0.910 1.476 0.287 0.675 µs 9.05 38.55

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 0.151 0.193 0.227 0.561 1.976 2.434 2.974 1.749 2.241 0.559 0.759 ppb 2.383 6.405

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 -9.656 -5.110 -3.626 0.041 3.304 4.602 5.745 6.930 9.712 1.929 0.002 µs -4.227 11.75

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 -450.219 -399.613 -324.522 21.288 118.424 177.410 196.190 442.946 577.023 140.831 -25.954 µs -6.532 20.28

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 -156.055 -138.016 -89.885 45.298 409.515 558.749 765.088 499.400 696.765 170.754 99.549 µs -0.3865 2.753

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) -2.360 -1.264 -0.896 -0.669 -0.595 -0.550 -0.516 0.301 0.714 0.166 -0.702 ms -165.2 1099

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 -6.217 -2.841 -0.778 1.808 3.377 4.317 5.371 4.154 7.158 1.352 1.625 ms -0.7512 6.677

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) -114.108 -90.443 -75.085 -43.761 -25.227 -17.590 -15.826 49.858 72.853 15.463 -46.061 µs -75.74 362.8

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) -904.013 -904.013 -805.383 -709.112 -380.312 -363.224 -363.224 425.071 540.789 181.008 -599.617 µs -93.07 457.2

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) -836.149 -822.695 -803.264 -465.627 -379.792 -362.650 -338.391 423.472 460.045 173.241 -571.352 µs -92.53 457.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 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) -446.344 -428.747 -418.988 -382.219 -342.518 -322.872 -313.553 76.470 105.875 22.941 -382.558 µs -5575 9.948e+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) -114.045 -84.970 -66.283 -17.882 49.647 97.849 106.679 115.930 182.819 33.951 -16.375 µs -6.818 17.43

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) -9.657 -5.111 -3.627 0.042 3.305 4.603 5.746 6.932 9.714 1.930 0.002 µs -4.227 11.75

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 6.248 8.187 11.943 50.070 366.956 412.432 432.123 355.013 404.245 144.317 152.799 µs 0.5754 1.484

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 269.292 300.917 393.278 625.712 855.604 955.390 1,028.225 462.326 654.473 140.902 619.404 µs 49.36 205.1

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.007 0.008 0.011 0.023 3.320 4.859 6.013 3.309 4.851 1.025 0.295 ms 1.417 9.276

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 0.636 1.152 3.207 10.523 21.066 56.700 70.509 17.859 55.548 8.699 11.752 ms 4.812 28.35

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) 8.260 8.874 10.869 21.332 38.651 51.351 322.041 27.782 42.477 25.370 24.546 µs 9.989 116.1

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) 6.839 6.839 12.255 53.452 359.235 376.834 376.834 346.980 369.995 131.272 131.787 µs 0.6529 1.726

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) 8.889 11.429 13.473 41.117 341.219 376.689 422.530 327.746 365.260 134.058 140.836 µs 0.5538 1.467

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) 13.841 14.925 19.011 32.408 61.940 839.579 1,208.664 42.929 824.654 95.238 44.568 µs 8.33 88.35

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) 5.832 9.810 12.348 24.511 47.432 75.905 83.859 35.084 66.095 11.884 26.637 µs 7.248 26.81

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.149 0.238 0.315 0.606 1.557 2.391 4.695 1.242 2.153 0.440 0.731 µs 5.008 25.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 17.779 17.785 17.796 17.922 18.113 18.132 18.140 0.317 0.347 0.097 17.939 ppm 6.169e+06 1.131e+09
Local Clock Time Offset -9.656 -5.110 -3.626 0.041 3.304 4.602 5.745 6.930 9.712 1.929 0.002 µs -4.227 11.75
Local RMS Frequency Jitter 0.151 0.193 0.227 0.561 1.976 2.434 2.974 1.749 2.241 0.559 0.759 ppb 2.383 6.405
Local RMS Time Jitter 0.293 0.367 0.414 0.599 1.324 1.843 2.703 0.910 1.476 0.287 0.675 µs 9.05 38.55
Server Jitter 128.101.101.101 6.248 8.187 11.943 50.070 366.956 412.432 432.123 355.013 404.245 144.317 152.799 µs 0.5754 1.484
Server Jitter 128.138.141.177 269.292 300.917 393.278 625.712 855.604 955.390 1,028.225 462.326 654.473 140.902 619.404 µs 49.36 205.1
Server Jitter 2001:470:0:2c8::2 (clock.nyc.he.net) 0.007 0.008 0.011 0.023 3.320 4.859 6.013 3.309 4.851 1.025 0.295 ms 1.417 9.276
Server Jitter 209.87.233.53 0.636 1.152 3.207 10.523 21.066 56.700 70.509 17.859 55.548 8.699 11.752 ms 4.812 28.35
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 8.260 8.874 10.869 21.332 38.651 51.351 322.041 27.782 42.477 25.370 24.546 µs 9.989 116.1
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 6.839 6.839 12.255 53.452 359.235 376.834 376.834 346.980 369.995 131.272 131.787 µs 0.6529 1.726
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 8.889 11.429 13.473 41.117 341.219 376.689 422.530 327.746 365.260 134.058 140.836 µs 0.5538 1.467
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 13.841 14.925 19.011 32.408 61.940 839.579 1,208.664 42.929 824.654 95.238 44.568 µs 8.33 88.35
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 5.832 9.810 12.348 24.511 47.432 75.905 83.859 35.084 66.095 11.884 26.637 µs 7.248 26.81
Server Jitter PPS(0) 0.149 0.238 0.315 0.606 1.557 2.391 4.695 1.242 2.153 0.440 0.731 µs 5.008 25.43
Server Offset 128.101.101.101 -450.219 -399.613 -324.522 21.288 118.424 177.410 196.190 442.946 577.023 140.831 -25.954 µs -6.532 20.28
Server Offset 128.138.141.177 -156.055 -138.016 -89.885 45.298 409.515 558.749 765.088 499.400 696.765 170.754 99.549 µs -0.3865 2.753
Server Offset 2001:470:0:2c8::2 (clock.nyc.he.net) -2.360 -1.264 -0.896 -0.669 -0.595 -0.550 -0.516 0.301 0.714 0.166 -0.702 ms -165.2 1099
Server Offset 209.87.233.53 -6.217 -2.841 -0.778 1.808 3.377 4.317 5.371 4.154 7.158 1.352 1.625 ms -0.7512 6.677
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -114.108 -90.443 -75.085 -43.761 -25.227 -17.590 -15.826 49.858 72.853 15.463 -46.061 µs -75.74 362.8
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -904.013 -904.013 -805.383 -709.112 -380.312 -363.224 -363.224 425.071 540.789 181.008 -599.617 µs -93.07 457.2
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -836.149 -822.695 -803.264 -465.627 -379.792 -362.650 -338.391 423.472 460.045 173.241 -571.352 µs -92.53 457.3
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) -446.344 -428.747 -418.988 -382.219 -342.518 -322.872 -313.553 76.470 105.875 22.941 -382.558 µs -5575 9.948e+04
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -114.045 -84.970 -66.283 -17.882 49.647 97.849 106.679 115.930 182.819 33.951 -16.375 µs -6.818 17.43
Server Offset PPS(0) -9.657 -5.111 -3.627 0.042 3.305 4.603 5.746 6.932 9.714 1.930 0.002 µs -4.227 11.75
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!