From Vienna to CERN: The European Innovation Behind Modern Network and Timing Infrastructure

Sub-nanosecond timing over Ethernet was not born in a product roadmap. It came out of CERN, where physicists needed the White Rabbit protocol to synchronize instruments across a particle accelerator with a precision that ordinary networking had no reason to attempt. The specification is now folded into IEEE 1588-2019 as the High Accuracy profile, and it has quietly become the reference point that timing vendors across Europe still measure themselves against.

That is a useful way to think about a handful of the vendors in Telnet’s own portfolio. They are not the biggest names in their categories, but they tend to be the ones doing the interesting engineering: a packet broker maker in Vienna, a clockmaker in western France that has been keeping time since before the telephone, a Suricata-based security platform built by open-source developers in Paris. Here is what each of them has been building lately.

Cubro: Precision Engineering With New Backing

Cubro has been designing network packet brokers, TAPs and probes out of Vienna since 2003, and in December 2025 the Swedish industrial group Addtech acquired a majority stake in the company. For a Telnet customer, the practical upshot is stability: Cubro keeps its Vienna engineering team and roadmap, now with a publicly traded parent behind it (Addtech trades on Nasdaq Stockholm).

The product itself keeps moving. Cubro’s Omnia platform runs application-layer classification directly on the packet broker, an architecture the company has been pushing further as encrypted traffic makes payload-based inspection less useful across the industry. It is the same “classify once, distribute everywhere” idea that shows up increasingly in how Telnet evaluates network visibility architecture generally, and Cubro is one of the vendors building toward it in hardware.

Profitap: Forty Years of TAPs, Reshaped for OT

Profitap’s roots go back to 1984 in Strasbourg, France, before the company relocated its headquarters and R&D to Eindhoven, Netherlands. That history matters less than what the team has done recently with it: the IOTA platform extends Profitap’s TAP and packet-broker lineage into portable, high-precision capture kits built for operational technology networks, where nanosecond-level timestamp accuracy in packet capture is often the difference between a diagnosable incident and a guess.

Profitap’s engineering has always leaned toward the physically compact and the field-deployable, and IOTA is the clearest expression of that instinct: fly-away capture kits that a field engineer can carry to a substation or a plant floor rather than a rack that has to be provisioned in advance.

Infosim: A University Spin-out That Stayed Independent

Infosim was founded in 2003 as a spin-out from the University of Würzburg, and more than twenty years later it is still headquartered there, still privately held, and still developing StableNet entirely out of its German R&D team. That kind of continuity is unusual in network management software, where consolidation is the norm.

StableNet’s release cadence has stayed active through that independence. Its unified approach to fault, performance and configuration management remains vendor-agnostic by design, which is a deliberate choice for a company that could have built a walled garden and didn’t.

Timebeat: Timing Software Built on Open Standards

Timebeat is a UK company building PTP and NTP synchronization as software first, hardware second, which is close to the opposite of how most of the timing industry has historically worked. Its stated position on vendor lock-in is blunt: interoperability is the point, not a concession. The Timebeat.app daemon replaces chrony, ntpd and ptp4l on a host, and the company’s grandmaster hardware line extends the same open approach into rack appliances and PCIe timecards.

Timebeat also builds explicitly for interoperability with White Rabbit-based networks, which is the same protocol lineage that opened this post. It is a small detail, but it says something about how connected European timing engineering still is to that original CERN work, even decades and several product categories removed from it.

Bodet: From Mechanical Clockmaking to Network Time

Bodet has been making clocks in Trémentines, France since the 19th century, long enough that the company’s own history predates the electrical grid it now helps synchronize. The relevant point for a network engineer is less the heritage and more what Bodet has done with it: its Netsilon line brings that clockmaking precision into NTP and PTP master clock appliances built for the same digital infrastructure everyone else in this post is building for.

Telnet has deployed Bodet clock systems where functional requirements could not be met by any other vendor and operational requirements were absolute. Performance has always met or exceeded the required standards.

Stamus Networks: Open-source Security Engineering Out of Paris

Stamus Networks was founded in 2014 by Éric Leblond and Peter Manev, both long-time core developers of Suricata, the open-source intrusion detection engine that much of the network security industry builds on in one form or another. Stamus is dual-headquartered in Paris and Indianapolis, but its product engineering and much of its leadership remain rooted in the same open-source security community that produced Suricata in the first place.

Clear NDR, Stamus’s flagship platform, turns that Suricata foundation into a full network detection and response system, and the company has kept contributing back to the open-source project rather than treating it purely as a dependency. That is a meaningfully different posture from most commercial NDR vendors, and it shows in how transparent Clear NDR is about what it is actually doing under the hood.

The Common Thread

None of these companies are chasing the same trend at the same time. Cubro is scaling with new capital behind it. Profitap is pointing forty years of TAP engineering at OT networks. Infosim has stayed independent long enough to keep StableNet vendor-agnostic on principle. Timebeat is building timing software that assumes interoperability rather than lock-in. Bodet is doing to network time what it has done to mechanical clocks for over a century. Stamus is building commercial security on an open-source foundation it still maintains.

What connects them is a certain patience with hard engineering problems, the same patience that turned a CERN physics requirement into an IEEE standard. Telnet works with all six because each one solves a specific, technical problem well, not because of where they happen to be headquartered. But it is worth noticing, occasionally, how much of the interesting work in this industry keeps coming out of the same part of the world.

Want to know where any of these fit into your network? Get in touch with our team and we’ll help you figure out what makes sense.

Precision Timing Applications in Healthcare and Emergency Services

Precision timing is often associated with telecommunications, financial trading, or power grids, but its role in healthcare and emergency services is just as critical. In environments where seconds, milliseconds, or even microseconds can influence outcomes, accurate and resilient time synchronization helps ensure systems operate safely, efficiently, and reliably.

As healthcare networks become more digital and emergency response systems more interconnected, precision timing is moving from a behind-the-scenes technical requirement to a foundational capability.

Why Timing Matters in Healthcare and Emergency Services

Modern healthcare and emergency operations rely on networked systems, including medical devices, clinical platforms, imaging, communications, and dispatch centers. Precise timing ensures these systems correlate events, maintain data integrity, and support real-time decisions. Inaccurate time can cause data mismatches, delayed responses, compliance issues, and risks to patient and public safety.

Timing architectures must resist disruptions such as GNSS interference, network congestion, or equipment failures. Redundant sources, diverse inputs, and high-stability holdover oscillators maintain accuracy when primary references fail. Continuous monitoring and performance validation allow rapid detection of timing issues and timely correction, keeping healthcare and emergency systems synchronized and operational.

Key Healthcare Applications of Precision Time Solutions

Medical Device Synchronization
– Relies on precision timing to ensure patient monitors, infusion pumps, ventilators, and diagnostic devices operate on a shared time reference
– Enables accurate correlation of vital signs, alarms, and clinical interventions across multiple systems
– Provides the temporal accuracy needed for confident decision-making and reliable event analysis in critical care environments

Electronic Health Records and Clinical Systems
– Maintains correct sequencing of clinical events across hospital and healthcare networks
– Supports continuity of care, accurate documentation, and medico-legal requirements
– Enables reliable analytics for performance measurement, trend analysis, and outcome improvement

Medical Imaging and Diagnostics
– Coordinates data acquisition and processing for MRI, CT, and PET systems
– Improves image accuracy while reducing artifacts
– Supports alignment and secure sharing of diagnostic data across multi-site healthcare networks

Emergency Services Applications of Precision Time Solutions

Emergency Dispatch and Response Coordination
– Provides precise timestamps for call receipt, resource assignment, and response tracking
– Improves situational awareness, performance measurement, and compliance with service-level requirements
– Enables accurate event correlation across police, fire, and emergency medical services

Public Safety Communications
– Supports reliable operation of LTE and 5G-based public safety networks
– Enables accurate handovers, location services, and prioritized communications during major incidents
– Maintains service availability through resilient timing architectures when primary sources are disrupted

Incident Reconstruction and Accountability
– Creates accurate timelines for post-incident investigation, reporting, and training
– Allows confident reconstruction of events across systems and agencies
– Supports continuous improvement and accountability to regulators and the public

Precision Timing Options

Accurate and reliable timing is critical for healthcare and emergency services, where every second can impact patient care and operational efficiency. Organizations need solutions that provide continuous, traceable, and resilient time across a variety of devices and systems. Telnet Networks delivers accurate and reliable timing for healthcare and emergency services through a portfolio of precision timing platforms and expert solution development and design services designed to keep complex networks fully aligned and operational. Enabling client organizations to provide continuous, traceable, and resilient time across a variety of devices and systems.

Safran SecureSync 2400

securesync gps time servers

As the preferred masterclock/time server solution in NENA compliant environments, the Safran SecureSync 2400 is a  Stratum-1 time server with multi-constellation GNSS support and hardware-assisted PTP and NTP services for precise time and frequency distribution. Its military-grade hardware supports redundant power supplies, multiple timing input and output formats, and high-stability oscillators for extended holdover. Advanced monitoring, alarm reporting, and security features enable continuous validation of timing performance, even during GNSS loss or interference.

Bodet Netsilon Master Clocks

Bodet Netsilon provides a cost effective option for environments that require reliable time synchronization without many of the bells and whistles. Bodet Netsilon servers provide a number of output and oscillator options to fit the needs of a variety of deployment scenarios as NTP or PTP  master clock. To ensure your healthcare or emergency service operations stay precisely synchronized and fully resilient, explore the right timing solution for your needs. Contact our sales team to discuss how Safran, Bodet, and our other precision timing solutions can keep your systems aligned and operating at their best.

Understanding Precision Timing in 5G and O-RAN Networks

5G is doing more than just speeding up our downloads—it’s completely changing how mobile networks are architected. Unlike the LTE era, which largely relied on frequency synchronization, 5G networks running on Time Division Duplex (TDD) spectrum operate on a much tighter leash.

In this landscape, “close enough” doesn’t cut it. To get maximum spectral efficiency and prevent radio interference, your network needs rigorous phase and time synchronization. At Telnet Networks, we know that timing is the invisible heartbeat of your RAN—if it skips a beat, the whole system feels it.

Why Timing is the Real MVP of 5G

The shift to TDD means that uplink and downlink transmissions happen on the same frequency, just separated by tiny slices of time. If your radios drift even slightly, those time slots start to overlap. The result? Signals collide (interference), calls drop, and your expensive spectrum goes to waste,.

Beyond basic connectivity, the “cool stuff” in 5G—like beamforming, massive MIMO, and cooperative multipoint (CoMP)—relies on multiple radios acting as a single coordinated unit. Without precise synchronization, these advanced features simply won’t work.

The Numbers: What 5G Actually Requires

To keep the network green, you need to hit some aggressive timing budgets:

  • The Golden Rule: For standard 5G TDD operations, the absolute time error across the network usually can’t exceed ±1.5 µs (microseconds),.
  • Advanced Applications: Things get tighter for advanced radio coordination. CoMP (Coordinated Multipoint) often demands relative timing of <1 µs between radios to prevent interference.
  • Positioning Services: If you are running location-based services (like asset tracking or emergency response), you might need accuracy as tight as 100 ns.
  • O-RAN Fronthaul: In Open RAN setups, to ensure different vendors’ equipment plays nicely together, components often need Class A compliance (around 65ns relative error).

Meeting these targets requires hardware that can see problems before they happen. Here is how solutions from Safran and Timebeat fit into the picture.

Safran: Resilience for the Long Haul

When you need to distribute time over long distances—like across a mobile backbone—fiber links can introduce jitter and asymmetry. Safran solves this with their White Rabbit technology (High Accuracy profile), which uses IEEE 1588-2019 to deliver sub-nanosecond accuracy over fiber optics.

Safran focuses on resilience. Their gear is built to keep your network ticking even if GNSS (GPS) signals are jammed or spoofed.

Top Safran Appliances:

  • SecureSync Grandmaster: This is a battle-tested GNSS time server. It prioritizes references and manages failovers automatically. If you lose your satellite signal, its internal oscillator holdover keeps your time drift under 1 µs for 24 hours.
  • WR Z16 (White Rabbit Node): Designed for distribution, this node achieves deterministic sub-nanosecond performance. It features a Failover Clock Algorithm (FOCA) that instantly switches sources if a glitch is detected, ensuring your backbone never blinks.

Timebeat: Sync at the Edge

As we move toward O-RAN and Private 5G, timing needs to move closer to the user. Timebeat specializes in bringing precision directly into the server infrastructure and solving the “single point of failure” problem.

The Open Time Appliance: The Power of Three

Traditional timing setups rely on a single Grandmaster clock. If it fails or gets spoofed, you have a problem. Timebeat’s Open Time Appliance uses a Clock Quorum approach—uniting three devices into a self-verifying network.

  • Quorum Consensus: The system cross-checks timing across three sources. If one clock drifts or provides bad data, the other two overrule it, ensuring the network always receives “proven” time.
  • Compact Efficiency: You get this triple-redundancy (which usually requires massive rack space) in a form factor that fits three units into a single 1RU space.
  • High Precision: Capable of <5ns accuracy, with multi-GNSS disciplining to verify signals across GPS, Galileo, and others.

The O-RAN Timecard

For server-based deployments, Timebeat offers the O-RAN Timecard (built on the Intel E810 / E835 NIC). This turns a standard commercial server into a precision sync hub.

  • Plug-and-Play Precision: It delivers nanosecond-level sync and is Class A O-RAN compliant (≤50ns).
  • Cost Effective: By integrating the Grandmaster function directly into the server (PCIe), you eliminate the need for expensive external timing boxes and save on cabling and power.
  • Resilient: Includes an integrated GNSS receiver and high-stability oscillator for holdover, perfect for private networks or indoor deployments where signal visibility is tricky.

Ready to Synchronize Your Strategy?

Bad timing shouldn’t be the bottleneck in your 5G deployment. Whether you need a resilient backbone or a server-integrated edge solution, Telnet Networks has the expertise to design the right architecture for your rollout.

Contact Telnet Networks Today for a Consultation – Let’s ensure your network never skips a beat.