TL;DR
- ▸GNSS used to be assumed reliable. Jamming, spoofing, indoor venues and ionospheric activity have made that assumption untenable.
- ▸Three realistic alternatives: harden the GNSS (multi-band, multi-constellation, anti-jam), distribute time over fibre with White Rabbit, or use a holdover-grade reference clock at a central site.
- ▸The right answer depends on the deployment economics and the worst-case credible disruption scenario.
The new GNSS reality
For most of the history of precision timing, GNSS was the cheap, reliable, ubiquitous primary reference. Stick an antenna on the roof, point it at the sky, get UTC. The assumption is no longer reliable. Jamming has become trivially cheap (drone-mounted jammers cost less than a mid-range GPU). Spoofing is field-deployable (academic teams have published working spoofers and there are documented commercial incidents). Ionospheric activity is rising with the solar cycle. And an increasing number of deployments are physically indoors with no roof access at all.
The result is that operators planning new precision timing infrastructure in 2026 can no longer assume GNSS will always be available. The risk model has to include credible GNSS denial scenarios — both deliberate and incidental — and the architecture has to deliver compliant timing through them.
What you do instead
Three options. Harden the GNSS: multi-band (L1+L5 or L1+L2C), multi-constellation (GPS plus Galileo plus at least one other), anti-jam antenna systems with RF filtering and spatial nulling, Galileo OSNMA cryptographic authentication where available. This is the cheapest and most operationally familiar path. Distribute time over fibre with White Rabbit: eliminates GNSS dependency at the cell site or venue by carrying precise time from a hardened central reference over operator-controlled fibre. Right answer when the operator controls the fibre. Use a holdover-grade reference clock at a central location: deploy a rubidium or caesium oscillator that maintains compliant time through multi-hour GNSS outages, distributed via PTP to the GNSS-denied edge.
The right answer depends on the deployment economics, the credible disruption scenario, and what infrastructure the operator controls. Most production deployments combine two of these — hardened GNSS as the primary reference and rubidium holdover as the backstop, for example.
Where this is heading
GNSS-free timing isn't a future concern; it's a present operational reality. Operators who plan for it now have credible deployments. Operators who don't will discover the gap during the next significant disruption event.
Where TimeBeat fits
TimeBeat hardware supports multi-band multi-constellation GNSS receivers, anti-jam antenna integration, rubidium holdover for the worst-case scenarios, and the Open Time Node WR for White Rabbit fibre distribution. The combination covers all three alternative architectures. Customers planning deployments in contested environments or indoor venues typically combine two of these — and the conversation about which combination fits a specific deployment is one we have regularly.
Frequently asked questions
Why is GNSS no longer reliable enough?+
What is anti-jam GNSS?+
Can White Rabbit replace GNSS at a venue?+
Related reading
Blog · LEO PNT
The Next Timing Upgrade: LEO PNT Indoors
Low Earth Orbit positioning, navigation and timing constellations promise to deliver GNSS-class timing to indoor environments where traditional GNSS can't reach. Where the technology is in 2026 and what it changes for precision time.
Blog · Resilience
Why Clock Quorum Techniques Are the Future of UTC Synchronisation
Clock quorum techniques aggregate multiple independent time references and detect anomalies by comparing them against each other. Why this is becoming the standard architecture for resilient UTC synchronisation.
Blog · Neutral host
Indoor Dense Urban Neutral Host
Indoor dense urban neutral host deployments are the next frontier of shared mobile infrastructure. What the timing fabric has to look like to deliver multi-operator coverage in environments where GNSS doesn't reach.

