Kubernetes Deployments in NYC1

lowDigitalOceanJul 9, 2026 20:31Duration: 28h 56m

networkdnscomputedeployment

DNS FailureNetwork / RoutingCapacity IssueDeployment Failure

Summary

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 Co

Impact

minor

Timeline

Jul 9, 2026 20:31

[investigating] 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.

via statuspage

+4h 46m

Jul 10, 2026 01:18

[monitoring] 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.

via statuspage

+24h 10m

Jul 11, 2026 01:27

[resolved] 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.

via statuspage

Lessons Learned

⚠DigitalOcean has experienced 94 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.

📊Incidents related to network, dns, compute, deployment have occurred 315 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.

💡This incident is categorized as: DNS Failure, Network / Routing, Capacity Issue, Deployment Failure. Consider implementing preventive measures specific to this failure category.