Our NTP Infrastructure Since 2005

By Richard DEMONGEOT | March 10, 2026 | Reading time: 10 min
NTP infrastructure evolution: from legacy servers to modern NTS-secured racks
NTP infrastructure evolution: from legacy servers to modern NTS-secured racks

Timeline: from 2005 to today

Every step of this infrastructure has been driven by the same conviction: time synchronization is a public good of the Internet that deserves serious and lasting investment.

2005

First NTP servers

Fresh out of university, the first NTP servers are put into service — including a server I managed for a friend's father. The goal is simple: contribute to the global NTP pool and participate in the community effort. At the time, it was driven by a thirst for learning and a certain vision of the Internet — you build, you share, you improve together.

2007

First public traces

The contribution to the global NTP pool becomes publicly visible. The domain ntp.demongeot.biz is already online and referenced in Web archives.

2010

Scaling up

Multiplication of servers in the pool. The infrastructure moves beyond a single server to become a coherent set of machines dedicated to time synchronization, spread across multiple points of presence.

2015

Upgrade to Stratum 1

Deployment of the first Stratum 1 server equipped with a GPS receiver with PPS (Pulse Per Second) signal. The infrastructure moves from secondary synchronization (Stratum 2) to a direct time reference, with microsecond-level accuracy. Understand NTP stratum levels →

2016

RDEM Systems SAS founded

Foundation of RDEM Systems. The NTP infrastructure, previously operated personally, begins its transition to a professional framework. The expertise accumulated over 11 years becomes a company asset.

From pendulum-based time reference to GNSS satellite-secured NTS distribution
From pendulum-based time reference to GNSS satellite-secured NTS distribution
2025

AS206014, NTS and official transfer

A pivotal year. Acquisition and deployment of AS206014 — NTP servers are now operated on RDEM Systems' own network, with full control over routing, peering, and quality of service. Direct connection to Parisian IXPs.

Late 2025: activation of NTS (Network Time Security) on the Stratum 2 servers, deployment of dual-stack IPv4/IPv6 on those same servers, support for 8 different TLDs for maximum DNS redundancy.

Official transfer of the entire historical NTP infrastructure to RDEM Systems. What was born as a volunteer contribution in 2005 is now a structured technical pillar of the company, with 20+ years of continuous operational experience.

Proof of history

In the NTP world, longevity is not just a matter of prestige. An operator who has maintained servers for over 20 years has weathered dozens of protocol updates, leap seconds, hardware failures, and network evolutions. This experience translates into proven reliability.

Current architecture

RDEM Systems' NTP infrastructure follows the NTP hierarchy, from Stratum 1 servers to end clients. Our two Stratum 1 servers are part of it, one GPS, the other GNSS with Galileo, alongside other public Stratum 1 servers:

[GPS satellites] [Galileo + GLONASS] [Public Stratum 1] | | Paris Observatory, [PPS + NMEA] [PPS + NMEA] PTB, LINX | | | [GPS Stratum 1] [GNSS Stratum 1] | ntp-0-gps-hq ntp-0-gnss-hq | IPv6, NTS IPv6 + site IPv4, NTS | \_ ntp-0-hq: both over IPv6 _/ | | | | +---------------+---+------------------------+ | +-------------+-------------+ | | | [Stratum 2] [Stratum 2] [Stratum 2] ntp1.rdem ntp2.rdem ntp3.rdem | | | ... (ntp4 to ntp16, NTS) +------+------+------+-----+ | | [NTP Pool FR] [Direct clients] | | [Your servers and equipment]

Reading of 25 October 2026 around 16:40 CET (refid field of our servers): 10 of our 16 Stratum 2 servers were following our own Stratum 1, rebuilt on 23 October, 5 the Paris Observatory and 1 a public Swiss NTS server, ntp01.maillink.ch. Our Stratum 1 is connected outside AS206014. Chrony chooses its source and may switch at any time: this reading describes a state, not a guarantee.

Infrastructure components

  • 2 Stratum 1 servers: two Raspberry Pis, one with a GPS receiver, the other with a GNSS receiver (Galileo, GLONASS), each with its PPS signal, hosted in our founder's personal lab (in French)
  • 16 Stratum 2 servers: ntp1 to ntp16.rdem-systems.com, in the global NTP pool — fourteen in France, two in Frankfurt
  • Four independent sub-pools: 0. to 3.ntp-pool.rdem-systems.com, four machines each. Every sub-pool carries four distinct autonomous systems, four distinct sites, and only one machine on the prefix we announce ourselves — should that announcement drop, no sub-pool would lose more than one machine in four. A client configures two of them and gets eight sources: chronyd keeps four per pool directive.
  • Primary network AS206014: BGP routing, peering at Parisian IXPs — some servers also hosted on transit operator networks or rented machines
  • Dual-stack IPv4/IPv6 on the 16 Stratum 2 servers and on ntp-0-hq, the entry point to our two Stratum 1 servers (over IPv4 it serves the GNSS one; ntp-0-gps-hq and ntp-0-gnss-hq are IPv6-only)
  • NTS (Network Time Security) enabled on the 16 Stratum 2 servers and on our two Stratum 1 servers: the GPS one since 23 October 2026, the GNSS one since the 27th
  • 8 different TLDs for maximum DNS redundancy
  • Equinix hosting in the Paris area, in our own racks
  • 24/7 monitoring with automated alerts

Two structural choices are documented separately: the selection criteria for the Equinix datacenters (power, peering, neutrality) and the DNS resolution spread across four distinct ASNs in line with RFC 2182. The second protocol matters almost as much as the first: an NTP server you can no longer resolve is no longer reachable.

Infrastructure in numbers

20+ years Continuous operation
Stratum 1 GPS + PPS reference
16 Public Stratum 2 servers
AS206014 Own BGP network
< 10 us Stratum 1 accuracy
24/7 Continuous monitoring

And the clients? Over five days in late October 2026, our 18 servers answered over 6 million distinct addresses and nearly 72 million requests. Who they are, at what rhythm, over IPv4 or IPv6: our NTP client measurements.

Our philosophy

We also operate The Speaking Clock, our free phone-accessible talking clock service — a concrete consumer-facing service synchronized by NTP.

What started as a volunteer contribution has become, over time, a core technical asset. But the philosophy hasn't changed:

We don't sell NTP services. We operate a public infrastructure because we believe that time synchronization is a public good. The same conviction that drove the first server in 2005 guides our decisions today:

  • Contributing to the NTP pool: our servers handle millions of daily requests for the community
  • Maintaining reference quality: maximum reliability score, sub-millisecond accuracy
  • Investing for the long term: 20+ years of continuous operation, and counting
  • Sharing knowledge: technical documentation, guides, and experience reports

Going further

This infrastructure is documented across other, more technical pages that detail each of the components mentioned above:

Free NTP Tools

Three independent tools to diagnose your time synchronization:

Frequently asked questions

How long has RDEM Systems been operating NTP servers?

The first NTP servers were put into service in 2005 by Richard DEMONGEOT, personally and as a volunteer contribution to the global NTP pool. RDEM Systems SAS, founded in 2016, has operated them since their transfer. The contribution is visible in Web archives as early as February 2007 on ntppool.org.

What is the difference between the historical NTP infrastructure and RDEM Systems?

The NTP infrastructure was personally operated by Richard DEMONGEOT since 2005 under the domain ntp.demongeot.biz, then officially transferred to RDEM Systems SAS. It now comprises 16 Stratum 2 servers serving NTS, seven of them on RDEM Systems' own network, AS206014, plus two separate Stratum 1 servers, one GPS, the other GNSS.

How many NTP servers does RDEM Systems operate?

RDEM Systems operates 16 public NTP servers (ntp1 to ntp16) at Stratum 2, all reachable over IPv4 and IPv6 and all serving NTS, plus two Stratum 1 servers, one disciplined by GPS, the other by GNSS (Galileo, GLONASS), which also serve NTS. Seven servers are hosted on AS206014, the others on transit operator networks or on machines rented or virtualised at third parties.