Skip to content

Instantly share code, notes, and snippets.

View krisarmstrong's full-sized avatar

Kris Armstrong krisarmstrong

2 followers · 8 following
View GitHub Profile
@krisarmstrong
krisarmstrong / Top_Public_Time_Servers.md
Last active December 22, 2025 17:19 — forked from mutin-sa/Top_Public_Time_Servers.md
List of Top Public Time Servers

NTP Servers Master List (Zero Data Loss)

Best Practices for Using NTP

  • Use multiple servers: Always configure at least 3–4 servers from different providers to avoid single points of failure.
  • Mix vendors & geographies: Don’t rely solely on one provider (e.g., all Google or all NIST). Spread across commercial, academic, and public pools.
  • Prefer Anycast where possible: For global reach, use pool.ntp.org, time.google.com, ntp.se, etc. These automatically route you to the nearest healthy server.
  • Favor stratum 1/2 servers: Stratum 1 servers are closest to the reference clock; stratum 2 are usually fine and often less overloaded.
  • Regional selection: Pick servers close to your geography (e.g., europe.pool.ntp.org in Europe, north-america.pool.ntp.org in North America).
  • Fallbacks: Include a mix of pool.ntp.org and vendor-specific (Google, Cloudflare, Microsoft) for redundancy.