whattimeisit.blog
Time standards

Network Time Protocol: How NTP Keeps Clocks in Sync

Network Time Protocol lets computers compare their clocks with time servers and correct drift. Here’s how NTP strata, NIST servers, accuracy, and clock checks work.

By Leo, editorUpdated November 10, 202610 min read7 sources
Computer and time receiver connected for network clock synchronization
Illustration created for WhatTimeIsIt.blog.
Quick answer

Network Time Protocol (NTP) is the standard way computers synchronize their clocks over a network. NTPv4 is specified by RFC 5905; it organizes servers by stratum and uses timing information to adjust a device’s clock toward UTC. Most users can check or trigger synchronization in their operating system’s date and time settings.

  • INTPv4 is specified in RFC 5905.
  • IINTP uses UDP port 123.
  • IIIStratum 1 servers connect directly to a reference clock.
  • IVNIST operates stratum-1 servers traceable to UTC(NIST).
  • VSNTP uses NTP’s message format.
I

What is Network Time Protocol?

Network Time Protocol, usually shortened to NTP, is a set of rules that lets networked devices exchange timing information and keep their clocks close to a shared standard. It is used by computers, servers, and network devices so timestamps from different systems can be compared. NTPv4 is defined by RFC 5905, published in June 2010. The specification describes how time information travels from primary servers to secondary servers and clients.

The reference is Coordinated Universal Time (UTC), not the local time shown on a screen. A computer’s time zone setting turns that underlying time into a local display. For example, Eastern Standard Time is UTC−5, while Eastern Daylight Time is UTC−4, as explained by NIST’s comparison of UTC and local time. If you want to compare a meeting time in different places, use a time zone converter rather than changing the computer’s clock.

NTP is a protocol, not a clock or a time standard. It does not create the official time; it distributes time information from reference clocks and servers. NIST maintains a real-time representation of UTC called UTC(NIST), one of the official U.S. time scales, while UTC is the internationally agreed standard for world time. Learn more about what UTC means and the official U.S. time reference.

II

How do devices synchronize with NTP?

An NTP client sends a request to a server and receives a response containing timing information. The client uses the exchange to estimate how its clock differs from the server and how much uncertainty may come from the network. It can then adjust the system clock. Because packets take time to travel, the client cannot simply treat the time a response arrives as the exact time at the server.

Many operating systems run time synchronization in the background, often starting at system boot. NIST says clients commonly contact one or more servers periodically, reject responses that appear incorrect, and average results they consider valid. This helps a device avoid relying on a single unusual reply. NTP uses UDP port 123, and the protocol’s algorithms are designed to reduce differences in both time and clock rate, according to RFC 5905.

Synchronization is not the same as instantly setting every clock to a new value. The client may correct its clock over time, depending on the size of the error and the operating system’s behavior. The precise method and settings vary by device. For a broader explanation of the clock hardware and software involved, see how computers keep time.

A useful way to think about NTP is as a continuing comparison process: the device checks its clock against network sources, accounts for delays and inconsistent replies, then keeps checking so small clock drift does not accumulate unchecked.

III

What do NTP strata mean?

Stratum describes a server’s position in the NTP hierarchy, not its overall quality score. A primary server synchronized directly to a reference clock is stratum 1. A server that synchronizes from that primary source can be stratum 2, and a server one level farther downstream can be stratum 3. Each downstream level is numbered one higher than the level it uses as an upstream source.

Stratum levels described in RFC 5905
StratumMeaning
1Primary server synchronized to a reference clock
2Secondary server synchronized from an upstream server
3Secondary server another level downstream
16Maximum stratum number specified; not a normal usable synchronized level

This hierarchy allows a source connected to a reference clock to serve other computers without every device needing its own direct connection to a reference clock. A business or institution may synchronize an internal server and have local devices use that server. For a home computer, the operating system generally handles the server choice and synchronization for you.

A lower stratum number does not automatically mean a better result for every client. The network route, delay, and stability between your device and its server matter too. RFC 5905 defines synchronization distance using root dispersion and half the root delay, and identifies one second as a distance threshold. Stratum is useful context, but it is not a substitute for measuring whether a source is providing stable, acceptable time.

IV

NTP vs. SNTP: what is the difference?

Simple Network Time Protocol (SNTP) uses the same message format as NTP, but typically has a simpler client behavior. A full NTP client may run continuously, query several sources, assess responses, and average those judged correct. An SNTP client may make a single timing request and use the result without the same degree of ongoing filtering and selection.

That distinction matters because receiving an NTP-formatted packet does not necessarily mean a device is using all of NTP’s synchronization algorithms. NIST describes some personal computers and network devices as making a single request; it calls this type of client SNTP. The distinction is about how the client uses timing information, not a different format on the wire.

For everyday use, an SNTP client may be adequate when the device only needs a reasonable clock setting and does not need highly precise or continuously assessed synchronization. A server, network appliance, or application that depends on reliable ordering of events may need more careful clock management. The appropriate choice depends on the system and its requirements, so don’t infer accuracy from the word “NTP” alone.

RFC 5905 says NTPv4 is backward compatible with earlier NTP and SNTP versions. Both NTP and SNTP exchanges use the same standard port, UDP 123. If a device setting simply says that automatic time is enabled, the operating system may not expose whether its implementation behaves as a full NTP client or a simpler one.

V

NIST Internet Time Service servers

NIST operates stratum-1 network time servers linked directly to UTC(NIST). Its Internet Time Service responds to Internet clients using NTP as well as the older DAYTIME and TIME protocols. NIST says its time information is traceable to UTC(NIST), and recommends that users access its service through the global name time.nist.gov. That name resolves to listed servers in round-robin sequence to distribute requests.

Examples from the NIST Internet Time Servers list
Server nameLocation or service note
time.nist.govGlobal address for servers at multiple locations
time-a-g.nist.govGaithersburg, Maryland; services available
time-a-wwv.nist.govWWV site in Fort Collins, Colorado; services available
ntp-d.nist.govAuthenticated NTP service

The current server list, including service status and addresses, is published by NIST Internet Time Servers. NIST advises against hard-coding a server so users cannot change it, and says software must not query its servers more frequently than once every four seconds. For most people, there is no need to enter a specific NIST server manually; operating-system defaults are generally sufficient.

Standard NTP requests do not generally use authentication. NIST also offers authenticated NTP messages that verify a message came from NIST and was not modified in transit, but those servers require a key from NIST. They do not respond to unauthenticated requests. NIST does not monitor or certify other time sources, so a server’s name or stratum should not be mistaken for a general certification.

VI

How accurate is NTP?

NTP can be very precise, but the result your device experiences depends on more than the server’s reference clock. Network stability and reciprocity—the similarity of the travel time in each direction—can strongly affect the user’s result, according to NIST’s Internet Time Service information. Congestion, routing changes, and a slow or inconsistent connection can make a network time estimate less certain even if the server itself keeps excellent time.

RFC 5905 gives typical performance examples rather than a promise for every device: primary servers on modern machines can be precise within a few tens of microseconds; secondary servers and clients on fast local networks can be within a few hundred microseconds at stated polling intervals. It also describes precision within a few tens of milliseconds for NTPv4 servers and clients at polling intervals up to 36 hours. These are specification examples, not a guarantee that a home computer or public Wi-Fi connection will achieve them.

Be careful not to confuse timestamp resolution with clock accuracy. The NTP timestamp format has better than one-nanosecond resolution in the specification, and its fractional field resolves about 232 picoseconds. That describes how finely a timestamp can be represented; it does not mean an internet-connected computer is automatically synchronized to that level.

For normal browsing, documents, and calendar reminders, small differences are rarely noticeable. For financial records, coordinated systems, or event logs, even modest clock offsets can complicate ordering. If two events are in different time zones, first compare them on a shared UTC basis or use a time difference tool; don’t assume a local display means the devices’ clocks disagree.

VII

How to check and sync your clock

Start with your device’s date and time settings. Confirm that automatic time and automatic time-zone options are enabled if those are appropriate for your location. NTP synchronizes the clock’s underlying time; a wrong time-zone setting can still make the displayed local time look wrong even when the clock is synchronized.

Windows, Mac, and Linux

  • Windows: NIST says you can right-click the system clock and choose “sync now” to contact a time server and adjust the clock if needed. Newer Windows versions may not let you choose the server in that interface.
  • Mac: Open Date & Time settings and check the time synchronization options. The exact path and wording can vary by system version.
  • Linux: Check the system’s date and time settings. NIST lists a graphical Time and Date setting under System > Admin > Time and Date, though menus vary among distributions.

NIST notes that most operating systems synchronize periodically in the background, usually beginning at system boot. If the time is still wrong, check the time zone and daylight saving time settings before manually changing the clock. A device may display an incorrect local hour because its location setting is wrong, not because its UTC clock is out of sync.

You can also compare your device with NIST’s time.gov, which displays UTC and the device’s clock. For another reference, check a world clock or compare a known UTC time using a converter. For example, 15:00 UTC corresponds to 10:00 a.m. Eastern Standard Time by subtracting five hours; during Eastern Daylight Time, subtract four hours instead. The U.S. 2026 daylight saving time period ended November 1, according to the supplied IANA time-zone data.

VIII

Limits, timestamps, and common mistakes

NTP gives a device a way to synchronize, but it cannot guarantee that every timestamp from every system will be directly comparable in every situation. A common mistake is to treat UTC, GMT, and local time as interchangeable labels. UTC is the standard reference; GMT is commonly used as a local representation of UTC when fractions of a second are not important. Local time zones apply offsets and may change for daylight saving time. Use a UTC clock when you need a shared reference point.

Leap seconds are another edge case. NIST explains that digital time formats such as NTP cannot represent the label 23:59:60. NIST’s method for a positive leap second repeats the binary timestamp for 23:59:59, so two consecutive seconds carry the same displayed label. Other systems may smear the adjustment over a longer period. Because time-message formats do not identify how a server handles the leap second, records from different sources can be difficult to combine around the event. Systems that need traceable timestamps should understand how their time source handles leap seconds.

NTP also has an era boundary. The 32-bit seconds portion of the standard 64-bit timestamp covers about 136 years, and era 0 wraps in 2036; RFC 5905 identifies February 8, 2036 as the first day of era 1. This is a timestamp representation issue, not a reason to expect ordinary clocks to fail on that date: clients and servers need to interpret the era correctly.

Finally, don’t use NTP to calculate a duration between two events if the clock may have changed or drifted between them. Use a duration tool for elapsed time, and use a calendar or date calculator for date arithmetic. NTP keeps clocks aligned; it does not remove the need to choose the right time zone, timestamp convention, or calculation method.

?

Questions people ask

What is the difference between NTP and UTC?

UTC is the time standard; NTP is a protocol computers use to obtain and maintain time based on a reference such as UTC. NTP does not define the official time or the local time zone displayed on your screen. NIST maintains UTC(NIST), a real-time representation of UTC used as an official U.S. time reference. See NIST’s UTC(NIST) overview.

What port does NTP use?

NTP uses UDP port 123. A network firewall or router configuration that blocks the relevant traffic can prevent a device from reaching its time server. If automatic synchronization fails, check your device’s time settings and network policy before changing the clock manually. The port specification is described in RFC 5905.

Is NIST’s time server free to use?

NIST provides an Internet Time Service for clients using NTP and other listed protocols. NIST recommends using time.nist.gov and says clients must not query its servers more frequently than once every four seconds. Authenticated NTP is a separate service that requires a key obtained from NIST; ordinary requests do not need that key.

What does stratum 1 mean?

A stratum-1 NTP server is a primary server synchronized directly to a reference clock. A downstream server adds one to the stratum level as it synchronizes from an upstream server. Stratum indicates a server’s place in the hierarchy, not a guarantee that it will be the most accurate choice for every device or network route.

Is SNTP less accurate than NTP?

SNTP uses the same NTP message format, but a simple SNTP client may make one request rather than continuously comparing multiple sources and evaluating responses. That can mean less filtering of network effects or inconsistent replies. The actual result depends on the client, server, and connection, so the label alone does not establish a precise accuracy level.

Why is my clock wrong if automatic time is on?

Automatic synchronization may be unable to reach a time server, or the device may have a wrong time-zone setting. Check that automatic date and time are enabled, confirm the selected time zone, and try the operating system’s sync option. NTP aligns the underlying clock to a time reference; the time zone determines how that time appears locally.

§

Edited by Leo, editor of WhatTimeIsIt.blog

Calculations on this page run in your browser using the IANA time zone database and standard calendar rules. Facts are checked against the government agency, standards body or official source linked in the text. Last reviewed November 10, 2026. See the editorial policy or report an error to hello@whattimeisit.blog.