- Level
- confirmed
- Worst impact
- Degraded
- Components
- DNS
- Down Index
- 23of 100
What to do
Check whether you use DigitalOcean DNS. 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 16h 48m it lasted.
Anything that failed between 2026-04-17 21:22 UTC and 2026-04-18 14: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 3
- identified
Our Engineering team is aware of a widespread, external issue affecting .co top-level domain (TLD). While this incident originates outside of DigitalOcean's infrastructure, you may experience errors when querying a .co domain, regardless of the DNS resolver being used. Our Engineers are actively deploying temporary backend mitigations to help minimize the impact on our customers. We will continue to monitor the situation closely and post updates as more information becomes available.
provider
- monitoring
Our Engineering team has implemented a fix to resolve the issue that was affecting the DNS resolution of .co top-level domain (TLD). During this time, users who are using DigitalOcean DNS resolvers in their resources should no longer experience issues related to the DNS resolution. Our Engineers are currently monitoring the situation. We will post an update as soon as the issue is fully resolved.
provider
- resolved
Our Engineering team has confirmed that the issue affecting the DNS resolution of .co top-level domain (TLD) has been resolved. The DNS resolution for .co domains is now working as expected. We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.
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-a17c0829a5
Is DigitalOcean still down?
No, this incident was resolved 2026-04-18 14:10 UTC. For DigitalOcean's live state, see https://down.guide/digitalocean.
How long did it last?
16h 48m, from 2026-04-17 21:22 UTC to 2026-04-18 14:10 UTC, by the times DigitalOcean posted.
What was affected?
DigitalOcean named DNS.
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.