pool.ntp.org Outage History

pool.ntp.org is up right now

pool.ntp.org had 6 outages in the last 2 years totaling 6321h 34m of downtime — averaging 0.2 incidents per month.

There were 6 pool.ntp.org outages since July 2, 2025 totaling 6321h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ntppool.org

Critical March 7, 2026

Database trouble

Detected by Pingoru
Mar 07, 2026, 02:06 AM UTC
Resolved
Apr 26, 2026, 08:04 AM UTC
Duration
50d 5h
Affected: Management PortalPublic websiteDNS updatesMonitoring System
Timeline · 3 updates
  1. investigating Mar 07, 2026, 02:06 AM UTC

    More database trouble! I can't wait to get rid of the current database server. A refactor to use PostgreSQL is well on the way, but got interrupted by the infrastructure migration.

  2. monitoring Mar 07, 2026, 02:43 AM UTC

    The system is recovering. The website outage was more than a day which is quite embarrassing.

  3. resolved Apr 26, 2026, 08:04 AM UTC

    System has been migrated as part of the infrastructure migration.

Read the full incident report →

Minor March 2, 2026

Data API outage

Detected by Pingoru
Mar 02, 2026, 05:29 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 →

Major September 24, 2025

Database outage

Detected by Pingoru
Sep 24, 2025, 10:44 PM UTC
Resolved
Sep 25, 2025, 10:26 AM UTC
Duration
11h 41m
Affected: Management PortalPublic websiteDNS updatesMonitoring System
Timeline · 3 updates
  1. investigating Sep 24, 2025, 10:44 PM UTC

    The database is having an outage (again!). Investigating.

  2. monitoring Sep 25, 2025, 12:20 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 25, 2025, 10:26 AM UTC

    Database cluster has been re-installed and stable for about an hour now.

Read the full incident report →

Major July 5, 2025

Database outage again!

Detected by Pingoru
Jul 05, 2025, 04:00 AM UTC
Resolved
Jul 05, 2025, 12:42 PM UTC
Duration
8h 42m
Affected: Management PortalPublic websiteDNS updatesMonitoring System
Timeline · 3 updates
  1. investigating Jul 05, 2025, 07:19 AM UTC

    The upgraded database is having a hard time, again!

  2. monitoring Jul 05, 2025, 09:15 AM UTC

    It's been recovered (since about an hour ago). More information at https://community.ntppool.org

  3. resolved Jul 05, 2025, 12:42 PM UTC

    The cluster is stable (and has been reconfigured with many more resources which seemed to be one of the causes of the frequent crashes and eventual loss of sync).

Read the full incident report →

Major July 2, 2025

Database upgrade

Detected by Pingoru
Jul 02, 2025, 01:32 PM UTC
Resolved
Jul 02, 2025, 08:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 02, 2025, 01:32 PM UTC

    The management website was partially offline for a database upgrade (that took longer than expected). Some data / updates from late Tuesday July 1st might have been lost.

Read the full incident report →