NTP Pool logo

Is NTP Pool Down?

SaaSLive status, outages, and incident history

No. NTP Pool is up right now.

Every monitored NTP Pool system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment NTP Pool breaks

NTP Pool is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official NTP Pool status page
How we know: the official NTP Pool status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

NTP Pool Status Summary

As of 21:15 UTC on 9 November 2026, NTP Pool is operational. PulsAPI checked NTP Pool's official status page and found 6 of 6 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for NTP Pool, counting degraded performance as up. The latest incident, "Missing metrics on statuspage", was on Sep 11, 2026 and lasted 0 min.

Cite as: PulsAPI, “NTP Pool status”, checked 9 November 2026, 21:15 UTC. https://www.pulsapi.com/services/ntp-pool

NTP Pool Component Status

The main NTP Pool systems on this page. All 6 are operational right now.

6operational
DNS updates
Operational
GeoDNS servers
Operational
Global NTP Service
Operational

3 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Management Portal, Monitoring System, Public website.

See all of them free

Component statuses may change independently during partial outages.

Recent NTP Pool Outages & Incidents

Incident history from the official NTP Pool status page, including resolution updates.

Missing metrics on statuspageResolved Sep 11, 2026 · 0 minResolved

During the incident today we also noticed (belatedly) that the status page metrics updater had been failing because the status page API key had expired, oops.

Database troubleResolved Sep 11, 2026 · 2h 22mResolved

MySQL went down because our Ceph storage cluster filled up. That traces back to a Ceph security upgrade we'd just finished. The new version checks S3 upload signatures more strictly than before, and that exposed a bug in the S3 client our monitoring system uses: it doesn't sign one of the headers Ceph now requires. Its uploads got rejected, and instead of giving up it retried forever. Each upload is really several requests: the bulk data went through fine, but the small file that finalizes it kept getting rejected, so the data piled up without ever completing into anything usable. More than a terabyte of duplicate data accumulated in about half a day, more once you count replication overhead. A full Ceph cluster stops accepting writes from everything, and our database lives on the same cluster, so all three MySQL nodes crashed at the same time. Ceph was back as soon as we'd cleaned out the orphaned uploads. MySQL took longer: two of the three nodes had fallen too far behind to rejoin automatically, and their rejoin attempts took the primary down twice more before we fixed them by hand. The site was down a bit over two hours in total. Monitoring data from that window never got stored and can't be recovered. No other data was lost. The client library's bug is already fixed upstream, but the fix hasn't shipped in a release Mimir or Tempo use yet, so we moved that traffic to a connection where it signs everything correctly instead of waiting for it. --- [2026-09-11T21:51:21.978Z] (resolved) This has been resolved. The cluster is healthy again and the underlying causes have been resolved. --- [2026-09-11T19:49:43.326Z] (identified) The symptoms and immediate cause have been identified and remedied. Working on restoring the database cluster to a healthy state. --- [2026-09-11T19:28:46.093Z] (investigating) The database cluster is crash looping and/or starting up very slowly after a crash. We're investigating.

NTP Pool Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a NTP Pool incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 3 days with incidentsNov 9

Going further back: NTP Pool uptime by month and every recorded NTP Pool outage.

Live NTP Pool Outage Reports

Problems reported by engineers using NTP Pool. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No NTP Pool problems reported yet.

Something wrong with NTP Pool on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About NTP Pool

NTP Pool publishes a public status page at status.ntppool.org covering 6 components, including Management Portal, Public website and DNS updates. PulsAPI tracks NTP Pool outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured NTP Pool uptime at 100.00%. Response times, incident history, and SLA tracking for NTP Pool are available on the PulsAPI dashboard.

NTP Pool Status FAQ

Is NTP Pool down right now?

The verdict at the top of this page comes from the latest poll of the official NTP Pool status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if NTP Pool is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until NTP Pool recovers.

How do I check NTP Pool uptime history?

PulsAPI tracks NTP Pool uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever NTP Pool changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect NTP Pool outages?

PulsAPI reads the official NTP Pool status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual NTP Pool components?

Yes. PulsAPI monitors 6 individual NTP Pool components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when NTP Pool goes down?

Yes. Create a free account and subscribe to NTP Pool: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with NTP Pool to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot NTP Pool problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor NTP Pool?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so NTP Pool plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track NTP Pool with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services