TIME SERVICE DECISIONS
Public vs Local NTP Servers for Clock Systems
Start with the time service your organization already operates. Then compare public NTP and a locally managed server by responsibility, network dependency and the evidence needed to keep the installation running.
Three options, one owner
The key question is not simply where the server sits. Decide who approves the source, monitors the service and responds when a clock loses synchronization.
Can we use the time service we already have?
An existing organization time service is often the first option to evaluate because its ownership, access controls and monitoring may already be established. Ask the IT team whether it is approved for the clock network, what service commitments apply and whether the proposed clock clients can use it. Do not assume that a service used by computers automatically accepts every clock.
- Identify the responsible service team and approved endpoint names.
- Confirm network reachability from the intended clock subnet.
- Agree how loss of synchronization will be detected and reported.
- Record the selected clock model and firmware evidence before ordering.
This page compares service sourcing. For the overall installation architecture, see NTP synchronized clock systems.
How do the three choices change ownership and dependencies?
| Decision | Existing organization service | Public NTP service | Local managed server |
|---|---|---|---|
| Primary owner | Your internal service team | External provider; your team owns client configuration | Your organization or a contracted operator |
| Network dependency | Approved route to the internal service | External connectivity and permitted network access | Local client path plus the server's reference path |
| Service terms | Internal service agreement | Provider terms and published limitations | Equipment support and operating agreement |
| Evidence to obtain | Permission, capacity, monitoring and recovery process | Usage policy, leap-second policy and availability terms | Reference design, configuration, maintenance and recovery evidence |
| Common mistake | Assuming it is available on every subnet | Treating a free public service as a contractual SLA | Assuming local means independent of all external references |
No column is automatically the best choice. Choose against your site's availability requirements, operating resources and supported client configuration.
When is public NTP a practical option?
Public NTP can be an option when external connectivity is acceptable, provider usage terms permit the intended use and the organization accepts the service limitations. It should be an explicit operating decision, not an address copied into every device without approval.
Google Public NTP states that it offers no service-level agreement. The NTP Pool has separate vendor guidance for products using its service by default. These examples show why a supplier must check the specific provider's rules rather than treat all public sources as interchangeable.
- Check the exact provider's usage terms and supported addressing method.
- Confirm the permitted network path with IT, without broadly opening access.
- Document monitoring, escalation and recovery if the source becomes unavailable.
- Verify the proposed client supports the intended configuration.
What does a local server still depend on?
A local server can keep the client-to-server path inside the site, but its time reference, power, network and maintenance remain dependencies. A local server may obtain time from an approved upstream service or a satellite reference, depending on its actual configuration. Its behavior after reference loss must be supported by evidence for the selected equipment.
Existing service path
Organization time service
↓ approved internal network
Clock clients
Local service path
Approved reference
↓ supported server input
Local time service
↓ internal network
Clock clients
These diagrams show responsibilities, not a promised product configuration. For source-level selection, compare NTP and GPS clock approaches. Review NTP clock server options only after defining the requirement.
Which leap-second policy will the installation use?
Agree one compatible leap-second strategy across the sources and clients before deployment. A provider using time smear and one using a different leap-second method can disagree around a leap event; combining sources without understanding their policy can create avoidable inconsistency.
Google explicitly warns against mixing its smeared service with non-smeared sources. RFC 8633 also discusses operational time-source selection and leap handling. These are service-design considerations, not evidence that a particular HC Electronics model implements a specific behavior.
Record the provider policy, approved source set, client configuration and verification method. Have the responsible team resolve incompatible policies before commissioning.
What evidence should be agreed before ordering?
Use a short decision record to connect the chosen service to the equipment and operating process. Record the selected source option, responsible owner, allowed network path, provider terms, leap policy and recovery expectations. Then request evidence for each product-dependent requirement rather than infer capability from the term NTP.
- Service: approved source names and the team responsible for them.
- Equipment: model, firmware and supported source configuration.
- Operation: monitoring, incident contact and configuration control.
- Verification: agreed checks for normal operation and source loss.
Define the service before selecting the displays
Share your network constraints and time-service ownership with our team. Use the catalogue download centre for available product documentation or explore the clock comparison guides.
Discuss Your Clock ProjectSources and scope
Operational guidance reviewed 13 November 2026: Google Public NTP FAQ, NTP Pool vendor guidance and RFC 8633: Network Time Protocol Best Current Practices. Provider terms can change. This comparison does not certify a device, guarantee an accuracy figure or replace site-specific IT approval.