down
Is Network Time Protocol down?
The Network Time Protocol is a networking protocol for clock synchronization between computer systems over packet-switched, variable-latency data networks
https://support.ntp.org/Servers/StratumOneTimeServers ↗A public website resource responded; the application, sign-in, and APIs were not tested.
Service disruption activity for Network Time Protocol
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-08 18:19:54 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
Network Time Protocol outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Network Time Protocol website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-11-08 18:19:54 UTC.
Public endpoint monitoring — this lightweight resource measures website connectivity and response time. It does not test the application, login, or API. Check official component status below for product availability.
Checked address: https://support.ntp.org/Servers/StratumOneTimeServers
DNS lookup: 2 ms · TCP connection: 24 ms · TLS handshake: 28 ms. Certificate expires 2027-01-08; trusted connection: yes.
25.4%
Successful website checks (24h)
15 successful / 59 measurable checks
3555 ms
Median response time
6181 ms
95th percentile response time
44 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Website reachable in latest check. A public website resource responded; the application, sign-in, and APIs were not tested.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
No mapped official components are available for this product. Parent-company status is not substituted for product status.
Official incident timeline
No product-matched incidents are available in the collected provider history. This does not prove that no incident occurred.
Recovery tracker
No recent recovery can be established from available evidence.
1 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
No sustained slowdown has been established against the earlier baseline.
Recent median: 2329 ms · Earlier median: 3570 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Network Time Protocol.
No active incidents recorded.
- Spectrum Availability Issue in Phoenix · monitoring
- Fedramp Customers have Delayed Purges · identified
About Network Time Protocol status on Iszdown
The Network Time Protocol is a networking protocol for clock synchronization between computer systems over packet-switched, variable-latency data networks. In operation since before 1985, NTP is one of the oldest Internet protocols in current use. NTP was designed by David L. Mills of the University of Delaware. NTP is intended to synchronize all participating computers to within a few milliseconds of Coordinated Universal Time. It uses the intersection algorithm, a modified version of Marzullo's algorithm, to select accurate time servers and is designed to mitigate the effects of variable network latency. NTP can usually maintain time to within tens of milliseconds over the public Internet, and can achieve better than one millisecond accuracy in local area networks under ideal conditions. Asymmetric routes and network congestion can cause errors of 100 ms or more.
This page combines the available Network Time Protocol report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
No mapped official components are available for this service. Latest public website measurement: 2026-11-08T18:19:54.000Z.
Visit the official Network Time Protocol website · How it works
What to check when Network Time Protocol is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Network Time Protocol will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
Network Time Protocol is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Network Time Protocol outage history
No product-matched official incidents have been archived for this service in the displayed history. This does not establish that it has never had an outage. See the daily calendar for other available evidence.
Frequently asked questions about Network Time Protocol
Is Network Time Protocol down right now?
Website reachable in latest check. A public website resource responded; the application, sign-in, and APIs were not tested. This page was assembled at 2026-11-08T18:20:35.000Z.
How many Network Time Protocol outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-07T18:20:00.000Z to 2026-11-08T18:20:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Network Time Protocol show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Network Time Protocol feature.
When was Network Time Protocol status last updated?
No current product status observation is available for Network Time Protocol. Reports, estimated activity, and website checks can provide additional context.
Has Network Time Protocol had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Network Time Protocol or report a problem?
Use “Watch this service” to save Network Time Protocol in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Network Time Protocol
Check a related product separately; its status can differ from Network Time Protocol.