Weekend Reads

* Peering market at a glance
https://labs.ripe.net/media/documents/Peering_market_at_a_glance.pdf
* Measuring NTP pool's robustness
https://www.ndss-symposium.org/ndss-paper/on-borrowed-time-measurement-informed-understanding-of-the-ntp-pools-robustness-to-monopoly-attacks/
* EU subsea cable security report
https://digital-strategy.ec.europa.eu/en/library/submarine-cable-security-toolbox-and-cable-projects-european-interest
* Observing address bogons in-the-wild
https://www.ndss-symposium.org/ndss-paper/aliens-among-us-observing-private-or-reserved-ips-on-the-public-internet/
* IP address registration geo-consistency
https://arxiv.org/abs/2602.11102

#BGP #NTP #SubseaCables #IPv4 #Geolocation

What is your preferred ntp client for your Linux systems?

#linux #NTP #sysadmin #homelab #selfhost #networking

Stop Arch to "phone home"

https://youtu.be/TlxjY2N3j8o

#linux #arch #ntp

Are we going to have "smart" microwave ovens soon just to keep the fucking clock on time through NTP?

#NTP #IoT #Time

Almost every system assumes time is correct. Certificates expire, logs align, databases replicate, caches invalidate. Yet time synchronization is treated as background noise.

I would argue that NTP is one of the most critical services on the internet, and almost no one thinks about it unless it breaks. When it does, failures cascade in ways that look unrelated. Authentication fails. Distributed systems disagree. Debugging becomes guesswork.

Time is infrastructure. It just hides better than most.

#Infrastructure #DistributedSystems #NTP #Infosec #TechReality