Missing metrics on statuspage
Timeline · 1 update
- 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.
pool.ntp.org Outage History
pool.ntp.org is up right nowpool.ntp.org had 9 outages in the last 2 years totaling 5137h 20m of downtime — averaging 0.4 incidents per month.
There were 9 pool.ntp.org outages since April 5, 2025 totaling 5137h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
Database trouble
Affected: Management PortalPublic websiteDNS updatesMonitoring System
Timeline · 4 updates
Data API outage
Timeline · 1 update
- 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/ )
More! database trouble
Affected: Management PortalPublic websiteDNS updatesGeoDNS serversGlobal NTP ServiceMonitoring System
Timeline · 5 updates
- 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.
- 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.
- identified Sep 27, 2025, 09:40 PM UTC
The database croaked again! I'm restoring from a ~20 minute old backup.
- monitoring Sep 28, 2025, 01:37 AM UTC
ok, we are stable again -- hopefully.
- resolved Apr 26, 2026, 08:05 AM UTC
System has been migrated to the new infrastructure.
Database outage
Affected: Management PortalPublic websiteDNS updatesMonitoring System
Timeline · 3 updates
- investigating Sep 24, 2025, 10:44 PM UTC
The database is having an outage (again!). Investigating.
- monitoring Sep 25, 2025, 12:20 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 25, 2025, 10:26 AM UTC
Database cluster has been re-installed and stable for about an hour now.
Database outage again!
Affected: Management PortalPublic websiteDNS updatesMonitoring System
Timeline · 3 updates
- investigating Jul 05, 2025, 07:19 AM UTC
The upgraded database is having a hard time, again!
- monitoring Jul 05, 2025, 09:15 AM UTC
It's been recovered (since about an hour ago). More information at https://community.ntppool.org
- 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).
Database upgrade
Timeline · 1 update
- 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.
Cluster outage
Affected: Management PortalPublic website
Timeline · 4 updates
- investigating Apr 13, 2025, 12:45 AM UTC
The kubernetes cluster is having a rough day again; management and and monitoring is down. DNS servers are operating normally.
- investigating Apr 13, 2025, 12:45 AM UTC
We are continuing to investigate this issue.
- investigating Apr 13, 2025, 01:51 AM UTC
All clear again (since a bit ago). Fixing a minor problem I caused a major problem by doing an unexpected update to a network configuration.
- resolved Apr 13, 2025, 01:51 AM UTC
This incident has been resolved.
Management system outage
Affected: Management PortalPublic websiteDNS updates
Timeline · 3 updates
- identified Apr 05, 2025, 02:19 AM UTC
A fiber cut is affecting the management system kubernetes cluster. The NTP Pool DNS service is unaffected. Equinix Metal status: https://status.equinixmetal.com/incidents/3svngx53jz9j
- identified Apr 05, 2025, 03:21 PM UTC
Fiber cut has been fixed and kubernetes cluster restored (over night).
- resolved Apr 05, 2025, 08:34 PM UTC
The system has been fully functional since the previous update; we've been monitoring since.