References to RDEM Systems published outside our own sites: network registries, open-source projects, third-party articles. Every line links to its source, which is authoritative.
These references are spread across several platforms: GitHub, PeeringDB, the SYRTE website, an upstream project, news sites. This page gathers them under a single identity: RDEM Systems, operator of AS206014.
All links were checked on September 18, 2026. A source that is taken down moves to the archive, without a link.
Reference time, interconnection registries, NTS server list
SYRTE is the laboratory that realizes UTC(OP), France's realization of Coordinated Universal Time. On its page about time distribution over the Internet, RDEM Systems is referenced by SYRTE among its NTP resources, in the "For more information" section. The neighbouring entries are ntp.org and support.ntp.org.
The link points to our guide to NTP servers in France.
AS206014, the autonomous system of RDEM Systems, is listed in the public interconnection databases. PeeringDB and bgp.he.net list its ports on five internet exchanges: LINX LON1, France-IX Paris, DE-CIX Frankfurt, AMS-IX and Hopus.
The design of this network is described on the AS206014 autonomous network page.
Contribution accepted into the reference list of NTS (Network Time Security) servers. We proposed adding our servers and the maintainer merged it: this is our own contribution, not a third-party citation. The list includes 11 public NTS servers from RDEM Systems, ntp1 to ntp11.rdem-systems.com.
We have since grown to 16 public NTP/NTS servers, ntp1 to ntp16.rdem-systems.com.
The five most recent are not in the list yet: adding ntp12 is proposed in a pull request that is still open.
Their configuration and usage are documented on the page for our public NTP and NTS servers.
Published code and fixes accepted by other projects
Our graphical interface started as a fork of this Proxmox Backup Server client written in Go. The GUI was merged back into the upstream project, which credits RDEM Systems: the README states that it is based on the Nimbus Backup GUI from RDEM Systems and ends with "© 2024-2026 Proxmox Backup Client GO Contributors and RDEM Systems". GPL-3.0 license.
The story is told in the article on the Windows GUI upstream contribution.
Windows client for backing up to Proxmox Backup Server, published under the GPL-3.0 license in our GitHub organization.
Build scripts published under the MIT license, producing signed proxmox-backup-client packages for Fedora, RHEL, Rocky Linux, AlmaLinux, Arch Linux and Alpine. The binary is Proxmox's own, repackaged unchanged; the repository is neither affiliated with nor endorsed by Proxmox Server Solutions GmbH.
Installation instructions are on the unofficial proxmox-backup-client repository page, and usage in the tutorial back up a Linux server with proxmox-backup-client.
A fix to the receive limit for extended-size BGP messages in bgpd, merged into the master branch, then brought to the 10.5, 10.6 and 10.7 stable branches through backports proposed by Richard Demongeot and accepted by the maintainers.
The technical details are on our open-source contributions page.
Publications that link to our content
The article, on how data centers heat up cities, cites the cooling incident at the Equinix PA4 data center in Pantin and links to our Equinix PA4 cooling incident report (French version).
The article covers NIS2 enforcement and what the first EU fines mean for Swiss companies. To summarize the compliance requirements that apply to backups, it links to our article on NIS2 backup compliance.
It also points out that the time needed to restore services after an incident must be documented and tested regularly. In our managed server services, that is the purpose of the periodic restore test and its report.
The comparison of Proxmox Backup Server and third-party tools lists our PBS vs Veeam comparison among its sources.
For infrastructures moving from VMware to Proxmox: our VMware to Proxmox migration guide and our managed Proxmox offering.
The article explains how to set RTO and RPO service by service instead of aiming for a one-hour recovery across the whole information system. To put a figure on what an hour of downtime costs an SME, it links to our downtime cost calculator.
The article covers the backups that ransomware targets first and immutability as the countermeasure. It draws on our article on immutable backup and ransomware protection for the share of attacks that go after backups.
The article compares replacement-value and depreciated-value insurance settlements for an IT estate. It folds the hourly cost of downtime into that calculation, linking to our downtime cost calculator.
The article weighs the cost of a local provider against how fast it responds to an incident. To put a figure on what an hour of downtime means for an SME, it links to our downtime cost calculator.
The article describes renewing a fleet of thirty laptops in waves rather than all at once. It quotes the €500 to €5,000 per hour range and links to our downtime cost calculator.
Sources taken down since, which we keep on record
edomotique.com published an article about pool.ntp.org that cited our contribution to the NTP Pool. The page has since been taken down: its address now redirects to the site's networking section. We keep the mention, without linking to a source that no longer exists. The contribution itself can still be checked in the NTP Pool.
5 B RUE DES NOYERS, 95300 PONTOISE, FRANCE