NTPsec

ntp1.wiktel.com

Report generated: Tue Jul 15 18:53:00 2025 UTC
Start Time: Mon Jul 14 18:53:00 2025 UTC
End Time: Tue Jul 15 18: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 -13.894 -6.314 -4.756 -0.337 5.528 7.544 11.065 10.284 13.858 3.092 0.034 µs -3.592 8.454
Local Clock Frequency Offset 17.402 17.424 17.478 17.649 17.747 17.769 17.805 0.269 0.345 0.082 17.633 ppm 9.641e+06 2.052e+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.273 0.371 0.450 0.665 1.478 2.211 5.525 1.028 1.840 0.358 0.758 µs 8.192 47.01

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.182 0.294 0.404 1.096 2.750 3.625 5.010 2.346 3.331 0.766 1.301 ppb 3.612 10.94

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 -13.894 -6.314 -4.756 -0.337 5.528 7.544 11.065 10.284 13.858 3.092 0.034 µs -3.592 8.454

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 -551.809 -470.367 -394.333 -48.721 118.325 154.666 164.862 512.658 625.033 182.450 -120.575 µs -9.76 27.03

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 -613.383 -518.532 -149.742 -1.506 390.203 621.267 679.496 539.945 1,139.799 177.485 36.303 µs -2.297 7.812

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 199.102.46.70

peer offset 199.102.46.70 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 199.102.46.70 -322.548 -301.415 -293.620 -251.792 87.115 98.990 113.988 380.735 400.405 174.856 -108.318 µs -9.075 23.44

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.960 -3.986 -2.138 1.499 3.608 4.572 5.902 5.747 8.557 1.781 1.215 ms -1.698 5.158

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) -110.034 -104.790 -87.610 -54.157 -23.886 -17.029 -15.879 63.724 87.761 19.915 -54.639 µs -63.96 287.1

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) -561.701 -338.726 -269.573 261.694 521.338 563.869 606.433 790.911 902.595 252.873 180.006 µs -1.43 3.346

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) -190.510 -172.742 -104.249 206.767 427.096 471.643 536.582 531.345 644.385 169.017 162.418 µs -0.2672 2.078

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) -19.395 -18.696 -16.737 0.015 0.065 0.081 0.110 16.802 18.777 5.741 -2.705 ms -9.36 32.38

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) -457.327 -443.300 -422.092 -371.861 -207.204 -140.623 -138.505 214.888 302.677 58.596 -360.277 µs -384.6 2865

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) -13.895 -6.315 -4.757 -0.338 5.529 7.545 11.066 10.286 13.860 3.093 0.034 µs -3.593 8.454

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 11.105 11.938 15.536 38.371 340.832 375.663 432.163 325.296 363.725 96.713 77.502 µs 1.525 4.79

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.211 0.304 0.380 0.630 0.909 1.252 1.463 0.529 0.949 0.171 0.635 ms 29.22 116

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 199.102.46.70

peer jitter 199.102.46.70 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 199.102.46.70 6.286 10.002 13.105 23.989 323.084 361.931 382.546 309.979 351.929 94.458 56.670 µs 1.251 4.441

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 2.712 3.035 4.082 10.856 23.634 35.258 61.544 19.551 32.223 6.659 11.859 ms 5.132 25.92

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) 9.876 9.943 11.938 23.170 44.456 54.435 181.409 32.518 44.492 13.229 25.601 µs 9.391 93.68

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) 12.492 12.945 15.723 47.270 323.073 376.648 409.428 307.350 363.703 90.494 85.576 µs 1.654 5.044

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) 6.776 7.255 12.516 34.025 328.729 380.576 388.115 316.213 373.321 91.890 67.915 µs 1.599 5.348

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) 0.011 0.013 0.019 0.039 6.437 10.607 12.336 6.418 10.594 2.267 1.154 ms 0.6068 4.823

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.652 9.324 13.509 27.122 53.523 62.200 65.406 40.014 52.876 11.447 29.094 µs 9.133 28.79

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.122 0.237 0.344 0.758 1.930 3.134 10.499 1.586 2.897 0.580 0.913 µs 4.9 32.13

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.402 17.424 17.478 17.649 17.747 17.769 17.805 0.269 0.345 0.082 17.633 ppm 9.641e+06 2.052e+09
Local Clock Time Offset -13.894 -6.314 -4.756 -0.337 5.528 7.544 11.065 10.284 13.858 3.092 0.034 µs -3.592 8.454
Local RMS Frequency Jitter 0.182 0.294 0.404 1.096 2.750 3.625 5.010 2.346 3.331 0.766 1.301 ppb 3.612 10.94
Local RMS Time Jitter 0.273 0.371 0.450 0.665 1.478 2.211 5.525 1.028 1.840 0.358 0.758 µs 8.192 47.01
Server Jitter 128.101.101.101 11.105 11.938 15.536 38.371 340.832 375.663 432.163 325.296 363.725 96.713 77.502 µs 1.525 4.79
Server Jitter 128.138.141.177 0.211 0.304 0.380 0.630 0.909 1.252 1.463 0.529 0.949 0.171 0.635 ms 29.22 116
Server Jitter 199.102.46.70 6.286 10.002 13.105 23.989 323.084 361.931 382.546 309.979 351.929 94.458 56.670 µs 1.251 4.441
Server Jitter 209.87.233.53 2.712 3.035 4.082 10.856 23.634 35.258 61.544 19.551 32.223 6.659 11.859 ms 5.132 25.92
Server Jitter 2602:fd53:11e:123::2 (time2.mbix.ca) 9.876 9.943 11.938 23.170 44.456 54.435 181.409 32.518 44.492 13.229 25.601 µs 9.391 93.68
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 12.492 12.945 15.723 47.270 323.073 376.648 409.428 307.350 363.703 90.494 85.576 µs 1.654 5.044
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 6.776 7.255 12.516 34.025 328.729 380.576 388.115 316.213 373.321 91.890 67.915 µs 1.599 5.348
Server Jitter 2607:f128:1:3::dd1 (dns1.steadfast.net) 0.011 0.013 0.019 0.039 6.437 10.607 12.336 6.418 10.594 2.267 1.154 ms 0.6068 4.823
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 5.652 9.324 13.509 27.122 53.523 62.200 65.406 40.014 52.876 11.447 29.094 µs 9.133 28.79
Server Jitter PPS(0) 0.122 0.237 0.344 0.758 1.930 3.134 10.499 1.586 2.897 0.580 0.913 µs 4.9 32.13
Server Offset 128.101.101.101 -551.809 -470.367 -394.333 -48.721 118.325 154.666 164.862 512.658 625.033 182.450 -120.575 µs -9.76 27.03
Server Offset 128.138.141.177 -613.383 -518.532 -149.742 -1.506 390.203 621.267 679.496 539.945 1,139.799 177.485 36.303 µs -2.297 7.812
Server Offset 199.102.46.70 -322.548 -301.415 -293.620 -251.792 87.115 98.990 113.988 380.735 400.405 174.856 -108.318 µs -9.075 23.44
Server Offset 209.87.233.53 -4.960 -3.986 -2.138 1.499 3.608 4.572 5.902 5.747 8.557 1.781 1.215 ms -1.698 5.158
Server Offset 2602:fd53:11e:123::2 (time2.mbix.ca) -110.034 -104.790 -87.610 -54.157 -23.886 -17.029 -15.879 63.724 87.761 19.915 -54.639 µs -63.96 287.1
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -561.701 -338.726 -269.573 261.694 521.338 563.869 606.433 790.911 902.595 252.873 180.006 µs -1.43 3.346
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -190.510 -172.742 -104.249 206.767 427.096 471.643 536.582 531.345 644.385 169.017 162.418 µs -0.2672 2.078
Server Offset 2607:f128:1:3::dd1 (dns1.steadfast.net) -19.395 -18.696 -16.737 0.015 0.065 0.081 0.110 16.802 18.777 5.741 -2.705 ms -9.36 32.38
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -457.327 -443.300 -422.092 -371.861 -207.204 -140.623 -138.505 214.888 302.677 58.596 -360.277 µs -384.6 2865
Server Offset PPS(0) -13.895 -6.315 -4.757 -0.338 5.529 7.545 11.066 10.286 13.860 3.093 0.034 µs -3.593 8.454
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!