Skip to content
Lizely

Public NTP Server List

Compare official public NTP hostnames and copy ready-to-review ntpd configuration lines.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Filter by provider or search for a hostname, scope, or leap-handling note.
  2. 2.Review the provider guidance and avoid mixing incompatible leap-smear strategies.
  3. 3.Copy the visible ntpd lines, adapt them to your time client, and verify reachability from the target system.

About Public NTP Server List

Public NTP Server List collects the official public hostnames most commonly needed when configuring a computer, router, lab device, or small network. Filter eleven entries from the NTP Pool Project, Google Public NTP, Cloudflare Time Service, and the NIST Internet Time Service. Each row identifies the provider, scope, leap handling, and a short operational note. Search by hostname or feature, then copy the visible rows as ntpd-style server lines with iburst.

The NTP Pool recommends the rotating 0, 1, 2, and 3.pool.ntp.org names rather than pinning a volunteer server IP. Google provides time.google.com plus four individual hostnames and uses leap smear. Cloudflare publishes time.cloudflare.com on its global network. NIST recommends the round-robin time.nist.gov address rather than permanently hard-coding one server IP. These are hostnames, so the provider can change the underlying addresses without requiring a configuration edit.

Leap handling matters. Google explicitly warns against mixing its smeared time with servers that do not use the same smear. Cloudflare documents that its service and NTP Pool behavior use the leap indicator without smearing, while NIST distributes UTC(NIST). Choose one coherent source strategy and follow the selected provider's usage terms. The copied text is a starting point, not a universal configuration: systemd-timesyncd, chrony, Windows Time, network appliances, and hosted platforms use different file formats and keywords.

The browser cannot perform a real NTP check because ordinary web pages cannot send UDP packets to port 123. The list therefore does not claim that a hostname is reachable from your current network. Firewalls, captive portals, DNS policy, and provider maintenance can affect service. For infrastructure where wrong time could affect authentication, logs, finance, safety, or incident response, use the operating-system or equipment vendor's supported configuration, multiple monitored sources, and an authenticated or local time architecture. The reference data was checked against official provider pages on 2026-07-18.

Methodology & sources

The static 11-row table is keyed by unique official hostnames and records only provider-published scope and leap behavior. Filtering is case-insensitive, and copied output emits one ntpd-style server line per visible hostname without performing a network request.

Frequently asked questions

Can this page test whether an NTP server is online?
No. Browser pages cannot send normal UDP NTP requests. Test reachability with the time client on the target system.
Can I mix Google Public NTP with other providers?
Google recommends not mixing its leap-smear service with non-smearing NTP sources because results around a leap second can be unpredictable.
Should I hard-code an NTP server IP address?
Generally no. Use the provider's published hostname so its underlying server addresses can change safely.

Related tools

Developer Tools guides

View all