- Level
- confirmed
- Worst impact
- Degraded
- Components
- NYC3, NYC3
- Down Index
- 16of 100
What to do
Check whether you use DigitalOcean NYC3, NYC3. 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 27m it lasted.
Anything that failed between 2026-07-04 14:42 UTC and 2026-07-04 15:10 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 2
- monitoring
Our Engineering team has implemented a fix to address the issue affecting Droplets in the NYC3 region. The issue, which began at 12:38 UTC, caused disruptions to customers attempting to perform actions on their Droplets in the NYC3 region. During this time, customers may also have experienced errors when trying to create Droplets in this region. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.
provider
- resolved
Our Engineering team has confirmed that the issue impacting Droplets in the NYC3 region has been fully resolved. Users can now perform actions on their Droplets or create new Droplets in this region without any issues. We appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.
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-dcaad34e8d
Is DigitalOcean still down?
No, this incident was resolved 2026-07-04 15:10 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.
How long did it last?
27m, from 2026-07-04 14:42 UTC to 2026-07-04 15:10 UTC, by the times DigitalOcean posted.
What was affected?
DigitalOcean named NYC3, NYC3.
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.