NTPsec

NTP4: SecureSync, Rubidium, NTP (Classic)
Three Day - May 01, 2026 11:00 UTC

Report generated: Fri May 1 11:11:14 2026 UTC
Start Time: Tue Apr 28 11:11:13 2026 UTC
End Time: Fri May 1 11:11:13 2026 UTC
Report Period: 3.0 days

Return to It's About Time

Section Time Frame NTP Server
Local Clock Time/Frequency Offsets One Hour NTP0: x86 SBC, Undisciplined, NTPSec
Local RMS Time Jitter Three Hour NTP1: RPi4B, Uputronics M8, NTPSec
Local RMS Frequency Jitter Six Hour NTP2: CM4, Bollar ZED-F9T, NTPSec
Local Clock Time Offset Histogram Twelve Hour NTP3: CM5, TimeHat LEA-M8T, NTPSec
Local Temperatures One Day NTP4: SecureSync, Rubidium, NTP (Classic)
Local Frequency/Temp Two Day NTP5: RPi3B+, Uputronics MAX-M8Q, NTPSec
Local GPS Three Day NTP6: CM4, TimeBeat OTC Mini, PTP
Server Offsets Seven Day NTP7: LeoNTP, Standalone GNSS, Firmware
Server Jitters Fourteen Day (Updated Daily)
Summary One Month (Updated Daily)
NTPQ Stats
GNSS Performance

NTP4 is a Safran SecureSync 1200 appliance with a Rubidium oscillator and u-blox timing GNSS receiver. It is used as a highly stable atomic reference clock for the network.

If graphs don't match report time above, force refresh the browser. The images have been cached.


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 -17.000 -1.000 -1.000 0.000 0.998 1.000 73.998 1.998 2.000 0.726 -0.000 µs 42.04 3755
Local Clock Frequency Offset 89.681 89.684 89.687 89.704 89.719 89.723 89.743 0.032 0.039 0.0094 89.703 ppm -0.0691 2.426

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.954 0.955 0.958 0.970 1.110 1.365 40.437 0.152 0.410 0.817 1.039 µs 24.43 791.4

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.017 0.061 0.098 0.199 0.289 0.405 12.779 0.191 0.344 0.282 0.215 ppb 22.35 686

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 -17.000 -1.000 -1.000 0.000 0.998 1.000 73.998 1.998 2.000 0.726 -0.000 µs 42.04 3755

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 89.681 89.684 89.687 89.704 89.719 89.723 89.743 0.032 0.039 0.0094 89.703 ppm -0.0691 2.426
Temp BOARD 58.000 58.000 58.000 58.750 59.750 59.880 59.880 1.750 1.880 0.371 58.751 °C
Temp CPU 58.000 58.000 58.000 59.120 59.880 59.880 59.880 1.880 1.880 0.435 59.053 °C
Temp OSC 48.270 48.430 48.520 48.750 49.010 49.080 49.160 0.490 0.650 0.150 48.754 °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.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 16.000 18.000 19.000 22.000 25.000 26.000 27.000 6.000 8.000 1.837 21.587 nSat 0.2399 2.856
TDOP 0.180 0.180 0.190 0.200 0.200 0.210 0.220 0.010 0.030 0.006 0.196 0.05664 2.972

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



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 10.0.0.241

peer offset 10.0.0.241 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.0.241 -1.231 14.488 25.893 42.342 58.614 65.088 549.843 32.721 50.600 13.170 43.036 µs 14.96 522.2

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

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

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

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



Server Offset 10.0.0.242

peer offset 10.0.0.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.0.242 -16.348 7.963 19.754 39.932 55.476 60.535 88.410 35.722 52.572 10.775 39.543 µs -0.6178 4.22

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 10.0.0.90

peer offset 10.0.0.90 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.0.90 -20.972 7.171 13.164 28.327 49.765 57.238 65.983 36.601 50.067 11.328 29.505 µs 0.3103 2.86

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 10.0.50.100

peer offset 10.0.50.100 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.50.100 -3.973 9.584 11.528 34.644 42.067 43.356 109.295 30.539 33.772 7.796 32.935 µs -1.462 6.797

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 10.0.50.50

peer offset 10.0.50.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.50.50 -109.812 34.912 47.446 68.472 100.894 106.952 297.338 53.448 72.040 16.799 71.668 µs 0.3599 11.86

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.



Refclock Offset 127.127.45.0

peer offset 127.127.45.0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock Offset 127.127.45.0 -17.000 -1.001 -1.000 -0.001 0.999 1.000 73.999 1.999 2.001 0.726 -0.001 µs 42.03 3753

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

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local serial GPS 200 ms; local PPS 20µs.

Clock Offset is field 5 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 10.0.0.241

peer jitter 10.0.0.241 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.0.241 0.001 0.008 0.012 0.025 0.352 2.274 9.716 0.340 2.266 0.369 0.101 ms 8.103 104.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 10.0.0.242

peer jitter 10.0.0.242 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.0.242 0.001 0.008 0.011 0.022 0.485 1.953 6.897 0.474 1.945 0.376 0.110 ms 7.24 73.56

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 10.0.0.90

peer jitter 10.0.0.90 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.0.90 0.001 0.008 0.011 0.025 0.353 1.835 9.986 0.342 1.827 0.437 0.103 ms 11.01 166.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 10.0.50.100

peer jitter 10.0.50.100 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.50.100 0.954 1.361 2.022 7.029 27.959 32.907 591.477 25.937 31.546 20.122 9.821 µs 23.9 675.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 10.0.50.50

peer jitter 10.0.50.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.50.50 0.954 3.940 5.564 13.710 38.510 52.873 234.449 32.946 48.933 13.604 18.648 µs 3.918 47.28

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.



Refclock RMS Jitter 127.127.45.0

peer jitter 127.127.45.0 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Refclock RMS Jitter 127.127.45.0 0.954 0.954 0.954 0.954 1.133 1.362 74.289 0.179 0.408 0.832 1.000 µs 43.08 2600

The RMS Jitter of a local refclock. 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 89.681 89.684 89.687 89.704 89.719 89.723 89.743 0.032 0.039 0.0094 89.703 ppm -0.0691 2.426
Local Clock Time Offset -17.000 -1.000 -1.000 0.000 0.998 1.000 73.998 1.998 2.000 0.726 -0.000 µs 42.04 3755
Local RMS Frequency Jitter 0.017 0.061 0.098 0.199 0.289 0.405 12.779 0.191 0.344 0.282 0.215 ppb 22.35 686
Local RMS Time Jitter 0.954 0.955 0.958 0.970 1.110 1.365 40.437 0.152 0.410 0.817 1.039 µs 24.43 791.4
Refclock Offset 127.127.45.0 -17.000 -1.001 -1.000 -0.001 0.999 1.000 73.999 1.999 2.001 0.726 -0.001 µs 42.03 3753
Refclock RMS Jitter 127.127.45.0 0.954 0.954 0.954 0.954 1.133 1.362 74.289 0.179 0.408 0.832 1.000 µs 43.08 2600
Server Jitter 10.0.0.241 0.001 0.008 0.012 0.025 0.352 2.274 9.716 0.340 2.266 0.369 0.101 ms 8.103 104.9
Server Jitter 10.0.0.242 0.001 0.008 0.011 0.022 0.485 1.953 6.897 0.474 1.945 0.376 0.110 ms 7.24 73.56
Server Jitter 10.0.0.90 0.001 0.008 0.011 0.025 0.353 1.835 9.986 0.342 1.827 0.437 0.103 ms 11.01 166.7
Server Jitter 10.0.50.100 0.954 1.361 2.022 7.029 27.959 32.907 591.477 25.937 31.546 20.122 9.821 µs 23.9 675.1
Server Jitter 10.0.50.50 0.954 3.940 5.564 13.710 38.510 52.873 234.449 32.946 48.933 13.604 18.648 µs 3.918 47.28
Server Offset 10.0.0.241 -1.231 14.488 25.893 42.342 58.614 65.088 549.843 32.721 50.600 13.170 43.036 µs 14.96 522.2
Server Offset 10.0.0.242 -16.348 7.963 19.754 39.932 55.476 60.535 88.410 35.722 52.572 10.775 39.543 µs -0.6178 4.22
Server Offset 10.0.0.90 -20.972 7.171 13.164 28.327 49.765 57.238 65.983 36.601 50.067 11.328 29.505 µs 0.3103 2.86
Server Offset 10.0.50.100 -3.973 9.584 11.528 34.644 42.067 43.356 109.295 30.539 33.772 7.796 32.935 µs -1.462 6.797
Server Offset 10.0.50.50 -109.812 34.912 47.446 68.472 100.894 106.952 297.338 53.448 72.040 16.799 71.668 µs 0.3599 11.86
TDOP 0.180 0.180 0.190 0.200 0.200 0.210 0.220 0.010 0.030 0.006 0.196 0.05664 2.972
Temp BOARD 58.000 58.000 58.000 58.750 59.750 59.880 59.880 1.750 1.880 0.371 58.751 °C
Temp CPU 58.000 58.000 58.000 59.120 59.880 59.880 59.880 1.880 1.880 0.435 59.053 °C
Temp OSC 48.270 48.430 48.520 48.750 49.010 49.080 49.160 0.490 0.650 0.150 48.754 °C
nSats 16.000 18.000 19.000 22.000 25.000 26.000 27.000 6.000 8.000 1.837 21.587 nSat 0.2399 2.856
Summary as CSV file

Our production NTP servers share the same mast-mounted Tallysman Accutenna® TW3972 Triple Band GNSS Antenna + L-band Correction Services antenna using a Tallysman TW164 1-to-4 Port Smart Power GNSS Signal Splitter. No external NTP servers are contacted and all servers, with the exception of NTP6, the LeoNTP 1200, poll each other. Internal NTP clients poll NTP4 or NTP6.

The LeoNTP 1200 is a black-box appliance that doesn't support timing reporting. Its status can be checked by viwing the Server Jitter & Offset from any of the other servers. It can be found at NTP7 or 10.0.50.55. The LeoNTP link above will take you to the Server Jitter between the LeoNTP and the currently selected server.

NTPQ Stats

NTPQ Statistics are not not available for this NTP server.'

GNSS Performance

GNSS Performance is not available for this NTP server.'

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.
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 FIsher-Pearson moment of skewness. There are other different ways to calculate Skewness Wikipedia describes Skewness best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
Kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses standard Kurtosis. There are other different ways to calculate 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".
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!