<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Time on Besmir Zanaj</title><link>https://cloudalbania.com/tags/time/</link><description>Recent content in Time on Besmir Zanaj</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 21 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudalbania.com/tags/time/index.xml" rel="self" type="application/rss+xml"/><item><title>Official NTP servers: building a list from the BIPM annual report</title><link>https://cloudalbania.com/2026-07-official-ntp-servers-building-a-list-from-the-bipm-annual-report/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://cloudalbania.com/2026-07-official-ntp-servers-building-a-list-from-the-bipm-annual-report/</guid><description>The problem Ask anyone where their servers get time from and the answer is almost always pool.ntp.org, time.google.com or time.cloudflare.com. Those work, but they are not official time. The pool is volunteer-run machines of unknown quality, and Google famously smears the leap second, which means it deliberately serves time that is wrong by up to 500 ppm around a leap event — fine for a fleet that must never see 23:59:60, not fine if you want traceability to UTC.</description></item></channel></rss>