Skip to content
DigitalOcean · Cloud and hostingJul 9, 2026, 20:31 UTC

Kubernetes Deployments in NYC1

MinorNot disclosedUpdated 20h ago
Jul 9, 20:31 UTCJul 11, 01:27 UTC
Duration
28h 56m
Impact
Minor
Root cause
Not disclosed
DigitalOcean, 90 days
30 incidents
Affected
NYC1Kubernetes - NYC1
Status page

Final update

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.

Timeline

  1. Resolved · Jul 11, 01:27 UTC
    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.
  2. Monitoring · Jul 10, 01:18 UTC
    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.
  3. Investigating · Jul 9, 20:31 UTC
    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.

More from DigitalOcean

Full history
StartedIncidentDuration
Sep 1609:48 UTCSupport Portal Service Disruption11h 21m
Sep 910:47 UTCPower Degradation impacting GPU Performance in ATL11h 38m
Aug 2417:14 UTCCloud Control Panel and API25h 50m
Aug 2305:11 UTCManaged Databases Creation9h 22m
Aug 2112:59 UTCContainer Registry and Spaces Accessibility1h 53m
Aug 1911:10 UTCMajor Service Interruption in MKC18h 25m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.