NTPsec

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

Report generated: Fri May 1 18:12:13 2026 UTC
Start Time: Tue Apr 28 18:12:12 2026 UTC
End Time: Fri May 1 18:12:12 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.745 -0.001 µs 40.37 3443
Local Clock Frequency Offset 89.681 89.684 89.687 89.703 89.719 89.723 89.743 0.032 0.039 0.0092 89.702 ppm 0.02731 2.522

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.114 1.584 40.437 0.156 0.629 0.844 1.045 µs 22.87 704.5

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.063 0.100 0.200 0.291 0.487 12.779 0.191 0.424 0.291 0.218 ppb 20.99 612.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 -17.000 -1.000 -1.000 0.000 0.998 1.000 73.998 1.998 2.000 0.745 -0.001 µs 40.37 3443

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.703 89.719 89.723 89.743 0.032 0.039 0.0092 89.702 ppm 0.02731 2.522
Temp BOARD 58.000 58.000 58.000 58.750 59.880 59.880 59.880 1.880 1.880 0.385 58.769 °C
Temp CPU 58.000 58.000 58.000 59.120 59.880 59.880 59.880 1.880 1.880 0.422 59.064 °C
Temp OSC 48.270 48.440 48.530 48.770 49.010 49.080 49.160 0.480 0.640 0.145 48.769 °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 21.000 25.000 26.000 27.000 6.000 8.000 1.861 21.560 nSat 0.2546 2.862
TDOP 0.180 0.180 0.190 0.200 0.200 0.210 0.220 0.010 0.030 0.006 0.195 0.08241 2.914

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 13.726 24.957 42.304 58.338 64.826 549.843 33.381 51.100 13.235 42.845 µs 14.68 510.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 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 8.398 20.339 40.082 55.361 60.397 88.410 35.022 51.999 10.601 39.663 µs -0.6127 4.189

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.962 13.599 30.342 51.734 58.348 67.271 38.135 50.386 11.789 31.089 µs 0.1977 2.646

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 -2.639 9.538 11.412 34.538 41.796 43.285 109.295 30.384 33.747 7.744 32.718 µs -1.46 6.803

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.420 49.701 71.269 102.783 108.305 297.338 53.082 73.885 17.604 74.922 µs 0.1488 9.594

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.745 -0.001 µs 40.36 3441

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.326 2.252 9.716 0.314 2.244 0.360 0.098 ms 8.432 114.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 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.023 0.466 2.013 6.897 0.455 2.005 0.374 0.108 ms 7.37 75.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 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.024 0.327 1.916 9.986 0.316 1.908 0.448 0.105 ms 10.55 152.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.397 2.086 6.985 27.885 32.658 591.477 25.799 31.261 20.136 9.817 µs 23.89 674.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 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 4.020 5.540 13.304 38.510 54.460 234.449 32.970 50.440 13.609 18.252 µs 3.949 46.57

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.134 1.362 74.289 0.180 0.408 0.860 1.004 µs 40.29 2306

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.703 89.719 89.723 89.743 0.032 0.039 0.0092 89.702 ppm 0.02731 2.522
Local Clock Time Offset -17.000 -1.000 -1.000 0.000 0.998 1.000 73.998 1.998 2.000 0.745 -0.001 µs 40.37 3443
Local RMS Frequency Jitter 0.017 0.063 0.100 0.200 0.291 0.487 12.779 0.191 0.424 0.291 0.218 ppb 20.99 612.5
Local RMS Time Jitter 0.954 0.955 0.958 0.970 1.114 1.584 40.437 0.156 0.629 0.844 1.045 µs 22.87 704.5
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.745 -0.001 µs 40.36 3441
Refclock RMS Jitter 127.127.45.0 0.954 0.954 0.954 0.954 1.134 1.362 74.289 0.180 0.408 0.860 1.004 µs 40.29 2306
Server Jitter 10.0.0.241 0.001 0.008 0.012 0.025 0.326 2.252 9.716 0.314 2.244 0.360 0.098 ms 8.432 114.2
Server Jitter 10.0.0.242 0.001 0.008 0.011 0.023 0.466 2.013 6.897 0.455 2.005 0.374 0.108 ms 7.37 75.4
Server Jitter 10.0.0.90 0.001 0.008 0.011 0.024 0.327 1.916 9.986 0.316 1.908 0.448 0.105 ms 10.55 152.7
Server Jitter 10.0.50.100 0.954 1.397 2.086 6.985 27.885 32.658 591.477 25.799 31.261 20.136 9.817 µs 23.89 674.3
Server Jitter 10.0.50.50 0.954 4.020 5.540 13.304 38.510 54.460 234.449 32.970 50.440 13.609 18.252 µs 3.949 46.57
Server Offset 10.0.0.241 -1.231 13.726 24.957 42.304 58.338 64.826 549.843 33.381 51.100 13.235 42.845 µs 14.68 510.9
Server Offset 10.0.0.242 -16.348 8.398 20.339 40.082 55.361 60.397 88.410 35.022 51.999 10.601 39.663 µs -0.6127 4.189
Server Offset 10.0.0.90 -20.972 7.962 13.599 30.342 51.734 58.348 67.271 38.135 50.386 11.789 31.089 µs 0.1977 2.646
Server Offset 10.0.50.100 -2.639 9.538 11.412 34.538 41.796 43.285 109.295 30.384 33.747 7.744 32.718 µs -1.46 6.803
Server Offset 10.0.50.50 -109.812 34.420 49.701 71.269 102.783 108.305 297.338 53.082 73.885 17.604 74.922 µs 0.1488 9.594
TDOP 0.180 0.180 0.190 0.200 0.200 0.210 0.220 0.010 0.030 0.006 0.195 0.08241 2.914
Temp BOARD 58.000 58.000 58.000 58.750 59.880 59.880 59.880 1.880 1.880 0.385 58.769 °C
Temp CPU 58.000 58.000 58.000 59.120 59.880 59.880 59.880 1.880 1.880 0.422 59.064 °C
Temp OSC 48.270 48.440 48.530 48.770 49.010 49.080 49.160 0.480 0.640 0.145 48.769 °C
nSats 16.000 18.000 19.000 21.000 25.000 26.000 27.000 6.000 8.000 1.861 21.560 nSat 0.2546 2.862
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!