NTPsec

ntp2.wiktel.com

Report generated: Sat Apr 26 04:45:05 2025 UTC
Start Time: Sat Apr 19 04:45:00 2025 UTC
End Time: Sat Apr 26 04:45:00 2025 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 -167.140 -8.201 -4.732 0.264 3.524 5.238 38.165 8.256 13.439 2.636 -0.034 µs -7.359 103.2
Local Clock Frequency Offset -15.426 -15.280 -15.032 -13.072 -12.547 -12.443 7.646 2.485 2.837 1.960 -13.292 ppm -486.5 3864

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.363 0.959 1.279 2.619 4.679 5.875 83.685 3.400 4.916 1.152 2.752 µs 14.14 422.3

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.615 1.638 2.130 4.340 7.476 9.163 115.519 5.346 7.525 2.414 4.550 ppb 18.32 510.7

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 -167.140 -8.201 -4.732 0.264 3.524 5.238 38.165 8.256 13.439 2.636 -0.034 µs -7.359 103.2

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 132.163.97.5

peer offset 132.163.97.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.163.97.5 -1.142 -1.123 -1.110 -1.074 -1.042 -1.028 3.017 0.068 0.095 0.180 -1.067 ms -329.8 2466

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 132.246.11.229

peer offset 132.246.11.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.229 -1,044.105 -812.516 -771.726 -744.850 -722.056 -694.612 -407.660 49.670 117.904 23.416 -745.941 µs -3.557e+04 1.172e+06

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 134.84.84.84

peer offset 134.84.84.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 134.84.84.84 -309.623 -54.469 -31.420 -10.380 15.556 45.206 103.942 46.976 99.675 20.868 -10.044 µs -12.06 112.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 204.9.54.119

peer offset 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.9.54.119 -947.874 -907.662 -899.832 -778.212 -765.333 -761.168 -755.755 134.499 146.494 60.508 -825.614 µs -3185 4.73e+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 2600:2600::99 (ntp1.wiktel.com)

peer offset 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:2600::99 (ntp1.wiktel.com) -391.897 -366.377 -358.089 -342.629 -326.250 -319.656 -310.028 31.839 46.721 9.935 -342.440 µs -4.472e+04 1.59e+06

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::1 (time1.mbix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -448.885 -425.295 -409.112 -391.915 -375.443 -366.959 -360.892 33.669 58.336 10.533 -392.449 µs -5.612e+04 2.152e+06

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) -598.343 -530.735 -487.195 -426.064 -351.978 -323.278 -289.979 135.217 207.457 41.179 -425.851 µs -1493 1.732e+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 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) -531.029 -500.414 -481.439 -424.637 -312.618 -267.949 -245.614 168.821 232.465 50.657 -414.001 µs -798.5 7557

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::50

peer offset 2607:f128::50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f128::50 691.216 726.018 742.058 782.146 817.828 835.157 856.585 75.770 109.139 22.871 781.249 µs 3.656e+04 1.216e+06

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:2 (ntp2.doit.wisc.edu)

peer offset 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -138.270 -112.429 -83.298 -32.848 15.389 55.801 127.200 98.687 168.230 31.153 -33.396 µs -14.77 46.77

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset SHM(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -167.141 -8.202 -4.733 0.265 3.525 5.239 38.166 8.258 13.441 2.637 -0.034 µs -7.357 103.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 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.163.97.5

peer jitter 132.163.97.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.163.97.5 5.094 13.286 17.943 35.043 60.791 73.036 4,060.937 42.848 59.750 196.347 48.329 µs 15.42 292.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 132.246.11.229

peer jitter 132.246.11.229 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.229 0.007 0.012 0.018 0.292 0.676 1.696 3.280 0.658 1.684 0.297 0.308 ms 2.688 16.53

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 134.84.84.84

peer jitter 134.84.84.84 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 134.84.84.84 0.000 2.725 3.586 7.261 19.671 41.256 364.930 16.085 38.531 12.997 9.404 µs 17.09 418

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 204.9.54.119

peer jitter 204.9.54.119 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.9.54.119 2.101 4.069 5.573 9.992 16.471 22.076 119.314 10.898 18.007 4.729 10.511 µs 14.85 244

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::99 (ntp1.wiktel.com)

peer jitter 2600:2600::99 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 3.732 6.531 8.949 19.305 33.584 40.258 446.503 24.635 33.727 19.967 20.892 µs 18.08 379.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 2602:fd53:11e:123::1 (time1.mbix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 3.871 5.288 7.069 13.282 27.406 68.345 3,767.495 20.337 63.057 195.503 27.191 µs 14.37 268.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 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) 2.936 5.229 6.909 14.128 47.531 103.910 3,935.320 40.622 98.681 159.732 25.420 µs 21.01 513.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::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) 2.246 4.381 6.393 14.377 44.307 125.213 4,069.929 37.914 120.832 251.122 36.660 µs 12.08 195.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 2607:f128::50

peer jitter 2607:f128::50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f128::50 5.790 10.280 15.568 32.646 68.175 370.998 1,363.969 52.607 360.718 87.221 43.664 µs 9.703 121.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 2607:f388::123:2 (ntp2.doit.wisc.edu)

peer jitter 2607:f388::123:2 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 5.811 9.456 12.301 25.900 895.985 938.872 1,312.366 883.684 929.416 231.608 93.031 µs 1.465 7.561

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.094 0.465 0.785 2.457 6.434 8.940 167.798 5.649 8.475 1.890 2.857 µs 6.596 259.6

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 -15.426 -15.280 -15.032 -13.072 -12.547 -12.443 7.646 2.485 2.837 1.960 -13.292 ppm -486.5 3864
Local Clock Time Offset -167.140 -8.201 -4.732 0.264 3.524 5.238 38.165 8.256 13.439 2.636 -0.034 µs -7.359 103.2
Local RMS Frequency Jitter 0.615 1.638 2.130 4.340 7.476 9.163 115.519 5.346 7.525 2.414 4.550 ppb 18.32 510.7
Local RMS Time Jitter 0.363 0.959 1.279 2.619 4.679 5.875 83.685 3.400 4.916 1.152 2.752 µs 14.14 422.3
Server Jitter 132.163.97.5 5.094 13.286 17.943 35.043 60.791 73.036 4,060.937 42.848 59.750 196.347 48.329 µs 15.42 292.3
Server Jitter 132.246.11.229 0.007 0.012 0.018 0.292 0.676 1.696 3.280 0.658 1.684 0.297 0.308 ms 2.688 16.53
Server Jitter 134.84.84.84 0.000 2.725 3.586 7.261 19.671 41.256 364.930 16.085 38.531 12.997 9.404 µs 17.09 418
Server Jitter 204.9.54.119 2.101 4.069 5.573 9.992 16.471 22.076 119.314 10.898 18.007 4.729 10.511 µs 14.85 244
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 3.732 6.531 8.949 19.305 33.584 40.258 446.503 24.635 33.727 19.967 20.892 µs 18.08 379.1
Server Jitter 2602:fd53:11e:123::1 (time1.mbix.ca) 3.871 5.288 7.069 13.282 27.406 68.345 3,767.495 20.337 63.057 195.503 27.191 µs 14.37 268.2
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 2.936 5.229 6.909 14.128 47.531 103.910 3,935.320 40.622 98.681 159.732 25.420 µs 21.01 513.9
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 2.246 4.381 6.393 14.377 44.307 125.213 4,069.929 37.914 120.832 251.122 36.660 µs 12.08 195.5
Server Jitter 2607:f128::50 5.790 10.280 15.568 32.646 68.175 370.998 1,363.969 52.607 360.718 87.221 43.664 µs 9.703 121.9
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 5.811 9.456 12.301 25.900 895.985 938.872 1,312.366 883.684 929.416 231.608 93.031 µs 1.465 7.561
Server Jitter SHM(1) 0.094 0.465 0.785 2.457 6.434 8.940 167.798 5.649 8.475 1.890 2.857 µs 6.596 259.6
Server Offset 132.163.97.5 -1.142 -1.123 -1.110 -1.074 -1.042 -1.028 3.017 0.068 0.095 0.180 -1.067 ms -329.8 2466
Server Offset 132.246.11.229 -1,044.105 -812.516 -771.726 -744.850 -722.056 -694.612 -407.660 49.670 117.904 23.416 -745.941 µs -3.557e+04 1.172e+06
Server Offset 134.84.84.84 -309.623 -54.469 -31.420 -10.380 15.556 45.206 103.942 46.976 99.675 20.868 -10.044 µs -12.06 112.8
Server Offset 204.9.54.119 -947.874 -907.662 -899.832 -778.212 -765.333 -761.168 -755.755 134.499 146.494 60.508 -825.614 µs -3185 4.73e+04
Server Offset 2600:2600::99 (ntp1.wiktel.com) -391.897 -366.377 -358.089 -342.629 -326.250 -319.656 -310.028 31.839 46.721 9.935 -342.440 µs -4.472e+04 1.59e+06
Server Offset 2602:fd53:11e:123::1 (time1.mbix.ca) -448.885 -425.295 -409.112 -391.915 -375.443 -366.959 -360.892 33.669 58.336 10.533 -392.449 µs -5.612e+04 2.152e+06
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -598.343 -530.735 -487.195 -426.064 -351.978 -323.278 -289.979 135.217 207.457 41.179 -425.851 µs -1493 1.732e+04
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -531.029 -500.414 -481.439 -424.637 -312.618 -267.949 -245.614 168.821 232.465 50.657 -414.001 µs -798.5 7557
Server Offset 2607:f128::50 691.216 726.018 742.058 782.146 817.828 835.157 856.585 75.770 109.139 22.871 781.249 µs 3.656e+04 1.216e+06
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -138.270 -112.429 -83.298 -32.848 15.389 55.801 127.200 98.687 168.230 31.153 -33.396 µs -14.77 46.77
Server Offset SHM(1) -167.141 -8.202 -4.733 0.265 3.525 5.239 38.166 8.258 13.441 2.637 -0.034 µs -7.357 103.1
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!