Outage in DigitalOcean
Kubernetes Deployments in NYC1
Resolved MinorIncident Report
Summary AI Generated
Intermittent DNS timeouts caused NodeNotReady events and disrupted Kubernetes deployments in DigitalOcean's NYC1 region for approximately 29 hours, affecting a small number of DOKS clusters running CoreDNS on shared-CPU Droplets. The issue stemmed from a documented limitation of shared-CPU nodes for latency-sensitive DNS workloads. Affected clusters were restored to normal operation, with DigitalOcean recommending dedicated CPU node pools and sufficient CoreDNS replicas to prevent recurrence.
Our Engineering team is investigating an issue affecting Kubernetes deployments in NYC1. Users may see intermittent DNS failures and NodeNotReady events from application workloads during this time.
We apologize for the inconvenience, we'll share new information on this page as soon as it is available.
Components affected
DigitalOcean NYC1Trusted by 1,000+ teams
The Status Page Aggregator with Early Outage Detection
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
7 days ago - at 07/11/2026 01:27AM
The issue affecting Kubernetes deployments in the NYC1 region has been resolved. Our investigation found intermittent DNS timeouts affecting a small number of DOKS clusters, with affected worker nodes running on shared-CPU Droplets. This is a documented limitation for latency-sensitive cluster DNS workloads such as CoreDNS.
The affected clusters are currently functional. To reduce the risk of recurrence, we recommend running CoreDNS on non-shared/dedicated CPU node pools and using sufficient CoreDNS replicas.
If you continue to see DNS failures or NodeNotReady events, please open a support ticket so we can investigate that cluster specifically.
MONITORING
8 days ago - at 07/10/2026 01:18AM
The issue affecting Kubernetes deployments in NYC1 has subsided. Workloads should now be functioning normally.
Our Engineering team is continuing to monitor the affected systems to confirm full resolution. We'll update this page if any further action is needed. We apologize for the inconvenience this may have caused.
INVESTIGATING
8 days ago - at 07/09/2026 08:31PM
Our Engineering team is investigating an issue affecting Kubernetes deployments in NYC1. Users may see intermittent DNS failures and NodeNotReady events from application workloads during this time.
We apologize for the inconvenience, we'll share new information on this page as soon as it is available.
Latest DigitalOcean outages
Reserved IP routing in TOR1 - 2 days ago
Limited access to Deepseek V4 Pro model - 13 days ago
Droplet Actions in NYC3 - 14 days ago
Managed Database Clusters - 15 days ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
