NTPsec

crane1.services.mbix.ca

Report generated: Sun Nov 15 17:45:04 2026 UTC
Start Time: Sun Nov 8 17:45:02 2026 UTC
End Time: Sun Nov 15 17:45:02 2026 UTC
Report Period: 7.0 days

Top   Daily Stats   Weekly Stats  

Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -51.058 -23.427 -17.626 -3.310 29.952 42.129 72.909 47.578 65.556 14.225 -0.000 µs -2.925 6.833
Local Clock Frequency Offset 72.869 72.884 72.892 72.950 73.457 73.554 73.663 0.565 0.671 0.197 73.056 ppm 5.04e+07 1.862e+10

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 5.671 8.887 10.957 18.333 27.903 32.140 43.690 16.946 23.253 5.170 18.722 µs 26.3 95.99

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 2.032 3.371 4.073 6.610 9.747 11.179 17.130 5.674 7.808 1.751 6.722 ppb 31.9 122.5

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 -51.058 -23.427 -17.626 -3.310 29.952 42.129 72.909 47.578 65.556 14.225 -0.000 µs -2.925 6.833

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset 72.869 72.884 72.892 72.950 73.457 73.554 73.663 0.565 0.671 0.197 73.056 ppm 5.04e+07 1.862e+10
Temp ZONE0 36.000 37.000 38.000 40.000 42.000 43.000 44.000 4.000 6.000 1.301 39.580 °C
Temp ZONE1 31.000 32.000 33.000 35.000 36.000 37.000 37.000 3.000 5.000 1.163 34.490 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 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 -62.782 -62.782 -46.870 31.913 76.092 94.139 94.139 122.962 156.921 36.630 25.407 µs -1.308 3.362

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.233.154.245

peer offset 128.233.154.245 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 128.233.154.245 -43.464 -16.003 -2.445 28.875 65.544 84.373 111.899 67.989 100.376 20.991 29.821 µs 1.593 4.811

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.238

peer offset 132.246.11.238 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 132.246.11.238 1.050 1.092 1.130 1.279 1.565 1.615 6.483 0.435 0.523 0.333 1.358 ms 50.16 469.4

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

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

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

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



Server Offset 2600:2600::199 (ntp2.wiktel.com)

peer offset 2600:2600::199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2600:2600::199 (ntp2.wiktel.com) -29.096 -13.866 -0.146 33.460 63.294 76.510 94.506 63.440 90.376 19.513 32.801 µs 2.248 5.517

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

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

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

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



Server Offset 2602:fde5:2a::11 (ntp1.torix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fde5:2a::11 (ntp1.torix.ca) 8.038 8.342 8.353 8.401 19.230 19.251 19.282 10.877 10.909 4.324 10.565 ms 8.824 28.64

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

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

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

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



Server Offset 2606:4700:f1::1 (time.cloudflare.com)

peer offset 2606:4700:f1::1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1,087.608 -954.364 -763.590 -405.500 124.653 271.106 515.450 888.243 1,225.470 256.643 -371.591 µs -21.56 70.83

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) -778.486 -665.231 -540.902 -470.496 -360.716 -240.048 -160.593 180.186 425.183 61.914 -465.667 µs -643.7 5699

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 2610:20:6f97:97::6 (time-e-wwv.nist.gov)

peer offset 2610:20:6f97:97::6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2610:20:6f97:97::6 (time-e-wwv.nist.gov) -63.651 -37.909 -23.887 17.304 68.401 89.481 120.544 92.288 127.390 27.983 18.818 µs -0.7103 3.119

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 2620:149:a33:3000::21 (usnyc3-ntp-001.aaplimg.com)

peer offset 2620:149:a33:3000::21 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:149:a33:3000::21 (usnyc3-ntp-001.aaplimg.com) 730.921 758.810 775.110 831.541 878.235 893.322 923.592 103.125 134.512 31.223 828.924 µs 1.675e+04 4.299e+05

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

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

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

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



Server Offset 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) -51.059 -23.428 -17.627 -3.311 29.953 42.130 72.910 47.580 65.558 14.226 -0.000 µs -2.925 6.833

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 0.000 0.000 0.000 20.561 60.322 87.869 87.869 60.322 87.869 18.973 21.795 µs 1.459 4.924

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.233.154.245

peer jitter 128.233.154.245 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 128.233.154.245 0.005 0.009 0.012 0.027 0.268 2.690 3.565 0.255 2.681 0.427 0.117 ms 3.142 23.88

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.238

peer jitter 132.246.11.238 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 132.246.11.238 0.023 0.052 0.075 0.328 2.340 4.214 180.864 2.265 4.162 9.243 1.065 ms 15.04 284.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.



Server Jitter 2600:2600::199 (ntp2.wiktel.com)

peer jitter 2600:2600::199 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2600:2600::199 (ntp2.wiktel.com) 5.646 8.716 11.251 22.650 45.237 58.338 87.704 33.986 49.622 10.702 24.902 µs 7.49 24.97

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2602:fde5:2a::11 (ntp1.torix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fde5:2a::11 (ntp1.torix.ca) 0.004 0.009 0.013 0.026 0.056 0.203 10.840 0.043 0.193 0.349 0.048 ms 21.8 593.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.



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.200 11.883 15.764 36.337 397.332 609.487 989.152 381.568 597.604 131.052 88.654 µs 1.852 8.793

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu)

peer jitter 2607:f388::123:1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 4.874 10.406 13.576 26.498 57.281 89.633 665.929 43.705 79.227 30.957 31.267 µs 14.13 265.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 2610:20:6f97:97::6 (time-e-wwv.nist.gov)

peer jitter 2610:20:6f97:97::6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2610:20:6f97:97::6 (time-e-wwv.nist.gov) 7.670 14.249 19.299 36.037 65.142 80.403 1,028.447 45.843 66.154 27.222 39.053 µs 25.91 910.7

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 2620:149:a33:3000::21 (usnyc3-ntp-001.aaplimg.com)

peer jitter 2620:149:a33:3000::21 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:149:a33:3000::21 (usnyc3-ntp-001.aaplimg.com) 0.007 0.013 0.020 0.076 46.929 61.398 74.769 46.909 61.385 15.818 10.624 ms 0.4969 3.173

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

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

RMS Jitter is field 8 in the peerstats log file.



Server Jitter PPS(0)

peer jitter PPS(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter PPS(0) 1.427 4.832 7.028 17.027 36.144 47.041 72.912 29.116 42.209 9.039 18.580 µs 5.463 17.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset 72.869 72.884 72.892 72.950 73.457 73.554 73.663 0.565 0.671 0.197 73.056 ppm 5.04e+07 1.862e+10
Local Clock Time Offset -51.058 -23.427 -17.626 -3.310 29.952 42.129 72.909 47.578 65.556 14.225 -0.000 µs -2.925 6.833
Local RMS Frequency Jitter 2.032 3.371 4.073 6.610 9.747 11.179 17.130 5.674 7.808 1.751 6.722 ppb 31.9 122.5
Local RMS Time Jitter 5.671 8.887 10.957 18.333 27.903 32.140 43.690 16.946 23.253 5.170 18.722 µs 26.3 95.99
Server Jitter 128.101.101.101 0.000 0.000 0.000 20.561 60.322 87.869 87.869 60.322 87.869 18.973 21.795 µs 1.459 4.924
Server Jitter 128.233.154.245 0.005 0.009 0.012 0.027 0.268 2.690 3.565 0.255 2.681 0.427 0.117 ms 3.142 23.88
Server Jitter 132.246.11.238 0.023 0.052 0.075 0.328 2.340 4.214 180.864 2.265 4.162 9.243 1.065 ms 15.04 284.6
Server Jitter 2600:2600::199 (ntp2.wiktel.com) 5.646 8.716 11.251 22.650 45.237 58.338 87.704 33.986 49.622 10.702 24.902 µs 7.49 24.97
Server Jitter 2602:fde5:2a::11 (ntp1.torix.ca) 0.004 0.009 0.013 0.026 0.056 0.203 10.840 0.043 0.193 0.349 0.048 ms 21.8 593.6
Server Jitter 2606:4700:f1::1 (time.cloudflare.com) 8.200 11.883 15.764 36.337 397.332 609.487 989.152 381.568 597.604 131.052 88.654 µs 1.852 8.793
Server Jitter 2607:f388::123:1 (ntp1.doit.wisc.edu) 4.874 10.406 13.576 26.498 57.281 89.633 665.929 43.705 79.227 30.957 31.267 µs 14.13 265.4
Server Jitter 2610:20:6f97:97::6 (time-e-wwv.nist.gov) 7.670 14.249 19.299 36.037 65.142 80.403 1,028.447 45.843 66.154 27.222 39.053 µs 25.91 910.7
Server Jitter 2620:149:a33:3000::21 (usnyc3-ntp-001.aaplimg.com) 0.007 0.013 0.020 0.076 46.929 61.398 74.769 46.909 61.385 15.818 10.624 ms 0.4969 3.173
Server Jitter PPS(0) 1.427 4.832 7.028 17.027 36.144 47.041 72.912 29.116 42.209 9.039 18.580 µs 5.463 17.4
Server Offset 128.101.101.101 -62.782 -62.782 -46.870 31.913 76.092 94.139 94.139 122.962 156.921 36.630 25.407 µs -1.308 3.362
Server Offset 128.233.154.245 -43.464 -16.003 -2.445 28.875 65.544 84.373 111.899 67.989 100.376 20.991 29.821 µs 1.593 4.811
Server Offset 132.246.11.238 1.050 1.092 1.130 1.279 1.565 1.615 6.483 0.435 0.523 0.333 1.358 ms 50.16 469.4
Server Offset 2600:2600::199 (ntp2.wiktel.com) -29.096 -13.866 -0.146 33.460 63.294 76.510 94.506 63.440 90.376 19.513 32.801 µs 2.248 5.517
Server Offset 2602:fde5:2a::11 (ntp1.torix.ca) 8.038 8.342 8.353 8.401 19.230 19.251 19.282 10.877 10.909 4.324 10.565 ms 8.824 28.64
Server Offset 2606:4700:f1::1 (time.cloudflare.com) -1,087.608 -954.364 -763.590 -405.500 124.653 271.106 515.450 888.243 1,225.470 256.643 -371.591 µs -21.56 70.83
Server Offset 2607:f388::123:1 (ntp1.doit.wisc.edu) -778.486 -665.231 -540.902 -470.496 -360.716 -240.048 -160.593 180.186 425.183 61.914 -465.667 µs -643.7 5699
Server Offset 2610:20:6f97:97::6 (time-e-wwv.nist.gov) -63.651 -37.909 -23.887 17.304 68.401 89.481 120.544 92.288 127.390 27.983 18.818 µs -0.7103 3.119
Server Offset 2620:149:a33:3000::21 (usnyc3-ntp-001.aaplimg.com) 730.921 758.810 775.110 831.541 878.235 893.322 923.592 103.125 134.512 31.223 828.924 µs 1.675e+04 4.299e+05
Server Offset PPS(0) -51.059 -23.428 -17.627 -3.311 29.953 42.130 72.910 47.580 65.558 14.226 -0.000 µs -2.925 6.833
Temp ZONE0 36.000 37.000 38.000 40.000 42.000 43.000 44.000 4.000 6.000 1.301 39.580 °C
Temp ZONE1 31.000 32.000 33.000 35.000 36.000 37.000 37.000 3.000 5.000 1.163 34.490 °C
Summary as CSV file


Glossary:

frequency offset:
The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
jitter, dispersion:
The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Server Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of kurtosis. A normal distribution has a kurtosis of three. NIST describes a kurtosis over three as "heavy tailed" and one under three as "light tailed".
ms, millisecond:
One thousandth of a second = 0.001 seconds, 1e-3 seconds
mu, mean:
The arithmetic mean: the sum of all the values divided by the number of values. The formula for mu is: "mu = (∑xi) / N". Where xi denotes the data points and N is the number of data points.
ns, nanosecond:
One billionth of a second, also one thousandth of a microsecond, 0.000000001 seconds and 1e-9 seconds.
percentile:
The value below which a given percentage of values fall.
ppb, parts per billion:
Ratio between two values. These following are all the same: 1 ppb, one in one billion, 1/1,000,000,000, 0.000,000,001, 1e-9 and 0.000,000,1%
ppm, parts per million:
Ratio between two values. These following are all the same: 1 ppm, one in one million, 1/1,000,000, 0.000,001, and 0.000,1%
‰, parts per thousand:
Ratio between two values. These following are all the same: 1 ‰. one in one thousand, 1/1,000, 0.001, and 0.1%
refclock:
Reference clock, a local GPS module or other local source of time.
remote clock:
Any clock reached over the network, LAN or WAN. Also called a peer or server.
time offset:
The difference between the ntpd calculated time and the local system clock's time. Also called phase offset.
σ, sigma:
Sigma denotes the standard deviation (SD) and is centered on the arithmetic mean of the data set. The SD is simply the square root of the variance of the data set. Two sigma is simply twice the standard deviation. Three sigma is three times sigma. Smaller is better.
The formula for sigma is: "σ = √[ ∑(xi-mu)^2 / N ]". Where xi denotes the data points and N is the number of data points.
skewness, Skew:
The skewness of a random variable X is the third standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
upstream clock:
Any server or reference clock used as a source of time.
µs, us, microsecond:
One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.



This page autogenerated by ntpviz, part of the NTPsec project
html 5    Valid CSS!