NTPsec

crane2.services.mbix.ca

Report generated: Mon Nov 9 05:45:03 2026 UTC
Start Time: Mon Nov 2 05:45:01 2026 UTC
End Time: Mon Nov 9 05:45:01 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 -35.281 -22.630 -17.246 -3.088 27.221 39.180 74.178 44.467 61.810 13.587 -0.000 µs -3.052 7.034
Local Clock Frequency Offset 81.595 81.634 81.686 81.833 81.929 81.949 81.987 0.243 0.315 0.074 81.823 ppm 1.341e+09 1.479e+12

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

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



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 6.024 9.678 11.481 17.741 26.176 30.191 45.964 14.695 20.513 4.517 18.143 µs 37.03 147.2

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.533 3.600 4.251 6.360 9.011 10.376 15.360 4.760 6.776 1.475 6.469 ppb 49.46 210.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 -35.281 -22.630 -17.246 -3.088 27.221 39.180 74.178 44.467 61.810 13.587 -0.000 µs -3.052 7.034

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 81.595 81.634 81.686 81.833 81.929 81.949 81.987 0.243 0.315 0.074 81.823 ppm 1.341e+09 1.479e+12
Temp ZONE0 37.000 38.000 39.000 40.000 42.000 42.000 43.000 3.000 4.000 0.985 39.998 °C
Temp ZONE1 35.000 36.000 36.000 38.000 39.000 39.000 40.000 3.000 3.000 0.777 37.582 °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 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.841 1.918 1.947 2.016 2.094 2.138 17.905 0.147 0.220 1.092 2.092 ms 17.84 264.9

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 -49.883 -49.883 -30.201 -0.095 49.087 61.291 61.291 79.288 111.174 23.121 2.558 µs -2.971 7.038

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 -15.784 0.006 0.014 0.041 0.080 0.096 15.942 0.066 0.090 1.093 0.104 ms 8.039 172.6

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) -5.181 12.061 21.819 50.114 86.223 102.751 116.140 64.404 90.690 19.829 51.827 µs 9.365 27.31

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::12 (ntp2.torix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2602:fde5:2a::12 (ntp2.torix.ca) 8.319 8.345 8.358 8.393 8.425 8.438 8.458 0.068 0.093 0.020 8.393 ms 6.915e+07 2.838e+10

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) -1.584 -1.115 -0.850 -0.327 0.254 0.403 0.576 1.103 1.518 0.329 -0.305 ms -13.07 40.35

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 -285.025 -67.608 -34.652 24.364 90.673 118.019 162.008 125.325 185.627 40.101 25.481 µs -1.67 8.255

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) -654.618 -542.117 -510.273 -460.359 -394.126 -39.207 1,830.372 116.147 502.910 152.480 -444.246 µs -60.52 296.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 2610:20:6f96:96::6 (time-e-b.nist.gov)

peer offset 2610:20:6f96:96::6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2610:20:6f96:96::6 (time-e-b.nist.gov) 27.417 61.385 72.862 111.702 159.387 180.520 206.472 86.525 119.135 26.137 113.588 µs 47.82 200

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:4000::21 (usnyc3-ntp-002.aaplimg.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 2620:149:a33:4000::21 (usnyc3-ntp-002.aaplimg.com) 781.318 801.464 813.527 846.493 883.708 900.949 913.430 70.181 99.485 21.832 847.357 µs 5.418e+04 2.053e+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 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) -35.282 -22.631 -17.247 -3.089 27.222 39.181 74.179 44.469 61.812 13.588 -0.000 µs -3.052 7.034

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.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.024 0.044 0.069 0.376 1.222 2.212 138.228 1.153 2.168 6.926 0.929 ms 13.59 249.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 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 0.000 0.000 15.996 39.137 53.564 53.564 39.137 53.564 13.203 16.928 µs 1.423 4.089

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 0.005 0.008 0.011 0.020 0.049 0.127 15.849 0.038 0.119 0.866 0.084 ms 12.3 210

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) 6.263 9.451 12.696 23.991 45.531 56.735 788.468 32.835 47.284 25.972 26.769 µs 24.61 717.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:fde5:2a::12 (ntp2.torix.ca)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2602:fde5:2a::12 (ntp2.torix.ca) 6.429 8.748 12.132 23.175 47.981 79.759 768.440 35.849 71.011 41.121 28.306 µs 13.72 223.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 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.945 12.271 19.734 147.923 609.357 843.272 1,669.614 589.623 831.001 200.982 212.765 µs 1.577 5.876

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 7.817 13.595 17.765 34.741 74.948 137.696 3,809.865 57.183 124.101 159.619 50.907 µs 14.24 292.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 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) 0.008 0.010 0.014 0.027 0.058 0.139 11.279 0.044 0.129 0.252 0.038 ms 40.58 1806

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:6f96:96::6 (time-e-b.nist.gov)

peer jitter 2610:20:6f96:96::6 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2610:20:6f96:96::6 (time-e-b.nist.gov) 0.006 0.015 0.018 0.034 0.061 0.078 24.363 0.042 0.063 0.539 0.048 ms 41.57 1874

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:4000::21 (usnyc3-ntp-002.aaplimg.com)

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

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 2620:149:a33:4000::21 (usnyc3-ntp-002.aaplimg.com) 0.009 0.015 0.026 0.085 51.096 64.292 76.090 51.071 64.277 19.833 14.216 ms 0.1297 1.89

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) 2.208 5.496 7.717 16.675 33.588 43.509 80.785 25.871 38.013 8.065 18.060 µs 6.798 22.67

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 81.595 81.634 81.686 81.833 81.929 81.949 81.987 0.243 0.315 0.074 81.823 ppm 1.341e+09 1.479e+12
Local Clock Time Offset -35.281 -22.630 -17.246 -3.088 27.221 39.180 74.178 44.467 61.810 13.587 -0.000 µs -3.052 7.034
Local RMS Frequency Jitter 2.533 3.600 4.251 6.360 9.011 10.376 15.360 4.760 6.776 1.475 6.469 ppb 49.46 210.5
Local RMS Time Jitter 6.024 9.678 11.481 17.741 26.176 30.191 45.964 14.695 20.513 4.517 18.143 µs 37.03 147.2
Server Jitter 132.246.11.229 0.024 0.044 0.069 0.376 1.222 2.212 138.228 1.153 2.168 6.926 0.929 ms 13.59 249.6
Server Jitter 134.84.84.84 0.000 0.000 0.000 15.996 39.137 53.564 53.564 39.137 53.564 13.203 16.928 µs 1.423 4.089
Server Jitter 204.9.54.119 0.005 0.008 0.011 0.020 0.049 0.127 15.849 0.038 0.119 0.866 0.084 ms 12.3 210
Server Jitter 2600:2600::99 (ntp1.wiktel.com) 6.263 9.451 12.696 23.991 45.531 56.735 788.468 32.835 47.284 25.972 26.769 µs 24.61 717.1
Server Jitter 2602:fde5:2a::12 (ntp2.torix.ca) 6.429 8.748 12.132 23.175 47.981 79.759 768.440 35.849 71.011 41.121 28.306 µs 13.72 223.5
Server Jitter 2606:4700:f1::123 (time.cloudflare.com) 6.945 12.271 19.734 147.923 609.357 843.272 1,669.614 589.623 831.001 200.982 212.765 µs 1.577 5.876
Server Jitter 2607:f128::50 7.817 13.595 17.765 34.741 74.948 137.696 3,809.865 57.183 124.101 159.619 50.907 µs 14.24 292.7
Server Jitter 2607:f388::123:2 (ntp2.doit.wisc.edu) 0.008 0.010 0.014 0.027 0.058 0.139 11.279 0.044 0.129 0.252 0.038 ms 40.58 1806
Server Jitter 2610:20:6f96:96::6 (time-e-b.nist.gov) 0.006 0.015 0.018 0.034 0.061 0.078 24.363 0.042 0.063 0.539 0.048 ms 41.57 1874
Server Jitter 2620:149:a33:4000::21 (usnyc3-ntp-002.aaplimg.com) 0.009 0.015 0.026 0.085 51.096 64.292 76.090 51.071 64.277 19.833 14.216 ms 0.1297 1.89
Server Jitter PPS(0) 2.208 5.496 7.717 16.675 33.588 43.509 80.785 25.871 38.013 8.065 18.060 µs 6.798 22.67
Server Offset 132.246.11.229 1.841 1.918 1.947 2.016 2.094 2.138 17.905 0.147 0.220 1.092 2.092 ms 17.84 264.9
Server Offset 134.84.84.84 -49.883 -49.883 -30.201 -0.095 49.087 61.291 61.291 79.288 111.174 23.121 2.558 µs -2.971 7.038
Server Offset 204.9.54.119 -15.784 0.006 0.014 0.041 0.080 0.096 15.942 0.066 0.090 1.093 0.104 ms 8.039 172.6
Server Offset 2600:2600::99 (ntp1.wiktel.com) -5.181 12.061 21.819 50.114 86.223 102.751 116.140 64.404 90.690 19.829 51.827 µs 9.365 27.31
Server Offset 2602:fde5:2a::12 (ntp2.torix.ca) 8.319 8.345 8.358 8.393 8.425 8.438 8.458 0.068 0.093 0.020 8.393 ms 6.915e+07 2.838e+10
Server Offset 2606:4700:f1::123 (time.cloudflare.com) -1.584 -1.115 -0.850 -0.327 0.254 0.403 0.576 1.103 1.518 0.329 -0.305 ms -13.07 40.35
Server Offset 2607:f128::50 -285.025 -67.608 -34.652 24.364 90.673 118.019 162.008 125.325 185.627 40.101 25.481 µs -1.67 8.255
Server Offset 2607:f388::123:2 (ntp2.doit.wisc.edu) -654.618 -542.117 -510.273 -460.359 -394.126 -39.207 1,830.372 116.147 502.910 152.480 -444.246 µs -60.52 296.4
Server Offset 2610:20:6f96:96::6 (time-e-b.nist.gov) 27.417 61.385 72.862 111.702 159.387 180.520 206.472 86.525 119.135 26.137 113.588 µs 47.82 200
Server Offset 2620:149:a33:4000::21 (usnyc3-ntp-002.aaplimg.com) 781.318 801.464 813.527 846.493 883.708 900.949 913.430 70.181 99.485 21.832 847.357 µs 5.418e+04 2.053e+06
Server Offset PPS(0) -35.282 -22.631 -17.247 -3.089 27.222 39.181 74.179 44.469 61.812 13.588 -0.000 µs -3.052 7.034
Temp ZONE0 37.000 38.000 39.000 40.000 42.000 42.000 43.000 3.000 4.000 0.985 39.998 °C
Temp ZONE1 35.000 36.000 36.000 38.000 39.000 39.000 40.000 3.000 3.000 0.777 37.582 °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!