- Level
- confirmed
- Worst impact
- Degraded
- Components
- NYC1
- Down Index
- 23of 100
What to do
Check whether you use DigitalOcean NYC1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 4h it lasted.
Anything that failed between 2026-07-09 20:31 UTC and 2026-07-11 01:27 UTC may need a replay.Subscribe to DigitalOcean's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=digitalocean works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from DigitalOcean 3
- 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.
provider
- 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.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-eec063e883
Is DigitalOcean still down?
No, this incident was resolved 2026-07-11 01:27 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.
How long did it last?
1d 4h, from 2026-07-09 20:31 UTC to 2026-07-11 01:27 UTC, by the times DigitalOcean posted.
What was affected?
DigitalOcean named NYC1.
What caused it?
DigitalOcean hasn't published a root cause. If it does, it shows here.
Where does this come from?
DigitalOcean's official status page, https://status.digitalocean.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.