pool.ntp.org Outage History

pool.ntp.org is up right now

pool.ntp.org had 4 outages in the last 2 years totaling 5097h 35m of downtime — averaging 0.2 incidents per month.

There were 4 pool.ntp.org outages since September 26, 2025 totaling 5097h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ntppool.org

Minor September 11, 2026

Missing metrics on statuspage

Detected by Pingoru
Sep 11, 2026, 10:00 PM UTC
Resolved
Sep 11, 2026, 10:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 11, 2026, 10:00 PM UTC

    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.

Read the full incident report →

Notice September 11, 2026

Database trouble

Detected by Pingoru
Sep 11, 2026, 07:28 PM UTC
Resolved
Sep 11, 2026, 09:51 PM UTC
Duration
2h 22m
Affected: Management PortalPublic websiteDNS updatesMonitoring System
Timeline · 4 updates

Read the full incident report →

Minor March 2, 2026

Data API outage

Detected by Pingoru
Mar 02, 2026, 02:00 AM UTC
Resolved
Mar 02, 2026, 02:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 02, 2026, 05:29 AM UTC

    The website (in particular the graphs) had a prolonged outage today. The graphs are back now, but will have some expected maintenance windows in the coming weeks related to the infrastructure migration (see https://news.ntppool.org/ )

Read the full incident report →

Notice September 26, 2025

More! database trouble

Detected by Pingoru
Sep 26, 2025, 12:52 AM UTC
Resolved
Apr 26, 2026, 08:05 AM UTC
Duration
212d 7h
Affected: Management PortalPublic websiteDNS updatesGeoDNS serversGlobal NTP ServiceMonitoring System
Timeline · 5 updates
  1. investigating Sep 26, 2025, 12:52 AM UTC

    The newly reset database cluster (from last night) decided to blow itself up again. I think the extra query load and data from the new monitoring system is making the setup fragile. Investigating.

  2. identified Sep 26, 2025, 01:25 AM UTC

    With a bit of help the kubernetes operator got the cluster working again, at least for now.

  3. identified Sep 27, 2025, 09:40 PM UTC

    The database croaked again! I'm restoring from a ~20 minute old backup.

  4. monitoring Sep 28, 2025, 01:37 AM UTC

    ok, we are stable again -- hopefully.

  5. resolved Apr 26, 2026, 08:05 AM UTC

    System has been migrated to the new infrastructure.

Read the full incident report →