GlobalOutageMap
← Live dashboard
DigitalOcean logoDigitalOcean

Kubernetes Deployments in NYC1

ResolvedminorOfficial source confirmedSingle region affectedFirst recorded update Jul 9, 2026, 08:31 PM · Resolved Jul 11, 2026, 01:27 AM

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...

DigitalOcean live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with DigitalOcean now? Check the current status

Affected services

NYC1

Updates (3)

  1. Jul 11, 2026, 01:27 AM
    Kubernetes Deployments in NYC1

    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

    DigitalOcean ↗
  2. Jul 10, 2026, 01:18 AM
    Kubernetes Deployments in NYC1

    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.

    DigitalOcean ↗
  3. Jul 9, 2026, 08:31 PM
    Kubernetes Deployments in NYC1

    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.

    DigitalOcean ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow DigitalOcean's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.